What it says
What this says
Current to 13 Oct 26Quarterly business review deck prepared 9 Nov 2025 by Daniel Okafor for an Enterprise customer. It reports growing usage, four low-priority tickets and no overdue invoices, and opens the renewal ahead of the 27 Feb 2026 contract end. It is not a contract.
What it is: a customer-facing QBR deck, stored as final, presented by Daniel Okafor with Lewis Kerr named as commercial owner. It reports "Contracted annual recurring revenue | £116k" and "Licensed users | 200" as the deck's own account summary, not executed paper.
Commits: little. It says "Daniel will send the formal renewal notice in good time before the contract end" and that Lewis "will walk through commercial terms". It states no new service levels or prices.
Unusual: usage is described as "just under sixty" active users against 200 licensed, so well under a third. The deck asks for value stories because hard evidence of value is needed for the renewal case.
Not settled: the renewal date for the conversation ("I'll come back to you with a proposed date"), the price at renewal, and any change to users or connectors. The deck is dated well before the as-of date, so the 27 Feb 2026 term end has passed and the evidence does not show what followed.
As found in this document
Current to 9 Oct 26- Date end27 Feb 2026Source: object_read:doc_076_011
- Date renewal27 Feb 2026Source: object_read:doc_076_011
- Renewal noticeDaniel will send the formal renewal notice in good time before the contract end.Daniel will send the formal renewal notice in good time before the contract end. · Source: object_read:doc_076_011
- Commercial terms walkthroughLewis Kerr will walk through commercial terms with youLewis Kerr will walk through commercial terms with you · Source: object_read:doc_076_011
The document
Body
Merriott Lyle Distribution - QBR
Quarterly business review | Enterprise | Prepared 9 November 2025
Presented by Daniel Okafor, Customer Success Manager, BB-Demo. Commercial owner: Lewis Kerr.
Status: Final.
Slide: Purpose of today
Thank you for your time. Today is a short, honest look at how the company brain is being used across Merriott Lyle Distribution, what it is doing for the branch, key-account and credit-control teams, and what we would like to do together before the contract end on 27 Feb 2026.
Three questions we want to answer:
- Are the right people using the brain, and is that growing?
- Is the service behaving the way it should for an Enterprise customer?
- What should the next stage of the rollout look like?
Slide: Your account at a glance
| Item | Position |
|---|---|
| Customer since | 28 Feb 2025 |
| Tier | Enterprise |
| Contract end | 27 Feb 2026 |
| Contracted annual recurring revenue | £116k |
| Licensed users | 200 |
| Hosting | Inside your own Snowflake account |
| Customer success manager | Daniel Okafor |
| Account owner | Lewis Kerr |
Read the whole document (6,641 characters)
Merriott Lyle is a builders' merchant and plumbing and heating wholesaler across the Midlands and the North. You chose Enterprise so that branch, key-account and credit-control teams can see each trade account's orders, disputes, calls and invoices together, rather than reconciling them by hand.
Slide: Usage and adoption
The headline is a good one.
- Active users: the average number of people active over the last thirty days is just under sixty. That is up by about a quarter compared with the previous quarter.
- Direction of travel: growth has come from more people returning to the brain, not from a single burst of activity.
- Licensed headroom: with two hundred licensed users, the brain is currently used by well under a third of the people it could serve. That is headroom, and it is where the next stage of value sits.
What this tells us: the early adopters have made the brain part of their working day, and word is clearly travelling between teams. The question for the next quarter is which teams and branches come next.
Slide: Value delivered
The reason for buying the brain was to give every team one view of a trade account. In practice we are seeing it used for:
- Branch teams checking a customer's recent orders and calls before they pick up the phone.
- Key-account managers preparing for account conversations using calls, emails and invoices in one place.
- Credit-control colleagues looking at disputes alongside invoices and correspondence, instead of chasing three systems.
We would like to capture a few specific examples from your teams in your own words for the renewal conversation. Where you have a story about a dispute settled sooner, or a call that went better because of what the brain surfaced, please share it with us. Hard evidence of value is what makes the case internally, and we would rather build it with you than assert it.
Slide: Service and support
| Measure | Position |
|---|---|
| Support tickets in the last thirty days | Four |
| High priority tickets in the last thirty days | None |
| Overdue invoices | None |
- The ticket volume is low and none was urgent. That is consistent with a stable, well-understood set up.
- Enterprise carries the strongest availability and first response commitments in our range, and service credits cover both availability and data freshness. Nothing in the last quarter has triggered a credit.
- The nightly refresh is running as expected, so teams should be starting each business day with current data.
- Your account is fully up to date on invoices.
If anyone on your side feels the experience is different from this picture, we want to hear it. Tickets only tell us part of the story.
Slide: Risks and watch points
Nothing is red. A few things we are keeping an eye on:
- Concentration of use. As the number of active users grows, we want to be sure usage is spread across branches and teams rather than resting on a small group of enthusiasts.
- Sources changing. If any connected system changes, such as a new configuration in your CRM or accounting system, please tell us early so that a connector does not quietly stop loading.
- Key people. If your internal sponsors or administrators change, let us know so that we can keep training and ownership clear.
Slide: Opportunities
- Wider rollout to more branches. The licence already covers far more people than are using the brain. A structured rollout, branch group by branch group, is the most direct way to turn that headroom into value.
- Deeper use in credit control. Disputes and invoices are where combined views save the most time, so we would like to look at what else credit control would want to ask the brain.
- Training. Short sessions for new branch users, run by us, would help adoption stick. An on-site training day is available as an add-on if that suits you better than remote sessions.
- A named sponsor. An executive sponsor on both sides helps keep the programme moving and gives us a clear route for decisions.
Slide: Plan for the next quarter
| Action | Owner | Timing |
|---|---|---|
| Agree which branch groups come next | Merriott Lyle and Daniel Okafor | Before the end of the year |
| Collect two or three value stories from team leads | Daniel Okafor with your team leads | Over the coming weeks |
| Confirm administrators and sponsors on your side | Merriott Lyle | Next check-in |
| Open the renewal conversation ahead of the contract end on 27 Feb 2026 | Lewis Kerr and Daniel Okafor | I'll come back to you with a proposed date |
Slide: Renewal and what happens next
Your current term runs to 27 Feb 2026. We would like the renewal to be a short, unsurprising conversation that builds on what is already working, and not something that lands late.
- Daniel will send the formal renewal notice in good time before the contract end.
- Lewis Kerr will walk through commercial terms with you, including any change to the number of users or connectors that reflects the rollout above.
- Anything you want changed in the way the service is delivered, tell us now so that it is reflected in the paperwork.
Slide: Close
Thank you again. In short: usage is growing, the service is behaving, and there is plenty of room to extend the brain to more of your people.
Just to close the loop, the one thing we would ask of you is a view on which branches or teams should be next. Everything else we can take away.
Best wishes, Daniel