Hamza Akhtar

Vellacott Payments / BB-Demo – Onboarding

Callcompleted

Vellacott Payments: documents logo Vellacott Payments: documents · 2025-08-01 12:45

Onboarding call on 1 Aug 2025. Tomasz wants each marketplace client seen whole and starts with five users on Enterprise. Complaints data has no confirmed owner, and Femi is a single point of failure for the technical side.

What was said

What this says

Current to 11 Oct 26

Onboarding call on 1 Aug 2025. Tomasz wants each marketplace client seen whole and starts with five users on Enterprise. Complaints data has no confirmed owner, and Femi is a single point of failure for the technical side.

What happened: Hamza walked through three actions. Snowflake access is closed, the source ranking is in the plan, and the complaints data owner is still open.

Customer view: Tomasz said seeing each marketplace client whole is the point of this purchase. He is keeping the start small on purpose, with about five users, until the answers are good.

Commercial: The customer is licensed for 150 users on Enterprise, so there is wide headroom. Single sign-on and group provisioning are needed before widening, and Femi has not yet looked at those settings.

Watch: Femi owns every technical item and has no deputy. The compliance owner of the complaints system had not confirmed access, so Tomasz took that on himself.

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

Themes

Current to 9 Oct 26
Theme
Enterprise onboarding owners
Importance
neutral
Sentiment
positive
Voice
decision-maker

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Femi writes the compliance paragraph today and Tomasz forwards it to compliance.
  • Femi sends the CRM service account and object list, and names a deputy before the next session.
  • Hamza Akhtar sends the recap and the status page link, and books the next session.

Risks

Current to 9 Oct 26
  • The complaints system owner in compliance has not confirmed access, so the complaints load could slip.
  • Femi is the owner for every technical item and has no deputy for the data side.
  • Single sign-on and group provisioning are not yet looked at, which could slow widening beyond the first users.

Opportunities

Current to 9 Oct 26
  • Widening from about five users towards the 150 licensed users once the answers are trusted.
  • Complaints, onboarding and partnership data on one client page is the stated purpose of the purchase.

Transcript

  1. Hamza Akhtar
    Hamza Akhtar None
    Hello, can you both hear me alright? I can see Tomasz, Femi I've got you as audio only so far.
  2. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Yes, loud and clear. Good afternoon, Hamza.
  3. Femi Olatunji
    Femi Olatunji None
    Hi, sorry, camera's being difficult. Give me a second. Right, is that better?
  4. Hamza Akhtar
    Hamza Akhtar None
    There you are. Brilliant. Good afternoon. How's your Friday going, anything exciting before the weekend?
  5. Femi Olatunji
    Femi Olatunji None
    Quiet, honestly. Everyone's half gone already because of the heat. The office is basically empty.
  6. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    I am here, so I work. Okay, let me be concrete. Three actions from last time. One, Snowflake access for your team. Two, the list of sources in priority order. Three, an owner for every source. Hamza, where are we?
  7. Hamza Akhtar
    Hamza Akhtar None
    Good, let's go through them in that order. Access first. Femi, you set up the role for us earlier this week, yes?
  8. Femi Olatunji
    Femi Olatunji None
    Yes, done on Tuesday. The role can create objects in the schema we agreed and nothing outside it. Our security team looked at the grants and they're happy. I sent you the details.
  9. Hamza Akhtar
    Hamza Akhtar None
    I saw it, thank you. I logged in yesterday and everything's where it should be. So that one's closed from our side.
  10. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Good. We close this today. Next.
  11. Hamza Akhtar
    Hamza Akhtar None
    Next is the source list. Tomasz, you sent the ranking on Monday and I've put it into the plan. Partnerships data first, so the CRM and the contract store, then merchant onboarding, and complaints last because it has the most moving parts.
  12. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Yes. And let me say why. If I see each marketplace client whole, I can see the complaint and the onboarding issue next to the commercial relationship. That is the point of this purchase. So partnerships first, but complaints must not slip to the end of the year.
  13. Hamza Akhtar
    Hamza Akhtar None
    Understood. I wouldn't let it slip. Because you're on Enterprise you have plenty of room on connectors, so we can load complaints in parallel if the owner side is ready. That's really the question for the third action.
  14. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Owners. Okay. Femi, you have the sheet.
  15. Femi Olatunji
    Femi Olatunji None
    I do, yes. So, partnerships CRM, that's Tomasz as the business owner and me as the technical one. Merchant onboarding, the business owner is the team lead in onboarding, and I'm still the technical contact. Complaints, hmm, that one's the gap.
  16. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    What's the gap exactly? What's the owner?
  17. Femi Olatunji
    Femi Olatunji None
    There's a person who runs the complaints queue day to day, but the system belongs to a colleague in compliance, and she hasn't confirmed she's happy for us to pull from it. I asked on Wednesday and haven't had an answer.
  18. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    No. We don't leave this floating. I will speak to compliance myself this afternoon. Femi, you send me one paragraph of what we need from them, and I forward it. Today.
  19. Femi Olatunji
    Femi Olatunji None
    Fine, I'll write it straight after this call.
  20. Hamza Akhtar
    Hamza Akhtar None
    That helps a lot. It's also worth saying in the paragraph that the data stays in your Snowflake account. It's usually the first worry from a compliance team, so it's better to say it up front.
  21. Femi Olatunji
    Femi Olatunji None
    Yes, good point. I'll put that in the first line.
  22. Hamza Akhtar
    Hamza Akhtar None
    Okay. Let me share my screen and show you the connector plan so we're all looking at the same thing. Can you see it?
  23. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Yes, I see a table.
  24. Hamza Akhtar
    Hamza Akhtar None
    That's the one. Each row is a source, with the owner, the credentials we need, and a target for when it's live. For partnerships I'd like the first load running by the middle of next week, so you can ask the brain something real before the month is out.
  25. Femi Olatunji
    Femi Olatunji None
    What do you need from me for that? Just a service account for the CRM?
  26. Hamza Akhtar
    Hamza Akhtar None
    A service account with read access, yes, and the list of objects you want included. If you're unsure, start narrow. It's much easier to add objects than to explain later why something was loaded that shouldn't have been.
  27. Femi Olatunji
    Femi Olatunji None
    Yeah, that's sensible. Narrow to start. So accounts, contacts, the partner agreements, and then we see.
  28. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Add the renewal fields for the clients too. I want to see the contract date next to the complaint history.
  29. Femi Olatunji
    Femi Olatunji None
    Right, the renewal fields. Noted.
  30. Hamza Akhtar
    Hamza Akhtar None
    Now users. You're licensed for a hundred and fifty, and I know it will be nowhere near that at the start. We have around five people active at the moment. Is that about what you expected?
  31. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Yes. Five is my team and Femi. It's a small start on purpose. I want the answers to be good before I invite the other teams. Bad first impressions are very hard to fix.
  32. Hamza Akhtar
    Hamza Akhtar None
    I completely agree. When you do widen it, we'll want single sign-on and group provisioning switched on first, so you're not adding people by hand. Femi, who owns that on your side?
  33. Femi Olatunji
    Femi Olatunji None
    That's me again, I'm afraid. Well, the identity team does the directory, but I'd be the one asking them. I haven't looked at the settings yet.
  34. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Femi, you are owner for everything. This is a risk. What's the owner if you are on holiday?
  35. Femi Olatunji
    Femi Olatunji None
    Fair. Yeah. I don't have a deputy for the data side. I could name someone from the platform team, but I'd have to ask first.
  36. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Then ask. Name a deputy by the next call. Hamza, put it in the plan as an action with Femi's name.
  37. Hamza Akhtar
    Hamza Akhtar None
    Done, it's in. Deputy admin, owner Femi, due before the next session.
  38. Hamza Akhtar
    Hamza Akhtar None
    Let me flag one more thing, and then I'll let you go. The nightly refresh. On Enterprise it's complete by seven in the morning your time on business days, and that's what we'll monitor. If you ever see the brain answering with yesterday's picture, tell us straight away, because that's a freshness question and we want to catch it early.
  39. Femi Olatunji
    Femi Olatunji None
    Okay. Is there somewhere I can see when the last refresh finished?
  40. Hamza Akhtar
    Hamza Akhtar None
    Yes, there's a status page in the admin area, and I'll send you the link with the recap. It also shows records indexed per source, so a flat line is easy to spot.
  41. Femi Olatunji
    Femi Olatunji None
    Perfect, that's what I wanted.
  42. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Good. Let me summarise so there is no confusion. Femi writes the compliance paragraph today, I forward it today. Femi sends the CRM service account and object list. Femi asks for a deputy. Hamza sends the recap and the status page link. Correct?
  43. Hamza Akhtar
    Hamza Akhtar None
    That's exactly it. I'll add the next session to your calendars, a couple of weeks from now, and we'll look at what's loaded and what people are asking.
  44. Femi Olatunji
    Femi Olatunji None
    Sounds good. Thanks, Hamza.
  45. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Thank you. Have a good weekend. Cheers, Tomasz.
  46. Hamza Akhtar
    Hamza Akhtar None
    You too, speak soon. Bye both.

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