What it says
What this says
As at Fri 9 Oct 2026A final BG-Demo QBR deck for an Enterprise customer, prepared by Daniel Okafor on 4 Mar 2026. It reports rising active users, light support and clear invoices. It quotes contracted £114k, contract end 27 Feb 2027, and makes no claim on questions asked or connectors.
What it is: an internal-style customer review deck by Daniel Okafor, marked "Status: Final, version 1". It reads adoption as healthy: "Rising sharply: a healthy trajectory, not a one-off spike", with 160 licensed users and ample headroom.
Commits: it states no new obligations. It records the Enterprise service credit position as covering "both availability and data freshness", a nightly refresh "by 07:00 customer local time on business days", and a planned renewal notice ahead of contract end on 27 Feb 2027.
Unusual: it gives no figures for active users, and the headline growth is unquantified. Key-person dependence is "Not assessed in this deck".
Not settled: questions asked, records indexed and connector counts are deliberately left out. The one high-priority ticket is still to be closed out, and the response time against the order form is not shown. The £114k is labelled contracted ARR in the deck, not checked here against the executed order form or invoices.
As found in this document
As at Fri 9 Oct 2026- Date end27 Feb 2027Source: the AI read of this record
- Date renewal27 Feb 2027Source: the AI read of this record
- Service credit coveragecovered for both availability and data freshness under the service credit termsSource: the AI read of this record
- Nightly refreshexpected to complete by 07:00 customer local time on business daysSource: the AI read of this record
- Renewal noticeSend the formal renewal notice ahead of contract end on 27 Feb 2027Source: the AI read of this record
The document
Body
Strensall Merchants - QBR
Quarterly business review | Prepared by Daniel Okafor, Customer Success Manager, BG-Demo | Wednesday 4 March 2026
Status: Final, version 1
1. Agenda
- Where we are: the account at a glance
- Adoption and usage
- Support and service
- Value delivered
- Risks and open questions
- Plan for the next quarter and the road to renewal
Thank you to everyone at Strensall Merchants who gave their time this quarter. Just to close the loop on the last review, the points we agreed are picked up in section 6.
2. The account at a glance
| Item | Detail |
|---|---|
| Customer | Strensall Merchants, York |
| Industry | Building materials distribution |
| Tier | Enterprise |
| Customer since | Friday 28 February 2025 |
| Contract end | 27 Feb 2027 |
| Annual recurring revenue (contracted) | £114k |
| Licensed users | 160 |
| BG-Demo account owner | Lewis Kerr |
| BG-Demo Customer Success Manager | Daniel Okafor |
| Invoices | Nothing overdue |
Read the whole document (6,024 characters)
Strensall Merchants is a builders' merchants group with a branch network across the North of England and the Midlands. It chose Enterprise so that branch, trade-credit and key-account teams can see each trade account's orders, deliveries, calls and credit together in one place, inside its own Snowflake account.
3. Adoption and usage
Headline: more people are using B-Viz than at the last review, and the increase is large.
- Average active users over the last thirty days rose strongly compared with the prior quarter.
- Active users sit comfortably within the 160 licensed users, so there is plenty of headroom as more branches come on board.
- The growth tells us the work done on branch and trade-credit teams is landing. People are asking B-Viz rather than reconciling systems by hand.
What we read from this
| Signal | Reading |
|---|---|
| Active users | Rising sharply: a healthy trajectory, not a one-off spike |
| Licence headroom | Ample; no pressure on the user allowance |
| Spread across teams | To be confirmed with the customer: we want to see that growth is broad, not concentrated in a few heavy users |
We have deliberately not drawn conclusions on questions asked or records indexed in this deck. We will bring those trends, month on month and against the same period last year, to the next review so that the value story rests on the best single measure of usage.
4. Support and service
| Measure | Position |
|---|---|
| Tickets raised in the last thirty days | Two |
| Of which high priority | One |
| Overdue invoices | None |
- Two tickets from a user base that has grown this much is a light load, and reads as a healthy account rather than a quiet one.
- The single high-priority ticket is being tracked against the Enterprise first-response commitment in the order form. Response times are counted from ticket timestamps, not from the wording of the ticket.
- As an Enterprise customer, Strensall Merchants is covered for both availability and data freshness under the service credit terms. No service credit position is raised in this review.
- The nightly refresh is expected to complete by 07:00 customer local time on business days. We will confirm freshness over the quarter with the team in York.
5. Value delivered
What the customer told us it bought B-Viz to do, and where we see it happening:
- One view of a trade account. Branch teams, trade-credit controllers and key-account managers look at the same orders, deliveries, calls and credit picture, rather than asking each other for it.
- Less manual reconciliation. The rise in active users suggests more colleagues are choosing to ask B-Viz first.
- Credit and relationship in the same place. Trade-credit decisions can be made with the account's recent conversations and delivery history in view.
We would like to turn these into a short value case in the customer's own words before the renewal conversation, so that the benefit can be stated plainly by the people who use it. Daniel will ask: how is the team finding it, and which questions do they now ask every week?
6. Risks and open questions
| Topic | Assessment | Next step |
|---|---|---|
| Key-person dependence | Not assessed in this deck | Review who asks the most questions at the next review |
| Branch coverage | Growth is encouraging, but breadth is not yet confirmed | Agree with the customer which branches and teams are next |
| Data freshness | No concern raised | Keep watching records indexed for any flat period |
| Support | Light volume, one high-priority ticket | Close out the ticket and confirm the customer is satisfied |
| Commercial | Invoices paid on time | None |
The evidence in this pack does not show connector counts or questions asked, so we make no claim on those.
7. Plan for the next quarter and the road to renewal
| Action | Owner | Timing |
|---|---|---|
| Close out the high-priority ticket and confirm resolution with the customer | Daniel Okafor | This month |
| Bring questions-asked and records-indexed trends to the next review | Daniel Okafor | Next review |
| Agree which branches and teams to bring on next, using the spare licence headroom | Daniel Okafor with Lewis Kerr | Over the coming weeks |
| Draft a short value case with the customer's own examples | Daniel Okafor | Before the renewal conversation |
| Send the formal renewal notice ahead of contract end on 27 Feb 2027 | Daniel Okafor | Per the contract notice period |
Opportunity. With adoption rising and licences to spare, the natural conversation is about reach: more teams and branches on the same Enterprise subscription. Any add-on, such as extra connectors, Premium support or the Sandbox, would be discussed only if the customer's needs point there.
Summary. A positive quarter: adoption up, support light, invoices clear. The priority now is to keep the momentum, understand who is driving it, and build the value case well before renewal.
Best wishes, Daniel
Unusual terms
As at Fri 9 Oct 2026- Licensed users 160 against 150 standard Enterprise
- Contracted ARR of £113,500 stated in deck