What was said
What this says
Current to 13 Oct 26Hannah Lowe demonstrated pages, search and chat on sample education data. Amanda Holt called it impressive and asked about confidentiality and connector failures. She will speak to Mohammed Hanif before deciding.
What happened: Tom Ashdown and Hannah Lowe demoed the brain on sample education data to Amanda Holt. Mohammed Hanif was not on the call.
Customer view: Amanda said it was impressive. On student data confidentiality she said "That's important for us."
Commercial: Tom restated fifty-six thousand all-in for year one and described the order form route. Amanda said she would talk to Mohammed and come back.
Watch: Hannah promised a one-hour urgent response, which matches Growth. The call also mentions quarterly check-ins, in line with Growth QBRs. Several student systems need connectors, so scoping matters. Tom promised a follow-up invite early the following week.
Themes
Current to 9 Oct 26Who was there
BB-Demo
Them
Follow-up
Next steps
Current to 9 Oct 26- Tom Ashdown to send a summary of the demo and a follow-up calendar invite early the following week.
- Tom Ashdown to confirm the commercial side with Mohammed Hanif, then issue an order form.
Risks
Current to 9 Oct 26- Mohammed Hanif was absent and still has to agree the commercial terms.
- Student data sensitivity means the security answers must satisfy the trust.
Opportunities
Current to 9 Oct 26- Growth tier at fifty-six thousand all-in for year one, with 8 weeks to go live.
Transcript
- Tom Ashdown NoneAmanda, hi. How's your week been?
- Amanda Holt NoneGood, thanks. Busy. Looking forward to seeing what this brain thing can actually do.
- Tom Ashdown NoneFair enough. Well, this is Hannah, one of our solutions engineers. She's going to walk you through the brain using some education data. It's not your data yet, but it'll give you a sense of how it works. Hannah?
- Hannah Lowe NoneHi Amanda. So what I'm going to do is show you the brain running on a sample of education data: student records, staff, finance. I'm going to walk through three things: pages, which are your dashboards; search, where you ask questions; and chat, where you can dig deeper with conversational queries. Sound good?
- Amanda Holt NonePerfect.
- Hannah Lowe NoneOK, so first thing, here's a page. This is showing me student numbers across schools, broken down by year group and by gender. I've built this in about five minutes using our drag-and-drop page builder. You don't need to code. Notice that number's live: it's connected to the underlying data, so if the source system updates, this updates.
- Amanda Holt NoneSo if I wanted to add another metric, say, absence rates, I could just add it to the page?
- Hannah Lowe NoneExactly. Drag in another widget, point it at the data you want, done. Now, let me show you search. I'm going to ask the brain a question: 'show me staff costs by school for the current term'.
- Hannah Lowe NoneSee, it's parsed my question and returned the answer, staff costs aggregated by school. And it's pulling from your finance system and your HR data at the same time. No manual reconciliation.
- Amanda Holt NoneThat's impressive.
- Hannah Lowe NoneAnd now chat. This is where you can follow up on an answer with more questions. Say I want to drill into the secondary schools, I can ask 'what's the breakdown by secondary only' and it remembers context. I can keep asking follow-up questions without starting over.
- Hannah Lowe NoneThe short answer is, you're running AI on top of your data. The longer answer is that we've indexed everything from your source systems: your student records, finance, HR, and you can query it however you need.
- Amanda Holt NoneHow does it handle confidentiality? Student data is sensitive.
- Hannah Lowe NoneGood question. The brain sits inside your Snowflake account, on your infrastructure. You control access: we can set permissions at the page level, so some users see student data, others only see financial data. And you've got audit logs of every question asked, every answer returned.
- Amanda Holt NoneThat's important for us.
- Tom Ashdown NoneThat's standard for everyone, Amanda. Security's built in.
- Hannah Lowe NoneLet me show you the admin panel. This is where you manage users, permissions, connectors. You can add a user, assign them to a school or a role, and they're done. The brain respects your permissions, if they're not allowed to see student data, they don't.
- Hannah Lowe NoneNow, how often does the data refresh? Nightly, by seven in the morning on business days. So every morning you've got fresh data from all your source systems.
- Amanda Holt NoneAnd if something breaks, a connector stops working, what happens?
- Hannah Lowe NoneWe monitor all the connectors. If one fails, we alert you and we start diagnosing. With Growth you've got support from us during business hours, and we commit to one-hour response time on urgent issues.
- Tom Ashdown NoneAnd you've got us. Anything goes wrong, you call or email, we're on it.
- Amanda Holt NoneOK. So if I wanted to take this forward, what's next?
- Tom Ashdown NoneNext would be a conversation with Mohammed about the commercial side, just confirm fifty-six thousand all-in for year one is something you can sign up to. Then we'd send you an order form, you'd get that reviewed, sign it, and we'd kick off implementation. Eight weeks and you're live.
- Amanda Holt NoneAnd you'd connect to all our different student systems?
- Hannah Lowe NoneWe'd need to understand each one, what systems you're using, what data's in them. During implementation week one we'd map all of that, weeks two through six we'd build connectors, week seven and eight you'd test and we'd train your team.
- Amanda Holt NoneThat sounds straightforward.
- Tom Ashdown NoneIt is. And once you're live, you've got quarterly check-ins with us to make sure you're getting value out of it.
- Amanda Holt NoneGreat. I'll chat to Mohammed and we'll get back to you.
- Tom Ashdown NoneNo drama. I'll send you a summary of what we've walked through and drop a calendar invite for a follow-up early next week.