Wattlebrook Insurance Services / BG-Demo – Demo
Callcompleted
Wattlebrook Insurance Services · 21 Jan 2026 09:15
Hannah Lowe demoed search, chat and pages on a test dataset shaped like Wattlebrook's broker and claims data. The customer asked practical questions on export, access and value. A proposal was promised for early the following week.
What was said
What this says
As at Fri 9 Oct 2026Hannah Lowe demoed search, chat and pages on a test dataset shaped like Wattlebrook's broker and claims data. The customer asked practical questions on export, access and value. A proposal was promised for early the following week.
What happened: Hannah Lowe demonstrated search, chat and pages on a test dataset built to look like Wattlebrook's broker submissions and claims data. Jess Mitchell, Brodie Kennedy and Jess Doyle asked practical questions on export, access and speed.
Customer view: Jess Doyle asked whether the team would no longer need to log into two different tools, and Hannah confirmed it. Jess Mitchell asked how many queries would be needed to get value and received no firm figure.
Commercial: Tom Ashdown positioned Starter with a four-week implementation and promised a proposal early the following week. Hannah said that on Starter everyone on the account sees everything, which may matter for claims data and points towards Growth.
Watch: no price was discussed on this call, and the evidence does not show a value case for Wattlebrook.
Themes
As at Fri 9 Oct 2026Who was there
BG-Demo
Them
Follow-up
Next steps
As at Fri 9 Oct 2026- Tom Ashdown to send the proposal covering systems, timelines and pricing early the following week.
- Tom Ashdown to answer Jess Mitchell's value question with a view on likely usage.
Risks
As at Fri 9 Oct 2026- Starter gives everyone on the account access to everything, which may not suit claims data.
- Jess Mitchell asked what usage is needed to get value and received no firm answer.
Opportunities
As at Fri 9 Oct 2026- Granular access control is a Growth feature, so the access question could lead to a Growth conversation.
- Joining broker submissions with claims data in one place is the use case the customer engaged with.
Transcript
Tom AshdownHi all, thanks for making the time. This is Hannah from our solutions team, she's going to walk you through the brain in action.
Hannah LoweHi everyone. What I want to show you today is how the brain would work with your broker submissions and claims data. I've built a test dataset that looks like yours. So let me share my screen.
Jess MitchellBrilliant, thanks.- Hannah LoweRight. You're logged in as a claims handler. You want to find all open claims from December. Watch what happens. I type in the search box: 'show me all claims filed in December that are still open'.
Brodie KennedyAnd that's pulling from multiple systems?- Hannah LoweExactly. It's hitting your CRM and your claims system at the same time. You get back a table with the claims, the amounts, who they're from, their status. Then you can filter that table: sort by amount, by date, whatever you need.
Jess DoyleSo we don't have to log into two different tools?- Hannah LoweNo. This is the point, one place to ask, one answer back.
- Jess MitchellHow do I export that?
- Hannah LoweYou can download it as a CSV, or pin it to a page so your team sees it every time they log in. Let me show you pages. A page is a bit like a dashboard: you put multiple searches on it, add notes, share it with your team.
- Brodie KennedyWho can see what?
- Hannah LoweOn Starter, everyone on your account sees everything. It's not granular. Growth and Enterprise have more control there.
- Jess MitchellOkay. What about chat?
- Hannah LoweChat's more conversational. Same data, but you ask in a back-and-forth. 'Show me December claims', it shows you. Then you ask 'how many are from Sydney' and it answers that without you having to write a new query.
- Jess DoyleIs it fast?
- Hannah LoweMilliseconds for most queries. Anything complex might take a few seconds, but you're not waiting.
- Tom AshdownAnd all your data is fresh. Hannah, remind them when that refresh happens.
- Hannah LoweNightly. We pull everything from your systems every evening, so by seven in the morning your data is current. If something changes during the day, it's in the brain by the next morning.
- Brodie KennedyWhat if something goes wrong? A connector stops working?
- Hannah LoweWe monitor that. If a connector fails, you'll see a warning in the brain. You can raise a ticket and we'll look at it. On Starter, you get a response within four business hours.
- Jess MitchellHow many queries do you think we'd need to ask to get value?
- Hannah LoweSome customers use it ten times a day, some a few times a week. It depends on your workflow. The key is that when you need to pull data together, you don't have to spend time in multiple systems.
- Tom AshdownAny other questions?
- Jess DoyleWhen could we go live if we wanted to?
- Tom AshdownFour weeks from signing. So if we close a deal now-ish, you'd be up and running in February.
- Jess MitchellOkay. What does the next step look like?
- Tom AshdownWe'd send you a proposal with the scope: which systems we're connecting, timelines, pricing. You review it, we answer questions, and if it works, we move to an order form. No drama. I'll get something over to you early next week. Cheers, all.