Hamza Akhtar

Penwortham Mutual / BB-Demo – Kickoff

Callcompleted

Penwortham Mutual: documents logo Penwortham Mutual: documents · 2026-06-04 11:45

Kickoff for Penwortham Mutual on 4 Jun 2026. The customer team accepted the architecture and connector plan. Security asked where data sits and how fresh it is. A security review call is still to be scheduled.

What was said

What this says

Current to 12 Oct 26

Kickoff for Penwortham Mutual on 4 Jun 2026. The customer team accepted the architecture and connector plan. Security asked where data sits and how fresh it is. A security review call is still to be scheduled.

What happened: Hamza Akhtar walked Clare Huddleston, Phil Catterall and Rizwan Patel through the architecture, connector roadmap and a twelve-week plan. Hollie Grieve introduced herself as customer success manager.

Customer view: Clare said the plan is exactly what they need. Rizwan focused on where the data sits and how often it refreshes.

Commercial: Hamza said the first three connectors go live within two weeks of access, while the plan lights up core connectors in weeks three to six. Check the stated timing against the live-within days in the order form.

Watch: Phil is the single contact for credentials, and the security review has no date yet.

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

Themes

Current to 9 Oct 26
Theme
Implementation kickoff and security
Importance
neutral
Sentiment
positive
Voice
champion

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Hamza Akhtar to send the summary email, security review agenda and credential request form on the day of the call.
  • Phil Catterall to start gathering credentials from his admins the following Monday.
  • Hollie Grieve to agree the go-live plan and user training schedule with Clare Huddleston.

Risks

Current to 9 Oct 26
  • The stated two-week connector timing differs from the plan's weeks three to six and needs checking against the order form commitment.
  • Credentials depend on Phil Catterall alone, and the security review date is not yet set.

Opportunities

Current to 9 Oct 26
  • Gong, SharePoint and HubSpot were named as possible later connectors, which could extend connector use beyond the first wave.

Transcript

  1. Hollie Grieve
    Hollie Grieve None
    Good morning everyone. Thanks for joining. I'm Hollie, the customer success manager for Penwortham going forward. Hamza is our implementation consultant and will be leading the technical work. We're here to kick off the implementation, walk through the plan, assign owners, and make sure we're all clear on expectations. Shall we start with introductions?
  2. Clare Huddleston
    Clare Huddleston None
    Yeah, good. I'm Clare, head of member operations. Phil is here, he's our data platform manager and will be the technical lead on your side. And Rizwan from information security will be sitting in on the data and security decisions.
  3. Hamza Akhtar
    Hamza Akhtar None
    Excellent. So the plan for this call is: I'll walk through the architecture and the connector roadmap, then we talk about the security review, and finally we confirm milestones and who owns what. Sound good?
  4. Phil Catterall
    Phil Catterall None
    Yes, let's go.
  5. Hamza Akhtar
    Hamza Akhtar None
    Right. So here's what we're building. You've got a Snowflake account; inside that, we're deploying the brain. The brain reads data from Salesforce for partner details and contracts; Zendesk for support interactions; Slack for internal chat; Microsoft 365 for email and calendar; Xero for financial data; and Snowflake itself for your data warehouse. That's the core first wave. From there, we can add Gong for call recordings, SharePoint for documents, HubSpot if you're running campaigns. The goal is that your partner operations and member operations teams can ask one question across all of that.
  6. Clare Huddleston
    Clare Huddleston None
    Perfect. That's exactly what we need.
  7. Rizwan Patel
    Rizwan Patel None
    I have a question on security. The brain is reading this data, where does it sit? Is it secure?
  8. Hamza Akhtar
    Hamza Akhtar None
    Good question. The brain sits entirely inside your Snowflake account. You control it, you govern it. No data leaves your Snowflake except through your existing access controls. Encryption, audit logs, role-based access, all standard Snowflake features. We'll walk you through the security design in detail in a separate security review call with Hamza, sorry, with me. We're scheduling that for next week.
  9. Rizwan Patel
    Rizwan Patel None
    Okay. Who has access to what inside Snowflake?
  10. Hamza Akhtar
    Hamza Akhtar None
    Your member operations users can query the brain tables that pertain to their role. Same for partner operations. Admins can see the full picture. Governance is fully configurable by you. During the security review, you'll see the exact role definitions and we can adjust them to match your policies.
  11. Phil Catterall
    Phil Catterall None
    And the connector setup, who does that?
  12. Hamza Akhtar
    Hamza Akhtar None
    We'll do the initial setup. For each connector, we'll need credentials and API access from you. Salesforce, Zendesk, Slack, Microsoft 365, Xero, we'll come to you with a setup guide for each one. You'll give us credentials, we spin it up and test it. First three connectors go live within two weeks of you giving us access. The rest roll out weekly.
  13. Phil Catterall
    Phil Catterall None
    So I'm the one you'll be asking for credentials?
  14. Hamza Akhtar
    Hamza Akhtar None
    Yeah, you're the main contact for that. We'll send you the credential requests, you'll liaise with your Salesforce admin, your Slack admin, etc., and get them back to us. We'll do the wiring on our side.
  15. Clare Huddleston
    Clare Huddleston None
    And timeline-wise, how long is this whole thing?
  16. Hamza Akhtar
    Hamza Akhtar None
    Twelve weeks start to finish. Week one and two we do security review and get credentials. Weeks three through six we light up the core connectors and do initial testing. Weeks seven through twelve we roll out the rest, train your team on using the brain, and hand over to Hollie. By week twelve you're live and independent.
  17. Hollie Grieve
    Hollie Grieve None
    And once you're live, I'll run quarterly check-ins with you to make sure you're getting value and to handle any questions. Plus you've got Premium support, a named engineer available business hours, seven to eight in the evening.
  18. Rizwan Patel
    Rizwan Patel None
    What about data freshness? How often is the data in the brain refreshed?
  19. Hamza Akhtar
    Hamza Akhtar None
    Nightly. The brain pulls data from all your connectors each night and loads it by seven in the morning, your local time. So when your team logs in Monday morning, they're seeing data as of Sunday night. If a system is down or data doesn't load, our support team will alert you.
  20. Clare Huddleston
    Clare Huddleston None
    Great. So next steps from here?
  21. Hamza Akhtar
    Hamza Akhtar None
    So: I'll send you the security review agenda for next week. Rizwan, I'll need you and Phil on that call. During that meeting we'll walk through the data model, encryption, access control, and you'll get a chance to ask security questions. Once that's done, we move to phase one. Phil, I'll send you the credential request template, and you start pulling credentials from your admins. Meanwhile, I'll be getting our Snowflake instance ready for your data.
  22. Phil Catterall
    Phil Catterall None
    Got it. I'll start gathering those by Monday next week.
  23. Hollie Grieve
    Hollie Grieve None
    And Clare, I'll be in touch with you about the go-live plan and user training schedule. We'll want to get all the stakeholders lined up.
  24. Clare Huddleston
    Clare Huddleston None
    Sounds good. I think we're ready to go.
  25. Hamza Akhtar
    Hamza Akhtar None
    Excellent. I'll send you all a summary email with action items, the security review date, and the credential request form today. Any last questions?
  26. Rizwan Patel
    Rizwan Patel None
    I think we're covered. Looking forward to the security review.
  27. Hamza Akhtar
    Hamza Akhtar None
    Thanks everyone. Cheers.

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