Lewis Kerr

Clonvara Insurance Services / BB-Demo – Demo

Callcompleted

Clonvara Insurance Services: documents logo Clonvara Insurance Services: documents · 2025-09-02 13:00

Second demo, 2 Sep 2025. Siobhán Dunne wants broker dashboards and a clear view of connector effort. She wants Brendan to see a written proposal and says budget is his call, with a decision date of 26 Sep 2025.

What was said

What this says

Current to 11 Oct 26

Second demo, 2 Sep 2025. Siobhán Dunne wants broker dashboards and a clear view of connector effort. She wants Brendan to see a written proposal and says budget is his call, with a decision date of 26 Sep 2025.

What happened: Hannah Lowe walked through connectors, then built a three-tile broker dashboard live. Siobhán asked for the claims view to be split by handler.

Customer view: She is comfortable with Growth limits, forty users and eight connectors, and expects four or five connectors at the start. She would keep dashboard builder rights to herself and her engineer.

Commercial: She likes the product but is not committing budget. Brendan holds that decision and has not yet seen the demo.

Watch: Three data fields need confirming on the customer side: first response, handler and broker naming. The first response field is already known to have two processes writing to it.

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

Themes

Current to 9 Oct 26
Theme
Growth tier demo
Importance
upsell
Sentiment
positive
Voice
champion

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Lewis Kerr to send the written proposal and book a session with Brendan around 10 Sep 2025.
  • Hannah Lowe to send the connector list and the three data fields to confirm on the day of the call.

Risks

Current to 9 Oct 26
  • Budget sits with Brendan, who had not yet seen the product.
  • Inconsistent source fields such as first response and handler could slow implementation.

Opportunities

Current to 9 Oct 26
  • Growth subscription with the dashboards builder for broker managers.
  • Room to add connectors later within the eight included.

Transcript

  1. Lewis Kerr
    Lewis Kerr None
    Good afternoon, Siobhán. Hannah's here too. Can you hear us?
  2. Siobhán Dunne
    Siobhán Dunne None
    Afternoon, both. Yes, loud and clear. Sorry, I'm eating a sandwich at my desk, I've had back to back since nine.
  3. Hannah Lowe
    Hannah Lowe None
    Don't mind us. Siobhán, as it's the second demo, what do you most need to leave with today?
  4. Siobhán Dunne
    Siobhán Dunne None
    Dashboards, for the broker managers. And connectors. How does it actually get the data out of our systems and how much work is that for my engineer? She's asked me about nothing else all week.
  5. Hannah Lowe
    Hannah Lowe None
    Good, then I'll start with connectors and finish with dashboards. Sharing my screen. This is the connector page. Each source is a connector: the CRM, the helpdesk, the document store. You switch each one on, give it read access, and choose what it should pull.
  6. Siobhán Dunne
    Siobhán Dunne None
    Read access only?
  7. Hannah Lowe
    Hannah Lowe None
    Read only. It never writes back to the source. I'll put that in writing, because I know your compliance people will ask.
  8. Siobhán Dunne
    Siobhán Dunne None
    Brendan will. He keeps a folder of every version of everything.
  9. Lewis Kerr
    Lewis Kerr None
    Which is why I like working with him, to be honest. Nothing gets lost.
  10. Hannah Lowe
    Hannah Lowe None
    So for you on Growth, you'd have up to eight connectors. From what you've described, you'd probably need around four or five to begin with. That leaves room if you add something later.
  11. Siobhán Dunne
    Siobhán Dunne None
    So we'd not be bumping into a limit straight away.
  12. Hannah Lowe
    Hannah Lowe None
    No. The connector limit is a hard one, so it's worth planning, but you've comfortable headroom. The user limit is softer, and for Growth it's forty.
  13. Siobhán Dunne
    Siobhán Dunne None
    Forty's fine to start. We'd be nowhere near that for a while.
  14. Hannah Lowe
    Hannah Lowe None
    Good. Now, how long does it take? The short answer is the first connector can be live quickly. The longer answer is that the time goes on agreeing what to pull and cleaning the awkward fields, like the one we found last time.
  15. Siobhán Dunne
    Siobhán Dunne None
    The first response field. Yes. My engineer's been looking at it. It's down to two different processes writing to it, it turns out. So we'll tidy that regardless.
  16. Hannah Lowe
    Hannah Lowe None
    That's very helpful, and honestly that's what implementation is mostly about. Not the plumbing, the agreement on what the data means.
  17. Siobhán Dunne
    Siobhán Dunne None
    Right. Let's do dashboards, then, because I've been looking forward to those.
  18. Hannah Lowe
    Hannah Lowe None
    Dashboards builder. It's one of the things Growth adds over Starter. I'll build one live. Siobhán, tell me what a broker manager would want to see when they open it on a Monday.
  19. Siobhán Dunne
    Siobhán Dunne None
    Their top brokers by activity, any claims that have been sitting, and queries that haven't had an answer. Three things. Let's keep the brokers front and centre.
  20. Hannah Lowe
    Hannah Lowe None
    Three tiles, then. First, brokers by activity. I choose the source, group by broker, and there it is. Second, the claims tickets open for longer than a set number of days, which you choose. Third, policy queries with no reply.
  21. Siobhán Dunne
    Siobhán Dunne None
    That's quick. And can the manager change the filter themselves? Or does it come back to me?
  22. Hannah Lowe
    Hannah Lowe None
    They can change filters on their own view without touching the dashboard itself. Only people you give builder rights to can change the dashboard. You decide who.
  23. Siobhán Dunne
    Siobhán Dunne None
    Good. I'd keep that to me and my engineer at the start.
  24. Lewis Kerr
    Lewis Kerr None
    That's sensible. Siobhán, if I can come in briefly, is there anything you've seen so far that you'd want changed?
  25. Siobhán Dunne
    Siobhán Dunne None
    Honestly, the thing I'd want is the claims view split by who's handling it, not just the broker. Is that possible?
  26. Hannah Lowe
    Hannah Lowe None
    If the handler is a field in the helpdesk, yes. If it's in someone's head, no. Do you know?
  27. Siobhán Dunne
    Siobhán Dunne None
    It's a field. I'll check it's filled in consistently, mind. Which, after the last one, I shouldn't assume.
  28. Hannah Lowe
    Hannah Lowe None
    Ha. Fair. I'll add it to the list of fields to confirm. Let me recap what we have to check on your side: first response, handler, and broker naming. Three things.
  29. Siobhán Dunne
    Siobhán Dunne None
    Three things. Got it.
  30. Lewis Kerr
    Lewis Kerr None
    Siobhán, from a timing point of view, where does this leave us? I'd like to confirm the plan rather than assume it.
  31. Siobhán Dunne
    Siobhán Dunne None
    I think I want Brendan to see this, then a proposal in writing. I'm not committing budget, that's his call, but I'm happy to say I'd like it.
  32. Lewis Kerr
    Lewis Kerr None
    Understood. So I'll send the proposal, and we'd book it in with Brendan around 10 Sep 2025 so that everyone's had time to read it. The date I'm working to for a decision is 26 Sep 2025, and I'd rather it was comfortable than rushed.
  33. Siobhán Dunne
    Siobhán Dunne None
    That's fine. I'll tell him to put it in his diary.
  34. Hannah Lowe
    Hannah Lowe None
    I'll send the connector list and the three data fields in writing today, so your engineer has them. Anything else?
  35. Siobhán Dunne
    Siobhán Dunne None
    No, that was grand. Thanks a million, both.
  36. Lewis Kerr
    Lewis Kerr None
    Thanks, Siobhán. Speak 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
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.

HelpAsk B

Ask B

B-Brain · read-only