B-Brain
Lewis Kerr

Lathom Sands Leisure Parks / BB-Demo – Demo

Callcompleted

Lathom Sands Leisure Parks logo Lathom Sands Leisure Parks · 2025-08-18 16:15

Victoria Gaskell saw a demo on her guest, booking and feedback data and asked for a Growth proposal to pitch to her manager. A follow-up call was to be set for about a week later. No decision was made.

What was said

What this says

Current to 14 Oct 26

Victoria Gaskell saw a demo on her guest, booking and feedback data and asked for a Growth proposal to pitch to her manager. A follow-up call was to be set for about a week later. No decision was made.

What happened: Hannah Lowe showed how booking, call and feedback data would link in one search. Lewis Kerr positioned Growth with eight connectors and forty users, and quoted fifty-six for the first year.

Customer view: Victoria called the interface "really clean" and wants her own team to ask questions instead of requesting reports. She must pitch it to her manager first.

Commercial: The figure quoted was "fifty-six" all-in for year one, then fifty a year. The call gives no currency or unit, so treat it as a verbal quote only. Lewis promised a proposal that afternoon.

Watch: Victoria is not the final decision-maker, and her manager was not on the call. Lewis estimated about twenty users initially against forty included.

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

Themes

Current to 9 Oct 26
Theme
Growth tier demo
Importance
upsell
Sentiment
positive
Voice
champion

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Lewis Kerr to send the Growth proposal on the day of the call.
  • Lewis Kerr to book a follow-up call with Victoria about a week later.

Risks

Current to 9 Oct 26
  • Victoria must win over her manager, who was not on the call.
  • The verbal fifty-six quote has no stated currency in the transcript, so the proposal must state it clearly.

Opportunities

Current to 9 Oct 26
  • A Growth subscription with four connectors at the start and room to grow to eight.
  • Extra users in blocks of ten if more of the team join later.

Transcript

  1. Lewis Kerr
    Lewis Kerr None
    Victoria, thanks for the time. Quick check, you're looking to see the brain working on your data, and you've got probably forty-five minutes? Is that right?
  2. Victoria Gaskell
    Victoria Gaskell None
    Yeah, roughly. I want to see how it'd work with our guest data and booking system. My team's always asking me for reports: who booked when, where they're from, what they spent. It'd be great to give them a tool instead.
  3. Lewis Kerr
    Lewis Kerr None
    Perfect. That's exactly what we're going to show. Victoria, this is Hannah: she's our solutions engineer, and she's going to walk through what you'd see. Hannah, take it away.
  4. Hannah Lowe
    Hannah Lowe None
    Thanks, Lewis. So Victoria, before we dive into the live instance, let me show you the architecture. Your guest data: names, addresses, booking dates, where they're from, that lives in your booking system. You've also got call recordings from your reservations team, and feedback from guests. The short answer is, we connect all of those. The longer answer is we map each data source so that a booking links to the calls about that booking, and the feedback about those guests. Then you query across everything.
  5. Victoria Gaskell
    Victoria Gaskell None
    So I'd see a guest's booking, their calls, and their feedback all in one place?
  6. Hannah Lowe
    Hannah Lowe None
    Exactly. Type 'show me guests from a region, their booking values, and their feedback', you get that in seconds.
  7. Lewis Kerr
    Lewis Kerr None
    And Victoria, you don't write SQL. You just ask. It's Google-like search, or you drag and drop a dashboard.
  8. Victoria Gaskell
    Victoria Gaskell None
    How long does that take to set up?
  9. Hannah Lowe
    Hannah Lowe None
    Connectors, that's the hard work. For you, we're looking at four: your booking system, the call recorder, the feedback tool, and maybe your email for reservations context. That's probably two weeks to design, test, go live. Then another couple of weeks for training and your team building first dashboards.
  10. Victoria Gaskell
    Victoria Gaskell None
    And you do the connector work?
  11. Hannah Lowe
    Hannah Lowe None
    Yeah. One of our engineers sits with your IT person, maps the data: basically, 'this field in your booking system is the guest ID, this field is the booking date', and we build the connector. You don't code anything.
  12. Lewis Kerr
    Lewis Kerr None
    Victoria, you'd be on Growth. That's eight connectors, forty users. You'd probably use maybe twenty initially: ops, customer service, your management team. Plenty of headroom.
  13. Victoria Gaskell
    Victoria Gaskell None
    And cost?
  14. Lewis Kerr
    Lewis Kerr None
    All-in for the first year, fifty-six. That's implementation and the annual subscription. After that, fifty a year. Quarterly, we'd sit down and make sure the dashboards are giving you what you need.
  15. Victoria Gaskell
    Victoria Gaskell None
    Fifty-six for how many months?
  16. Lewis Kerr
    Lewis Kerr None
    Twelve. Annual contract, January to January. And you can add users in blocks of ten if you need to bring more of the team in later.
  17. Hannah Lowe
    Hannah Lowe None
    Can I show you the interface real quick? I've mocked up what your guest query would look like.
  18. Victoria Gaskell
    Victoria Gaskell None
    Yeah, please.
  19. Hannah Lowe
    Hannah Lowe None
    So this is the search. You type your question, I'm going to ask 'show me guest bookings by region and booking value'. And here's the result. Guests listed, where they're from, their booking values. You can export this, share it, build a dashboard from it. And if you want to drill down, say, click on a region, it re-filters.
  20. Victoria Gaskell
    Victoria Gaskell None
    That's actually really clean. So my team could each ask their own questions?
  21. Hannah Lowe
    Hannah Lowe None
    Yeah. Every user gets logged in, sees all the dashboards and search, and can query. We'd train them on what's possible, common questions, how to build a dashboard. Takes maybe two hours per person initially. Then they're independent.
  22. Lewis Kerr
    Lewis Kerr None
    Victoria, typical pattern is this, first month, team's asking questions. Month two, three, they're building their own dashboards. Month four, you're making decisions faster because you've got data at your fingertips instead of asking you for a report. Month five, you're wondering how you ever lived without it. That's what we see.
  23. Victoria Gaskell
    Victoria Gaskell None
    When would you start?
  24. Lewis Kerr
    Lewis Kerr None
    If you decide to go, we'd sign the order form and pick a start date. Most teams say early September, but that's your call.
  25. Victoria Gaskell
    Victoria Gaskell None
    I think this is really interesting. I want to see what the team thinks, I mean, I'll pitch it to my manager, and I'd like to get a proposal. Can you send that over?
  26. Lewis Kerr
    Lewis Kerr None
    Will do, today. It'll have the Growth tier, the fifty-six figure, the eight connectors, the timeline. You review it, pass it around, and let's grab a follow-up call in a week or so. Sound good?
  27. Victoria Gaskell
    Victoria Gaskell None
    Yeah, perfect.
  28. Lewis Kerr
    Lewis Kerr None
    Great. I'll get that over this afternoon. And Victoria, if the team has questions after they read it, we're happy to do a short call.
  29. Victoria Gaskell
    Victoria Gaskell None
    Thanks, Lewis. Cheers.
  30. Lewis Kerr
    Lewis Kerr None
    Kind regards, Victoria. Hannah, thanks.
  31. Hannah Lowe
    Hannah Lowe None
    Thanks, Victoria. 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
Organisations225
People at customers862
BB-Demo staff58
Calls1,995
Email threads3,013
Support tickets1,159
Documents1,218
Deals315
Invoices285
Events49
News items119

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.

Help

Ask B

B-Brain · read-only