Hamza Akhtar

Pemaquid Analytics / BB-Demo – Onboarding

Callcompleted

Pemaquid Analytics: documents logo Pemaquid Analytics: documents · 2026-05-05 16:00

On the 5 May 2026 onboarding call Caitlin Mercer said she needs evidence of what the fifty thousand a year buys before she promises the board anything. Source access, name mapping and a pilot group were agreed.

What was said

What this says

Current to 11 Oct 26

On the 5 May 2026 onboarding call Caitlin Mercer said she needs evidence of what the fifty thousand a year buys before she promises the board anything. Source access, name mapping and a pilot group were agreed.

What happened: Hamza Akhtar, Caitlin Mercer and Priscilla Bowen agreed connector access, a distributor name mapping template and a small first user group. Caitlin played the actions back at the end.

Customer view: Caitlin wants one view per distributor and wants renewals to stop being a surprise. She will not promise the board anything without evidence.

Commercial: The contract started on 1 Apr 2026 with 40 users licensed, and the renewal is on 1 Apr 2027. Questions asked and usage by person were agreed as the value signals for the first quarterly review.

Watch: Differing distributor names across systems will need Priscilla's mapping work. Hamza warned that one person asking most questions is a risk in itself.

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

Themes

Current to 9 Oct 26
Theme
Value evidence before renewal
Importance
renewal
Sentiment
mixed
Voice
decision-maker

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Priscilla Bowen gets a service user created for the call recorder.
  • Hamza Akhtar sends the permissions note and mapping template, then holds a working session with Priscilla on Monday afternoon.
  • Caitlin Mercer picks the first group of people and their questions before that session.

Risks

Current to 9 Oct 26
  • Caitlin Mercer needs evidence of value for the fifty thousand a year before she will back it to the board.
  • Distributor names differ between systems, which could weaken the one view per distributor.
  • Usage is mostly Priscilla Bowen, so value could sit with one person.

Opportunities

Current to 9 Oct 26
  • A pilot group of the team closest to renewals could grow use across the 40 licensed users.
  • Questions asked and usage by person give a clear value story for the first quarterly review.

Transcript

  1. Hamza Akhtar
    Hamza Akhtar None
    Hi both, can you hear me all right?
  2. Priscilla Bowen
    Priscilla Bowen None
    Yep, loud and clear. Hi Hamza.
  3. Caitlin Mercer
    Caitlin Mercer None
    Hey! Sorry, give me one second, I'm changing rooms. Okay. I'm here. Good afternoon.
  4. Hamza Akhtar
    Hamza Akhtar None
    Afternoon, Caitlin. Good to have you both on the same call at last. How's the week treating you?
  5. Caitlin Mercer
    Caitlin Mercer None
    Busy. We've got a stack of renewals landing this month and a couple of them I'm not loving, so I'm in that mode. Which is exactly why I'm excited about this. This is the thing that's supposed to stop renewals being a surprise.
  6. Hamza Akhtar
    Hamza Akhtar None
    That's a good way to frame it, and it's what I'd like to anchor today on. So the plan for the next forty minutes or so: where we are, which sources we connect first, who looks after what on your side, and how we get your team in using it.
  7. Caitlin Mercer
    Caitlin Mercer None
    Love it. What's the signal, though? Like, when we're done, how do I know it's working?
  8. Hamza Akhtar
    Hamza Akhtar None
    Fair. I'd suggest two things. One, the data is loading and staying fresh, so the brain is actually seeing each distributor's tickets, usage and renewal calls. Two, people are asking it real questions. The second one is the one that tells you whether it's valuable.
  9. Caitlin Mercer
    Caitlin Mercer None
    Okay, yes. Questions asked. Can we get that on a dashboard?
  10. Hamza Akhtar
    Hamza Akhtar None
    You can. Growth includes the dashboards builder, so Priscilla can put that together once there's something to count. Right now it would be a very short line.
  11. Priscilla Bowen
    Priscilla Bowen None
    Ha. It's basically me in there at the moment. I've been clicking around and asking it a few things, mostly to see what it does with our distributor names.
  12. Hamza Akhtar
    Hamza Akhtar None
    That's completely normal at this stage. Contract started on 1 Apr 2026, the brain is running inside your Snowflake account, and you're licensed for 40 users, so there's a lot of headroom. The job is to fill it sensibly rather than all at once.
  13. Caitlin Mercer
    Caitlin Mercer None
    Right, and I'm very conscious that we're on the hook for fifty thousand a year, £50k, so I need to be able to say what we got for it. I'm not going to promise the board anything without evidence.
  14. Hamza Akhtar
    Hamza Akhtar None
    Understood. And the renewal isn't until 1 Apr 2027, so you've got a full year to build that evidence. I'd rather we have a clean story by the first quarterly review than a rushed one.
  15. Caitlin Mercer
    Caitlin Mercer None
    Good. Okay. So where are we with the sources?
  16. Hamza Akhtar
    Hamza Akhtar None
    Priscilla, you may want to jump in here. The CRM is connected and loading. The helpdesk and the call recorder are the two that matter most for your use case, and those are what I'd like to finish this week and next. Where did you get to on access?
  17. Priscilla Bowen
    Priscilla Bowen None
    So the helpdesk I can do, I'm an admin there. The call recorder, I need to ask our ops lead to create a service user, because I don't want to connect it with my own login and have it break when my password rotates.
  18. Hamza Akhtar
    Hamza Akhtar None
    Good instinct. A dedicated service user is the right way. I'll send you a short note on the permissions it needs, read access is enough, so you can hand it to them as it is.
  19. Priscilla Bowen
    Priscilla Bowen None
    Perfect. That saves me writing it.
  20. Caitlin Mercer
    Caitlin Mercer None
    Can I ask something slightly different? Because the whole point for me is one view per distributor. If I open a distributor, I want tickets, usage and the last renewal conversation in one place. Is that what this does out of the box, or is that work?
  21. Hamza Akhtar
    Hamza Akhtar None
    A bit of both, honestly. The pages and the chat do the joining for you, but the joining depends on the distributor being recognised the same way in every system. If one is called the full legal name in the CRM and a nickname in the helpdesk, we have to tell it they're the same.
  22. Priscilla Bowen
    Priscilla Bowen None
    Oh, that's going to be us. We have a few where the name differs between systems. Some have a parent group and a local depot.
  23. Caitlin Mercer
    Caitlin Mercer None
    Yeah, that's the messy part. Okay. Let's operationalise it, then. Who owns the mapping?
  24. Hamza Akhtar
    Hamza Akhtar None
    I'd say Priscilla owns it day to day, because she knows the data, and I'll sit with her to do the first pass. Then it becomes a thing she maintains when a new distributor is added.
  25. Caitlin Mercer
    Caitlin Mercer None
    Priscilla, are you okay with that? It's more than I'd like to drop on you without checking.
  26. Priscilla Bowen
    Priscilla Bowen None
    Yeah, no, it's fine. It's what I'd be doing by hand anyway. I'd just like a list of what it needs from me so I'm not guessing.
  27. Hamza Akhtar
    Hamza Akhtar None
    I'll send a simple template after this. One row per distributor, the name as each system knows it, and the person on your side who looks after them.
  28. Caitlin Mercer
    Caitlin Mercer None
    Great. Now users. I've got my team of, what, about a dozen people who'd live in this. I don't want to give it to everyone and have it be a ghost town in a month.
  29. Hamza Akhtar
    Hamza Akhtar None
    Agreed, so my suggestion is a small first group. Pick the people who are closest to renewals, give them a handful of questions they actually ask every week, and let them try it for a fortnight. Then widen.
  30. Caitlin Mercer
    Caitlin Mercer None
    Okay. So like, which distributors are at risk this quarter and why. That kind of thing.
  31. Hamza Akhtar
    Hamza Akhtar None
    Exactly that. And once the helpdesk and the calls are in, it can answer it from tickets and what people said on calls, not just from the CRM stage.
  32. Priscilla Bowen
    Priscilla Bowen None
    Is there a way to see who's asking what? Because Caitlin will want to know, and I'd want to know if it's all one person.
  33. Hamza Akhtar
    Hamza Akhtar None
    Yes, as an admin you can see usage by person. It's worth watching, because if one person is asking most of the questions, that's a risk in itself. It means the value sits with them.
  34. Caitlin Mercer
    Caitlin Mercer None
    Right, I like that. That's the signal. I'll want that in the first review.
  35. Hamza Akhtar
    Hamza Akhtar None
    Noted. One thing on freshness so nobody's caught out: the refresh runs overnight and should be done by seven in the morning your time on business days. If the first load looks a day behind, that's usually the reason.
  36. Priscilla Bowen
    Priscilla Bowen None
    Good to know. I'd have panicked.
  37. Caitlin Mercer
    Caitlin Mercer None
    Okay, so let me play it back. Priscilla gets the service user for the call recorder. Hamza sends the permissions note and the mapping template. Priscilla and Hamza do a working session on the distributor names. And I pick the first group of people and their questions. Did I miss anything?
  38. Hamza Akhtar
    Hamza Akhtar None
    That's it. I'd add that I'll check the helpdesk is loading cleanly before our next session, so we're not debugging live. Priscilla, would early next week work for the working session?
  39. Priscilla Bowen
    Priscilla Bowen None
    Monday afternoon works for me.
  40. Caitlin Mercer
    Caitlin Mercer None
    Great. I'll send you my list of names before that. Thanks, both, this was useful.
  41. Hamza Akhtar
    Hamza Akhtar None
    Thanks, Caitlin, thanks Priscilla. Speak on Monday.
  42. Priscilla Bowen
    Priscilla Bowen None
    Cheers, Hamza. Bye.

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