What was said
What this says
As at Fri 9 Oct 2026Hannah Lowe demoed the brain on Wendover Kast's sample extract. Heather Bauman liked the single agency page; Kyle Brandvold needs permissions and schema answered. Heather cannot commit budget until finance sees it.
What happened: Demo on 13 Aug 2026 with Heather Bauman, Kyle Brandvold and Janet Pruitt. Hannah showed an agency page and a plain-language question about referrals, built on the sample extract.
Customer view: Heather wants service and underwriting looking at the same page. Janet would use it daily if it matches the policy system. Kyle's concerns are where it runs, permissions and the existing pipeline.
Commercial: Jordan Pike restated Enterprise at £155k including implementation, with 8 Jan 2027 pencilled as the decision date. Heather said finance has to see it and Kyle must be comfortable first.
Watch: Hannah owes Kyle an answer on how permissions inherit from Snowflake roles, and Kyle will share a schema outline. A further architecture and security session is proposed.
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 a written summary with Hannah Lowe's permissions answer and the schema request.
- Hannah Lowe to confirm how permissions inherit from Snowflake roles, within a day of the call.
- Hannah Lowe to set up a shorter architecture and security session with Kyle Brandvold and IT.
Risks
As at Fri 9 Oct 2026- Heather cannot commit budget alone and finance has not yet seen the proposal.
- Kyle is not yet comfortable on permissions inheritance from Snowflake roles, which Hannah has still to confirm.
- The sample extract holds only a slice of submission data, so the demo ranking is not real evidence.
Opportunities
As at Fri 9 Oct 2026- Janet would use the referrals question daily if the data matches the policy system.
- Kyle's existing Snowflake pipeline can be read directly, which may shorten connector work.
Transcript
- Jordan PikeHey everyone, can you hear me okay? I see Heather, Kyle, Janet. Great.
- Heather BaumanLoud and clear. Good afternoon, Jordan. Hannah, hello.
- Hannah LoweGood afternoon, all. Audio's fine my end.
- Kyle BrandvoldHi. Give me a second, my camera's being stubborn. There. Hello.
- Heather BaumanWhile we're settling in, quick story. An agency up north called me yesterday, a contractors' book, and they'd sent the same loss run three times to three different people here. Three. Each of us had a different version of who they were.
- Janet PruittAnd I had the fourth, I think. Underwriting had its own copy.
- Jordan PikeTo be transparent, that's the story we hear most. Here's the plan: quick agenda, then Hannah shows the brain on the sample extract you sent over, and we leave time for questions. I want to keep us inside the hour. Sound right?
- Heather BaumanSounds right. Let's keep this moving.
- Hannah LoweBefore I share my screen, what do you most need to know from today? Then I can point the demo at that rather than just walk the menu.
- Heather BaumanHonestly, one thing. What does the agent see? Not what we see. If I search an agency, what comes back, and is it the same answer my underwriting people get?
- Kyle BrandvoldMine is where it runs and who can see what. I've read the architecture note, but I'd like to hear it said.
- Hannah LoweGood. The short answer is: it runs inside your own Snowflake account, so the data doesn't leave it. The longer answer is that I'll show you that, and then the permissions, so you're not taking my word for it.
- Kyle BrandvoldOkay. That's the part I care about.
- Hannah LoweSharing now. Can you see the search page?
- Janet PruittYes, I see it.
- Hannah LoweSo this is built from the extract you gave us: agency records, a policy export, a sample of service tickets. I'll type the name of one agency from your file. To be precise, what comes back is a page assembled from every source we've connected, with each line saying where it came from.
- Heather BaumanWalk me through it. What's that top block?
- Hannah LoweThat's the agency summary. Contact history, open tickets, written premium by line, and the recent submissions. Each one links back to the record in the source system, so if the number looks wrong you can click through and check it.
- Heather BaumanOkay, so my service person and the underwriter are looking at the same page.
- Hannah LoweThe same page, yes. What each of them sees can differ by permission, but the underlying record is one.
- Janet PruittCan I ask it something instead of searching? Like, which agencies in this file have referrals sitting longest?
- Hannah LoweYes. Let me type it as you said it. Which agencies have referrals waiting longest.
- Hannah LoweThere. A ranked list, and the answer states which fields it used. Be careful with this one: your sample only has a slice of the submission data, so I wouldn't read the ranking as real. It shows the shape.
- Janet PruittFair. But that's exactly the question I spend Monday mornings on, in a spreadsheet.
- Jordan PikeJanet, what would make this a yes for your team? Is it the ranking, or is it getting the data to line up?
- Janet PruittLining up. If I trust it matches the policy system, I'd use it daily.
- Kyle BrandvoldThat's a connector question, really. How do you get from the policy admin system into Snowflake? We've got an existing pipeline.
- Hannah LoweRight. If you already land that data in Snowflake, we read it from there. We don't need to replace your pipeline. Where there's no existing feed, we'd design a connector with you. I'd want to see your current tables before promising anything about timing.
- Kyle BrandvoldI can share a schema outline. Not production data.
- Hannah LoweThat's all I need. I'll put that in writing so we're both clear what's asked for.
- Heather BaumanLet me try the agent side. Say an agency rings in and says their commission statement is wrong. What happens here?
- Hannah LoweYour service rep opens the agency page, asks about the statement, and gets the related tickets and the finance records, with sources. They still make the call. The brain doesn't write to your systems.
- Heather BaumanGood. I don't want anything changing records behind my people's backs.
- Hannah LoweUnderstood. Read only against your systems.
- Kyle BrandvoldAnd the permissions? If the service team shouldn't see underwriting notes, how's that handled?
- Hannah LoweLet me show you. Here's the access view. You set which roles see which sources, and the answers only draw on what that person may see. I'd like to confirm one detail on how that inherits from your Snowflake roles before I describe it fully, so give me a day on that.
- Kyle BrandvoldThat works. I'd rather you check than guess.
- Heather BaumanSame here. I won't push past security. If Kyle's not comfortable, we wait.
- Jordan PikeAppreciate that. Here's where we are on the commercial side, briefly. We're looking at Enterprise, and the deal value we've discussed is £155,000, implementation included. We're pencilling a decision for 8 Jan 2027, but that's your timeline, not ours.
- Heather BaumanRight. I can't commit budget on my own. Finance has to see it. Let's get Kyle comfortable first, then I take it up.
- Jordan PikePerfect. Next steps from me: a short written summary after this call, with Hannah's answers on permissions and the schema ask. Hannah, anything else?
- Hannah LoweOnly that I'd like another session, shorter, with Kyle and anyone from IT, on the architecture and security review. Another colleague on our side may lead that one.
- Heather BaumanSounds good. Thanks, everybody.
- Janet PruittThanks, this was useful.
- Jordan PikeThanks, all. Speak soon.