Tom Ashdown

Rookhaven Asset Management / BB-Demo – Discovery

Callcompleted

Rookhaven Asset Management: documents logo Rookhaven Asset Management: documents · 2026-06-09 14:00

Rookhaven's Head of Client Data set criteria: one client view, shared records and lineage. The COO wants security and procurement before any signature and asked for a price breakdown. A close of 18 Dec 2026 is only a plan.

What was said

What this says

Current to 11 Oct 26

Rookhaven's Head of Client Data set criteria: one client view, shared records and lineage. The COO wants security and procurement before any signature and asked for a price breakdown. A close of 18 Dec 2026 is only a plan.

What happened: Discovery call on 9 Jun 2026 with Eleanor Whitlock and Julian Ferrers. Client data sits in Salesforce, Zendesk, mailboxes and hand-reconciled finance data, and two people can build two different pictures of a client.

Commercial: Tom Ashdown said about £155,000 all in for a first deal, including one-off implementation, is an internal pencil figure and not the annual price. Julian asked for a written breakdown and said cost discipline matters.

Customer view: Eleanor wants lineage for every answer and a security and risk review before commitment. Julian will not sign before procurement and security.

Watch: The 18 Dec 2026 close is a plan that moves with their review. Tom has not yet named sector references.

AI · claude-sonnet-5-5 · 11 Oct 2026

Themes

Current to 9 Oct 26
Theme
Enterprise discovery, security gate
Importance
neutral
Sentiment
neutral
Voice
decision-maker

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Tom Ashdown to send a written price breakdown separating implementation from the annual subscription.
  • Tom Ashdown to confirm what BB-Demo can share about financial services customers and arrange a reference conversation.
  • Tom Ashdown to schedule a lineage demo with the head of client service, and Eleanor to send her systems list.

Risks

Current to 9 Oct 26
  • Security, risk and procurement review must complete before any signature, so timing depends on their process.
  • Julian stressed cost discipline, and the figure Tom mentioned was informal and not the annual price.

Opportunities

Current to 9 Oct 26
  • Enterprise fits their stated needs: company-wide scope, SSO and SCIM, lineage and a Snowflake-resident brain.
  • Eleanor wants her own team as admins and named Salesforce, Zendesk, Microsoft 365 and finance data as first connectors.

Transcript

  1. Tom Ashdown
    Tom Ashdown None
    Afternoon, Eleanor. Can you hear me alright? I've got the recorder running, so apologies in advance for anything daft I say. How's your week been?
  2. Eleanor Whitlock
    Eleanor Whitlock None
    Afternoon, Tom. Yes, you're coming through clearly. It's been a busy week, quarter-end reporting is close and my team have been buried. Julian is just dialling in now.
  3. Julian Ferrers
    Julian Ferrers None
    Good afternoon both. Apologies, I was held up. What's the decision required today?
  4. Tom Ashdown
    Tom Ashdown None
    Afternoon, Julian. Good to meet you. No decision today, no drama. This is a discovery call. I want to understand how client data works at Rookhaven now, and whether what we do is even a fit. Then we can work out a sensible next step.
  5. Julian Ferrers
    Julian Ferrers None
    Understood. Eleanor will lead. I'll listen.
  6. Eleanor Whitlock
    Eleanor Whitlock None
    Thank you. If I may, I'd like to restate the criteria we're evaluating against, so we're all anchored. First, one trusted view of each client across institutional and wealth. Second, client service and distribution working from the same record rather than their own spreadsheets. Third, from a governance standpoint, a clear lineage for every answer. What's the source, who changed it, and when.
  7. Tom Ashdown
    Tom Ashdown None
    That's really clear, thank you. Lineage is a big one for us as well. Every answer the brain gives points back to the record it came from. I'll show you that properly in a demo, but let me ask first. Where does client data live today? Roughly.
  8. Eleanor Whitlock
    Eleanor Whitlock None
    Roughly, then. The client relationship records sit in Salesforce. Service conversations are partly in Zendesk and partly in shared mailboxes, which is not ideal. Call notes are in various places. Finance and fee data come out of the accounting side and are reconciled by hand.
  9. Tom Ashdown
    Tom Ashdown None
    Right. And when you say reconciled by hand, what does that look like on a Tuesday afternoon?
  10. Eleanor Whitlock
    Eleanor Whitlock None
    Someone in client service opens three systems and a spreadsheet, and builds a picture of a client before a review meeting. It takes a good part of a morning. And two people can build two different pictures.
  11. Tom Ashdown
    Tom Ashdown None
    Mm. And that's the bit that worries you from the regulator side, presumably. Two versions of the truth.
  12. Eleanor Whitlock
    Eleanor Whitlock None
    Precisely. If we were asked how a figure in a client pack was derived, the honest answer today is that it depends who made it.
  13. Julian Ferrers
    Julian Ferrers None
    What's the operational risk if the data is wrong in a client pack?
  14. Eleanor Whitlock
    Eleanor Whitlock None
    Reputational first, Julian, and potentially a conduct question. It's one reason I'd want this reviewed by security and by risk before we go any further.
  15. Tom Ashdown
    Tom Ashdown None
    Which is the right order, honestly. Let me explain how we're built, because it matters for that. The brain runs inside your own Snowflake account. Your data doesn't go to us and sit somewhere else. We build and run the layer in your environment, under your controls.
  16. Eleanor Whitlock
    Eleanor Whitlock None
    Inside our Snowflake account. So our existing access controls apply.
  17. Tom Ashdown
    Tom Ashdown None
    That's the idea, yes. You'd go through our security review as part of Enterprise, and my team supports your security people through it. Whatever questionnaire you have, we'd work through it with you.
  18. Julian Ferrers
    Julian Ferrers None
    Let's see the security review first. Who else uses you in our sector?
  19. Tom Ashdown
    Tom Ashdown None
    Fair question. I don't want to name customers without their say, so leave that with me. I'll come back with what I'm allowed to share about financial services customers, and we can arrange a reference conversation if that helps.
  20. Julian Ferrers
    Julian Ferrers None
    Please do. Thank you.
  21. Eleanor Whitlock
    Eleanor Whitlock None
    Tom, may I ask about scope? We've been thinking Enterprise because of the company-wide aspect and SSO. But I don't want to assume. What does that tier actually include?
  22. Tom Ashdown
    Tom Ashdown None
    Sure. Enterprise is company-wide, with SSO and SCIM, more users and connectors than the lower tiers, an executive sponsor on our side, and the security review support I mentioned. It's the one regulated buyers usually land on. Growth is for several teams, but you've told me client service and distribution, plus governance, so I'd expect Enterprise.
  23. Eleanor Whitlock
    Eleanor Whitlock None
    And the order of magnitude commercially? Julian will want to know.
  24. Tom Ashdown
    Tom Ashdown None
    I won't quote from memory, I'd rather confirm it in writing. What we've pencilled in internally is about £155,000 all in for a first deal, which includes the one-off implementation. That's not the annual number, so please don't read it as the yearly price. I'll send a proper breakdown that separates the two.
  25. Julian Ferrers
    Julian Ferrers None
    Understood. Cost discipline matters to us. A breakdown, please.
  26. Tom Ashdown
    Tom Ashdown None
    You'll have it, Julian. Now, Eleanor, systems. Which would we need to connect first for the client-service view to work?
  27. Eleanor Whitlock
    Eleanor Whitlock None
    Salesforce and Zendesk, certainly. Then the mailboxes in Microsoft 365, and the finance data. I would want to confirm the full list with my team rather than guess. I can send a systems list.
  28. Tom Ashdown
    Tom Ashdown None
    Brilliant, that'd be really useful. And who in your world would actually ask the brain questions day to day? Just so I picture it.
  29. Eleanor Whitlock
    Eleanor Whitlock None
    Mainly client service, and the head of client service would be the one to convince. Distribution would be second. I'd also want my own team as admins, so that stewardship stays with data.
  30. Tom Ashdown
    Tom Ashdown None
    Makes sense. Would it help if we did a demo with the head of client service in the room? I can show it against something shaped like your data, so they see their own world.
  31. Eleanor Whitlock
    Eleanor Whitlock None
    Yes, I think that would help. I'd like them to see lineage in particular. And I'd want written confirmation of how the security review would run before we commit to anything.
  32. Julian Ferrers
    Julian Ferrers None
    I'll need to drop shortly. Eleanor, you'll keep me informed. Procurement and security before any signature.
  33. Eleanor Whitlock
    Eleanor Whitlock None
    Of course, Julian.
  34. Tom Ashdown
    Tom Ashdown None
    That's absolutely right, Julian. For planning only, we've pencilled in 18 December 2026 as a possible close, but that's a plan and not a promise. It moves with your review, not with my diary.
  35. Julian Ferrers
    Julian Ferrers None
    Noted. Thank you both. Julian Ferrers, signing off.
  36. Eleanor Whitlock
    Eleanor Whitlock None
    Tom, so I'm clear on next steps. You'll send the price breakdown and what you can share about sector customers. I'll send the systems list. And we'll fix a demo with client service.
  37. Tom Ashdown
    Tom Ashdown None
    Spot on. Let's get something in the diary for the demo this week if we can, and I'll send times today. Anything else on your mind before we finish?
  38. Eleanor Whitlock
    Eleanor Whitlock None
    No, that's everything for now. Thank you, Tom. Best regards, Eleanor.
  39. Tom Ashdown
    Tom Ashdown None
    Cheers, Eleanor. Speak soon.

BB-Demo is a fictional company; every organisation and person here is invented. B-Brain is the tool. Built by site/build_site.py from the site tree, data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Brain is one place to read everything the company knows about its customers: the CRM, calls, emails, support tickets, product usage, invoices, documents, news and HR. Every page is built from those systems and the data is current to Fri 9 Oct 2026.

How to use the site

How to ask

Press Ask Brain in the header. Type a question, or pick one of the examples.

The site itself does not call an AI model; answers in Claude come from the same figures you see here.

What the data covers

DataRecords
Organisations150
People at customers573
BB-Demo staff48
Calls1,382
Email threads2,122
Support tickets789
Documents850
Deals217
Invoices187
Events49
News items84

Data as of Fri 9 Oct 2026. Text marked AI was written by the brain from the records listed in its made-from link; an AI output that cannot cite its evidence is refused and the previous text kept. Where two systems disagree (for example a contract and the CRM), the key facts show both values and mark the difference.

BB-Demo is a fictional company: every organisation, person and figure here is invented for this demonstration. B-Brain is the tool that reads its data.

Who to contact

Email support@b-brain.example or talk to your B-Brain account team. Tell us the page address and what looked wrong; a screenshot helps.

HelpAsk B

Ask B

B-Brain · read-only