Ask
Daniel Okafor

Delancey Haig / BB-Demo – Check In

Callcompleted

Delancey Haig: documents logo Delancey Haig: documents · 2026-06-09 15:00

Kwame Asante, CTO, confirmed Delancey Haig will not renew Growth and will build an in-house data capability. The call set out connector shut-down, handover and access ending on 2 Jul 2026. Service was not the reason.

made from

What was said

What this says

Current to 11 Oct 26

Kwame Asante, CTO, confirmed Delancey Haig will not renew Growth and will build an in-house data capability. The call set out connector shut-down, handover and access ending on 2 Jul 2026. Service was not the reason.

What happened: On the 9 Jun 2026 call, Kwame Asante confirmed the Growth subscription will not renew when the term ends on 2 Jul 2026. The rest of the call planned the wind-down: connector schedule, credentials, data dictionary and a final check.

Customer view: Kwame and Holly Tranter both said service was fine, with no tickets and on-time refreshes. Kwame put the decision down to build versus buy, with his own team running fewer platforms.

Commercial: Invoices are settled and Daniel Okafor's records show nothing outstanding. Kwame said he does not expect to return, but the tables stay in the customer's Snowflake account, so a later restart would be quicker.

Watch: Holly said directors stopped using the brain once the decision was in sight. The question-asking feature is the piece Kwame said will be hardest to replace.

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

AImade from

Themes

Current to 9 Oct 26
Theme
Non-renewal, in-house build
Importance
churn
Sentiment
mixed
Voice
decision-maker
AImade from

Who was there

BB-Demo

CRMmade from

Them

CRMmade from

Follow-up

Next steps

Current to 9 Oct 26
  • Laura Penhaligon sends the connector schedule and credential list early next week, then the data dictionary and exported definitions.
  • Daniel Okafor sends a written summary within a day, including the order form data clauses.
  • Daniel sends written confirmation that access is removed after access ends on 2 Jul 2026.
AImade from

Risks

Current to 9 Oct 26
  • The in-house build replaces the subscription, so no renewal follows the term ending 2 Jul 2026.
  • Kwame said he does not expect to return as a customer.
AImade from

Opportunities

Current to 9 Oct 26
  • Data stays in the customer's Snowflake account, so a later restart would be quicker than a fresh start.
  • Kwame would welcome an hour between Daniel and the new data hire on how the brain was built.
AImade from

Transcript

  1. Daniel Okafor
    Daniel Okafor None
    Hello, can you hear me all right? Good afternoon, and thank you all for making the time. Just checking who has joined. I can see Holly and Kwame, and Laura is on from our side as well.
  2. Holly Tranter
    Holly Tranter None
    Hi Daniel, yes, I can hear you fine. Afternoon, everyone.
  3. Kwame Asante
    Kwame Asante None
    Afternoon. Before we get going, Laura, have you got the architecture diagram to hand? I'd like to see where each piece sits before we talk about anything else.
  4. Laura Penhaligon
    Laura Penhaligon None
    Hi Kwame, hi Holly. Yes, I have it open. Give me a second to share it. Can you see it?
  5. Kwame Asante
    Kwame Asante None
    Not yet. Ah, there it is. Right. So this is the Snowflake account on the left, and your layer sits inside it.
  6. Laura Penhaligon
    Laura Penhaligon None
    Exactly. That's the key point for today, really. Everything the brain builds from your sources is stored as tables and objects inside your own Snowflake account. We never took a copy out to a platform of ours.
  7. Kwame Asante
    Kwame Asante None
    Good. Where does the data live once you've switched off? I want that said plainly, so I can put it in the paper.
  8. Laura Penhaligon
    Laura Penhaligon None
    Plainly: it stays where it is. The tables, the indexed records, the history of what was loaded each night, all of that stays in your account and belongs to you. What goes is our application layer on top, so the chat, the search and the pages that we serve.
  9. Daniel Okafor
    Daniel Okafor None
    And if I can add something here, because I know this is not the call anyone planned a year ago. I wanted to say thank you first. Kwame, Holly, you have both been very straightforward with us about the decision, and that makes it much easier to do this properly.
  10. Kwame Asante
    Kwame Asante None
    Appreciated, Daniel. It's not a reflection on the product. My team is building an in-house data capability and I'd rather the firm runs a small number of platforms itself. It came down to the build-versus-buy case, and this time the case went the other way.
  11. Daniel Okafor
    Daniel Okafor None
    Understood, and I won't try to reopen it. Just to close the loop, I'd like us to leave today with a clear list of what happens, in what order, and who does what. Is that all right?
  12. Kwame Asante
    Kwame Asante None
    That's what I wanted. Go ahead.
  13. Daniel Okafor
    Daniel Okafor None
    So, the contract runs to Thursday 2 July 2026. That is the last day BB-Demo has any access to your environment. The renewal would have started the day after, Friday 3 July 2026, and it won't now, so nothing will be invoiced beyond the current term.
  14. Holly Tranter
    Holly Tranter None
    Right. And the invoices are all settled on our side, I checked with our finance team this week. The forty users and the forty-four thousand a year, that's the full term, paid up.
  15. Daniel Okafor
    Daniel Okafor None
    That matches what we have, thank you, Holly. Nothing outstanding on our records either.
  16. Kwame Asante
    Kwame Asante None
    Fine. Laura, walk me through the shut-down sequence. What happens to the connectors and in what order?
  17. Laura Penhaligon
    Laura Penhaligon None
    Sure. Each source has its own connector, and each one runs a nightly load into your account. My suggestion is we stop them one at a time rather than all at once, so that you can see nothing breaks downstream. The last nightly refresh runs, we confirm it completed, and then we disable that connector and remove the credentials it was using.
  18. Holly Tranter
    Holly Tranter None
    Which credentials are those? Are they ones I created?
  19. Laura Penhaligon
    Laura Penhaligon None
    Mostly yes. When we set up, you created service users or API keys in each source system for us. Those are the ones we'd ask you to revoke on your side as well, belt and braces. I'll write down exactly which ones, per source, so you can tick them off.
  20. Holly Tranter
    Holly Tranter None
    That would help. I know where most of them are but there was one from the very early days that I'd want to double check.
  21. Laura Penhaligon
    Laura Penhaligon None
    Mm, I remember. It's in the setup notes from the implementation. I'll include it.
  22. Kwame Asante
    Kwame Asante None
    And the dates. You said stagger them. I'd like actual dates per connector, not just a sequence.
  23. Daniel Okafor
    Daniel Okafor None
    That's fair. What I can commit to is the outer edge: nothing of ours is live after Thursday 2 July 2026, and every connector will be off before then. The exact day for each one I'd like Laura to put in writing, and I'll come back to you by the end of the week with that schedule so you can agree it.
  24. Kwame Asante
    Kwame Asante None
    Good. I'd rather not have a connector running on the last day with nobody watching it.
  25. Laura Penhaligon
    Laura Penhaligon None
    Agreed, and I'd sooner leave a few working days either side of the end for exactly that reason. If something looks odd in the tables after a connector goes, you have time to ask us.
  26. Holly Tranter
    Holly Tranter None
    Can I ask about the history? When the connectors stop, are the old records still queryable in Snowflake, or do they go stale and get tidied away?
  27. Laura Penhaligon
    Laura Penhaligon None
    They stay. Nothing gets deleted by us. They simply stop being refreshed, so the tables will show the state of things as of the last load. If your new team wants to build on them, or just archive them, that's entirely your choice.
  28. Kwame Asante
    Kwame Asante None
    Right. And the structure of those tables, is it documented? If my people are going to read them, they'll need to know what each one is.
  29. Laura Penhaligon
    Laura Penhaligon None
    Yes, we can give you a data dictionary: table names, what each one holds, how they relate, and which source they came from. It's something we'd normally produce in the handover anyway, so I'll make sure it's current rather than the version from go-live.
  30. Kwame Asante
    Kwame Asante None
    Please. That's the thing I'd most like to have in hand.
  31. Daniel Okafor
    Daniel Okafor None
    Noted. Holly, may I ask how the team has been finding it in recent weeks? I'm conscious we've seen fewer people logging in than earlier in the year, and I'd like to understand it rather than assume.
  32. Holly Tranter
    Holly Tranter None
    Honestly, it dropped away once the decision was in sight. A lot of the client-account directors went back to their own reports. It was never that it didn't work. People just stopped investing in it, and I can't blame them.
  33. Daniel Okafor
    Daniel Okafor None
    That's useful to hear, and I appreciate you saying it. It's very human, isn't it? When something is ending, the habit goes first.
  34. Holly Tranter
    Holly Tranter None
    Yes, exactly that. A couple of them still ask me for the combined view of a client, their vacancies, placements, invoices and complaints, because that's what they liked.
  35. Kwame Asante
    Kwame Asante None
    And that's one of the things my team will need to recreate. It's on the list. We'll build it ourselves, on the same tables if it makes sense.
  36. Laura Penhaligon
    Laura Penhaligon None
    That might be a helpful starting point, actually. The dashboards and pages the directors used, I can export the definitions, so you can see which fields and joins they relied on.
  37. Kwame Asante
    Kwame Asante None
    Do that. What format would that be?
  38. Laura Penhaligon
    Laura Penhaligon None
    Plain files you can open without us: the queries behind each view, plus a readable description of each page. Nothing that needs our software to make sense of it.
  39. Kwame Asante
    Kwame Asante None
    Good. I don't want a dependency left behind that I only find out about in the autumn.
  40. Daniel Okafor
    Daniel Okafor None
    Understandably. Let me make sure I have it in the right order, and please stop me if I've got it wrong. One, Laura sends the connector schedule and the credential list. Two, Holly revokes the credentials after each connector is confirmed off. Three, Laura sends the data dictionary and the exported definitions. Four, we do a short final check together before access ends on Thursday 2 July 2026.
  41. Holly Tranter
    Holly Tranter None
    That sounds right. When would the final check be?
  42. Daniel Okafor
    Daniel Okafor None
    I don't want to guess a date that isn't mine to give. Laura holds the technical calendar, so I'll ask her to propose a slot in the last week and I'll confirm it with you in writing.
  43. Laura Penhaligon
    Laura Penhaligon None
    Yes, I'll offer a couple of options. Afternoons suit you better, I think, Holly?
  44. Holly Tranter
    Holly Tranter None
    Afternoons are better, yes. Mornings are the stand-ups and the nightly checks.
  45. Kwame Asante
    Kwame Asante None
    One more architecture question while Laura's still sharing. SSO. We don't have it on Growth, but is there anything that authenticates through you that I should know about?
  46. Laura Penhaligon
    Laura Penhaligon None
    No, on Growth it's standard user accounts in our application layer. When the layer stops being served, those accounts simply stop working. There's nothing of yours tied to them in Snowflake, other than the roles we created for the connectors.
  47. Kwame Asante
    Kwame Asante None
    The roles. Those I'd want removed as well. Holly, put that on the checklist.
  48. Holly Tranter
    Holly Tranter None
    Already writing it down. Roles and warehouse permissions for the BB-Demo service user.
  49. Laura Penhaligon
    Laura Penhaligon None
    I'll list those too, by name, so there's no ambiguity about what's ours and what's yours.
  50. Kwame Asante
    Kwame Asante None
    And the compute? Anything we're paying for in Snowflake that exists only because of the brain?
  51. Laura Penhaligon
    Laura Penhaligon None
    Good question. The nightly loads run on warehouses in your account, so that usage is billed by Snowflake to you. When the connectors stop, that usage stops with them. I can point at which warehouse and schedule are involved so you can suspend or drop them cleanly.
  52. Kwame Asante
    Kwame Asante None
    That's the sort of thing that ends up costing money for months if nobody tidies it. Yes, include it.
  53. Daniel Okafor
    Daniel Okafor None
    Very sensible. I'll make sure it's in the written summary as its own line.
  54. Holly Tranter
    Holly Tranter None
    Daniel, can I ask something slightly different? If we wanted to come back to this in a year or so, is there anything we should do now to make that easy?
  55. Daniel Okafor
    Daniel Okafor None
    I appreciate you asking, Holly, and I'll answer it honestly. Because everything stays in your Snowflake account, there's very little to undo. If you left the tables in place, a later start would be quicker than a fresh one, because the sources and the structure are already mapped. But please don't keep anything on our account. Do what is right for your new setup.
  56. Kwame Asante
    Kwame Asante None
    I'll be direct, Daniel: I don't expect to, but it's useful to know the door isn't locked.
  57. Daniel Okafor
    Daniel Okafor None
    It's never locked. And whoever joins your data team, I'd be glad to talk to them about how the thing was built, if it saves them time.
  58. Kwame Asante
    Kwame Asante None
    That might be worthwhile, actually. I'll mention it when we hire. It would be a good use of an hour.
  59. Holly Tranter
    Holly Tranter None
    On the user side, what do I need to tell people? There'll be directors who open the page next month and find it gone.
  60. Daniel Okafor
    Daniel Okafor None
    I'd tell them the date, and I'd tell them where the figures will come from instead. If it helps, Laura and I can draft a short note for you to send, in your words, so it doesn't read as coming from a vendor.
  61. Holly Tranter
    Holly Tranter None
    That would be lovely, thank you. Two or three lines would do.
  62. Kwame Asante
    Kwame Asante None
    Keep it short. And I'll want to read it before it goes.
  63. Daniel Okafor
    Daniel Okafor None
    Of course. You'll see it first.
  64. Laura Penhaligon
    Laura Penhaligon None
    Can I raise one thing about the pages? Some of them have comments and notes people added over time. Those are in the export, but I'd like Holly to tell me whether anyone would be unhappy about them being handed over, in case there's anything sensitive.
  65. Holly Tranter
    Holly Tranter None
    Hm. Good point. Most of it is routine. Some of the account directors wrote candid notes about clients, though. I'd want to look through before it goes beyond me and Kwame.
  66. Kwame Asante
    Kwame Asante None
    It stays inside the firm either way. But yes, Holly reviews it first. Not a problem.
  67. Laura Penhaligon
    Laura Penhaligon None
    Then I'll send the export to Holly only, and she can release it onwards.
  68. Holly Tranter
    Holly Tranter None
    Perfect.
  69. Kwame Asante
    Kwame Asante None
    Right. Is there anything contractual I should be aware of? Notice, data return, anything in the order form that I've missed?
  70. Daniel Okafor
    Daniel Okafor None
    The order form is the document that governs, and what it says on data is consistent with what Laura has described: your data remains yours and in your account. I won't paraphrase beyond that on a call. If you'd like, I'll point you to the relevant clauses in the follow-up so your team can read them directly.
  71. Kwame Asante
    Kwame Asante None
    Do that. I don't take a vendor's word on these things, as you know, and that's not personal.
  72. Daniel Okafor
    Daniel Okafor None
    Not at all. I'd think less of you if you did.
  73. Kwame Asante
    Kwame Asante None
    Ha. Thank you.
  74. Holly Tranter
    Holly Tranter None
    Sorry, one last practical thing. The Zendesk side. We had a connector for the helpdesk. Is that handled the same way as the others?
  75. Laura Penhaligon
    Laura Penhaligon None
    The same way, yes. Same order, same process: last load, confirm, disable, revoke. The helpdesk and the accounting connector both load a lot of history, so I'll check those tables carefully at the end, just to make sure the final load is complete.
  76. Holly Tranter
    Holly Tranter None
    Okay, good. I just wanted to be sure it wasn't treated differently.
  77. Kwame Asante
    Kwame Asante None
    Let me say what I'd like to take away. I want a written options paper from my own side for the board, and for that I need the data dictionary, the schedule and the list of what's ours. I can't sign anything off without those.
  78. Daniel Okafor
    Daniel Okafor None
    Then those three come first. Laura, would you be able to get the schedule and the credential list to them early next week?
  79. Laura Penhaligon
    Laura Penhaligon None
    Yes, early next week for those two. The data dictionary needs a bit more care, because I want it checked against the live tables rather than the original design. I'll say when I'll have it once I've started.
  80. Kwame Asante
    Kwame Asante None
    That's acceptable. Correct is better than quick.
  81. Daniel Okafor
    Daniel Okafor None
    Good. Is there anything about the last months that went wrong for you that we should hear? I'd rather know.
  82. Holly Tranter
    Holly Tranter None
    Nothing went wrong. There were no tickets and nothing was broken. The refresh was on time every morning, as far as I saw. It just didn't earn its place in the firm's plans, I think.
  83. Kwame Asante
    Kwame Asante None
    I'd second that. Service was fine. This is about ownership, nothing else.
  84. Daniel Okafor
    Daniel Okafor None
    Thank you, both. That's kind of you to say, and it's helpful for us to hear that it was the shape of the decision rather than the service.
  85. Daniel Okafor
    Daniel Okafor None
    Holly, if I can just ask: were there parts of it the directors genuinely valued, that we should pass on to your build team as something to keep?
  86. Holly Tranter
    Holly Tranter None
    The single client view, definitely. And being able to ask a plain question, like which clients have had a complaint and a late invoice in the same month. People liked that they didn't have to ask me or a colleague in IT.
  87. Kwame Asante
    Kwame Asante None
    That's useful for my team to hear. The question-asking part is the harder piece to replace, I'll be honest. We'll start with the reports.
  88. Daniel Okafor
    Daniel Okafor None
    It's a fair way to start. Laura, you could include the most common questions people asked in the handover, as examples. It may help them see what to build towards.
  89. Laura Penhaligon
    Laura Penhaligon None
    I can do that. I'll pull out the ones that were asked most often and attach them as plain text.
  90. Kwame Asante
    Kwame Asante None
    That would be a good addition. Thank you.
  91. Holly Tranter
    Holly Tranter None
    Is there anything you need from me before the final week? I'd rather do it now than be scrambling.
  92. Laura Penhaligon
    Laura Penhaligon None
    Two things. A named person on your side who can approve each connector being switched off, so I'm not waiting on an answer, and confirmation of who should receive the export. I assume that's you.
  93. Holly Tranter
    Holly Tranter None
    Both me, with Kwame copied. If I'm away, he decides.
  94. Kwame Asante
    Kwame Asante None
    Fine. Copy me on everything and I'll step in if needed.
  95. Daniel Okafor
    Daniel Okafor None
    Lovely, that's clear. And on our side, anything to do with timing or the contract comes through me, anything technical comes through Laura. That way you're never wondering who to ask.
  96. Kwame Asante
    Kwame Asante None
    Good, I like that. One owner each.
  97. Holly Tranter
    Holly Tranter None
    Do we get something in writing at the very end? A confirmation that access is removed, and so on.
  98. Daniel Okafor
    Daniel Okafor None
    Yes. After access ends on Thursday 2 July 2026, I'll send a short written confirmation that our access has been removed and that the connectors are off. If you'd like it to name the roles and credentials, Laura can add those so it matches your checklist.
  99. Kwame Asante
    Kwame Asante None
    I would like that. Names and all.
  100. Laura Penhaligon
    Laura Penhaligon None
    No problem. It's easy enough to produce once the removals are done.
  101. Holly Tranter
    Holly Tranter None
    Can I just check one thing about timing, please? You said the last day is Thursday 2 July 2026. Does that mean you're still reachable on that day, or earlier in the week?
  102. Daniel Okafor
    Daniel Okafor None
    We'll be reachable all through, including that Thursday. What changes on the Thursday is that our access to your environment ends. If something odd turns up afterwards, send it to me and I'll make sure it's looked at, even though we can no longer touch the account.
  103. Kwame Asante
    Kwame Asante None
    That's decent of you. Though I'd hope there's nothing.
  104. Daniel Okafor
    Daniel Okafor None
    I hope so too.
  105. Holly Tranter
    Holly Tranter None
    I'd like to say, for what it's worth, that it was a good partnership. Laura set us up very well and the team we dealt with were always patient with me, particularly early on when I had no idea how the connectors worked.
  106. Laura Penhaligon
    Laura Penhaligon None
    Thank you, Holly, that's lovely. You picked it up faster than you remember, honestly.
  107. Kwame Asante
    Kwame Asante None
    She did. Better than I did, certainly.
  108. Holly Tranter
    Holly Tranter None
    Ha, thank you both.
  109. Daniel Okafor
    Daniel Okafor None
    Kwame, may I ask one thing that's more personal than practical? The data team you're building, are you well on the way with hiring?
  110. Kwame Asante
    Kwame Asante None
    Getting there. A couple of people in place, a couple more to find. It's the right time of year, people are moving. We'll be running by the autumn, in a modest way.
  111. Daniel Okafor
    Daniel Okafor None
    I wish you well with it. Truly. It's an interesting build and the foundations are already in your account, which should help.
  112. Kwame Asante
    Kwame Asante None
    That's the other reason I wanted it to stay in Snowflake from the start. Thank you for respecting that.
  113. Laura Penhaligon
    Laura Penhaligon None
    Can I add one practical suggestion for your team? Before the connectors stop, take a snapshot or a clone of the key tables, so you have a fixed copy at a known date. It costs very little and it means your new work starts from a stable base.
  114. Kwame Asante
    Kwame Asante None
    A clone at the final load. Yes, that's sensible. Holly, add it.
  115. Holly Tranter
    Holly Tranter None
    Adding it. Clone the tables once the last refresh has completed.
  116. Laura Penhaligon
    Laura Penhaligon None
    Right. And I'll tell you the moment the last refresh for each connector has gone through, so you know when to do it.
  117. Kwame Asante
    Kwame Asante None
    Good. That removes any guesswork.
  118. Daniel Okafor
    Daniel Okafor None
    Let me recap what each of us is doing, so that nobody leaves guessing. I'll send the written summary of this call within a day or so, including the clauses on data in the order form and the line on warehouse usage. Laura sends the connector schedule and credential list early next week, then the data dictionary and exported definitions when they're checked. Holly reviews the export, revokes credentials as each connector is confirmed off, and clones the tables after the last refresh. Kwame, you read the draft note for the directors before it goes.
  119. Holly Tranter
    Holly Tranter None
    That's everything I have. I'd add the roles and warehouse permissions, but that's covered.
  120. Kwame Asante
    Kwame Asante None
    I have the same list. If anything changes in the schedule, I want to hear it from Daniel directly, not discover it.
  121. Daniel Okafor
    Daniel Okafor None
    Understood. You will. And if I don't know something, I'll say that rather than guess.
  122. Kwame Asante
    Kwame Asante None
    Good.
  123. Holly Tranter
    Holly Tranter None
    Daniel, is it okay if I send you questions by email as they come up? I'd rather not wait for another call.
  124. Daniel Okafor
    Daniel Okafor None
    Please do. Email is best, and I'll reply the same day where I can. If it's a technical question I'll bring Laura in straight away.
  125. Laura Penhaligon
    Laura Penhaligon None
    Or copy me. Either way it reaches me.
  126. Holly Tranter
    Holly Tranter None
    Will do, both of you.
  127. Kwame Asante
    Kwame Asante None
    Daniel, one thing before we finish. I should say, for the record, that I appreciate how the account has been handled. You've given us what we asked for without trying to talk us round. Not every supplier does that.
  128. Daniel Okafor
    Daniel Okafor None
    That means a lot, Kwame, thank you. Our aim is simply that you finish with everything you need and nothing you didn't expect. The people matter more to me than the contract, and I've enjoyed working with this team.
  129. Kwame Asante
    Kwame Asante None
    Likewise.
  130. Holly Tranter
    Holly Tranter None
    Same from me.
  131. Laura Penhaligon
    Laura Penhaligon None
    And from me. It was a pleasure to build it with you, Holly. I'll get the first pieces to you next week.
  132. Holly Tranter
    Holly Tranter None
    Thank you, Laura. I'll look out for them.
  133. Daniel Okafor
    Daniel Okafor None
    Is there anything else anyone wants to raise before we stop? Anything at all, even if it feels small.
  134. Holly Tranter
    Holly Tranter None
    Just checking I'm not forgetting the licence side. Forty users. Nothing to do with those, they just lapse on the date?
  135. Daniel Okafor
    Daniel Okafor None
    Right, they simply lapse when the term ends on Thursday 2 July 2026. There's nothing for you to cancel and no action needed from you on the seats.
  136. Holly Tranter
    Holly Tranter None
    Lovely. That's the last of my questions.
  137. Kwame Asante
    Kwame Asante None
    Nothing from me. Send me the paper trail and I'll take it from there.
  138. Daniel Okafor
    Daniel Okafor None
    Will do. Then thank you all, again, for the time and for being so clear with us. I'll be in touch within a day, and you'll hear from Laura early next week.
  139. Laura Penhaligon
    Laura Penhaligon None
    Speak soon, both. Take care.
  140. Holly Tranter
    Holly Tranter None
    Thanks, everyone. Bye for now.
  141. Kwame Asante
    Kwame Asante None
    Thank you. Goodbye.
  142. Daniel Okafor
    Daniel Okafor None
    Best wishes to you both. Goodbye for now.
Callsmade from

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
Organisations150
People at customers573
BB-Demo staff48
Calls1,382
Email threads2,122
Support tickets789
Documents850
Deals217
Invoices187
Events49
News items84

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