Lewis Kerr

Clonvara Insurance Services / BB-Demo – Discovery

Callcompleted

Clonvara Insurance Services: documents logo Clonvara Insurance Services: documents · 2025-08-07 09:15

Siobhán Dunne and Brendan Moran described broker, policy and claims data split across three systems. Lewis Kerr pointed to the Growth tier and gave an indicative £53,800 working figure. A demo on Clonvara's own sample data was agreed as the next step.

What was said

What this says

Current to 11 Oct 26

Siobhán Dunne and Brendan Moran described broker, policy and claims data split across three systems. Lewis Kerr pointed to the Growth tier and gave an indicative £53,800 working figure. A demo on Clonvara's own sample data was agreed as the next step.

What happened: Lewis Kerr ran a listening-led discovery call. Siobhán described three disconnected systems, stitched together mostly by her team in the evenings.

Customer view: Brendan wants brokers served well and a controlled answer when the regulator asks how Clonvara knows what it knows. Siobhán asked to keep the brokers first, because if they do not feel it nobody uses it.

Commercial: Lewis placed the need at Growth, since several teams are involved but not the whole company. He gave a working figure of £53,800 including implementation and before VAT, which Brendan accepted as indicative only.

Watch: Brendan asked twice about pricing version and data location, and wants the data-location answer in writing. He does not want to be rushed to a decision.

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

Themes

Current to 9 Oct 26
Theme
Discovery, broker data consolidation
Importance
neutral
Sentiment
positive
Voice
decision-maker

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Lewis Kerr sends a short summary of the call and a written note on where the data lives.
  • Lewis and the BB-Demo solutions engineer set up a demo on Clonvara's sample data with Siobhán, her data engineer and Cian.
  • Lewis aims to send an itemised, dated proposal by 12 Aug 2025 if the demo goes well.

Risks

Current to 9 Oct 26
  • Brendan Moran does not want to be rushed to a decision for anyone's quarter end.
  • The £53,800 figure is only an indicative working figure, not a proposal, and pricing version was a stated concern.
  • The compliance questions on where the data sits and on security review must be answered carefully and in writing.

Opportunities

Current to 9 Oct 26
  • Growth tier fits several teams: analytics, underwriters, broker managers and claims.
  • Clonvara already has a Snowflake account, which suits a brain built inside the customer's own account.

Transcript

  1. Lewis Kerr
    Lewis Kerr None
    Good morning, Siobhán, good morning Brendan. Can you both hear me?
  2. Siobhán Dunne
    Siobhán Dunne None
    Morning, Lewis. Loud and clear. Brendan, you're on mute, I think.
  3. Brendan Moran
    Brendan Moran None
    Apologies. Good morning, both. Can you hear me now?
  4. Lewis Kerr
    Lewis Kerr None
    Yes, perfect. Thanks for making the time, I know it's a busy week. Siobhán, you mentioned Dublin is still half on holiday.
  5. Siobhán Dunne
    Siobhán Dunne None
    Half the city and most of the brokers, grand. So the quiet is welcome, honestly.
  6. Lewis Kerr
    Lewis Kerr None
    Good. So what I'd like to do today is mostly listen. I want to understand what you're trying to see, where it lives at the moment, and what a good outcome looks like. Then I can tell you honestly whether we're a fit, and what the next step would be. Does that work?
  7. Brendan Moran
    Brendan Moran None
    That works well. I would only add that from a compliance point of view I will want to understand where the data sits, but perhaps that comes later.
  8. Lewis Kerr
    Lewis Kerr None
    It comes in a moment, actually, because it's a good place to start. Short version, the brain is built and runs inside your own Snowflake account. Your data doesn't go to us. I'll have our solutions engineer take you through that properly, but I wanted you to hear it first.
  9. Brendan Moran
    Brendan Moran None
    That is helpful. Thank you. Please do put that in writing at some stage.
  10. Lewis Kerr
    Lewis Kerr None
    Will do. Siobhán, can I start with you? What's the problem you're trying to fix?
  11. Siobhán Dunne
    Siobhán Dunne None
    Grand, so. We have broker activity in one place, policy queries in another, and claims tickets in a third. Each of them is fine on its own. But when a broker rings and says, you've had three queries from me this month and a claim that's been sitting, nobody on my side can answer without opening three systems and a spreadsheet.
  12. Lewis Kerr
    Lewis Kerr None
    And who's doing that stitching at the moment?
  13. Siobhán Dunne
    Siobhán Dunne None
    Mostly my team, and mostly in the evenings, if I'm honest. I've a data engineer who's brilliant but she's one person. And then the underwriters do their own version of it, which is where it gets messy. What's the source of truth? Depends who you ask.
  14. Lewis Kerr
    Lewis Kerr None
    That's a familiar one. What do the systems look like? Without going into detail, what's the CRM, what's the helpdesk, where do documents live?
  15. Siobhán Dunne
    Siobhán Dunne None
    There's a CRM for the brokers, a helpdesk for the claims tickets, and the policy side is partly a core system and partly files. Microsoft 365 for the documents. And we've a Snowflake account already, which is part of why this came up.
  16. Lewis Kerr
    Lewis Kerr None
    Good, that makes it simpler. Brendan, from your side, what would make this worth doing?
  17. Brendan Moran
    Brendan Moran None
    I think there are two things. The first is that the brokers are served well, and I can show that. The second is that when the regulator asks how we know what we know, the answer is a controlled one and not somebody's spreadsheet. Both of those matter, frankly, more than saving a few hours.
  18. Siobhán Dunne
    Siobhán Dunne None
    Let's keep the brokers front and centre, though. The regulator point is real, but if the brokers don't feel it, nobody uses it.
  19. Brendan Moran
    Brendan Moran None
    Agreed. Fair challenge.
  20. Lewis Kerr
    Lewis Kerr None
    That's useful, because it tells me what to show you. Can I ask how many people you'd imagine using this in the first instance?
  21. Siobhán Dunne
    Siobhán Dunne None
    Starting? The analytics team, a few of the underwriters, the broker managers and a couple of people from claims. Not the whole company. Not yet.
  22. Lewis Kerr
    Lewis Kerr None
    Several teams, but not everyone. That sounds like our Growth tier to me, rather than anything bigger. I wouldn't want to push you onto more than the usage supports.
  23. Brendan Moran
    Brendan Moran None
    Which version of the pricing are we looking at, if I may? I would like to be careful about that from the beginning.
  24. Lewis Kerr
    Lewis Kerr None
    Fair. I'd rather not hold you to a number today, because we haven't scoped it. The working figure on my sheet for Growth is £53,800 as a total, implementation included, and that's before VAT. When I send a proposal it will be itemised and dated, so you'll know exactly which version it is.
  25. Brendan Moran
    Brendan Moran None
    Thank you. That is in the range I had assumed. Let us treat it as indicative.
  26. Siobhán Dunne
    Siobhán Dunne None
    Can I ask something about the implementation? How long before we see anything? Because I've been burned on that before.
  27. Lewis Kerr
    Lewis Kerr None
    Honest answer, for Growth it's around eight weeks from start to being properly live. But what you'd see first is your own data in a demo well before that. That's the next step I'd propose, a demo on your own sample data rather than ours.
  28. Siobhán Dunne
    Siobhán Dunne None
    I'd like that. My data engineer will want to be on it, and one of the underwriters. Cian, probably. He asks the awkward questions.
  29. Lewis Kerr
    Lewis Kerr None
    Awkward questions are the best kind. I'll bring Hannah, our solutions engineer, she'll handle the technical side and the security questions.
  30. Brendan Moran
    Brendan Moran None
    And the security review, will that be needed?
  31. Lewis Kerr
    Lewis Kerr None
    Hannah will tell you exactly what we do and don't cover and I'll leave the detail to her. She won't overstate anything, that's one thing I can promise.
  32. Brendan Moran
    Brendan Moran None
    Good. That is how I would prefer it.
  33. Lewis Kerr
    Lewis Kerr None
    So to put a number on the timing, I'd like to be in a position to send you a proposal by 12 Aug 2025, if the demo goes the way we hope. Is that sensible, or too quick?
  34. Siobhán Dunne
    Siobhán Dunne None
    That's tight, with the holidays. But if the demo is in the next couple of weeks, it's doable.
  35. Brendan Moran
    Brendan Moran None
    I would not want to be rushed to a decision for anyone's quarter end, but a proposal to read is perfectly reasonable.
  36. Lewis Kerr
    Lewis Kerr None
    Understood, and no one's pushing you. Let me recap. I send a short summary of today and the note about where the data lives. Hannah and I set up a demo on your sample data with Siobhán, her engineer and Cian. And we look at a proposal after that.
  37. Siobhán Dunne
    Siobhán Dunne None
    Grand. I'll find a couple of dates and send them over, and I'll sort out the sample data this week.
  38. Lewis Kerr
    Lewis Kerr None
    Perfect. Thanks, both. I'll send that over today.
  39. Brendan Moran
    Brendan Moran None
    Thank you, Lewis. Goodbye for now.
  40. Siobhán Dunne
    Siobhán Dunne None
    Thanks a million, Lewis. Talk soon.

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
Organisations75
People at customers290
BB-Demo staff40
Calls784
Email threads1,169
Support tickets449
Documents477
Deals117
Invoices101
Events49
News items56

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.

Ask B

Ask B

B-Brain · read-only