Ask
Matteo Ricci

Penwortham Mutual / BB-Demo – Demo

Callcompleted

Penwortham Mutual: documents logo Penwortham Mutual: documents · 2026-03-16 11:15

Demo of the company brain to Clare Huddleston and Phil Catterall on 16 Mar 2026. Phil judged the Enterprise set-up feasible; the next step is a written proposal and a walk-through with finance present.

What was said

What this says

Current to 11 Oct 26

Demo of the company brain to Clare Huddleston and Phil Catterall on 16 Mar 2026. Phil judged the Enterprise set-up feasible; the next step is a written proposal and a walk-through with finance present.

What happened: On 16 Mar 2026 Hannah Lowe demoed the brain, with Matteo Ricci hosting. Phil Catterall probed architecture, the custom policy-system connector, freshness, access control and post-implementation support.

Customer view: Phil said it looks feasible and that the architecture and support model make sense. Clare Huddleston, Head of Member Operations, found the chat interface slick and asked about saving, sharing and dashboards.

Commercial: The demo was pitched at Enterprise: role-based access control, the dashboard builder, Premium support and 99.9% availability. Matteo proposed a proposal walk-through with both of them and someone from finance who signs off.

Watch: Hannah quoted a one-hour P1 response for Premium support, while the proposal call gives thirty minutes. She also said the custom connector would be live within a few days, while the proposal call says the first three connectors take two to three weeks.

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

Themes

Current to 9 Oct 26
Theme
Enterprise demo and feasibility
Importance
upsell
Sentiment
positive
Voice
champion

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Matteo Ricci sends call notes and a proposal draft early the following week.
  • Matteo books an hour-long proposal walk-through with Clare, Phil and a finance approver.
  • Hannah Lowe confirms the custom connector timing so the proposal states one consistent commitment.

Risks

Current to 9 Oct 26
  • The one-hour P1 response quoted in the demo differs from the thirty-minute Enterprise figure given later, which could become a contract dispute.
  • The custom policy-system connector was promised live within a few days, which sets an expectation the implementation plan may not match.
  • A finance sign-off is still needed and nobody from finance attended the demo.

Opportunities

Current to 9 Oct 26
  • Enterprise fit is strong: access control by function, dashboards for board reports and Premium support all landed well.
  • Phil's technical concerns were answered, so the proposal can focus on scope and price.

Transcript

  1. Hannah Lowe
    Hannah Lowe None
    Hi Clare, Phil, thanks for joining. Matteo's here too. Before I dive into the demo, what would be most useful for you to see? Phil, I imagine you want to understand the architecture and integration side?
  2. Phil Catterall
    Phil Catterall None
    Yeah, exactly. How we'd connect to the policy system, what the data pipeline looks like, and how fresh the data would be. And security, how is access controlled?
  3. Hannah Lowe
    Hannah Lowe None
    Got it. And Clare, for you, I imagine you want to see what it feels like to ask a question and get an answer back?
  4. Clare Huddleston
    Clare Huddleston None
    Yeah, that would be good. What's the user experience like?
  5. Hannah Lowe
    Hannah Lowe None
    Okay. So let me start with the architecture so Phil's got the picture. Everything runs in your Snowflake. We deploy an application layer, that's where the interface lives. Your data never leaves Snowflake. All the connectors feed into a staging layer, we unify the schema, and then the query engine sits on top of that. So when you ask a question, it's running across all your sources in one go.
  6. Phil Catterall
    Phil Catterall None
    And the connectors to your policy system, would that be custom?
  7. Hannah Lowe
    Hannah Lowe None
    We'd build a custom connector to your policy admin system. We have pre-built ones for common systems, but your policy system isn't one of them, so we'd design one specifically for you. That would be part of the implementation.
  8. Phil Catterall
    Phil Catterall None
    How long does a custom connector usually take?
  9. Hannah Lowe
    Hannah Lowe None
    For a system like yours, with a reasonable API and clear documentation, we'd have it live within a few days of starting. But that's part of the 12-week programme, so it's costed in.
  10. Phil Catterall
    Phil Catterall None
    Okay. And data freshness?
  11. Hannah Lowe
    Hannah Lowe None
    Nightly refresh. The connectors pull data every night, and everything's refreshed and live by 07:00 your time the next morning. So your team's got fresh data every business day.
  12. Phil Catterall
    Phil Catterall None
    And if a connector breaks? Say the policy system API changes?
  13. Hannah Lowe
    Hannah Lowe None
    We monitor it. If a connector stalls, we'll alert you. And we'd work with you to fix it, usually that's an API change on their end, so we'd adjust the connector to match. You'd hear from us before your team even knows there's a problem.
  14. Phil Catterall
    Phil Catterall None
    Fair enough. What about access control? Can we restrict who sees what data?
  15. Hannah Lowe
    Hannah Lowe None
    At the Enterprise tier, yes. Role-based access control. You can say Member Operations sees member and claims data, but not underwriting; Finance sees the financial view; Partner Management sees partner-level data. We use row-level security in Snowflake so the restrictions are enforced at the data layer.
  16. Phil Catterall
    Phil Catterall None
    Good. What about audit?
  17. Hannah Lowe
    Hannah Lowe None
    Everything's logged. Who asked what question, when, what the answer was. That's all in Snowflake so your team can audit it whenever you need to.
  18. Phil Catterall
    Phil Catterall None
    Okay, that's good. Let me see the interface now.
  19. Hannah Lowe
    Hannah Lowe None
    Sure. So here's the chat interface. You ask a question in plain English. Let me show you an example. I'll type: "What's the total revenue across all schemes this year?"
  20. Hannah Lowe
    Hannah Lowe None
    And there's the answer, a number, with a breakdown by scheme. No SQL, no waiting. Questions usually come back in a few seconds.
  21. Clare Huddleston
    Clare Huddleston None
    That's really slick. Can we ask follow-ups?
  22. Hannah Lowe
    Hannah Lowe None
    Yeah, exactly. So now you could ask: "What's the breakdown by partner?" And it remembers the context from the previous question.
  23. Hannah Lowe
    Hannah Lowe None
    So now you've got revenue split by partner. You can keep going. "What's the churn rate by partner?" And so on.
  24. Clare Huddleston
    Clare Huddleston None
    And what if I want to save that and share it with someone else?
  25. Hannah Lowe
    Hannah Lowe None
    You can save a conversation, share it with team members. Or if you want to turn it into something for a board report, you can save it as a dashboard.
  26. Clare Huddleston
    Clare Huddleston None
    Okay, that's useful. How hard is it to build a dashboard?
  27. Hannah Lowe
    Hannah Lowe None
    Not hard. Click the dashboard builder, pick the metrics you want to show, arrange them how you want, and you're done. Takes a few minutes. That's one of the upgrades you get at Enterprise.
  28. Phil Catterall
    Phil Catterall None
    And search? Can we search for something by keyword?
  29. Hannah Lowe
    Hannah Lowe None
    You can. "Find policies maturing this quarter", it'll search across all the policy data and show you relevant results.
  30. Clare Huddleston
    Clare Huddleston None
    Nice. So the user experience is pretty intuitive?
  31. Hannah Lowe
    Hannah Lowe None
    It's designed to feel like talking to a human. Most teams are productive within a week or two.
  32. Matteo Ricci
    Matteo Ricci None
    And Phil, any other questions on the tech side? I know implementation's a big step.
  33. Phil Catterall
    Phil Catterall None
    How much support do we get during the implementation? If we hit issues?
  34. Hannah Lowe
    Hannah Lowe None
    You get dedicated support during the 12 weeks. We assign a named engineer, weekly check-ins, and a direct contact if anything stalls. By week 12, your team's trained up and ready to go live.
  35. Phil Catterall
    Phil Catterall None
    Sounds workable. One more thing, what happens after implementation? How's support handled then?
  36. Hannah Lowe
    Hannah Lowe None
    At Enterprise, you get Premium support: a named engineer, 07:00 to 20:00 UK time, one-hour response on P1 issues. Or if something's urgent outside those hours, you can still reach us.
  37. Phil Catterall
    Phil Catterall None
    Right. And the SLA?
  38. Hannah Lowe
    Hannah Lowe None
    99.9% availability. We back that up with service credits if we miss it.
  39. Phil Catterall
    Phil Catterall None
    Okay, I think I've got the picture. This looks feasible. The architecture makes sense, the support model is solid.
  40. Matteo Ricci
    Matteo Ricci None
    Brilliant. So next step for us would be to move into a proposal: scope out exactly which systems we're connecting, how many users, any other add-ons. Once you've signed off on that, we'll move to a contract. Should we schedule something to walk through the proposal?
  41. Clare Huddleston
    Clare Huddleston None
    Yeah, let's do that. How long would that take?
  42. Matteo Ricci
    Matteo Ricci None
    About an hour, similar to this. We'd want both of you, plus probably someone from your finance team who needs to sign off.
  43. Phil Catterall
    Phil Catterall None
    We can sort that. How long till you'd have a proposal to discuss?
  44. Matteo Ricci
    Matteo Ricci None
    I'll get something together by early next week.
  45. Clare Huddleston
    Clare Huddleston None
    Great.
  46. Matteo Ricci
    Matteo Ricci None
    I'll send over notes from this call, and a proposal draft. Then we can get the three of us back together to walk through it. Sound good?
  47. Phil Catterall
    Phil Catterall None
    Yeah, works for us.
  48. Hannah Lowe
    Hannah Lowe None
    Brilliant. Any other questions before I let you go?
  49. Phil Catterall
    Phil Catterall None
    No, that was really helpful. Thanks.
  50. Hannah Lowe
    Hannah Lowe None
    Cheers. 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.

Help

Ask B

B-Brain · read-only