What it says
What this says
Current to 13 Oct 26Final QBR deck by Daniel Okafor, dated 28 Dec 2025, for an Enterprise subscription with contracted annual recurring revenue of £115k ending 9 Jan 2026. Adoption is the concern: about thirty-six active users against 180 licensed, and falling.
What it is: a customer success QBR deck prepared by Daniel Okafor, Customer Success Manager. It says "Contract end | 9 Jan 2026" and lists the account owner as Tom Ashdown.
Commits: it binds no party. It is a review with an action plan, and the renewal terms are left to Tom to confirm.
Risk: active users are "down by around a fifth compared with the previous quarter", and the deck states one high priority ticket in thirty days. It also says no outcome measures have been agreed.
Not settled: which teams account for the fall, the renewal terms and any renewal price. The deck is dated before the contract end, so it does not show whether renewal happened. Payments are stated as on time, with no overdue invoices.
As found in this document
Current to 9 Oct 26- Date end9 Jan 2026Source: object_read:doc_154_015
- Date renewal9 Jan 2026Source: object_read:doc_154_015
The document
Body
Brimscombe Energy - QBR
Quarterly business review | Enterprise subscription | Prepared by Daniel Okafor, Customer Success Manager, BB-Demo
Status: Final, version one. Review date: Sunday 28 December 2025.
Agenda
- Where the account stands
- Usage and adoption
- Value the teams are getting
- Support and service
- Risks we want to be open about
- Renewal and the plan to the contract end date
Account snapshot
| Item | Position |
|---|---|
| Customer | Brimscombe Energy, Gloucester |
| Sector | Energy supply |
| Tier | Enterprise |
| Customer since | Friday 10 January 2025 |
| Contract end | 9 Jan 2026 |
| Contracted annual recurring revenue | £115k |
| Licensed users | 180 |
| Account owner | Tom Ashdown |
| Customer Success Manager | Daniel Okafor |
| Invoices | None overdue |
Brimscombe bought Enterprise so that the key-account, collections and complaints teams could see each business customer's sites, contracts, calls and bills together in one place, rather than reconciling several systems by hand. This review looks at how far that has landed in the first year.
Usage and adoption
This is the slide we most want to discuss.
Read the whole document (5,237 characters)
- Average active users over the last thirty days sit at about thirty-six, against one hundred and eighty licensed users. That is roughly a fifth of the seats.
- Active users are down by around a fifth compared with the previous quarter. The direction matters more than the level here, and the direction is not the one we hoped for.
- We have not yet seen which teams account for the fall. Part of the work before the renewal conversation is to split the figure by key-account, collections and complaints, so that we are not guessing.
| Measure | Reading | What it suggests |
|---|---|---|
| Active users, thirty-day average | About thirty-six | Well below the licensed number |
| Change on previous quarter | Down by about a fifth | Adoption is slipping, not growing |
| Licensed users | 180 | Seats are available; they are not being used |
We would rather say plainly that adoption has softened than present a tidy picture. A large gap between licensed and active users is the first thing a finance reader will notice at renewal.
Value the teams are getting
- The original case was a single view of each business customer: sites, contracts, calls and bills together.
- Teams that do use the brain are asking questions of that combined view instead of switching between systems.
- What we cannot yet show is a measured outcome, such as time saved in collections or faster handling of complaints. The usage data tells us how often people ask, not what changed as a result.
To make the value case properly, we would like to agree two or three outcomes with Brimscombe that the teams themselves recognise, and report against them at the next review.
Support and service
- One support ticket in the last thirty days, and it was flagged as high priority.
- No overdue invoices. Payments have been on time throughout the year.
- Nothing in the service record points to an availability or data freshness problem. The softer usage is therefore more likely to be about habit and ownership inside the teams than about the platform.
A single ticket from a base this size is not a sign of a healthy, busy account. It is worth treating as quiet rather than as good news until we have spoken to the teams.
Risks we want to be open about
| Risk | Why it matters | What we propose |
|---|---|---|
| Falling active users | The gap to licensed seats weakens the value story at renewal | Split usage by team and speak to each team lead |
| No agreed outcome measures | Hard to say what the brain is worth to Brimscombe | Agree a short list of outcomes with the account owner |
| Renewal date is close | The contract ends on 9 Jan 2026 | Hold the renewal conversation without delay |
We are not asserting that Brimscombe is unhappy. Payments are on time and there is no pattern of complaints. The concern is that quiet usage with a close renewal date is exactly when value needs to be shown, not assumed.
Plan to the contract end date
| Action | Owner | When |
|---|---|---|
| Break down active users by team and by person | Daniel Okafor | This week |
| Short call with each team lead to understand what is and is not working | Daniel Okafor with Tom Ashdown | Before the contract end date |
| Agree outcome measures and the number of seats the teams genuinely need | Daniel Okafor | Before the contract end date |
| Confirm renewal terms for the next term | Tom Ashdown | Before 9 Jan 2026 |
I will come back to you with the usage breakdown as soon as it is ready, and I will not put a date on the renewal terms until Tom has confirmed them.
Summary
- Enterprise contract of £115k annual recurring revenue, ending 9 Jan 2026.
- Finance picture is clean: no overdue invoices.
- Adoption is the issue: about a fifth of licensed seats active, and falling.
- The next step is to understand which teams have drifted and to agree the outcomes that show value before the renewal.
Just to close the loop: the aim is to leave Brimscombe with a renewal that reflects how the teams really use the brain, not a number that looks good on paper.
Best wishes, Daniel