B-Brain
Tom Ashdown

Brimscombe Energy / BB-Demo – Negotiation

Callcompleted

Brimscombe Energy logo Brimscombe Energy · 2024-12-02 11:15

Negotiation call close to agreement. Graham Tovey has no objection if three things are in writing and Siân Pritchard is satisfied. Signature is targeted before the break, Fri 27 Dec 2024 at the latest.

What was said

What this says

Current to 13 Oct 26

Negotiation call close to agreement. Graham Tovey has no objection if three things are in writing and Siân Pritchard is satisfied. Signature is targeted before the break, Fri 27 Dec 2024 at the latest.

What happened: Tom Ashdown and Owen Tallis took Graham Tovey and Siân Pritchard through the Enterprise terms on 2 Dec 2024. The deal as it sits is £145k in total with implementation included, and any movement is on the first term only.

Customer view: Siân's concerns were the regulator, data freshness for collections by 07:00, and the load on her team during the build. Graham will sign only once she is satisfied.

Commercial: Enterprise credits a freshness miss as well as downtime, and the customer wants that wording in the order form at no extra charge. Procurement and legal will review the order form and data terms before signature.

Watch: the security questionnaire return, which Siân will confirm by Wednesday, and the legal read she cannot control.

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

Themes

Current to 9 Oct 26
Theme
Enterprise order form terms
Importance
neutral
Sentiment
positive
Voice
decision-maker

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Tom Ashdown to send the security pack to Siân Pritchard the same day.
  • Tom Ashdown to send the revised order form with freshness wording and the data terms by the end of that week.
  • Siân Pritchard to confirm by Wednesday whether the questionnaire can be returned by the end of the following week.

Risks

Current to 9 Oct 26
  • The date could slip into January if the security review or the legal read is not back in time.
  • Graham's sign-off depends on three written items: freshness wording, escalation route and data exit terms.
  • A quiet connector failure would be felt by collections before BB-Demo raises it, unless the escalation route is agreed.

Opportunities

Current to 9 Oct 26
  • Enterprise freshness credit, written into the order form, answers Siân's main operational worry.
  • Training the key accounts team on their own data could drive early adoption.

Transcript

  1. Tom Ashdown
    Tom Ashdown None
    Hello, can you hear me alright? Siân, I think you're on mute. No, there you go.
  2. Siân Pritchard
    Siân Pritchard None
    Morning, Tom. Yes, I can hear you fine. Graham's just finishing another call, he said to make a start if he's a minute or two.
  3. Tom Ashdown
    Tom Ashdown None
    No drama. How's your week been so far? Mondays are funny, aren't they, everyone back at their desk with a list as long as your arm.
  4. Siân Pritchard
    Siân Pritchard None
    Busy, but in a good way. Since the demo, the collections team have kept sending me questions they'd want to put to the brain. I'm not claiming anything from that yet, mind. Let's measure it before we claim it.
  5. Tom Ashdown
    Tom Ashdown None
    Fair enough, and that's the right way round. Oh, hang on, here's Owen. Owen, you're on mute.
  6. Owen Tallis
    Owen Tallis None
    Sorry, there we go. Morning, both. Graham not on yet?
  7. Graham Tovey
    Graham Tovey None
    I'm here. Good morning, everyone, apologies for the delay. What's the headline?
  8. Owen Tallis
    Owen Tallis None
    Headline is we're close. Where we stand against the date: we're aiming to have the order form signed by Friday 27 December 2024, and what's left is the commercial terms and your security questions. Tom, you've been closest to it, do you want to take them through?
  9. Tom Ashdown
    Tom Ashdown None
    Yeah, course. So, Graham, Siân, where we've landed is Enterprise, the company-wide tier. That brings single sign-on and SCIM, and Graham, you'd be the executive sponsor on your side, with a named sponsor on ours. The deal as it sits is £145,000 in total, implementation included. I want to be really clear that isn't an annual figure, it's the whole deal. I'll confirm the annual part in writing rather than quote it from memory.
  10. Graham Tovey
    Graham Tovey None
    Understood. Tell me early, not late: is that number going to move?
  11. Owen Tallis
    Owen Tallis None
    Not upwards. If there's any movement at all, it's on the first term only, and let's not discount twice. So whatever we agree is what we work from, and it falls away at renewal. I'd rather say that now than have it land on you in a year.
  12. Graham Tovey
    Graham Tovey None
    Good. That's the commercial point settled as far as I'm concerned, subject to Siân's view. I don't sign without it.
  13. Siân Pritchard
    Siân Pritchard None
    Which I appreciate, Graham. So my questions aren't really about price. There are three things: the regulator, the freshness of the data for the collections team, and who in my team has to do what during the build.
  14. Tom Ashdown
    Tom Ashdown None
    Great, let's take them in that order if that suits. Start with the regulator.
  15. Siân Pritchard
    Siân Pritchard None
    So, complaint answers. We have to meet the regulator's rules on how we respond and how quickly, and I never let a deadline slip. What I need to know is, when a complaint comes in from a business customer, can the handler see the sites, the contract, the calls and the bills in one place? And can I show an auditor where each fact in the answer came from? What does the record say, and can I prove it?
  16. Tom Ashdown
    Tom Ashdown None
    Yes. That's the point of it, really. It pulls your CRM, the call recorder, the helpdesk and the billing system into one layer, and every answer points back to the record it came from. And because it runs inside your own Snowflake account, the data doesn't leave your environment.
  17. Graham Tovey
    Graham Tovey None
    What does the customer see?
  18. Siân Pritchard
    Siân Pritchard None
    Nothing different, Graham, that's the idea. What changes is the speed and the consistency of what our people tell them. A customer ringing about a bill gets the same answer from key accounts as from collections. One customer, one view.
  19. Graham Tovey
    Graham Tovey None
    And how does this hold up with Ofgem?
  20. Owen Tallis
    Owen Tallis None
    That's what the security review is for, and Enterprise includes our support for it. Our team works through your questionnaire alongside yours. I'd rather you hear that from the paperwork than from a promise on a call.
  21. Graham Tovey
    Graham Tovey None
    Fine. Siân, you'll own that with your people?
  22. Siân Pritchard
    Siân Pritchard None
    Yes. A colleague in IT security will take the questionnaire, and someone from our legal team will want to read the data terms. I'll introduce them to Tom by email this week.
  23. Tom Ashdown
    Tom Ashdown None
    Brilliant. Leave that with me, I'll send the pack over today so they've got it before the introductions.
  24. Owen Tallis
    Owen Tallis None
    What's the next dated step on that? Who gets it, and when does it come back?
  25. Tom Ashdown
    Tom Ashdown None
    Pack goes to Siân today. Siân, would your IT colleague manage to return the questionnaire by the end of next week? If not, say, and we'll plan around it.
  26. Siân Pritchard
    Siân Pritchard None
    Let me check with them. I think so, but I don't want to promise for someone else. I'll tell you by Wednesday.
  27. Owen Tallis
    Owen Tallis None
    Wednesday's fine. Put that down, Tom.
  28. Tom Ashdown
    Tom Ashdown None
    Done. I'm just writing it in the notes now. Sorry, it's a bit of a mess, I've got three things open.
  29. Graham Tovey
    Graham Tovey None
    Can I ask one more on the regulator before we move on? If something goes wrong with a source, say the billing data stops loading, how would my people know?
  30. Tom Ashdown
    Tom Ashdown None
    Good question. Honestly, the dangerous one is the quiet one, where a source stops loading and nobody notices. So we watch the number of records coming in for each connector, and if it goes flat we'd expect to raise it with you before your teams find it. Usually that follows somebody changing a system at your end, so the sooner you tell us about changes, the better.
  31. Graham Tovey
    Graham Tovey None
    Then I'd want that said plainly in the paperwork. Tell me early, not late.
  32. Owen Tallis
    Owen Tallis None
    Agreed. We'll put the escalation route in writing, named person on our side, named person on yours.
  33. Siân Pritchard
    Siân Pritchard None
    That would help me a lot. At the moment, if the billing extract fails, I find out when someone in collections rings me, and that's too late.
  34. Tom Ashdown
    Tom Ashdown None
    Right, no, that's what we're trying to avoid. Shall I move on to freshness? That's your second one.
  35. Siân Pritchard
    Siân Pritchard None
    Please. Collections start early. If the overnight refresh hasn't finished by seven, they're working from yesterday's picture, and then the whole point is lost. Somebody chases a customer who paid last night. I can't have that.
  36. Tom Ashdown
    Tom Ashdown None
    Yeah. So the refresh is complete by 07:00 your local time on business days, on every tier. That's the standard. Where Enterprise differs is that you're credited if freshness is missed, not only if the service is down. Those are different things. The brain can be up and answering questions and still be on stale data.
  37. Graham Tovey
    Graham Tovey None
    So available is not the same as fresh.
  38. Tom Ashdown
    Tom Ashdown None
    Exactly that, Graham. On the lower tiers you'd only be credited for availability. On Enterprise it covers both.
  39. Siân Pritchard
    Siân Pritchard None
    Good, that's what I wanted to hear. Can it be written into the order form, not just sit in the standard terms?
  40. Owen Tallis
    Owen Tallis None
    It can. An executed order form can set these out explicitly and that's what governs. Tom will mark it up. Let's make sure the wording says freshness by 07:00, business days, and names the credit.
  41. Tom Ashdown
    Tom Ashdown None
    Leave that with me. I'll put it in the revised draft.
  42. Graham Tovey
    Graham Tovey None
    And the price doesn't change when you write that in?
  43. Owen Tallis
    Owen Tallis None
    No. It's already part of Enterprise. We're making it visible, not charging for it.
  44. Graham Tovey
    Graham Tovey None
    Good.
  45. Siân Pritchard
    Siân Pritchard None
    Sorry, I was just checking my notes. Third one, the build. I'll be the owner on our side, and I've a couple of analysts I can give time to it, but they've also got the day job. I need to know what you'll ask of them week to week.
  46. Tom Ashdown
    Tom Ashdown None
    Fair. Honestly it's front-loaded. Early on we need someone who knows each source, who can grant access and say what the fields really mean. After that it's a short check-in and someone to confirm the answers look right against what they know. You'd be the person who says whether it's right, not the person doing the plumbing.
  47. Siân Pritchard
    Siân Pritchard None
    That I can do. Which systems do you want first?
  48. Tom Ashdown
    Tom Ashdown None
    What would you say matters most for complaints and collections?
  49. Siân Pritchard
    Siân Pritchard None
    The CRM, the call recorder and the billing system. Helpdesk after that. The rest can follow once we've seen it work.
  50. Tom Ashdown
    Tom Ashdown None
    That's sensible, and I'd keep it to those. One thing worth saying: any connector we promise in the order form carries a commitment to be live within an agreed number of days. So I'd rather list the ones you're sure about and add more later than promise everything on day one.
  51. Owen Tallis
    Owen Tallis None
    We'd rather commit to fewer and deliver. It's better for you and better for us.
  52. Graham Tovey
    Graham Tovey None
    I agree. Siân, you're content with those first three?
  53. Siân Pritchard
    Siân Pritchard None
    Yes. And I'll say now, I expect the key accounts team to use it first, then collections, then complaints. I don't want to oversell what happens in the first weeks. Let's measure it before we claim it.
  54. Tom Ashdown
    Tom Ashdown None
    That's how I'd want it. And on the number of people using it, Enterprise is built for company-wide use, so there's headroom. If you grow past it, we can add users, but I'd not worry about that now.
  55. Graham Tovey
    Graham Tovey None
    What do I need to be doing as sponsor?
  56. Owen Tallis
    Owen Tallis None
    Mostly very little, which is how we like it. A short review with Siân and our CSM, Daniel Okafor, who'll look after the account after signature. Your job is to be the person who says if it isn't delivering what you were told.
  57. Graham Tovey
    Graham Tovey None
    That I can do. And Daniel will tell me when something's wrong, not after.
  58. Owen Tallis
    Owen Tallis None
    That's the expectation, yes.
  59. Siân Pritchard
    Siân Pritchard None
    Tom, can I ask about the data. If we ever stopped using it, what happens? Graham will ask me, so I'd rather know.
  60. Tom Ashdown
    Tom Ashdown None
    Good one. It's built in your Snowflake account, so it's yours. We don't hold your data on our side. What you'd lose is the working layer we built and run for you. I'll set that out properly in writing, because it's the sort of thing I'd rather not paraphrase.
  61. Graham Tovey
    Graham Tovey None
    Please do. I'd want our legal team to see it.
  62. Tom Ashdown
    Tom Ashdown None
    Will do. Both that and the order form changes go together, so they're not reading it in bits.
  63. Owen Tallis
    Owen Tallis None
    Right. Can I pin down who signs? Graham, you, with Siân's view. Is there anyone else, procurement, legal?
  64. Graham Tovey
    Graham Tovey None
    I sign. Our procurement team will want to review the order form and the master agreement first, and our legal team will read the data terms. That's the order. I won't sign until Siân has told me she's satisfied.
  65. Siân Pritchard
    Siân Pritchard None
    And I won't say that until the security answers are back. I'd rather be slow and right.
  66. Owen Tallis
    Owen Tallis None
    Understood. So the dated steps. Tom sends the security pack today. Siân tells us by Wednesday whether the questionnaire can come back by the end of next week. Tom sends the revised order form with the freshness wording and the data terms by the end of this week. Then it's with your procurement and legal teams.
  67. Tom Ashdown
    Tom Ashdown None
    Yep, that's what I have. End of this week for the order form, no problem.
  68. Graham Tovey
    Graham Tovey None
    And the date you mentioned. The Friday after Christmas. I'd rather we signed before the break, frankly. If it slips into January, nobody is looking at it.
  69. Owen Tallis
    Owen Tallis None
    That's fair, and I'd rather not leave a deal on a hopeful date. Here's what I'd suggest. We keep Friday 27 December 2024 as the latest, but we aim to be done before the break. If the security review is not back in time, I'll tell you straight away and we'll reset the date, rather than let it drift.
  70. Graham Tovey
    Graham Tovey None
    That's what I'm asking for.
  71. Siân Pritchard
    Siân Pritchard None
    I think it's realistic if the answers come back in good time in December. It's the legal read I can't control. But I'll chase it.
  72. Tom Ashdown
    Tom Ashdown None
    Then I'll make that as easy as I can. Is it worth putting a short call in the diary for next week, just to check where everything is? Say twenty minutes, Siân and me, no need for the rest.
  73. Siân Pritchard
    Siân Pritchard None
    Yes, let's get something in the diary. Midweek is best for me.
  74. Tom Ashdown
    Tom Ashdown None
    Lovely. I'll send an invite this afternoon.
  75. Owen Tallis
    Owen Tallis None
    Anything else we should settle while we're all here? Anything that would stop Graham signing?
  76. Graham Tovey
    Graham Tovey None
    Nothing stopping it. I want the three things in writing: the freshness wording, the escalation route, and what happens to the data if we leave. Provided those are there and Siân's content, I've no objection.
  77. Siân Pritchard
    Siân Pritchard None
    The only other thing is the training for the teams once it's live. I'd like the key accounts team to see it on our own customers, not a demo, so they believe it.
  78. Tom Ashdown
    Tom Ashdown None
    Absolutely, that's how we'd do it, on your data. Daniel will pick that up with you once the first sources are in. I'll make sure it's in the plan so it doesn't get lost.
  79. Siân Pritchard
    Siân Pritchard None
    Good. Then I'm comfortable with where we are.
  80. Graham Tovey
    Graham Tovey None
    Then so am I, subject to the paperwork.
  81. Owen Tallis
    Owen Tallis None
    Right. Let me read it back so we're all holding the same thing. Enterprise, the total for the deal being £145,000 with implementation included, annual part confirmed by Tom in writing. Freshness by 07:00 on business days, credited, written into the order form. Escalation route named on both sides. Data terms explained. Security questionnaire with Siân's IT colleague. Signature by Friday 27 December 2024 at the latest, and sooner if we can.
  82. Graham Tovey
    Graham Tovey None
    That's accurate.
  83. Siân Pritchard
    Siân Pritchard None
    Yes. That's what I have as well.
  84. Tom Ashdown
    Tom Ashdown None
    Cracking. I'll get the pack and the order form out, no drama. If anything shifts at your end, just shout and we'll sort it.
  85. Owen Tallis
    Owen Tallis None
    And if it shifts at ours, you'll hear first. Thanks, both.
  86. Graham Tovey
    Graham Tovey None
    Thank you, all. Good call. Siân, speak later this week.
  87. Siân Pritchard
    Siân Pritchard None
    Will do, Graham. Diolch, everyone. Speak Wednesday, Tom.
  88. Tom Ashdown
    Tom Ashdown None
    Cheers, Siân, cheers, Graham. Have a good week.
  89. Owen Tallis
    Owen Tallis None
    Bye for now.

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