What was said
What this says
Current to 11 Oct 26Demo for Clonvara Insurance Services on a sample extract. Siobhán Dunne and Cian Farrell liked the one-click source trail and honest uncertainty. They asked for a longer second demo covering dashboards and connectors.
What happened: Hannah Lowe demoed search and chat on a sample extract with sensitive fields removed. Siobhán asked whether underwriters can trust the answers and Cian asked for answers with their source.
Customer view: Siobhán liked that the brain flags uncertainty and does not correct source records. She said the open-claims-by-broker view would save her an evening a week.
Commercial: Siobhán asked for a longer second demo covering dashboards and connectors, and wants Brendan to see the broker view. Lewis Kerr tied this to 26 Sep 2025 as the point for a proposal decision.
Watch: Cian wants the policy side as strong as the claims side. The first-response field in the sample is inconsistent, which is a data point for the customer's data engineer.
Themes
Current to 9 Oct 26Who was there
BB-Demo
Them
Follow-up
Next steps
Current to 9 Oct 26- Hannah Lowe to send a note on what was covered and the open points on data fields.
- Lewis Kerr to suggest a date for the longer second demo with Brendan invited.
- Lewis Kerr to work towards a proposal decision by 2025-09-26.
Risks
Current to 9 Oct 26- Cian wants the policy side as strong as the claims side and may be unconvinced until he sees it.
- The first-response field in the sample is inconsistent, which could weaken answers on policy queries.
Opportunities
Current to 9 Oct 26- A longer second demo on dashboards and connectors, with Brendan seeing the broker view, moves the deal towards a proposal.
- A saved open-claims-by-broker view gives broker managers a concrete early use.
Transcript
- Lewis Kerr NoneGood morning, everyone. Siobhán, Cian, welcome. Hannah's with me, she'll drive the demo.
- Siobhán Dunne NoneMorning, Lewis. Hi, Hannah. Cian's just sitting down, he's had a morning.
- Cian Farrell NoneMorning. Sorry, I'm here. Can you hear me? I think my headset is doing something odd.
- Hannah Lowe NoneWe can hear you fine, Cian. Thanks for joining. Before I share anything, can I ask what you most need to know today? I'd rather aim at that than walk you through every page.
- Siobhán Dunne NoneSo, two things. Can it see the broker activity, the policy queries and the claims tickets together, on a single broker. And can the underwriters trust what it says. What's the source of truth?
- Cian Farrell NoneFrom my side, I want to know if it can answer the kind of question I get asked, like which brokers have had repeated queries on the same policy type. And whether I can see where the answer came from.
- Hannah Lowe NoneGood, that gives me a clear aim. I'll share my screen now. What you're seeing is a brain built on a sample extract you sent us, sitting in a Snowflake account set up for this demo. Same shape as it would be in yours.
- Siobhán Dunne NoneIs that our real data?
- Hannah Lowe NoneTo be precise, it's the sample extract you gave us, with the fields you flagged as sensitive removed. So it's your structure and your kind of records, but not live production data.
- Siobhán Dunne NoneGood, that's what I wanted to hear.
- Hannah Lowe NoneRight. Let me start with search, because it's the simplest. I'll type a broker's name. And what comes back is one page: the CRM activity, the policy queries and the claims tickets, in order, with the source named next to each line.
- Cian Farrell NoneMm. So that line there, that's from the helpdesk?
- Hannah Lowe NoneYes. And if you click on it, it opens the original ticket. That's the answer to where did it come from, it's always one click back to the record.
- Cian Farrell NoneOkay. That's better than what I have now, which is a screenshot somebody sent me.
- Lewis Kerr NoneHa. That's the sort of thing we hear a lot.
- Hannah Lowe NoneNow the chat. Cian, you tell me a question and I'll type it exactly as you say it.
- Cian Farrell NoneWhich brokers have raised more than one query on the same policy type in the last quarter?
- Hannah Lowe NoneTyping that. It takes a few seconds. There. It's given a short list, and underneath each name the queries it counted. And it's also saying what it's not sure about, here, where two records might be the same broker spelled differently.
- Siobhán Dunne NoneOh, that's honest. I like that it flags it. Last tool we looked at just gave an answer with total confidence.
- Hannah Lowe NoneThe short answer is it will be wrong sometimes, like any tool. The longer answer is that it shows its working, so you can see when to challenge it. I'd rather you knew that now.
- Cian Farrell NoneWhat about if the underlying record is wrong? Say the underwriter keyed the policy type incorrectly.
- Hannah Lowe NoneThen the brain reflects what's in the source. It doesn't fix it, it surfaces it. But because you can see both records side by side, it's usually quicker to spot the discrepancy than before. Fixing the source stays with you.
- Siobhán Dunne NoneAnd that's the right way round, to be honest. I wouldn't want a tool quietly correcting our records.
- Lewis Kerr NoneSiobhán, can I ask, does the claims ticket view cover what you were hoping for?
- Siobhán Dunne NoneNearly. Hannah, could you filter the claims tickets by how long they've been open, per broker? That's what the broker managers keep asking for.
- Hannah Lowe NoneYes. Let me do that. I'll ask it in plain words. Show me open claims tickets for this broker, oldest first. And there it is, with the age beside each one. I can save that as a view so the broker managers have it ready.
- Siobhán Dunne NoneThat would save me an evening a week, I'd say. Cian, you agree?
- Cian Farrell NoneFor the broker managers, yes. For me, I'd want the policy side as strong as the claims side. Can we look at that before the end?
- Hannah Lowe NoneAbsolutely. Give me a minute to switch to the policy view. Lewis, anything you want to say while I load that?
- Lewis Kerr NoneOnly that this is the sample, and what you'd get in the real thing is built on your actual sources, in your account. Hannah will say how connectors work in the follow-up call.
- Hannah Lowe NoneRight, policy view. Same search, but this time the policy queries lead. Cian, ask me something.
- Cian Farrell NoneShow me policy queries where the broker came back within a week of the first response.
- Hannah Lowe NoneThat's a good one. Typing it. Hmm, it's asking me to clarify what counts as the first response. That's a fair question, because in your sample the field isn't consistent. So that's a real data point for you, not a limitation of the tool.
- Siobhán Dunne NoneThat's one for my data engineer. Noted. Honestly that's useful in itself.
- Cian Farrell NoneAgreed, I didn't know that field was patchy.
- Hannah Lowe NoneI'll write that up in the follow-up so it's not lost. Anything else you want to try in the time we have left?
- Siobhán Dunne NoneCan we do a second demo, a longer one, where we go into dashboards and how the connectors would work? And maybe I'd like Brendan to see the broker view.
- Lewis Kerr NoneYes. Let's do that. I'll suggest a date in the coming weeks and keep 26 Sep 2025 in mind as the point we'd want a proposal decision by, so you're not rushed but we've a shape to work to.
- Siobhán Dunne NoneGrand. That works for me.
- Hannah Lowe NoneI'll send a short note on what we covered and the open points on the data fields. Thanks, all.
- Cian Farrell NoneThanks. That was more useful than I expected.
- Lewis Kerr NoneThanks, everyone. I'll send that over today. Speak soon.