What was said
What this says
Current to 11 Oct 26Neil Barlow described client data scattered across three places and manual hours to build a client view. Lewis Kerr recommended Growth and Neil agreed to a demo on Ravensholt's own data the following week.
What happened: Lewis Kerr ran a first discovery call with Neil Barlow, who leads operations. Neil said client data sits in three places and building a family office view is a manual job.
Commercial: Lewis recommended Growth for a team of thirty to forty at £44,000 a year plus a £12,000 implementation over eight weeks. The v2 Growth list is £50,000, so the quoted annual price looks like the v1 figure and needs confirming before a proposal.
Watch: Neil asked whether eight weeks was a lot of time from Ravensholt's side, and Lewis called it a light lift. The five hours saved per question was Lewis's estimate, not Neil's.
Next: Theo, the solutions engineer, is to demo on Ravensholt's own data. The evidence does not show whether it was held.
Themes
Current to 9 Oct 26Who was there
BB-Demo
Them
Follow-up
Next steps
Current to 9 Oct 26- Lewis Kerr to send the demo invitation and have Theo run a demo on Ravensholt's own data.
- Lewis Kerr to confirm the correct Growth list price before any proposal is issued.
Risks
Current to 9 Oct 26- Neil questioned the eight-week implementation effort, and a light-lift promise may not hold once IT permissions and connectors are tested.
- The quoted £44,000 annual price differs from the v2 Growth list of £50,000 and may need correcting in the proposal.
- Only Neil took part, so the evidence does not show who else would buy or sponsor the brain.
Opportunities
Current to 9 Oct 26- A client-service team of thirty to forty fits the forty users included in Growth.
- Manual client-view work across Salesforce, notes and email is a clear use case for the brain.
Transcript
- Lewis Kerr NoneHi Neil, thanks for taking the time. How's your week been?
- Neil Barlow NoneBusy, good. So what is the brain exactly?
- Lewis Kerr NoneRight, so, the short version is we sit on top of your CRM, your calls, your emails, and we let anyone in your team ask it questions instead of hunting through three systems. The long version is a bit more architecture, but, what's the biggest problem you face right now when you need to answer a question about a client?
- Neil Barlow NoneData lives in three places. We've got Salesforce for relationships, but clients ring in and the notes go somewhere else. Emails are scattered. If someone needs to pull together a view of what we know about a particular family office, it's a manual job. Hours, sometimes.
- Lewis Kerr NoneYeah, that's where the brain saves time. You connect your systems, we index everything, and someone can ask: 'Show me all interactions with the MacDonald family office in the last quarter,' and it just gives you the answer. To put a number on it, that's probably five hours of work gone, every time someone asks.
- Neil Barlow NoneAnd this lives where?
- Lewis Kerr NoneInside your Snowflake account. You own the data. We build the AI layer and run it, but it's all inside your environment. You've got access to everything.
- Neil Barlow NoneRight. And how many people would use this?
- Lewis Kerr NoneHow big's your client-service team?
- Neil Barlow NoneAbout thirty, forty. Relationship managers, some support staff.
- Lewis Kerr NonePerfect. For you we'd recommend Growth. That's forty users included, eight connectors: so you could have Salesforce, the call recorder, Outlook, and five more. Annual price is £44,000. Implementation is £12,000, takes eight weeks to get everything live and tested properly.
- Neil Barlow NoneAnd you refresh the data how often?
- Lewis Kerr NoneNightly. Complete refresh by 07:00, your local time, every business day. So a call recorded today, it's in the brain by the next morning.
- Neil Barlow NoneWhat happens if you go down?
- Lewis Kerr NoneOn Growth you've got 99.5 availability. That's, we're up 99.5 per cent of the time. If there's an outage, your data's already in Snowflake, so even while we're fixing it, the brain can still answer from what's already synced. No data loss.
- Neil Barlow NoneOK. And what's involved in the implementation? Eight weeks is, that's a lot of time from our side?
- Lewis Kerr NoneNot really, no. We do most of it. We'll talk to your IT team maybe once a week: they'll make sure we've got the right permissions, and we'll test the connectors. But it's not a big lift from your side. And when it's done, we'll do training so your team knows how to use it.
- Neil Barlow NoneAlright. What's the next step?
- Lewis Kerr NoneI'd like to get Theo over: he's our solutions engineer: to do a demo on your data, walk through the architecture with you, and answer any architecture or security questions. Keen for next week?
- Neil Barlow NoneYeah, let's do it. I'll get in the diary.
- Lewis Kerr NoneI'll send that over today. Cheers.