B-Brain
Daniel Okafor

Brimscombe Energy / BB-Demo – Qbr

Callcompleted

Brimscombe Energy logo Brimscombe Energy · 2026-09-23 15:30

Quarterly review with Brimscombe Energy: teams like the brain but Siân Pritchard calls value positive and unmeasured. Active users are in the mid-forties of 180 licensed, and one morning load ran a day late.

What was said

What this says

Current to 13 Oct 26

Quarterly review with Brimscombe Energy: teams like the brain but Siân Pritchard calls value positive and unmeasured. Active users are in the mid-forties of 180 licensed, and one morning load ran a day late.

What happened: The QBR on 23 Sep 2026 was led by Daniel Okafor. Graham Tovey joined late, after Siân Pritchard, Nikhil Rao and Tom Ashdown had covered usage, tickets and value.

Customer view: Siân called value positive but unmeasured and cannot yet put a figure on time saved per complaint. Active users sit in the mid-forties against 180 licensed, concentrated in complaints and key-account teams.

Commercial: Tom confirmed the order form at £120k a year, with matching invoices and nothing overdue. Graham will not discuss the renewal in detail until he sees numbers; the term runs to 9 Jan 2027.

Watch: One morning load ran a day behind after a source schema change, and Enterprise covers freshness as well as availability. Nikhil is writing a change process and an alert for late loads.

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

Themes

Current to 9 Oct 26
Theme
Unmeasured value, usage dip
Importance
renewal
Sentiment
mixed
Voice
decision-maker

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Daniel Okafor sends Siân Pritchard training session options by the end of next week.
  • Siân Pritchard provides a before sample from the complaints team in a couple of weeks for the value summary.
  • Tom Ashdown confirms contract figures against the signed order form and finds a time for the renewal conversation.

Risks

Current to 9 Oct 26
  • Value is unmeasured, and Graham Tovey wants numbers before discussing the renewal.
  • Active users are in the mid-forties of 180 licensed, concentrated in a few teams.
  • A late load on Enterprise touches the data freshness commitment and regulatory complaint deadlines.

Opportunities

Current to 9 Oct 26
  • Short training sessions, collections first, could widen adoption.
  • A before and after sample on complaint handling could give the renewal a measured value case.

Transcript

  1. Daniel Okafor
    Daniel Okafor None
    Hello, can everyone hear me alright? Good. Thank you all for your time this afternoon, I know the diary is tight midweek. Let me just check who has joined. I can see Siân, Nikhil, and Tom is with me. Graham, are you on your way?
  2. Siân Pritchard
    Siân Pritchard None
    Graham's in another meeting that's running over, he said to start without him and he'll join when he can. Hi Daniel, hi Tom. Before we start, can I say what the teams asked the brain this week? It's relevant.
  3. Daniel Okafor
    Daniel Okafor None
    Please, that's the best way to open one of these.
  4. Siân Pritchard
    Siân Pritchard None
    So the complaints team used it on Monday to pull everything we hold on one business customer before a call: sites, the contract, the last few calls and the bills. Previously that was four systems and a lot of waiting. Collections did the same yesterday. One customer, one view. That's the pattern I want to talk about today.
  5. Tom Ashdown
    Tom Ashdown None
    Brilliant, that's what we hoped for when we sat down in the first place. How's your week been otherwise, Siân? Anything else going on that I should know about?
  6. Siân Pritchard
    Siân Pritchard None
    Busy, but good busy. Regulatory reporting season, so the complaints team is leaning on it more than usual. Nikhil can tell you about the platform side.
  7. Nikhil Rao
    Nikhil Rao None
    Platform's fine. Nightly loads have finished before the morning on every business day this month bar one. I checked the load history. I'll come back to that one when we get to tickets.
  8. Daniel Okafor
    Daniel Okafor None
    Thanks, Nikhil. Let me share my screen and take us through the quarter. Tell me if you can see it. I've put together usage, the tickets, and then what I think the value story is, and I'd like you to correct me where I'm wrong.
  9. Siân Pritchard
    Siân Pritchard None
    I can see it. Go on.
  10. Daniel Okafor
    Daniel Okafor None
    Right. Starting with people. You're licensed for 180 users on Enterprise, and over the last month the average number of active users has sat in the mid-forties. That's a touch down on the previous quarter, nothing dramatic, but I'd rather we talked about it than skipped over it.
  11. Siân Pritchard
    Siân Pritchard None
    Yes. I saw that. And I'd rather be straight about it: the heavy users are the complaints and key-account teams, and collections are using it in bursts, mostly around month end. Let's measure it before we claim it, so I don't want to say adoption is wider than it is.
  12. Daniel Okafor
    Daniel Okafor None
    That's fair, and it matches what I see. A small group asking a lot of the questions, and a long tail of people who have logged in and not come back. How is the team finding it, from where you sit? Not the champions, the people who got access because their manager said so.
  13. Siân Pritchard
    Siân Pritchard None
    Mixed, honestly. Some of them don't know what to ask. They treat it like a search box. When someone shows them a question that pulls a customer's calls and bills together, they get it straight away. It's a training thing more than a product thing.
  14. Tom Ashdown
    Tom Ashdown None
    Can I jump in, Daniel? That sounds like a thing we could help with. We've got people who'll run a session on how to ask good questions, no drama. Would a couple of short sessions with the collections team be useful, do you think?
  15. Siân Pritchard
    Siân Pritchard None
    It would. Collections especially, because their questions are very repetitive and they'd get a lot out of a few well-chosen ones. I'd want the complaints team's best examples used, since they're real.
  16. Daniel Okafor
    Daniel Okafor None
    Lovely. I'll take that one, just to close the loop on who does what: I'll come back to you by the end of next week with two or three options for format and timing, and you tell me which teams to prioritise.
  17. Siân Pritchard
    Siân Pritchard None
    Diolch. That works.
  18. Daniel Okafor
    Daniel Okafor None
    Okay, tickets. Two in the last month, one of them high priority. Nikhil, shall I let you describe the high priority one, since you raised it?
  19. Nikhil Rao
    Nikhil Rao None
    Yes. One morning load didn't land before the start of the day. Complaints noticed the answers were a day behind. I checked the load history, it was a schema change on a source, and we got it re-run. That's the whole story.
  20. Daniel Okafor
    Daniel Okafor None
    And I'd say the response from our side was within what Enterprise gives you, thirty minutes on a P1, but please say if it didn't feel like that.
  21. Nikhil Rao
    Nikhil Rao None
    It was fine. I'm not complaining about the response. What I'd like is a heads-up from us before we change a source, which is on my side. I'll write that into our change process.
  22. Siân Pritchard
    Siân Pritchard None
    That's useful, Nikhil. I'll say for the record that when freshness slips, the complaints team feels it first. A complaint answer built on yesterday's data is a risk with the regulator.
  23. Daniel Okafor
    Daniel Okafor None
    Understood. And that's worth saying clearly, because on Enterprise the freshness commitment is something you can lean on, not only availability. We'll keep an eye on the refresh timing and tell you early if we see a pattern.
  24. Nikhil Rao
    Nikhil Rao None
    Right. Which role has access to the refresh logs on your side? I want our auditors to be able to follow it, and I'm not going to share anything by email.
  25. Daniel Okafor
    Daniel Okafor None
    Fair. I'll check that with our engineers and come back to you through the admin console route, not email. I won't guess at it.
  26. Nikhil Rao
    Nikhil Rao None
    Good.
  27. Siân Pritchard
    Siân Pritchard None
    Daniel, can I raise value? Because that's what Graham will ask me when he joins, and I need something I can stand behind.
  28. Daniel Okafor
    Daniel Okafor None
    Please. That's the heart of it.
  29. Siân Pritchard
    Siân Pritchard None
    I can tell you the teams like it. I can't yet put a figure on time saved per complaint, and I won't make one up. What I'd like for the renewal conversation is a way to measure how long it takes to assemble a customer view now against before. Even a rough sample would do.
  30. Daniel Okafor
    Daniel Okafor None
    I think we can do that. We have the questions asked, who asked them and how often, and you have the complaint handling times on your side. If your team can give me a before picture from last year, even a small sample of cases, I can line it up against the usage and we can see what the brain has changed.
  31. Siân Pritchard
    Siân Pritchard None
    I can get you a sample from the complaints team. Give me a couple of weeks.
  32. Daniel Okafor
    Daniel Okafor None
    That's perfect. I'll hold the draft value summary until your sample comes in, so we're not guessing.
  33. Tom Ashdown
    Tom Ashdown None
    While we're on the renewal, shall I just flag where we are with the paperwork? Siân, Graham will want this too, so I'll say it once he's on and again now if that's alright.
  34. Siân Pritchard
    Siân Pritchard None
    Go ahead. He'll want it short.
  35. Tom Ashdown
    Tom Ashdown None
    So you came on in January 2025, on Friday 10 January 2025, and the term runs to 9 Jan 2027, with the renewal falling on 10 Jan 2027. The order form has you at £120,500 a year, and the invoices match that, so nothing odd on the billing side. I'll confirm the exact figures against the signed copy before anyone relies on them, I don't quote from memory.
  36. Siân Pritchard
    Siân Pritchard None
    Understood. And nothing overdue on your side, to my knowledge, finance would have told me.
  37. Tom Ashdown
    Tom Ashdown None
    Nothing overdue, no. All clean. So what I'd like is to get something in the diary for the renewal conversation. Not tomorrow, but with enough room that Graham isn't surprised by anything. Leave that with me and Daniel.
  38. Graham Tovey
    Graham Tovey None
    Sorry, I'm here. Apologies for the delay. Headline please, Daniel.
  39. Daniel Okafor
    Daniel Okafor None
    Welcome, Graham, thank you for joining. Headline: the brain is stable and trusted by the teams that use it, with one slow morning load this month that Nikhil dealt with. Active use is a little down on last quarter, concentrated in a few teams, and we're planning training to widen it.
  40. Graham Tovey
    Graham Tovey None
    Thank you. What does the customer see, in practice, when a load is late?
  41. Siân Pritchard
    Siân Pritchard None
    Only that the answer is a day behind, Graham. We caught it before anything left the building, but it's the kind of thing that could matter on a complaint. Nikhil is tightening our own change process around it.
  42. Graham Tovey
    Graham Tovey None
    Good. Tell me early, not late, both of you. How does that hold up with Ofgem if it happens on a deadline?
  43. Nikhil Rao
    Nikhil Rao None
    We have a manual check on complaint deadlines, so the answer is we'd see it before it mattered. I'd rather not rely on that. I'm working on an alert when a load is late.
  44. Graham Tovey
    Graham Tovey None
    Please do. Siân, what's your view on the value so far?
  45. Siân Pritchard
    Siân Pritchard None
    Positive, but unmeasured, and I've told Daniel that. We're putting together a before and after on complaint handling so I can show you something real in time for January, not a feeling.
  46. Graham Tovey
    Graham Tovey None
    That's the right approach. I'm not going to discuss the renewal in detail today, I'd rather see your numbers first. But I'm happy to have the conversation once you have them.
  47. Tom Ashdown
    Tom Ashdown None
    That's all I wanted to hear, Graham. No drama. I'll get a time in the diary for the early part of the autumn, and we'll work back from 10 Jan 2027 so nobody's rushing.
  48. Graham Tovey
    Graham Tovey None
    Fine. Thank you all. I have to go to another meeting. Siân, send me the summary when it's ready.
  49. Siân Pritchard
    Siân Pritchard None
    Will do. Diolch, Graham.
  50. Daniel Okafor
    Daniel Okafor None
    Thanks, Graham. Right, with that, let me just close the loop on what we've agreed, and then I'll give you your time back.
  51. Daniel Okafor
    Daniel Okafor None
    One: I come back to Siân by the end of next week with options for short training sessions, collections first. Two: Siân gets a before sample from the complaints team in a couple of weeks, and I line it up with usage for the value summary. Three: I check the refresh log access route with our engineers and tell Nikhil, not by email. Four: Tom confirms the contract figures against the signed order form and finds a time for the renewal conversation. Did I miss anything?
  52. Nikhil Rao
    Nikhil Rao None
    My alert on late loads. I'll tell you when it's in. Not on a Friday.
  53. Daniel Okafor
    Daniel Okafor None
    Of course, I'd not expect it on a Friday. Thank you, Nikhil.
  54. Siân Pritchard
    Siân Pritchard None
    That's everything from me. Thanks both, it was a useful one.
  55. Tom Ashdown
    Tom Ashdown None
    Cheers, everyone. Speak soon.
  56. Daniel Okafor
    Daniel Okafor None
    Best wishes, all. Thank you again for your time.

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