Halberd Point Insurance / BB-Demo – Demo
Callcompleted
Halberd Point Insurance: documents · 2026-09-07 15:30
Andre Holloway, Director of Data and Analytics, saw a demo on sample data and called it better than expected. He wants a security review before committing and will take it to Maria and the team.
What was said
What this says
Current to 11 Oct 26Andre Holloway, Director of Data and Analytics, saw a demo on sample data and called it better than expected. He wants a security review before committing and will take it to Maria and the team.
What happened: The 7 Sep 2026 demo ran on sample data from CRM, claims and Xero. Andre's key use case is joining claims and underwriting, today a day-long manual pull from two systems.
Customer view: Andre asked about access controls, dashboards and who manages connectors. He reacted well, then asked to see real claims data.
Commercial: BB-Demo pitched Enterprise: twelve weeks including security review, Premium support and a Sandbox first. The next step is a security questionnaire, then proposal and contract.
Watch: Maria's role and the buying decision are not shown in the call. Hannah Lowe owes a technical spec and questionnaire, and the evidence does not show a price or date.
Themes
Current to 9 Oct 26Theme
Enterprise demo, security review
Importance
upsell
Sentiment
positive
Voice
champion
Who was there
BB-Demo
CRMmade from
Them
CRMmade from
Follow-up
Next steps
Current to 9 Oct 26- Hannah Lowe to send the technical spec and security questionnaire this week.
- Jordan Pike to move to proposal and contract once security is satisfied.
Risks
Current to 9 Oct 26- A security review is a gate before any proposal, and Maria's role in the decision is not shown.
- Andre wants to see real claims data, but only sample data was used in the demo.
Opportunities
Current to 9 Oct 26- Enterprise fit: cross-system claims and underwriting questions, role-based access and Premium support.
- Sandbox on real systems could let Andre and his security team test before go-live.
Transcript
Hannah Lowe NoneHi Andre. Before we dive into the demo, what's the highest-value question you'd like the brain to answer for you? What would change your business if you could ask it right now?
Andre Holloway NoneGood question. So, I mean, we process claims and underwrite policies, and the two don't talk. If I could ask the brain, 'Show me policies that have had claims filed, and group them by risk profile and total payouts,' that would be huge. Right now that's a manual pull from two systems, takes someone a day.- Hannah Lowe NonePerfect. That's exactly the use case we see. So here's what I've set up: we've connected to your Snowflake and pulled in sample data from your CRM, your claims system, and Xero. I'm going to ask the brain your question.
- Andre Holloway NoneYep.
- Hannah Lowe NoneOkay, so the query is running. And, there. Policies with claims, grouped by risk profile, total payouts by profile, and, this is the kicker, a list of which underwriter touched each policy. So you can see who's booking the risky business, who's not. That's a thirty-second query. To be precise, the brain is doing a join across three different systems, aggregating, and running a calculation, all live.
- Andre Holloway NoneWow. So if I wanted to drill into one of these risk profiles, say the high-risk ones, what can I do?
- Hannah Lowe NoneYou can ask follow-up questions: Which of these policies are up for renewal? What was the average time to claim? Is there a pattern? The short answer is that you can explore the data the way a human would. The longer answer is that we've built this so that you don't have to learn a query language, you just ask the brain in English.
- Andre Holloway NoneAnd this is all secure? I mean, access controls, who sees what?
- Hannah Lowe NoneYes. So the brain has role-based access built in. We'll work with you to define roles: underwriter, claims manager, finance, whatever, and we'll lock down which data each role can see. So an underwriter might see policies but not claims payout data, for instance. And because the brain runs inside your Snowflake account, the underlying data security is entirely yours. To be precise, we're not storing or copying your data, it all lives in your account.
- Andre Holloway NoneOkay, that's... that makes me feel better. What about dashboards? Can I build dashboards from this?
- Hannah Lowe NoneYou can. So you can either ask the brain questions one-off, in chat, or you can build a dashboard that runs the same query every day or every week and shows you the results. Underwriters love this: they've got a KPI dashboard for their book of business, it updates automatically, they're not waiting on anyone.
Jordan Pike NoneAnd all of that is backed by Premium support on Enterprise: named engineer, thirty-minute first response, and data freshness SLA.- Hannah Lowe NoneRight. So I'll walk you through the technical architecture now. We've got connectors here, think of these as data pipelines from your three systems into the brain. The brain is a semantic layer on top of your Snowflake, and then the interface: chat, dashboards, search, is what your teams use. The refresh happens every night, complete by seven in the morning your time.
- Andre Holloway NoneAnd you manage all of this? The connectors, the refresh, everything?
- Hannah Lowe NoneYes. Our team owns the pipeline. If your claims system updates something and breaks a connector, we fix it. You just focus on asking questions and using the data. I'll put together a full technical spec doc and send it over: shows the architecture, the security controls, the SLA commitments, the whole thing.
- Andre Holloway NoneThis is, honestly, this is better than I expected. Can we demo this on our actual data? Like, with real claims data?
- Hannah Lowe NoneGood question. So what we've done here is sample data for the demo. For the actual implementation, we'll work with your data team, we'll set up the connectors on your real systems, and we'll do the whole thing in a Sandbox environment first: so you can test, your security team can review, all of that, before we flip the switch and go live.
- Andre Holloway NoneOkay. And how long is the implementation again?
- Hannah Lowe NoneTwelve weeks for Enterprise. That includes the security review: we'll work with your security team: building the connectors, configuring the access controls, training your people, and going live.
- Jordan Pike NoneAnd once you're live, we do quarterly business reviews with you, we talk about value, we talk about new use cases, and you've got us to lean on if you want to add more connectors or users.
- Andre Holloway NoneAlright. I think the next step is we take this to Maria and the team, and we probably want to do a security review before we commit. Can you do that?
- Hannah Lowe NoneAbsolutely. I'll prepare a security questionnaire: we'll walk through your controls, your data handling, all of it. That's part of the Enterprise process anyway.
- Jordan Pike NoneAnd then once you're happy with the security, we'll move into proposal and contract. Sound good?
- Andre Holloway NoneYeah, that works. Thanks, both.
- Hannah Lowe NoneThanks, Andre. I'll send that technical spec and the security questionnaire over this week. Cheers.
- Jordan Pike NoneSpeak soon.
Callsmade from