Ask
Hamza Akhtar

Pemaquid Analytics / BB-Demo – Kickoff

Callcompleted

Pemaquid Analytics: documents logo Pemaquid Analytics: documents · 2026-04-13 14:15

Kickoff for Pemaquid Analytics on Growth, held 13 Apr 2026. Caitlin is a clear champion. Ingrid wants to approve sources before any connector goes live. Priscilla is the only admin, and usage data sits with engineering.

What was said

What this says

Current to 11 Oct 26

Kickoff for Pemaquid Analytics on Growth, held 13 Apr 2026. Caitlin is a clear champion. Ingrid wants to approve sources before any connector goes live. Priscilla is the only admin, and usage data sits with engineering.

What happened: Hollie recapped the Growth contract, 1 Apr 2026 to 31 Mar 2027, renewal on 1 Apr 2027. Hamza walked through sources and sequence: helpdesk and CRM first, then the call recorder, then usage.

Customer view: Caitlin said renewals were a surprise for her own team and she bought this to get ahead of them. Ingrid accepted the Snowflake-resident design but asked for a written gate: no connector before she approves the source and role.

Commercial: Caitlin expects to start with the customer success team and fill the 40 licensed users over time. That is headroom, and a first dashboard through the dashboards builder would show value early.

Watch: Priscilla is the sole admin and agreed to name a backup by the next check-in. Usage data belongs to engineering, and Priscilla has no direct access to it.

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

Themes

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

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Priscilla Bowen to name a backup admin by the next check-in.
  • Ingrid Solberg to create the Snowflake database and role by the end of the week so Hamza Akhtar can start connecting on Monday.
  • Hamza Akhtar to send the written plan with owners and the source list straight after the call.

Risks

Current to 9 Oct 26
  • Priscilla is the only admin and has no backup yet, a single point of failure for the Growth setup.
  • Product usage data is owned by engineering and Priscilla has no direct access, so that source may arrive late.
  • Ingrid's gate means no connector goes live until she approves the source and its role, so slow approval delays value.

Opportunities

Current to 9 Oct 26
  • Forty licensed users on Growth leave headroom as the team widens beyond customer success.
  • The dashboards builder gives Caitlin an early visible win from helpdesk and CRM data.
  • A usage connector would give the per-distributor picture Caitlin asked for.

Transcript

  1. Hollie Grieve
    Hollie Grieve None
    Hello, everyone. Can you all hear me? Caitlin, I can see you, Priscilla, Ingrid, and Hamza's here from our side.
  2. Caitlin Mercer
    Caitlin Mercer None
    Hi Hollie! Yep, all good. We're all in the room except Ingrid, who's just dialling in.
  3. Ingrid Solberg
    Ingrid Solberg None
    I'm here. Sorry, I was finishing something. Good afternoon.
  4. Hamza Akhtar
    Hamza Akhtar None
    Afternoon all. Hamza here. I'll be the person doing the technical side of the implementation, so you'll probably get sick of me.
  5. Hollie Grieve
    Hollie Grieve None
    Right, thanks for making time. The plan for the next hour or so: first a quick recap of what you've bought and what the contract looks like, then the sources we're going to connect and who owns each, then access and security, and finally what happens in the next couple of weeks. Does that work?
  6. Caitlin Mercer
    Caitlin Mercer None
    Works for me. Let's go.
  7. Hollie Grieve
    Hollie Grieve None
    So you're on Growth. The contract started on 1 April 2026 and runs to 31 March 2027, with renewal on 1 April 2027. It's fifty thousand pounds a year, £50,000, and there are forty licensed users. The first thing I'd say is, don't worry about the renewal for now. But I do like to put the date on the table, because everything we do in the first few months is aimed at that conversation being easy.
  8. Caitlin Mercer
    Caitlin Mercer None
    Love that, because that's literally why we bought this. Renewals were a surprise. I want to be on the front foot with our own distributors, so I appreciate you thinking the same way about us.
  9. Hollie Grieve
    Hollie Grieve None
    Of course. Growth also gives you quarterly reviews with me, and the dashboards builder, which I think Caitlin will like.
  10. Caitlin Mercer
    Caitlin Mercer None
    Yes. Can we get that on a dashboard is basically my whole job description.
  11. Priscilla Bowen
    Priscilla Bowen None
    She does say it a lot.
  12. Caitlin Mercer
    Caitlin Mercer None
    I do. Okay, so what's the signal we want, and where does it come from?
  13. Hamza Akhtar
    Hamza Akhtar None
    Good question to start on. So, Caitlin, you told us in the earlier conversations that the picture you want per distributor is tickets, product usage and the renewal calls, all together. Let me play that back, and tell me if I've got it wrong.
  14. Hamza Akhtar
    Hamza Akhtar None
    The helpdesk gives us the tickets. Your CRM gives us the accounts, the contacts and the renewal dates. The call recorder gives us the calls. And then there's product usage, which I think comes from your own application data. Is that right? And is there anything else you'd put on that list that I haven't mentioned?
  15. Priscilla Bowen
    Priscilla Bowen None
    That's most of it. The usage side is the one I'd worry about. It sits in a database that engineering owns, and I don't have direct access. So I'd need to bring someone from that team in.
  16. Hamza Akhtar
    Hamza Akhtar None
    That's a useful thing to know now. Usage is often the long pole. Would you be able to find out who owns it, and whether they'd be willing to expose a view for us, rather than give us the whole thing?
  17. Priscilla Bowen
    Priscilla Bowen None
    I think so. I'll ask this week. Probably one of the data engineers, and I'd need Ingrid to agree to how it's shared.
  18. Ingrid Solberg
    Ingrid Solberg None
    Yes, that's where I come in. Before we go further, can I ask the basic question? Where does the data live, and who can see it?
  19. Hamza Akhtar
    Hamza Akhtar None
    Sure. So the brain is built and runs inside your own Snowflake account. We don't copy your data out to a store of our own. You create a database and a role for it, you decide what that role can read, and we work within that.
  20. Ingrid Solberg
    Ingrid Solberg None
    And you work within it how? Is there a BB-Demo person logging in?
  21. Hamza Akhtar
    Hamza Akhtar None
    During implementation, me, yes, using access you grant. You can see in your own Snowflake what I run, because it's your account. When we're finished, you can narrow it or remove it, and the brain carries on for your users.
  22. Ingrid Solberg
    Ingrid Solberg None
    Okay. That's better than most of what I see. I'd still want to review the list of sources before anything connects, and I'd want to see the roles written down. Not as an obstacle, just so it's on record.
  23. Hollie Grieve
    Hollie Grieve None
    Completely reasonable. Hamza, can you put that into the plan as a step in its own right? Sources reviewed by Ingrid before any connector goes live.
  24. Hamza Akhtar
    Hamza Akhtar None
    Yes. I'll write it as a gate. Nothing connects until you've said yes to the source and the role it reads with.
  25. Ingrid Solberg
    Ingrid Solberg None
    Thank you. That's what I wanted to hear.
  26. Caitlin Mercer
    Caitlin Mercer None
    Can I come in on the people side for a second? Who's actually going to use it, and who's the admin?
  27. Hollie Grieve
    Hollie Grieve None
    Good, because it's the part people leave till last. You've got forty licensed users. Caitlin, who's in the first group?
  28. Caitlin Mercer
    Caitlin Mercer None
    My whole customer success team first. Account managers, the renewals people, and the support leads who look after the biggest distributors. After that, probably a handful from sales and finance who want to see renewal risk. I don't think we fill all forty on day one. But I'd rather have headroom than be asking for more in a month.
  29. Hollie Grieve
    Hollie Grieve None
    That's sensible. Starting with the CS team gives us the best chance of people actually asking questions, and we can widen after a few weeks.
  30. Priscilla Bowen
    Priscilla Bowen None
    And I'm the admin. I'll be the one adding people and looking after the setup, day to day.
  31. Hollie Grieve
    Hollie Grieve None
    Great. One thing I always say, Priscilla, and it's not a criticism of anyone: it helps to have a second person who can do what you do. If you're away, or if you move on, you don't want it to be a single point of failure.
  32. Priscilla Bowen
    Priscilla Bowen None
    No, that's fair. Let me think about who. I could probably pull in someone from the ops side.
  33. Caitlin Mercer
    Caitlin Mercer None
    Put it on the list. Priscilla, name a backup by the next check-in.
  34. Priscilla Bowen
    Priscilla Bowen None
    Done. Backup admin, by the next check-in.
  35. Hamza Akhtar
    Hamza Akhtar None
    Okay. Let me do the sequence, because I think we've got most of the pieces. First week, Ingrid creates the database and the role in Snowflake, and approves the first sources. Then the helpdesk and the CRM, because those are the quickest and give you something to look at. Then the call recorder. Usage comes in when engineering is ready, and I'd rather not hold the rest of it up waiting.
  36. Caitlin Mercer
    Caitlin Mercer None
    I like that. Value early, then add. What will we actually be able to see once the helpdesk and the CRM are in?
  37. Hamza Akhtar
    Hamza Akhtar None
    You'll be able to ask things like which distributors have had the most tickets recently, or which have a renewal coming and an open complaint. It won't be the full picture, but it'll be the first time that sits in one place.
  38. Caitlin Mercer
    Caitlin Mercer None
    That's the demo I wanted. Okay, great.
  39. Ingrid Solberg
    Ingrid Solberg None
    One more from me. The nightly refresh. If something fails, does anyone tell us, or do we find out when someone gets a stale answer?
  40. Hollie Grieve
    Hollie Grieve None
    You'll see it in the brain, and I'll see it too. The refresh is meant to be finished by seven in the morning, your local time, on business days. If a source stops loading, that's something we pick up and raise with you. But to be straight, Ingrid, if the change is on your side, a system being changed or a login expiring, we may find out after you do. So tell us when you change something.
  41. Ingrid Solberg
    Ingrid Solberg None
    That's fair. I'll make sure change notices include you. I'd rather that than the alternative.
  42. Priscilla Bowen
    Priscilla Bowen None
    Is there a shared place where we can see the plan? I don't want to be hunting through email for what's happening.
  43. Hollie Grieve
    Hollie Grieve None
    Hamza will send the written plan after this, with owners against every step, and I'll keep it current. If anything moves, you'll see it there.
  44. Hamza Akhtar
    Hamza Akhtar None
    Yes. Owner, date, status. Nothing clever.
  45. Caitlin Mercer
    Caitlin Mercer None
    Love it. Okay, who's doing what? Let me read back. Ingrid: Snowflake database and role, and review the sources. Priscilla: find who owns usage, and name a backup admin. Me: confirm the first group of users. Hamza: the written plan. Hollie: the check-in. Did I miss anything?
  46. Hollie Grieve
    Hollie Grieve None
    That's everything. I'd add one date. Let's get the Snowflake access done by the end of this week, so Hamza can start connecting on Monday.
  47. Ingrid Solberg
    Ingrid Solberg None
    That's doable. If I've got the source list in writing today or tomorrow.
  48. Hamza Akhtar
    Hamza Akhtar None
    I'll send it straight after the call, so you'll have it this afternoon.
  49. Hollie Grieve
    Hollie Grieve None
    Brilliant. Thanks, all. This has been a really good start. We'll speak again in a fortnight or so, and sooner if anything gets stuck.
  50. Caitlin Mercer
    Caitlin Mercer None
    Thanks Hollie, thanks Hamza. Best, everyone.
  51. Priscilla Bowen
    Priscilla Bowen None
    Thanks all.
  52. Ingrid Solberg
    Ingrid Solberg None
    Thanks. 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