B-Brain
Brimscombe Energy logo

Brimscombe Energy - QBR

Documentfinal

Brimscombe Energy logo Brimscombe Energy · qbr_deck · final · 2025-12-28

Final 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 says

What this says

Current to 13 Oct 26

Final 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.

AI · claude-sonnet-5-5 · 13 Oct 2026

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

ItemPosition
CustomerBrimscombe Energy, Gloucester
SectorEnergy supply
TierEnterprise
Customer sinceFriday 10 January 2025
Contract end9 Jan 2026
Contracted annual recurring revenue£115k
Licensed users180
Account ownerTom Ashdown
Customer Success ManagerDaniel Okafor
InvoicesNone 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.
MeasureReadingWhat it suggests
Active users, thirty-day averageAbout thirty-sixWell below the licensed number
Change on previous quarterDown by about a fifthAdoption is slipping, not growing
Licensed users180Seats 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

RiskWhy it mattersWhat we propose
Falling active usersThe gap to licensed seats weakens the value story at renewalSplit usage by team and speak to each team lead
No agreed outcome measuresHard to say what the brain is worth to BrimscombeAgree a short list of outcomes with the account owner
Renewal date is closeThe contract ends on 9 Jan 2026Hold 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

ActionOwnerWhen
Break down active users by team and by personDaniel OkaforThis week
Short call with each team lead to understand what is and is not workingDaniel Okafor with Tom AshdownBefore the contract end date
Agree outcome measures and the number of seats the teams genuinely needDaniel OkaforBefore the contract end date
Confirm renewal terms for the next termTom AshdownBefore 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

Documentsmade from

Unusual terms

Not yet analysedThe unusual terms of object_read:doc_154_015 are empty: the record found none.

BB-Demo is a fictional company; every organisation and person here is invented. B-Brain is the tool. Built by site/build_site.py from the site tree, data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Brain is one place to read everything the company knows about its customers: the CRM, calls, emails, support tickets, product usage, invoices, documents, news and HR. Every page is built from those systems and the data is current to Fri 9 Oct 2026.

How to use the site

How to ask

Press Ask Brain in the header. Type a question, or pick one of the examples.

The site itself does not call an AI model; answers in Claude come from the same figures you see here.

What the data covers

DataRecords
Organisations225
People at customers862
BB-Demo staff58
Calls1,995
Email threads3,013
Support tickets1,159
Documents1,218
Deals315
Invoices285
Events49
News items119

Data as of Fri 9 Oct 2026. Text marked AI was written by the brain from the records listed in its made-from link; an AI output that cannot cite its evidence is refused and the previous text kept. Where two systems disagree (for example a contract and the CRM), the key facts show both values and mark the difference.

BB-Demo is a fictional company: every organisation, person and figure here is invented for this demonstration. B-Brain is the tool that reads its data.

Who to contact

Email support@b-brain.example or talk to your B-Brain account team. Tell us the page address and what looked wrong; a screenshot helps.

Help

Ask B

B-Brain · read-only