B-Glass
Daniel Okafor

Brimscombe Energy / BG-Demo – QBR

Callcompleted

Brimscombe Energy logo Brimscombe Energy · 29 Dec 2025 09:15

QBR on 29 Dec 2025: active users down just over a quarter against one hundred and eighty Enterprise licences. Siân Pritchard will not recommend renewing at the same size without an explanation. Renewal date is 10 Jan 2026.

What was said

What this says

As at Fri 9 Oct 2026

QBR on 29 Dec 2025: active users down just over a quarter against one hundred and eighty Enterprise licences. Siân Pritchard will not recommend renewing at the same size without an explanation. Renewal date is 10 Jan 2026.

What happened: Daniel Okafor showed a bit over thirty active users in the last thirty days against one hundred and eighty licences, down just over a quarter on the previous quarter. Nikhil Rao said nightly loads finished before seven and records indexed are still growing.

Customer view: Siân is asked in budget conversations what the brain is worth and wants three measurable numbers per team. Nikhil said autumn permission changes may have cut access, and he has not yet tested it.

Commercial: The order form runs to 9 Jan 2026 with renewal on 10 Jan 2026, Enterprise at £115k, matching what was invoiced and paid on time. Tom Ashdown quoted no new price and will confirm terms in writing.

Watch: One ticket in a month alongside falling usage may be silence rather than health, and the renewal date is close.

AI · claude-sonnet-5-5 · as at Fri 9 Oct 2026

Themes

As at Fri 9 Oct 2026
Theme
falling usage, renewal value case
Importance
renewal
Sentiment
mixed
Voice
champion

Who was there

BG-Demo

Them

Follow-up

Next steps

As at Fri 9 Oct 2026
  • Daniel Okafor to send the usage split by team and role and the ticket timestamps by the end of the week.
  • Nikhil Rao to check which groups lost access in the autumn change and report back by the same deadline.
  • Tom Ashdown to arrange a short renewal call and confirm the terms in writing before it.

Risks

As at Fri 9 Oct 2026
  • Active users are down just over a quarter against one hundred and eighty Enterprise licences, so renewal at the same size is in doubt.
  • The autumn permission tightening may have removed access without anyone noticing, and it is untested.
  • The renewal date of 10 Jan 2026 is close and there is no value case in hand yet.

Opportunities

As at Fri 9 Oct 2026
  • If access is the cause, a quick fix could restore usage before the renewal conversation.
  • A short refresher for key-account users built on the questions that get the most from the brain.
  • A per-team value case using existing baselines, such as complaint deadlines, could support the renewal.

Transcript

  1. Daniel Okafor
    Daniel Okafor
    Good morning, everyone. Thank you for making the time, especially this week. Can you all hear me all right? I think I can see Siân and Nikhil. Is Tom with us yet?
  2. Tom Ashdown
    Tom Ashdown
    I'm here, I'm here. Sorry, was fighting with the mute button. Morning all. How's everyone's week been? Properly quiet, I'd imagine, between the two bank holidays.
  3. Siân Pritchard
    Siân Pritchard
    Morning, Tom. Quiet in the office, yes, though the complaints queue doesn't know it's Christmas. Skeleton crew, but the phones haven't stopped.
  4. Nikhil Rao
    Nikhil Rao
    Morning. Audio's fine.
  5. Daniel Okafor
    Daniel Okafor
    Lovely. Siân, you usually start us off with what the teams have been asking the brain, so would you mind? Then I'll take us through the usage picture, and we'll leave time at the end for the renewal.
  6. Siân Pritchard
    Siân Pritchard
    Of course. This week, the complaints team asked it for every open complaint where the customer has more than one site and the contract end date falls in the next quarter. That one's genuinely useful, because the regulator's clock runs per complaint, and they used to build that list by hand. Key accounts asked for a one-page view of each business customer before their review calls. And collections asked which of the accounts in arrears had also rung us in the last month.
  7. Daniel Okafor
    Daniel Okafor
    That's exactly the one customer, one view idea you set out at the start. How is the team finding it, on the whole? Because I want to be honest with you, the numbers I'm about to show are not the ones I'd like to be showing.
  8. Siân Pritchard
    Siân Pritchard
    Go on then. Evidence first. What does the record say?
  9. Daniel Okafor
    Daniel Okafor
    Right. Give me a second to share. Can you see the usage page?
  10. Tom Ashdown
    Tom Ashdown
    Yep, I've got it. Bit small. Can you zoom in?
  11. Daniel Okafor
    Daniel Okafor
    Is that better? So you're licensed for one hundred and eighty users on Enterprise. Over the last thirty days the average number of people actually active has been a bit over thirty. That's fewer than one in five of the licences. And compared with the previous quarter, active users are down by just over a quarter.
  12. Siân Pritchard
    Siân Pritchard
    Mm. That's a bigger drop than I'd have guessed. I'd have said a fifth, maybe.
  13. Daniel Okafor
    Daniel Okafor
    I know. And I don't want to over-read it, because this fortnight is going to flatter nobody. But the dip started before Christmas, so I don't think we can put all of it down to the holidays.
  14. Tom Ashdown
    Tom Ashdown
    And that's not a one-off blip, is it? It's the trend you're seeing across the quarter, Daniel?
  15. Daniel Okafor
    Daniel Okafor
    It's the trend across the quarter, yes. Each month a little lower than the one before. Questions asked are down with it, which is the number I care about most, because that's the clearest sign of people getting value.
  16. Siân Pritchard
    Siân Pritchard
    Right. Well, let's measure it before we claim it. Can you split that by team? Because my instinct is that the complaints team is steady, they have to be, it's compliance, and the drop is somewhere else. Key accounts, maybe collections.
  17. Daniel Okafor
    Daniel Okafor
    I can, and I'll come back to you with that split by the end of this week. Just from what I can see here, the people who ask the most questions are still asking. It's the lighter users who've gone quiet. But I'd rather give you it properly than guess on a call.
  18. Siân Pritchard
    Siân Pritchard
    Fair. I don't want to wave it away either. If sixty or so people have stopped opening it, I need to know why before January, not after.
  19. Nikhil Rao
    Nikhil Rao
    Can I add something on the platform side?
  20. Daniel Okafor
    Daniel Okafor
    Please, Nikhil.
  21. Nikhil Rao
    Nikhil Rao
    I checked the load history this morning, before the call. Every nightly load has finished before seven on working days for the whole quarter. No gaps. Records indexed are still growing. So the data isn't stale. If people have stopped using it, it isn't because the brain is behind.
  22. Siân Pritchard
    Siân Pritchard
    That's useful, thank you. So it's not a freshness problem. It's a habit problem, or a trust problem.
  23. Nikhil Rao
    Nikhil Rao
    Or neither. I'd want to see it by role before saying. Which role has access matters here. We moved some permissions around in the autumn.
  24. Daniel Okafor
    Daniel Okafor
    That's a good thought, and I hadn't connected it. Could you tell me roughly what changed? Just to close the loop on whether someone could have lost access without meaning to.
  25. Nikhil Rao
    Nikhil Rao
    We tightened a couple of groups. Least privilege. Some people who'd had broad read access were moved to narrower ones. It was meant to be a tidy-up. I haven't tested whether any of them lost the brain as a side effect. I'll check and tell you. I won't guess.
  26. Siân Pritchard
    Siân Pritchard
    Nikhil, I'm not criticising. The access review had to happen, the auditors asked for it. But if it knocked people out, that would explain a fair bit.
  27. Nikhil Rao
    Nikhil Rao
    Understood. It's a schema change on our side, not yours, so I'll own it. Give me until the end of the week.
  28. Tom Ashdown
    Tom Ashdown
    No drama either way, to be fair. If it's access, that's a quick fix. Better we find it now than in the middle of renewal.
  29. Daniel Okafor
    Daniel Okafor
    Agreed. Let me show you the other pieces, then. Tickets. You raised one in the last thirty days, and it was marked high priority.
  30. Nikhil Rao
    Nikhil Rao
    That was mine. A source stopped loading after we changed something upstream. Not a BG-Demo fault. I raised it as high because a morning refresh was at risk.
  31. Daniel Okafor
    Daniel Okafor
    Thank you. I looked at the timestamps, and the first response came well inside the thirty minutes you have on Enterprise. I'll send you the exact times so you have them for your records, and so nobody has to take my word for it.
  32. Nikhil Rao
    Nikhil Rao
    Fine. Response was quick. No complaint.
  33. Siân Pritchard
    Siân Pritchard
    So one ticket in a month, which for a company our size is very quiet. Normally I'd say that's a good sign. Here I'm not sure it is.
  34. Daniel Okafor
    Daniel Okafor
    I think you're right to be cautious. A low ticket count alongside falling usage can be silence rather than health. I'd much rather you were raising how-to questions with us than quietly working around it.
  35. Siân Pritchard
    Siân Pritchard
    Mm. That's what worries me. Let me be direct. I get asked, in budget conversations, what the brain is worth. I've spoken about it at events. I've said it's changed how three teams work. If the active numbers keep sliding, I can't stand behind that with a straight face.
  36. Tom Ashdown
    Tom Ashdown
    And that's fair, Siân. That's why I wanted to be on this one and not just send the paperwork. Daniel's got the usage, but I'd like to hear what you actually need to take upstairs.
  37. Siân Pritchard
    Siân Pritchard
    A value case I can measure. Not adjectives. How many complaint answers went out inside the deadline, how long the key-account prep takes now against before, how many accounts collections reached sooner. Three numbers, per team, that I can put in front of the person who signs off our spend.
  38. Daniel Okafor
    Daniel Okafor
    I can help with the usage side. For the time-saved side, you'd have to tell me which baselines your teams trust, because I don't want to invent a before and after that your people wouldn't recognise.
  39. Siân Pritchard
    Siân Pritchard
    Quite right. Complaints I can do, we track the deadlines already. Key accounts are harder. Prep time was never logged.
  40. Tom Ashdown
    Tom Ashdown
    So we say that. Where there's a baseline, we use it. Where there isn't, we don't pretend. Isn't that more convincing anyway?
  41. Siân Pritchard
    Siân Pritchard
    It's the only version I'd sign my name to.
  42. Daniel Okafor
    Daniel Okafor
    Then let me put the renewal on the table, so nothing surprises anyone. Tom, I'll hand over.
  43. Tom Ashdown
    Tom Ashdown
    Cheers, Daniel. So, the order form runs to 9 Jan 2026 and the renewal date is 10 Jan 2026. I know, it's close, and it's holiday week, so I'm not going to pretend that's ideal. You're on Enterprise at one hundred and fifteen thousand pounds a year, £115,000, and that matches what's been invoiced. You've paid on time, nothing overdue at all.
  44. Siân Pritchard
    Siân Pritchard
    Yes. Finance have never had a reason to chase you, and I'd like to keep it that way.
  45. Tom Ashdown
    Tom Ashdown
    Good. Now, I'll say this plainly. I'm not going to quote you any new price from memory. Anything about the renewal terms I'll confirm in writing before we talk about it again. What I want today is to agree what we're solving for, so the paperwork isn't the bit that goes wrong.
  46. Siân Pritchard
    Siân Pritchard
    Then what I'm solving for is this. I can't recommend renewing at the same size if I can't explain why usage fell. I'm not saying I want to leave. I'm saying I need the explanation first.
  47. Nikhil Rao
    Nikhil Rao
    And I'd say, from the platform, nothing here makes me want to leave. The loads are clean. The ticket was handled. If access caused the drop, that's ours to fix.
  48. Tom Ashdown
    Tom Ashdown
    That helps, Nikhil, thanks. So the order of play is, first we find out whether it's access or habit. Then we put numbers to what the teams get. Then we talk about the renewal with facts in the room. Is that a sensible sequence?
  49. Siân Pritchard
    Siân Pritchard
    It is. But the date is the date. I can't have it land on a Friday afternoon with nothing in front of me.
  50. Daniel Okafor
    Daniel Okafor
    No, and I wouldn't want that either. Let me set out who does what, and you stop me if any of it isn't right. I'll send the usage split by team and by role, and the ticket timestamps, before the end of the week.
  51. Nikhil Rao
    Nikhil Rao
    I'll check which groups lost access in the autumn change and report back. Same deadline. I won't touch production on a Friday, so if a fix is needed it goes in on Monday.
  52. Siân Pritchard
    Siân Pritchard
    And I'll ask the team leads what they've stopped doing in the brain and why, in their own words, not mine. Then I'll write up the complaints figures, because those I can stand behind.
  53. Tom Ashdown
    Tom Ashdown
    Leave the renewal paperwork with me. I'll get something in the diary for a short call once everyone's back, so we're not leaving it to the last minute, and I'll confirm the terms in writing before that call.
  54. Daniel Okafor
    Daniel Okafor
    Just before we finish, Siân, may I ask one more? When your teams are back at their desks, would it help if I ran a short refresher for the key-account people? Nothing grand. Half an hour on the questions that get the most from the brain.
  55. Siân Pritchard
    Siân Pritchard
    Yes. I think that's a good idea. Possibly it's simply that people got used to the first few questions and never moved on. Let's see what the split says first, then decide who needs it.
  56. Daniel Okafor
    Daniel Okafor
    Of course. I'll come back to you by the end of the week with everything, and I'll flag it if anything looks worse than we've said today.
  57. Tom Ashdown
    Tom Ashdown
    Brilliant. Thanks all, genuinely. I know nobody wanted a call this week. Enjoy what's left of the break, if you get any.
  58. Siân Pritchard
    Siân Pritchard
    Diolch, all. Speak soon.
  59. Nikhil Rao
    Nikhil Rao
    Thanks. Bye.
  60. Daniel Okafor
    Daniel Okafor
    Best wishes, everyone. Take care.

BG-Demo is a fictional company; every organisation and person here is invented. B-Glass is the tool. Data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Glass 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 B (the speech bubble) in the header, or open the Ask B page. Type a question, or pick one of the suggestions.

What the data covers

DataRecords
Organisations225
People at customers862
BG-Demo staff records (in post and leavers)58
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 AI 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.

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

Who to contact

Email info@b-glass.uk or talk to your B-Glass account team. Tell us the page address and what looked wrong; a screenshot helps.

Help

Ask B

B-Glass · read-only