What was said
What this says
As at Fri 9 Oct 2026On 9 Jul 2026 Andre Holloway and CFO Maria Coleman described siloed data and manual reconciliation across underwriting, claims and finance. Jordan Pike positioned Enterprise and agreed to set up a demo on their data.
What happened: Halberd Point described separate systems for underwriting, claims and accounting that do not talk to each other. Jordan proposed Enterprise: twelve weeks, SSO, SCIM, a full security review and a first year of a hundred and fifty-five thousand.
Customer view: Maria raised security and service levels as a regulated insurer. Andre said it sounded like it could really help.
Commercial: Jordan set out the thirty-minute first response, the named engineer and freshness credits. A demo with IT and possibly an underwriting lead was agreed.
Watch: Andre preferred early September, Jordan had suggested mid-September. The evidence does not show whether the demo took place.
Themes
As at Fri 9 Oct 2026Who was there
BG-Demo
Them
Follow-up
Next steps
As at Fri 9 Oct 2026- Jordan Pike to send demo options and the invite, with IT and an underwriting lead invited.
- Andre Holloway to confirm the demo attendees from Halberd Point.
- Jordan Pike to confirm whether the demo on Halberd Point's own data was held and agree scope and kick-off.
Risks
As at Fri 9 Oct 2026- As a regulated insurer, Halberd Point will test security controls, and the security review sits inside the Enterprise implementation.
- The demo timing was not firmly fixed, and the evidence does not show whether it happened.
Opportunities
As at Fri 9 Oct 2026- Several teams across underwriting, claims and finance fit the Enterprise tier with SSO and SCIM.
- The CFO's interest in freshness credits and a thirty-minute first response gives a value case built on service levels.
Transcript
- Jordan PikeHey Andre, Maria, thanks for jumping on. So we've got about thirty minutes, and I want to get a sense of what you're trying to solve, what's breaking right now, and whether the brain is the right fit for you. Sound okay?
- Andre HollowayYeah, absolutely. So we're Halberd Point, specialty commercial insurance, and we've got a real challenge. We've got underwriters, claims people, finance, all with their own systems. Data is siloed. When we need to answer a question about a risk or a claim, it takes forever to pull it together.
- Maria ColemanAnd from a finance perspective, it's the same: we can't reconcile the numbers across our CRM, our claims system, our accounting system, without a lot of manual work. It's a risk, it's expensive, and it's slow.
- Jordan PikeOkay, so you've got multiple teams, regulated environment, that rings Enterprise for me. Let me ask: what systems are you running right now?
- Andre HollowaySo we've got a CRM for underwriting and sales, we've got a claims management system, we've got Xero for accounting, and we're running all of it. I mean, we've got reporting tools, but they don't talk to each other.
- Jordan PikeRight. So the brain would sit inside your Snowflake, do you guys use Snowflake?
- Andre HollowayWe do, yeah. We've got data engineers on staff.
- Jordan PikePerfect. So the brain runs inside your account, we build connectors from your CRM, the claims system, Xero, and you get a query layer where anyone in the company can ask questions without having to know SQL or rely on the data team to run reports.
- Maria ColemanWhat about security? I mean, we're regulated, we're talking about insurance claims and customer data. What controls do you have?
- Jordan PikeSo that's exactly why Enterprise exists. You get SSO, SCIM for user management, role-based access controls, you can lock down who sees what. And because it's inside your Snowflake, you control the underlying data security too. We do a full security review as part of the Enterprise implementation.
- Andre HollowayHow long is the implementation?
- Jordan PikeFor Enterprise, it's twelve weeks. That includes the security review, building all the connectors, getting your team trained and live.
- Maria ColemanAnd the investment?
- Jordan PikeSo there's an implementation fee for the twelve weeks, that's fixed, and then an annual subscription for the platform. All in, first year would be a hundred and fifty-five thousand. We can break down the details when you're ready.
- Maria ColemanOkay. And the ongoing service level? If something breaks, how fast do you respond?
- Jordan PikeEnterprise gets a thirty-minute first response time for critical issues, and we've got a named engineer assigned to your account. Plus, we keep your data fresh every night, refresh complete by seven in the morning your time. You're also in scope for the freshness SLA, so if the data isn't fresh, you get service credits.
- Andre HollowayThis is– this sounds like it could really help us. What's the next step?
- Jordan PikeSo the next step is a demo. We connect to your systems and show you the brain working on your actual data. Then we can talk about whether to move forward, what the full scope looks like, and when we'd kick off. Does mid-September work for a demo?
- Andre HollowayYeah, early September is better, if you can do it.
- Jordan PikeLet me check my calendar and I'll send you a couple of options. But first, who else should be in the demo? Just you two, or IT, anyone else?
- Andre HollowayDefinitely our IT person. We might bring in one of the underwriting leads as well, just to see it in action from their perspective.
- Jordan PikePerfect. I'll schedule that and send the invite. Thanks both. Speak soon.
- Maria ColemanThanks, Jordan.