Quennell Harte / BB-Demo – Demo
Callcompleted
Quennell Harte: documents · 2026-05-06 11:30
Demo on 6 May 2026 for Ellie Rowcliffe and Ben Tozer covering Snowflake residency, nightly sync, search, chat and access control. Ellie said they are ready to talk terms. Simon Harte was not on the call.
What was said
What this says
Current to 11 Oct 26Demo on 6 May 2026 for Ellie Rowcliffe and Ben Tozer covering Snowflake residency, nightly sync, search, chat and access control. Ellie said they are ready to talk terms. Simon Harte was not on the call.
What happened: Hannah Lowe and Sophie Ling demonstrated the brain to Ellie Rowcliffe and Ben Tozer on 6 May 2026. Ben tested data residency, permissions and adding a new system later.
Customer view: Ellie said the unbilled time query would have taken her hours manually, and that nightly refresh is fine. She then asked to talk terms.
Commercial: This is a buying signal for a new subscription and a four week implementation. Simon, the MD, was absent, so the evidence does not show who signs.
Watch: Hannah said a new connector would be live within a few days, an informal promise to align with any order form.
Themes
Current to 9 Oct 26Theme
Demo and buying signal
Importance
upsell
Sentiment
positive
Voice
champion
Who was there
BB-Demo
CRMmade from
Them
CRMmade from
Follow-up
Next steps
Current to 9 Oct 26- Sophie Ling to send the proposal with pricing and timeline to Ellie Rowcliffe by end of that week.
- Sophie Ling to get Simon Harte into the next call on terms.
Risks
Current to 9 Oct 26- Simon Harte, the managing director, was not on the call, so the decision-maker has not seen the demo.
- Hannah's live within a few days remark for a new connector is informal and may not match an order form commitment.
Opportunities
Current to 9 Oct 26- Ellie is ready to talk terms, so a proposal for a Starter subscription and four week implementation can move forward.
- A future accounting connector was raised by Ben, which could become an add-on conversation.
Transcript
Sophie Ling NoneHi all, thanks for joining. This is Hannah, she's our Solutions Engineer. We're going to show you the brain on data similar to yours so you can see how it'd work.
Hannah Lowe NoneHi Ellie, hi Ben. So what I'll do is walk through the architecture first, just to be precise about where the data lives and how it flows, then show you some queries. Sound OK?
Ellie Rowcliffe NoneYeah, let's do it.- Hannah Lowe NoneOK, so the brain is an application that sits in your own Snowflake account. Every night, we sync data from your connected systems: so CRM, your project system, email, into Snowflake. The brain indexes that data and makes it queryable. All your data stays in Snowflake, in your cloud account, under your control.
Ben Tozer NoneSo the data never leaves our infrastructure?- Hannah Lowe NoneNever. It's all within your account. The brain is a Python application that runs inside Snowflake and responds to your queries. From a network perspective, you access it through a web interface, but the query execution is internal to your account.
- Ben Tozer NoneOK, that's good. And the sync, is that incremental or a full copy every night?
- Hannah Lowe NoneIncremental, so we pull changes since the last sync. That's more efficient and keeps your data fresh without hammering your systems.
- Ellie Rowcliffe NoneHow long does a sync usually take?
- Hannah Lowe NoneFor a setup like yours, CRM, project system, email, usually thirty to forty minutes. They run overnight, so you wake up with fresh data.
- Hannah Lowe NoneOK, so let me show you the interface. This is the search view. You can filter and build a query visually. Say we want to see all projects for a specific client. I'll filter on client name, and there: all their projects with status, timeline, budget, actual spend. That data's pulled from your project system.
- Ellie Rowcliffe NoneNice. And if I want to see the emails from that client relationship too?
- Hannah Lowe NoneI can add another filter. Just add 'email conversations with this client' and they appear below the projects. So you've got the whole relationship in one view.
- Ben Tozer NoneAnd security, who can see what? Can you set permissions per user?
- Hannah Lowe NoneGood question. So permissions are managed in the brain, you control who can access which data. For example, you could restrict certain projects to certain team members, or make client data visible only to account managers. It's role-based access control.
- Sophie Ling NoneAnd Ben, from an admin perspective, once we've built the connectors, there's very little hands-on work. It's mostly, we handle the monitoring, you get notified if a sync fails.
- Ben Tozer NoneOK, that's good to know. And if we want to add a new system later, say, we get new accounting software, can we add a connector?
- Hannah Lowe NoneYeah, absolutely. You'd let us know, we'd build the connector and test it, and it's live within a few days.
- Hannah Lowe NoneLet me show you the chat interface as well. This is the natural-language mode. I just type what I want to know. Say, show me unbilled time across all projects. The brain understands that query, searches your data, and there, a breakdown of unbilled hours by project with the dollar value. All live.
- Ellie Rowcliffe NoneThat would've taken me hours manually.
- Hannah Lowe NoneRight, and you can do it anytime. Here's another, show me retrofit projects in the past two years. And there's a list with scope, budget, outcome. You could use that to win new retrofit work.
- Ellie Rowcliffe NoneExactly. We've done that three times but they're all scattered across projects. This would surface that expertise really quickly.
- Sophie Ling NoneAnd you can save queries as pages, so 'unbilled time' becomes a report you just click to see the latest data.
- Ben Tozer NoneHow often does the data refresh?
- Hannah Lowe NoneEvery night. The short answer is nightly. The longer answer is: we can refresh as often as you need, but nightly is standard and covers most workflows.
- Ellie Rowcliffe NoneNightly's fine for us.
- Hannah Lowe NonePerfect. So to walk through the build process, we'd schedule a connector-design session where you tell us which systems to connect and which fields matter. For you, that's probably two hours. Then we build and test the connectors, get your Snowflake set up, and go live. Four weeks end-to-end.
- Ben Tozer NoneAnd you handle all the Snowflake setup?
- Hannah Lowe NoneWe do. You just need to give us a Snowflake account, new or existing, and we take it from there.
- Ellie Rowcliffe NoneGreat. I think this is really helpful. Sophie, I think we're ready to talk terms.
- Sophie Ling NonePerfect. I'll send you a proposal by end of week with pricing and timeline, and we can discuss any questions on the next call.
- Ben Tozer NoneCheers.
- Hannah Lowe NoneThanks both, and reach out if you have any technical questions.
Callsmade from