What was said
What this says
Current to 13 Oct 26Demo of the brain on sampled Ellerby data for Rebecca Oakes and Megan Statham. Both reacted well; Megan wants security detail in writing for IT. Priya Raman to send a Growth proposal and set up a call with the CFO.
What happened: Hannah Lowe showed search, a supplier dashboard and chat on a sample of Ellerby's complaints, supplier tickets and practice performance data. Rebecca asked whether her team could use it without building anything.
Customer view: Megan asked about connectors, refresh and security, and said "Yeah, that's exactly what we wanted to hear" when told BB-Demo owns the connectors and refresh. Rebecca's pain point was supplier management and manual reconciliation.
Commercial: Priya will send a proposal with Growth tier pricing and the implementation timeline. Rebecca will check with Vikram and offer time slots for a half-hour commercial call.
Watch: Megan needs security and architecture detail in writing to brief IT. The evidence does not show a decision or a price discussed on this call.
Themes
Current to 9 Oct 26Who was there
BB-Demo
Them
Follow-up
Next steps
Current to 9 Oct 26- Priya Raman to send the Growth proposal by end of day tomorrow.
- Hannah Lowe to provide written technical and security detail for IT.
- Rebecca Oakes to send time slots for a half-hour call with Vikram Sethi.
Risks
Current to 9 Oct 26- Security and architecture detail must reach Megan in writing before IT can be briefed.
- The financial buyer, Vikram, was not on this call and has not yet engaged.
Opportunities
Current to 9 Oct 26- A Growth tier proposal with implementation is the agreed next step.
- A supplier dashboard speaks directly to Rebecca's stated pain point.
Transcript
- Priya Raman NoneMorning, can you hear me okay? Brilliant. So Rebecca, Megan, thanks for making the time. I've got Hannah from our solutions team here who's going to walk you through what the brain looks like on your actual data today.
- Rebecca Oakes NoneYes, hi Priya. We're all set. Looking forward to seeing how this works.
- Hannah Lowe NoneThanks both. So what we've done is pull a sample of your patient complaints and supplier tickets into a demo environment, plus some practice performance data, so you can see how the brain brings all of that together in one place. Megan, I know you'll want to understand the architecture, so I've got some diagrams we'll walk through after.
- Megan Statham NoneThat's helpful. I was wondering how the connectors actually plug into our systems.
- Hannah Lowe NoneGood question. The short answer is we connect via API where it's available, or direct database read access if that makes sense for your setup. No custom code needed on your side. Let me share the screen and show you what this looks like in practice.
- Rebecca Oakes NoneCan you see my screen or is it the other way around?
- Hannah Lowe NoneYou should be able to see mine. So here's the home page: you can search across your data, browse recent items, or jump into a dashboard. Let me search for 'high-risk practices' and you'll see it pulls from your complaints system and cross-references it with your performance metrics. Watch how fast that comes back.
- Megan Statham NoneThat's quick. How often does it refresh?
- Hannah Lowe NoneNightly refresh, complete by seven in the morning your local time, every business day. Rebecca, you mentioned supplier management was a pain point, let me show you how you could build a dashboard for that. So I'm clicking into pages… and here's one someone's built that shows suppliers ranked by open tickets and invoice amount.
- Rebecca Oakes NoneSo our team could just log in and see that without building it themselves?
- Hannah Lowe NoneExactly. Or if you want to ask a one-off question, you use the chat feature. So I could type 'which practices have more than five open complaints this month' and it'll answer me in plain English. You can ask follow-ups and dig into the data that way.
- Priya Raman NoneSo the beauty here is Rebecca's team stops spending time reconciling systems by hand, they ask the brain instead. Megan, you're not managing any of this, we own the connectors, we own the refresh. Your people just use it.
- Megan Statham NoneYeah, that's exactly what we wanted to hear.
- Hannah Lowe NoneAnd once you're live, Esther from our customer success team will work with you through the kickoff to make sure everyone's trained up. We've got documentation, video walkthroughs, the lot. Any technical questions now?
- Megan Statham NoneHow do we handle security? I'll need to brief our IT team.
- Hannah Lowe NoneSmart question. The brain runs inside your Snowflake account, so your data never leaves your environment. We'll put all the technical architecture and security details in writing before we move forward. I'll make sure you've got everything IT needs.
- Priya Raman NoneSo in terms of next steps, I'll send you a proposal with the Growth tier pricing and the implementation timeline. Then we'd love to get Vikram on a call next week so we can walk through the commercial side with him and answer any questions. Does that suit?
- Rebecca Oakes NoneYeah, I'll check with Vikram and send you back a couple of time slots. How long would that call be?
- Priya Raman NoneHalf an hour should do it. I'll have the proposal to you by end of day tomorrow, and then we'll get it in the diary. Cheers both, speak soon.