Veldmaat Payments - QBR
Documentfinal Veldmaat Payments: documents · qbr_deck · final · 2026-05-28
Quarterly business review deck for Veldmaat Payments on the Growth tier, prepared by Elena Novak on 28 May 2026. It reports a steady, positive account with rising usage and two high-priority tickets. It states no price and no availability or P1 figure.
What it says
What this says
Current to 11 Oct 26Quarterly business review deck for Veldmaat Payments on the Growth tier, prepared by Elena Novak on 28 May 2026. It reports a steady, positive account with rising usage and two high-priority tickets. It states no price and no availability or P1 figure.
What it is: a customer-facing QBR deck from Elena Novak, Customer Success Manager, EU. It says the customer has been with BB-Demo "since 5 Jan 2026" and that the term "runs to 4 Jan 2027".
Commits: it is not a contract and sets no service levels or price. It commits Elena to send a written summary of cause and resolution for two tickets and to send agreed actions in writing.
Unusual: usage is given only in words ("Nearly double the previous quarter"), with no figures, and the rise is described as "from a low starting point". The value case is not yet quantified: "put a number on time saved".
Not settled: the deck does not name the Veldmaat signatory, state the ticket dates or response times, or give a renewal price. The renewal conversation is still ahead, with Tom Ashdown named as account owner for usage notes.
As found in this document
Current to 9 Oct 26- Date end4 Jan 2027Source: object_read:doc_003_011
- Date start5 Jan 2026Source: object_read:doc_003_011
The document
Body
Veldmaat Payments - QBR
Quarterly business review, Growth tier Prepared by Elena Novak, Customer Success Manager, EU, BB-Demo Date: 28 May 2026
Where we are
- Veldmaat has been a customer since 5 Jan 2026 and the current term runs to 4 Jan 2027.
- The brain is live over HubSpot, Zendesk and the accounting system, giving one view of each merchant.
- The account is in good standing: no overdue invoices.
- Tone of the account: steady and positive, with clear room to grow use.
Usage
| Measure | Position |
|---|---|
| Active users | Nearly double the previous quarter |
| Licensed users | Well below the Growth user allowance, so plenty of headroom |
| Direction | Rising across both account management and merchant risk |
To confirm, the rise is from a low starting point, which is normal in the first months after go-live. The more important question is whether the same people keep coming back, and early signs are that they do.
Value
Read the whole document (2,206 characters)
- Account managers can see a merchant's CRM history and open helpdesk tickets in one place, instead of switching between systems.
- Merchant risk works from the same picture as account management, which was the original reason for buying.
- The next step is to put a number on time saved, so that the value case is written down before the renewal conversation.
Issues
- Two tickets were raised in the last thirty days, and both were marked high priority.
- Both were handled under the Growth service level for first response. Elena will send the written summary of cause and resolution.
- No pattern of repeat problems with a single connector has been identified so far.
Plan for the next quarter
| Action | Owner |
|---|---|
| Agree three or four questions each team should be able to answer in the brain | Elena Novak with Veldmaat team leads |
| Invite the remaining licensed users and run a short refresher session | Elena Novak |
| Review whether a dashboard for merchant risk is worth building | Veldmaat merchant risk lead, supported by BB-Demo |
| Note usage growth for the account owner ahead of the renewal | Tom Ashdown |
I will make sure that the agreed actions are sent in writing after the review.
Kind regards, Elena