Veenendrecht Payments - QBR
Documentfinal Veenendrecht Payments · qbr_deck · final · 2026-06-22
Final QBR dated 22 Jun 2026 for a Growth customer since 5 Feb 2026. It cites £48k contracted annual recurring revenue, 40 licensed users, between seven and eight active, no tickets or service misses, and a term ending 4 Feb 2027.
What it says
What this says
Current to 13 Oct 26Final QBR dated 22 Jun 2026 for a Growth customer since 5 Feb 2026. It cites £48k contracted annual recurring revenue, 40 licensed users, between seven and eight active, no tickets or service misses, and a term ending 4 Feb 2027.
What it is: a BB-Demo-authored quarterly business review by Elena Novak, filed as final, covering usage, support, value and next quarter's actions. It is a review deck, not a contract.
States: "Contracted annual recurring revenue: £48k" and "Current term runs to 4 Feb 2027". These are BB-Demo's own statements and should be checked against the executed order form.
Usage: active users "between seven and eight" against 40 licensed, "roughly doubled" on the prior quarter. That leaves clear headroom, and no overdue invoices are reported.
Not settled: "We have not yet put a figure on time saved", so no value case exists yet. The deck does not say who asks the most questions, and the renewal notice period is not stated.
As found in this document
Current to 9 Oct 26- Date end4 Feb 2027Source: object_read:doc_160_011
- Date renewal4 Feb 2027Source: object_read:doc_160_011
- Date start5 Feb 2026Source: object_read:doc_160_011
The document
Body
Veenendrecht Payments - QBR
Quarterly business review prepared by Elena Novak, Customer Success Manager, EU, BB-Demo
Review date: 22 Jun 2026 Status: Final
Where we are
- Customer since 5 Feb 2026, on the Growth tier.
- Contracted annual recurring revenue: £48k.
- Licensed users: 40.
- Current term runs to 4 Feb 2027.
- Account owner: Matteo Ricci. Customer Success Manager: Elena Novak.
The purpose of this review is to confirm how the company brain is being used by merchant success and merchant risk, to note what is working, and to agree what we do together over the coming months.
Why Veenendrecht Payments bought the brain
As a payment service provider for subscription and software businesses, supervised by De Nederlandsche Bank, the team needed merchant success and merchant risk to see each merchant's disputes, tickets and volumes together, rather than reconciling separate systems by hand. Growth was chosen because it covers several teams on one shared layer, with the dashboards builder and a quarterly review.
Usage
Read the whole document (3,671 characters)
| Measure | Position this quarter |
|---|---|
| Licensed users | 40 |
| Average active users over the last thirty days | between seven and eight |
| Change in active users against the prior quarter | roughly doubled |
| Overdue invoices | none |
As agreed, we read usage by trajectory rather than by level. Active users have roughly doubled since the prior quarter, which is the right direction for an account that is still in its first term. The active base is still a small share of the licensed users, so there is clear headroom to bring more of the merchant success and merchant risk teams in.
Support and service
- No tickets were raised in the last thirty days, and none of high priority.
- There were no service misses to report.
- Invoices are paid on time, with nothing overdue.
To confirm: a quiet support queue is read here alongside rising usage, which points to a team that is getting on with using the brain rather than struggling with it.
Value delivered
- Merchant success and merchant risk now work from the same view of a merchant, covering disputes, tickets and volumes.
- The number of people asking questions of the brain has grown clearly since the prior quarter.
- The team spends less time moving between systems to answer a single merchant question.
We have not yet put a figure on time saved. I will make sure that we agree with the team how they would like to measure it, so that the value case is written down before renewal.
Risks and watch points
- Adoption breadth. Growth in active users is encouraging, but it should spread across both teams, not sit with a few heavy users.
- Key people. We should confirm who asks the most questions, so that the account does not depend on one or two individuals.
- Renewal. The term ends on 4 Feb 2027. The renewal conversation should start well ahead of the notice period.
Plan for the next quarter
| Action | Owner | Timing |
|---|---|---|
| Run a short onboarding session for merchant risk users not yet active | Elena Novak | Within the next few weeks |
| Agree how value will be measured and recorded | Elena Novak with the customer's team leads | Before the next review |
| Review connector needs as new sources are added | Matteo Ricci | At the next review |
| Prepare the renewal discussion | Matteo Ricci and Elena Novak | Ahead of the renewal notice |
Next steps
- Elena will send these actions in writing after the review.
- The next quarterly review will be booked with the customer's team leads.
- Matteo will follow up on any wish for further connectors or users.
Kind regards, Elena