Hamza Akhtar

Vellacott Payments / BB-Demo – Onboarding

Callcompleted

Vellacott Payments: documents logo Vellacott Payments: documents · 2025-08-06 11:30

Onboarding call on 6 Aug 2025. Connector order agreed, CRM first. Complaints head will own the data once she understands what happens to case notes, and the CRM has duplicate marketplace clients.

What was said

What this says

Current to 11 Oct 26

Onboarding call on 6 Aug 2025. Connector order agreed, CRM first. Complaints head will own the data once she understands what happens to case notes, and the CRM has duplicate marketplace clients.

What happened: Hamza confirmed the connector order, with the finance system last because of access questions. Femi's service account exists, but the network policy still needs security review.

Customer view: Tomasz said he wants the five-person team plus Femi only, and nobody else until the data is right. The complaints head is willing to own the data but worries about free-text case notes.

Commercial: Hamza pointed to the Enterprise field scoping and in-account data as the answer. That is a direct use of what was sold, and he offered a short call with her.

Watch: Duplicate marketplace clients in the CRM undercut the whole-client view. Single sign-on approach is undecided, and the refresh must wait for late customer batch jobs.

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

Themes

Current to 9 Oct 26
Theme
Connector order, complaints ownership
Importance
neutral
Sentiment
positive
Voice
decision-maker

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Hamza Akhtar sets up a short call with the complaints head and sends the field scoping notes.
  • Femi completes the security paperwork today and pulls the worst duplicates list by Friday.
  • Femi brings the single sign-on decision to the next call.

Risks

Current to 9 Oct 26
  • Complaints head has not signed off as owner until she understands how case notes are used.
  • Network policy review by the customer's security team is still open, which blocks the CRM load.
  • Duplicate marketplace clients in the CRM could give a fragmented picture.

Opportunities

Current to 9 Oct 26
  • Enterprise field scoping and in-account data directly answer the complaints head's concern.
  • A small trusted group of five plus Femi can be the base for wider rollout across the 150 licensed users.

Transcript

  1. Hamza Akhtar
    Hamza Akhtar None
    Hello, can you hear me alright?
  2. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Yes, loud and clear. Morning, Hamza. Femi is just joining, I can see him in the lobby.
  3. Femi Olatunji
    Femi Olatunji None
    Morning, sorry, I was stuck on another call. Is my audio okay? I've got a new headset.
  4. Hamza Akhtar
    Hamza Akhtar None
    Sounds fine to me. Bit grey in London today, is it the same where you are?
  5. Femi Olatunji
    Femi Olatunji None
    Same. Rain on the window, which is at least a reason to stay in.
  6. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Okay. Let me be concrete, because I like to start with the three actions from last time. One, Femi confirms the service account inside Snowflake. Two, Hamza sends the order of connectors. Three, I name an owner for the complaints data. Where are we?
  7. Hamza Akhtar
    Hamza Akhtar None
    I can take mine first. The connector order went over yesterday afternoon, it should be in your inbox. I put the CRM first, then the helpdesk, then the call recorder, and the finance system last.
  8. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Yes, I have it. Why finance last?
  9. Hamza Akhtar
    Hamza Akhtar None
    Mostly because it has the most questions about who can see what. Payments data is sensitive, and I'd rather we have the access model settled before we load anything from there. The others are lower risk, so they give us a quick win.
  10. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Fine. I agree. Femi?
  11. Femi Olatunji
    Femi Olatunji None
    So, the service account. Yes and no. It's created, it has the role, and I tested it on a small schema. What I haven't done is the network policy side, because our security team want to look at it again, since we're a regulated firm.
  12. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    What's the owner of that? Who in security?
  13. Femi Olatunji
    Femi Olatunji None
    A colleague in our security team. I'll chase them today, they were fine with the principle during the review before we signed. It's just paperwork now.
  14. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Good. We close this today, then. Femi, send me a note when it's done, even one line.
  15. Femi Olatunji
    Femi Olatunji None
    Will do.
  16. Hamza Akhtar
    Hamza Akhtar None
    And Tomasz, the third one, the complaints data owner?
  17. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Yes. It's the head of our complaints team. I spoke to her on Monday. She is happy to be the owner but she wants to understand what the brain will do with the case notes before she signs off. Free text, you know, sometimes names, sometimes details we don't want floating around.
  18. Hamza Akhtar
    Hamza Akhtar None
    That's a fair worry, and it's what the Enterprise controls are for. We can scope which fields get indexed, and the whole thing runs inside your Snowflake account, so the data doesn't leave your environment. I can show her that on a short call if that helps.
  19. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Yes, please. Let's do that. Femi, can you join as well? She'll have technical questions.
  20. Femi Olatunji
    Femi Olatunji None
    Sure, put it in the diary.
  21. Hamza Akhtar
    Hamza Akhtar None
    Right. Let me share my screen and walk through the setup plan, so we're all looking at the same thing. Can you see it?
  22. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Yes, I see the table.
  23. Hamza Akhtar
    Hamza Akhtar None
    Okay. So there are three phases. First, the foundation: the account, the roles, the first connector. Second, the connectors in the order I sent. Third, the people side, which is single sign-on, provisioning and getting teams onto it. You're licensed for one hundred and fifty users, so provisioning matters.
  24. Femi Olatunji
    Femi Olatunji None
    On the single sign-on, our identity team is still deciding between two approaches. I don't want to promise a date.
  25. Hamza Akhtar
    Hamza Akhtar None
    That's fine, it's the last phase anyway. We don't need it for the first users, they can come in with invitations. I'd just like to know the approach a couple of weeks before we get there.
  26. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Femi, owner for that decision?
  27. Femi Olatunji
    Femi Olatunji None
    Me, with our identity team. I'll get you an answer by the next call.
  28. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Good. Write it down, Hamza.
  29. Hamza Akhtar
    Hamza Akhtar None
    Written. Now, for the first connector, the CRM. Femi, what's the state of the data there? Anything odd I should know about before we point the brain at it?
  30. Femi Olatunji
    Femi Olatunji None
    Honestly, it's decent for accounts and contacts. The partner fields are messy. Marketplace clients have been entered a few different ways over the years, so you will see duplicates. Same client, slightly different names.
  31. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    That's the main reason I wanted this. Each marketplace client seen whole. If we have three versions of one client, the brain will show three half pictures.
  32. Hamza Akhtar
    Hamza Akhtar None
    Understood. We don't have to fix it before loading. What I'd suggest is that we load it as it is, look at what the duplicates actually look like, and then decide whether you clean at source or we map them. Cleaning at source is better in the long run, but it shouldn't block us.
  33. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Agreed. Femi, can you pull a list of the worst ones? Not all, just the worst.
  34. Femi Olatunji
    Femi Olatunji None
    Yeah, I can do a rough query. Give me until Friday.
  35. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Friday. Okay.
  36. Hamza Akhtar
    Hamza Akhtar None
    Let me show you what the first load will look like, so it's less abstract. This is a demo space, not your data, but the shape is the same. Each client gets a page, and under it you see calls, emails, tickets, and the questions people asked about it.
  37. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Mm. And the complaints sit on that same page?
  38. Hamza Akhtar
    Hamza Akhtar None
    Once the helpdesk or whichever system holds them is connected, yes. That's the idea of the Enterprise setup you bought, partnerships, onboarding and complaints looking at one client together.
  39. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Good. That is exactly the picture. Let me be concrete about who uses it first. Five people in my team, plus Femi. Nobody else until the data is right.
  40. Hamza Akhtar
    Hamza Akhtar None
    That's sensible. Small group, quick feedback. I'd rather have five people who trust it than a hundred and fifty who tried it once.
  41. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Ha, yes. Exactly.
  42. Femi Olatunji
    Femi Olatunji None
    Hamza, one technical thing. For the nightly refresh, when exactly does it run? Our batch jobs finish late sometimes and I don't want you reading half-written tables.
  43. Hamza Akhtar
    Hamza Akhtar None
    Good question. The refresh is meant to be finished by seven in the morning, your local time, on business days. So if your batch lands before it starts, we're fine. If it runs late, we should talk, and we can look at a dependency so it waits.
  44. Femi Olatunji
    Femi Olatunji None
    Okay, mine normally finishes well before then. I'll watch it for a week and tell you if there's drift.
  45. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Good. So, summary. Femi, security paperwork today, identity decision by next call, duplicates list by Friday. Hamza?
  46. Hamza Akhtar
    Hamza Akhtar None
    I load the CRM connector once the network policy is confirmed, and I set up the short call with your complaints head. I'll also send the field scoping notes so she has something to read first.
  47. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    And me, I confirm the complaints owner once she's seen the scoping. Right. Anything else?
  48. Femi Olatunji
    Femi Olatunji None
    Not from me.
  49. Hamza Akhtar
    Hamza Akhtar None
    Nothing here. Thanks both, that was useful.
  50. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Cheers, Hamza. 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.

HelpAsk B

Ask B

B-Brain · read-only