B-Brain
Elena Novak

Ardcarne Life Assurance / BB-Demo – Kickoff

Callcompleted

Ardcarne Life Assurance logo Ardcarne Life Assurance · 2026-10-06 15:30

Ardcarne's Chief Data Officer wants one trusted view of each broker firm. She starts small, expects usage to grow in a controlled way, and asked what happens at term end on 30 Sep 2027. The nightly extract is the main unknown.

What was said

What this says

Current to 13 Oct 26

Ardcarne's Chief Data Officer wants one trusted view of each broker firm. She starts small, expects usage to grow in a controlled way, and asked what happens at term end on 30 Sep 2027. The nightly extract is the main unknown.

What happened: Elena Novak ran the kickoff with Theo Gallagher and Ollie Pearson. Niamh Costello set the first outcome as a single trusted view per broker firm, with individual brokers out of scope for now.

Customer view: Niamh said she was nervous about this one and will watch the first weeks closely. She wants early, honest warning if usage lags.

Commercial: Niamh asked what happens at the end of the term. Elena confirmed the Enterprise subscription of £125k runs to 30 Sep 2027, with renewal on 1 Oct 2027, and that the executed order form governs.

Watch: the policy administration extract decides the first connector group and the date of a first view. Theo still owes the exit plan test evidence, the July outage note and the control mapping evidence.

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

Themes

Current to 9 Oct 26
Theme
Enterprise kickoff, broker firm view
Importance
renewal
Sentiment
mixed
Voice
decision-maker

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Niamh asks the policy administration team about the nightly extract and confirms the broker CRM admin; Ollie Pearson then gives a first view date.
  • Theo Gallagher confirms the exit plan test date with the platform team and sends it in writing by the end of that week.
  • Elena Novak brings an adoption plan to the first review and sends the written actions.

Risks

Current to 9 Oct 26
  • The policy administration extract is old, owned by a small team, and may not be reusable, which would lengthen the first connector group.
  • Low early usage could prompt a value question from finance, as Niamh said she would be asked what was paid for.
  • Exit plan test evidence, the July outage note and the control mapping evidence remain open for her CISO.

Opportunities

Current to 9 Oct 26
  • Broker distribution and customer service join once the firm view is trusted, which fills the 150 users the Enterprise licence includes.
  • A planned adoption plan and a fortnightly cadence give a route to show value before the first renewal.

Transcript

  1. Elena Novak
    Elena Novak None
    Hello, Niamh, can you hear us all right? I think we have a slight echo on our side.
  2. Niamh Costello
    Niamh Costello None
    I can hear you fine. Good afternoon, Elena. No echo here, it might be Theo's microphone.
  3. Theo Gallagher
    Theo Gallagher None
    Afternoon, both. Let me mute the laptop speakers, give me a second. Better?
  4. Elena Novak
    Elena Novak None
    Much better, thank you. Ollie, you are with us as well?
  5. Ollie Pearson
    Ollie Pearson None
    Here, sorry, I was finding the right window. Afternoon, Niamh, good to meet you properly. I've only seen your name on the paperwork until now.
  6. Niamh Costello
    Niamh Costello None
    Likewise. It's been a long road to get to this point, so I'm glad to be on a call that isn't a questionnaire.
  7. Theo Gallagher
    Theo Gallagher None
    Ha. Fair. We did send you quite a few of those.
  8. Elena Novak
    Elena Novak None
    Shall we begin? I sent the agenda by email this morning, but to confirm, there are five items. One, the outcome Ardcarne wants from the first ninety days, in Niamh's words. Two, the security handover from Theo, so that nothing from the review is lost. Three, the connectors and the order we bring them in. Four, users, access and who owns what on your side. Five, the cadence between us and the written actions. Is that acceptable, Niamh?
  9. Niamh Costello
    Niamh Costello None
    That's fine. Can I start with the outcome, since it frames everything else?
  10. Elena Novak
    Elena Novak None
    Please do.
  11. Niamh Costello
    Niamh Costello None
    So, the reason we bought this. Right now, if somebody in broker distribution asks how a particular broker firm is doing, and somebody in customer service asks the same question, they get two different answers, because they're each looking at their own system. What does good look like for the brokers? One view of each firm. Same answer for both teams, and an answer I could put in front of the regulator without apologising for it.
  12. Ollie Pearson
    Ollie Pearson None
    That's very clear. When you say one view of each firm, is the broker firm the unit, or do you also need to go down to individual brokers within a firm?
  13. Niamh Costello
    Niamh Costello None
    Firm first. Individuals later, maybe. Let's not over-engineer it. If we get the firm view right and trusted, that's a win for the first quarter.
  14. Ollie Pearson
    Ollie Pearson None
    Good, that makes the sequencing simpler. I'll come back to that in the connectors item.
  15. Elena Novak
    Elena Novak None
    To confirm what I have written: the first outcome is a single trusted view per broker firm, shared by broker distribution and customer service, with individual brokers out of scope for now. I will make sure that is the first line of the written actions.
  16. Niamh Costello
    Niamh Costello None
    Perfect.
  17. Elena Novak
    Elena Novak None
    Theo, if you would take item two.
  18. Theo Gallagher
    Theo Gallagher None
    Yes. I'll list the open items first, with owners, because that's how I like to run these. The review itself is closed and the order form is executed, so what I have is not blocking, it's follow-through. There are a few. One, the exit plan: you have the document, but you asked us to show it working rather than described, so we owe you evidence of a test of that plan. Owner is me, with the platform team for the technical side. Two, the post-incident note on the July outage. Your security team has the draft; I'd like to confirm the final wording against what they asked for. Owner is me again. Three, the control mapping against DORA: it's delivered, but there are a couple of control references where you wanted the evidence attached rather than linked. That's mine too, I'm afraid.
  19. Niamh Costello
    Niamh Costello None
    You say a few. Are any of those things that my CISO would regard as unresolved?
  20. Theo Gallagher
    Theo Gallagher None
    Not unresolved, no. Closed in principle, open in paperwork. I'd rather say that plainly than dress it up. The exit plan test is the one with real work in it.
  21. Niamh Costello
    Niamh Costello None
    Okay. I need him comfortable, and he was reasonable through the whole review, so I'd rather he heard it from you than from me. When can he see the test evidence?
  22. Theo Gallagher
    Theo Gallagher None
    Here is the dated commitment, but I have to be careful. The test depends on the platform team's calendar, and I don't want to give you a date I haven't checked with them. I'll ask them today and put a date in the written actions by end of this week.
  23. Niamh Costello
    Niamh Costello None
    That's acceptable. I'd rather have a date you've checked than a date you've guessed. I've had enough of the other kind.
  24. Theo Gallagher
    Theo Gallagher None
    Understood. And on the July outage, I'd say this for the record: the review ran through it, and you saw how we handled it, which I think is part of why you were comfortable signing. But the note needs to be final and not a draft, so I won't call it final until your security team has seen it.
  25. Niamh Costello
    Niamh Costello None
    Good. Don't call it final until they've said so.
  26. Elena Novak
    Elena Novak None
    Noted. Three items for Theo, each with an owner, and the exit plan date to be confirmed with the platform team before it is written down. Niamh, is there anything on the security side that you would like added?
  27. Niamh Costello
    Niamh Costello None
    One thing. Whoever on your side has access to our data inside the environment, I want that list. Not now, but as part of the early actions.
  28. Theo Gallagher
    Theo Gallagher None
    Yes. Because it runs inside your Snowflake account, you control the roles, and what we'd give you is the list of roles we ask for and why. Ollie will know which of those are needed for the build.
  29. Ollie Pearson
    Ollie Pearson None
    Right, yes. I'd keep it to the minimum for the build, and we widen it only if we have to, with your approval each time. I can send that role list as part of the plan.
  30. Niamh Costello
    Niamh Costello None
    Good.
  31. Elena Novak
    Elena Novak None
    Then item three. Ollie, please.
  32. Ollie Pearson
    Ollie Pearson None
    Sure. I'll share my screen, bear with me. Can you see the plan?
  33. Niamh Costello
    Niamh Costello None
    I can see a document. It's quite small.
  34. Ollie Pearson
    Ollie Pearson None
    Let me make it bigger. How's that?
  35. Niamh Costello
    Niamh Costello None
    Yes, that's fine.
  36. Ollie Pearson
    Ollie Pearson None
    So, Enterprise gives you up to twenty connectors, and the implementation is planned over twelve weeks. I would not use all twenty in the first wave. What I'd propose is three groups. The first is the sources that make the broker firm view, which is your broker CRM, the policy administration extract and the helpdesk your customer service team uses. The second group is the communication layer, calls and email, because that's where the context sits. The third is the finance and reference data, which can wait until the firm view is trusted.
  37. Niamh Costello
    Niamh Costello None
    That ordering makes sense to me. My worry is the policy administration extract. That system is old, and the team that looks after it is small.
  38. Ollie Pearson
    Ollie Pearson None
    That's useful to know. Is the extract something that already runs on a schedule, or would somebody have to build it?
  39. Niamh Costello
    Niamh Costello None
    It runs nightly for another purpose. I'd have to check whether we can point you at the same file.
  40. Ollie Pearson
    Ollie Pearson None
    That would be ideal, reusing a file that already exists and is already controlled. Could you ask that team? Then I'd know whether the first group is a couple of weeks or something longer.
  41. Niamh Costello
    Niamh Costello None
    I'll ask this week. I don't want that to be the thing that holds us up.
  42. Elena Novak
    Elena Novak None
    To confirm: Niamh will ask the team that owns the policy administration extract whether the existing nightly file can be used, and report back to Ollie. I will put that in the actions with her name beside it.
  43. Niamh Costello
    Niamh Costello None
    Yes, with my name.
  44. Ollie Pearson
    Ollie Pearson None
    One more thing on connectors, and it's from experience rather than anything specific to you. Sources change. A system gets upgraded, a field gets renamed, and a connector quietly stops loading. So I'd like us to agree early who on your side tells us when a source system is going to change.
  45. Niamh Costello
    Niamh Costello None
    That's a fair point and it's one we're not good at. Changes go through a change board, but the data office isn't always in the room.
  46. Elena Novak
    Elena Novak None
    Perhaps one of your team could be named as the contact for source changes, and we would add that to the agreed roles.
  47. Niamh Costello
    Niamh Costello None
    I'll name someone from my team. I'd rather it's one person with a deputy than a mailbox that nobody reads.
  48. Ollie Pearson
    Ollie Pearson None
    Perfect. A person with a deputy is exactly right.
  49. Theo Gallagher
    Theo Gallagher None
    Can I add something on the connector order, from the security side? If the helpdesk and the broker CRM both carry personal data, I'd like us to agree what is indexed and what is left out before the first load, not after.
  50. Niamh Costello
    Niamh Costello None
    Yes, absolutely. That's a conversation for me, my CISO and the privacy team, and I'd like it before anything loads. Can you send us the field list you'd expect to bring in?
  51. Ollie Pearson
    Ollie Pearson None
    I can. I'll draft it from the connector documentation, and your team can strike out whatever shouldn't come across.
  52. Niamh Costello
    Niamh Costello None
    Good. That's the right way round.
  53. Elena Novak
    Elena Novak None
    Now item four, users and access. Niamh, your licence is for one hundred and fifty users, and Enterprise includes single sign-on and SCIM. How do you see the rollout?
  54. Niamh Costello
    Niamh Costello None
    Small first. At the moment it's me and a couple of people from the data office, and that's deliberate. I don't want a hundred and fifty people logging in on day one to a thing that's half built. Broker distribution and customer service come in once the firm view is trusted.
  55. Elena Novak
    Elena Novak None
    That is sensible. I would only say that the licence is there when you need it, so there is no pressure from our side to fill it.
  56. Niamh Costello
    Niamh Costello None
    Good to hear, but I'd still like to see usage grow in a controlled way. If it sits at three people for six months, I'll be asked what we paid for.
  57. Elena Novak
    Elena Novak None
    Then perhaps we agree a simple adoption plan with your team leads, so that the growth is planned and not accidental. I would bring that to the first review.
  58. Niamh Costello
    Niamh Costello None
    Yes, please. And be honest with me. If it isn't being used, tell me early. I'd rather hear that from you.
  59. Elena Novak
    Elena Novak None
    I will make sure that you do.
  60. Theo Gallagher
    Theo Gallagher None
    On single sign-on, that's one for your identity team. Do you know who would configure it on your side?
  61. Niamh Costello
    Niamh Costello None
    A colleague in IT. I'll introduce them to you by email, so it's not me relaying messages.
  62. Theo Gallagher
    Theo Gallagher None
    That would be better. I'd want to see the sign-on set up before anyone beyond the core group gets access, so it's not something we retrofit.
  63. Niamh Costello
    Niamh Costello None
    Agreed.
  64. Ollie Pearson
    Ollie Pearson None
    Just to sanity check the timeline, because I know you'll ask. The contract started on 1 Oct 2026, so we're in the first week of a twelve week implementation. The first group of connectors is the critical path, and the policy administration question is the main unknown.
  65. Niamh Costello
    Niamh Costello None
    I never accept vague timelines, as Elena will tell you, so let me ask it directly. When do I see a first firm view, even a rough one?
  66. Ollie Pearson
    Ollie Pearson None
    Fair question. If the extract can be reused, I'd expect a rough view some weeks in, not at the end. But I won't put a date on it until I've heard from your policy administration team. I'll give you a real date as soon as I have that answer.
  67. Niamh Costello
    Niamh Costello None
    Okay. Then the extract is the thing to chase, and I'll do that tomorrow.
  68. Elena Novak
    Elena Novak None
    Thank you. I will record that Niamh owns the extract question, and that Ollie will give the first view date once it is answered.
  69. Niamh Costello
    Niamh Costello None
    May I ask one thing about the commercial side, so it's out of the way? The contract is for the year, with the annual fee of £125k, and it ends on 30 Sep 2027. I want to be clear what happens at the end, because finance will ask me.
  70. Elena Novak
    Elena Novak None
    Of course. To confirm, the annual subscription is £125,000, it is invoiced in line with the order form, and the term runs to 30 Sep 2027, with renewal on 1 Oct 2027. As your CSM, I would start the renewal conversation well ahead, and you would have our written notice of it, so there is no surprise. I would not expect you to have to chase us.
  71. Niamh Costello
    Niamh Costello None
    That's what I wanted to hear. I'll tell finance it's the order form that governs, and nothing else.
  72. Elena Novak
    Elena Novak None
    Yes, the executed order form governs. If anyone asks for something different, please send them to me.
  73. Theo Gallagher
    Theo Gallagher None
    While we're on governance, can I propose something small? A short written note every two weeks of the open security items, even if the list is empty. It costs me ten minutes and it means your CISO never has to ask.
  74. Niamh Costello
    Niamh Costello None
    I like that very much. Empty lists are underrated.
  75. Elena Novak
    Elena Novak None
    Then the cadence, item five. I would suggest a short call every two weeks during implementation, with me, Ollie and you, and Theo as needed. After go live we move to the regular reviews that come with Enterprise, and you will have an executive sponsor on our side. Does that suit you?
  76. Niamh Costello
    Niamh Costello None
    Every two weeks is right. Same slot if you can. Late afternoon suits me, like today.
  77. Elena Novak
    Elena Novak None
    I will send the invitations after this call, same time of day.
  78. Ollie Pearson
    Ollie Pearson None
    Before we finish, can I check one assumption? I've been planning on the basis that the broker CRM admin is available for the first connector. If that person is on leave or busy, I'd want to know now.
  79. Niamh Costello
    Niamh Costello None
    I believe so, but I'll confirm. Put it on my list with the extract.
  80. Ollie Pearson
    Ollie Pearson None
    Will do. Two items for you then, and I'll keep them short so they don't get lost.
  81. Niamh Costello
    Niamh Costello None
    Can I say one more thing, more general? I was nervous about this one, honestly. The review took a long time and it ran through the outage, and there were days I wondered whether we'd get here. I'm glad we did, but I'll be watching the first weeks closely.
  82. Theo Gallagher
    Theo Gallagher None
    That's reasonable, and I'd expect nothing less. We'd rather you watched closely and saw us do what we said.
  83. Elena Novak
    Elena Novak None
    I agree. We will tell you early if anything slips, and in writing.
  84. Niamh Costello
    Niamh Costello None
    That's all I ask.
  85. Elena Novak
    Elena Novak None
    Let me read back the actions, so we are agreed before I write them up. One, Theo: confirm a date for the exit plan test with the platform team, and send it in writing by end of this week. Two, Theo: final wording on the July outage note, once your security team has reviewed it, and the control mapping evidence attached. Three, Ollie: the role list and the field list, for your approval before any load. Four, Niamh: ask the policy administration team about the nightly extract, confirm the broker CRM admin, name a contact and deputy for source changes, and introduce your colleague in IT for single sign-on. Five, me: the invitations, the adoption plan for the first review, and these actions in writing today. Have I missed anything?
  86. Niamh Costello
    Niamh Costello None
    No, that's everything. Thank you, Elena, that was well run.
  87. Ollie Pearson
    Ollie Pearson None
    That's all of mine. I'll get the role list over by tomorrow.
  88. Theo Gallagher
    Theo Gallagher None
    Mine will follow by the end of the week, once I've spoken to the platform team. Thanks, everyone.
  89. Niamh Costello
    Niamh Costello None
    Right, I'll let you go. Talk to you in a fortnight. Best of luck with the extract question, or rather, best of luck to me.
  90. Elena Novak
    Elena Novak None
    Thank you, Niamh. Kind regards to your team. Goodbye for now.
  91. Niamh Costello
    Niamh Costello 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
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