Ask
Callie Brennan

Kelvinhaugh Pension Services / BB-Demo – Kickoff

Callcompleted

Kelvinhaugh Pension Services: documents logo Kelvinhaugh Pension Services: documents · 2024-02-16 11:30

On the 16 Feb 2024 kickoff, Kelvinhaugh agreed to start with the CRM and helpdesk, with mailbox scope held until IT signs off. Fiona Drummond described the team as curious more than convinced.

What was said

What this says

Current to 11 Oct 26

On the 16 Feb 2024 kickoff, Kelvinhaugh agreed to start with the CRM and helpdesk, with mailbox scope held until IT signs off. Fiona Drummond described the team as curious more than convinced.

What happened: Callie Brennan ran the kickoff with Daniel Okafor and covered the four-connector limit, sources, access and owners. Starter was confirmed at £18k a year, with the term running to 8 Feb 2025.

Customer view: Iain Lumsden raised member data and health information in mailboxes, and wants scope in writing before anything is switched on. Ailsa Dunlop warned that client names in the CRM are inconsistent.

Commercial: Fiona said she would rather get four connectors right than rush into eight. Daniel offered to discuss more connectors at the check-in.

Watch: Fiona wants the relationship managers to see something they can ask a real question of quickly. The evidence does not show any refresh having landed yet.

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

Themes

Current to 9 Oct 26
Theme
Starter onboarding and data scope
Importance
neutral
Sentiment
mixed
Voice
champion

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Ailsa Dunlop sends the messy client sample and helpdesk access, and Iain Lumsden sends the shared mailbox list.
  • Daniel Okafor sends the standard data protection pack to Iain Lumsden.
  • Callie Brennan writes the setup note and sends the plan, with Fiona Drummond nominating the owner field and first users.

Risks

Current to 9 Oct 26
  • Mailbox scope is unresolved because member and health data sit in emails, and label exclusion is untested.
  • Inconsistent client names in the CRM could delay a clean field mapping and the first useful answers.
  • The team is curious rather than convinced, so early adoption depends on a quick first result.

Opportunities

Current to 9 Oct 26
  • The four-connector hard limit against more customer systems could lead to a connector add-on or a Growth conversation at the check-in.
  • Fiona Drummond plans to bring a relationship manager in once there is something to look at, which widens the user base.

Transcript

  1. Daniel Okafor
    Daniel Okafor None
    Hello, hello. Thanks everyone for making the time. Let me just check who's joined. Fiona, Ailsa, and I think Iain is just coming in.
  2. Fiona Drummond
    Fiona Drummond None
    Morning, Daniel. Yes, I can see Iain's tile now.
  3. Iain Lumsden
    Iain Lumsden None
    Morning. Sorry, I was stuck on another call. Can you hear me all right?
  4. Daniel Okafor
    Daniel Okafor None
    Loud and clear. And Callie's here too. She'll run most of the hour, and I'll chip in on the commercial side and on how the team finds it afterwards.
  5. Callie Brennan
    Callie Brennan None
    Hi all. Thanks, Daniel. So, the plan for the next hour. First, a quick recap of what Starter gives you. Then the sources we connect and in what order. Then access and security. Then who owns what on your side, and we finish with dates. Does that sound all right?
  6. Fiona Drummond
    Fiona Drummond None
    That's fine. Can I just say, let's start with the people who'll use it. The relationship managers asked me this week what they'd actually be able to ask it, so I'd like them in my head while we go through the sources.
  7. Callie Brennan
    Callie Brennan None
    Perfect, that's exactly the right way round. So, Starter is one team, fifteen users, and four connectors. The four is a hard limit, the fifteen is a soft one. Which means we need to choose the four carefully.
  8. Ailsa Dunlop
    Ailsa Dunlop None
    Four. Right. We've got more systems than that, so it'll be a bit of a negotiation with ourselves.
  9. Daniel Okafor
    Daniel Okafor None
    It always is, Ailsa. And it can change later. You're on Starter at £17,550 a year, term running to 8 Feb 2025, and we can talk about more connectors at the check-in if you find you need them.
  10. Fiona Drummond
    Fiona Drummond None
    Understood. I'd rather get four right than rush into eight.
  11. Callie Brennan
    Callie Brennan None
    Good. So what I need from your side is a short list, and let me suggest a shape for it. Where do the relationship managers keep their client notes and contacts? Where do the emails with trustees and scheme sponsors live? Where are the meeting recordings, if there are any? And where do the queries and tickets go?
  12. Fiona Drummond
    Fiona Drummond None
    Contacts and notes, that's the CRM. Emails are in the shared mailboxes mostly, and some of the partners keep their own folders, which is a bit messy. Calls, we do record some of the trustee meetings. And queries from members go to the helpdesk, which Ailsa looks after.
  13. Ailsa Dunlop
    Ailsa Dunlop None
    Well, I administer it. Whether I look after it is another matter.
  14. Callie Brennan
    Callie Brennan None
    That's a perfectly good answer. So the CRM, the mailboxes, the call recorder and the helpdesk is one possible four. Is anything on there a worry?
  15. Iain Lumsden
    Iain Lumsden None
    The mailboxes, yes. I'd want to be clear what gets read. We hold member data, and some of those emails will have personal details in them. Pension scheme data, sometimes health information for ill-health retirements.
  16. Daniel Okafor
    Daniel Okafor None
    That's a fair thing to raise, Iain, and I'd rather we talk about it properly than skim past it. Callie, do you want to cover how it sits in the Snowflake account?
  17. Callie Brennan
    Callie Brennan None
    Sure. So the brain is built and run inside your own Snowflake account. Nothing is copied out to us. What we do is configure which sources load and which fields map, and you decide that. Before we switch on the refresh for any source, I need written access from you, and that includes the scope. So for the mailboxes, we can limit to named shared mailboxes and leave personal ones alone.
  18. Iain Lumsden
    Iain Lumsden None
    Named mailboxes would be a lot more comfortable. And can we exclude by label? Say, anything marked as medical.
  19. Callie Brennan
    Callie Brennan None
    Let me not say yes to that on the spot, because I haven't checked how your mailbox labels come through. I'll test it on a sample and tell you what I find. I don't want to say it should be fine and then be wrong.
  20. Iain Lumsden
    Iain Lumsden None
    That's honest, thank you. I'll send you the list of the shared mailboxes by the end of the week.
  21. Daniel Okafor
    Daniel Okafor None
    Just to close the loop, Iain, I'll also send over our standard data protection pack so you have it in writing, and you can mark it up with anything missing.
  22. Iain Lumsden
    Iain Lumsden None
    Good. That'll save me asking for it.
  23. Fiona Drummond
    Fiona Drummond None
    While we're on sources, can I push on the order? If we only get one source working in the first fortnight, which would you start with?
  24. Callie Brennan
    Callie Brennan None
    The CRM. It's the spine. Everything else hangs off the client and the contact records, so if that maps cleanly, the mailboxes and the tickets have something to attach to. Then the helpdesk, then the mailboxes once Iain is comfortable, then the call recorder.
  25. Ailsa Dunlop
    Ailsa Dunlop None
    The CRM is going to be the awkward one, I'll be honest. Client names aren't consistent. The same scheme can be written three ways.
  26. Callie Brennan
    Callie Brennan None
    That's useful to know now rather than later. Could you pull a sample of, say, the messiest clients, and I'll build the field mapping around those? If it handles the worst ones, it'll handle the rest.
  27. Ailsa Dunlop
    Ailsa Dunlop None
    I can do that. I'll put it in the shared folder.
  28. Fiona Drummond
    Fiona Drummond None
    Who owns the client, in the brain, I mean? In our world the answer is sometimes the partner and sometimes the relationship manager, and sometimes both think it's the other one.
  29. Daniel Okafor
    Daniel Okafor None
    That's a good question, and it usually gets answered by the CRM field you already use. We take what's there. If it's muddy, that's something we'd flag in the setup note rather than guess.
  30. Fiona Drummond
    Fiona Drummond None
    Fine. Then I'll nominate the owner field as the thing to tidy first. Ailsa, is that all right?
  31. Ailsa Dunlop
    Ailsa Dunlop None
    Yes. It's on my list anyway.
  32. Callie Brennan
    Callie Brennan None
    Right, owners. For the brain on your side I'd like three things named. One person who is the admin day to day, one person who signs off access and security, and one person who speaks for the users. Does that fit?
  33. Fiona Drummond
    Fiona Drummond None
    Ailsa admin, Iain security, and I'll be the voice of the users for now. Though I'd like to bring a relationship manager in once there's something for them to look at.
  34. Callie Brennan
    Callie Brennan None
    That's lovely. And Ailsa, I want you able to run it alone by the end of onboarding. So we'll do a short walk-through of the admin screens each week and I'll leave you a setup note.
  35. Ailsa Dunlop
    Ailsa Dunlop None
    A setup note would be really welcome. Last time we adopted something, it all lived in one person's head.
  36. Daniel Okafor
    Daniel Okafor None
    How is the team finding the idea of it so far, Fiona? Honest answer.
  37. Fiona Drummond
    Fiona Drummond None
    Curious more than convinced. They've heard me talk about it, which isn't the same as seeing it. So the quicker we get to something they can ask a real question of, the better.
  38. Daniel Okafor
    Daniel Okafor None
    Understood. That's the measure I'd hold us to too.
  39. Callie Brennan
    Callie Brennan None
    Okay, so dates, and I'll say them as weeks because I'd rather not promise a day I don't own yet. Access in writing for the CRM and the helpdesk by the end of next week. First refresh on those two the week after. Mailboxes and the call recorder follow once Iain has signed off scope.
  40. Iain Lumsden
    Iain Lumsden None
    That works for me. I'd want to see the scope in writing before anything is switched on.
  41. Callie Brennan
    Callie Brennan None
    Which is exactly how I'll do it. Nothing starts without it.
  42. Fiona Drummond
    Fiona Drummond None
    And the users? There are fifteen seats. I don't want to invite everybody and have them look at an empty screen.
  43. Callie Brennan
    Callie Brennan None
    Agreed. I'd invite Ailsa and yourself first, then a handful of relationship managers once the first refresh has landed and we've checked it.
  44. Daniel Okafor
    Daniel Okafor None
    Anything we haven't covered? Anything that's worrying you and you haven't said?
  45. Ailsa Dunlop
    Ailsa Dunlop None
    Only the client names, and I've said that. Otherwise no.
  46. Iain Lumsden
    Iain Lumsden None
    The mailbox scope. But I think we've landed it.
  47. Fiona Drummond
    Fiona Drummond None
    I'm happy. It's quite a lot of homework for the three of us, but it's the right homework.
  48. Callie Brennan
    Callie Brennan None
    Then to recap. Ailsa sends the messy client sample and the helpdesk access. Iain sends the shared mailbox list and gets the data protection pack from Daniel. Fiona nominates the owner field and thinks about who the first users are. I write the setup note and send the plan today.
  49. Daniel Okafor
    Daniel Okafor None
    And I'll come back to you all once the first refresh has landed to see how it looks. Thank you, everyone. Lovely to have you on board.
  50. Fiona Drummond
    Fiona Drummond None
    Thanks all. Speak soon.
  51. Iain Lumsden
    Iain Lumsden None
    Thanks. Bye.
  52. Ailsa Dunlop
    Ailsa Dunlop None
    Bye all.

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