Hamza Akhtar

Vellacott Payments / BB-Demo – Onboarding

Callcompleted

Vellacott Payments: documents logo Vellacott Payments: documents · 2025-07-25 13:15

Onboarding call with Tomasz Wiśniewski and Femi Olatunji. CRM and helpdesk go first, the onboarding tracker sheet second. A small group of users starts while the data is checked, ahead of any wider invite.

What was said

What this says

Current to 11 Oct 26

Onboarding call with Tomasz Wiśniewski and Femi Olatunji. CRM and helpdesk go first, the onboarding tracker sheet second. A small group of users starts while the data is checked, ahead of any wider invite.

What happened: Femi has admin access and sees an empty account until the first connector is live. Tomasz will send the client list and arrange a merchant onboarding lead to sit with Femi.

Customer view: Tomasz restated the purpose: partnerships, merchant onboarding and complaints should see each client whole. He does not want anyone judging a half-empty brain.

Watch: Onboarding status sits partly in a shared sheet that Tomasz admits is not a proper system. Hamza Akhtar called it the least stable kind of source, so it follows the CRM and helpdesk.

Commercial: The pilot is about five people against a 150 user licence, so seat headroom is large. SSO is expected early, pending the IT colleague.

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

Themes

Current to 9 Oct 26
Theme
Onboarding and first connectors
Importance
neutral
Sentiment
neutral
Voice
champion

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Femi Olatunji provides CRM and helpdesk credentials by Tuesday.
  • Tomasz Wiśniewski arranges the merchant onboarding lead to sit with Femi by Wednesday.
  • Hamza Akhtar configures the connectors and runs the first refresh once credentials arrive.

Risks

Current to 9 Oct 26
  • The onboarding tracker is an unstable shared sheet and needs a merchant onboarding lead to explain its columns.
  • A slow first sync or a half-empty brain could damage first impressions with the pilot users.
  • SSO timing depends on an IT colleague who has not yet agreed a date.

Opportunities

Current to 9 Oct 26
  • Pilot of about five users on a 150 user licence leaves clear room to widen once the first load is checked.
  • Access groups mapped on top of Snowflake roles give a reason for a follow-up working session.

Transcript

  1. Hamza Akhtar
    Hamza Akhtar None
    Hello, can you both hear me alright?
  2. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Yes, loud and clear. Good afternoon, Hamza. Femi is just joining, I can see him in the lobby.
  3. Femi Olatunji
    Femi Olatunji None
    Sorry, sorry. Previous meeting overran. I'm here now. Can you hear me? My headset was being difficult.
  4. Hamza Akhtar
    Hamza Akhtar None
    Perfectly fine. Afternoon, Femi. Lovely, that's everyone. How's the week been?
  5. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Busy. Friday, so everybody is trying to close things before the weekend. But good. Let me be concrete and start with the three actions from last time, if that is okay.
  6. Hamza Akhtar
    Hamza Akhtar None
    Please do. I've got them written down but I'd rather hear them from you.
  7. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    One, Femi gets admin access to the Snowflake account for the brain, so he can see what is being created. Two, we send you the list of marketplace clients we want to see first. Three, we decide which systems connect first. Femi, where are we on one?
  8. Femi Olatunji
    Femi Olatunji None
    One is done. I got the role approved on Monday, and I've logged in and looked around. It's quite empty at the moment, which I assume is expected.
  9. Hamza Akhtar
    Hamza Akhtar None
    Yes, that's expected. You'll see the schemas and the warehouse we set up, but nothing is loaded until the first connector goes live. So that's what today is really for.
  10. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Two, the client list. I have it. It's a short list, the marketplace clients where complaints and onboarding issues have been hardest to see together. I will send it today. What's the owner? Me. Today.
  11. Hamza Akhtar
    Hamza Akhtar None
    Great. That helps, because I'd like the first load to be built around those clients rather than everything at once.
  12. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Exactly. We bought this so partnerships, merchant onboarding and complaints see each client whole. Not three teams, three spreadsheets.
  13. Hamza Akhtar
    Hamza Akhtar None
    Right. So that's the third action, then. Which sources feed that picture? I'd suggest we think in three groups: the CRM for the client and contract side, the helpdesk for tickets and complaints, and then wherever your onboarding status lives.
  14. Femi Olatunji
    Femi Olatunji None
    Onboarding status is the awkward one. Some of it is in the CRM, and some is in a tracker the merchant onboarding team keeps. It's not a proper system, honestly. It's more of a shared sheet that has grown.
  15. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    It is a sheet. I will not pretend. But it is the truth for onboarding, so we cannot skip it.
  16. Hamza Akhtar
    Hamza Akhtar None
    No, understood. We can bring a sheet in, but it's the least stable kind of source, so my suggestion is we start with the CRM and helpdesk, prove the shape, and add the tracker second. Does that sit right?
  17. Femi Olatunji
    Femi Olatunji None
    That sounds sensible to me. The CRM and helpdesk have proper service accounts already, so I can sort credentials quickly. The tracker I'd want to tidy first anyway.
  18. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Good. Who tidies the tracker? Femi?
  19. Femi Olatunji
    Femi Olatunji None
    I can do the structure. But somebody from merchant onboarding needs to confirm what the columns actually mean. I don't want to guess.
  20. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Fine. I will ask the lead for merchant onboarding to sit with you for an hour. That is my action. By Wednesday.
  21. Hamza Akhtar
    Hamza Akhtar None
    Brilliant. Let me write that down. So, Tomasz, the lead from merchant onboarding with Femi, by Wednesday.
  22. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Yes.
  23. Hamza Akhtar
    Hamza Akhtar None
    Now, a couple of things from our side so nobody is surprised. You're on Enterprise, so the security review is behind us, and the plan assumes your single sign-on is switched on early. Femi, is that something your identity people are expecting?
  24. Femi Olatunji
    Femi Olatunji None
    They know it's coming. A colleague in IT is the person for that, and I'll introduce them to you by email. They want to see the settings page before they agree a date.
  25. Hamza Akhtar
    Hamza Akhtar None
    Sure, I'll send the configuration notes so they have something to read beforehand. Do you want users provisioned automatically, or by hand to start with?
  26. Femi Olatunji
    Femi Olatunji None
    Automatically, eventually. By hand at first, I think. We have only a handful of people using it right now, and I'd like to watch what they ask before we open it to the whole licence.
  27. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Agreed. Five or so people now is the right size. Partnerships operations, two from complaints, and Femi. We grow after the first load works.
  28. Hamza Akhtar
    Hamza Akhtar None
    That's a sensible way to do it. You've got room for one hundred and fifty users on the licence, so there's no pressure on numbers. The pressure is on the data being right.
  29. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Yes. I do not want anyone asking questions of a half-empty brain and deciding it is useless. First impressions, they stick.
  30. Hamza Akhtar
    Hamza Akhtar None
    I completely agree. So I'd rather hold the wider invite until we've loaded the clients on your list and run a few test questions together. Does that fit with your timeline?
  31. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Yes, if the first load is next week. Is that realistic, Femi?
  32. Femi Olatunji
    Femi Olatunji None
    Credentials for the CRM and helpdesk by Tuesday. Then it's down to how long the first sync takes. I'd not promise more than that.
  33. Hamza Akhtar
    Hamza Akhtar None
    That's honest and it's fine. Once the credentials are in I can have the connectors configured the same day, and the first refresh will run overnight. You'd see records in the morning.
  34. Femi Olatunji
    Femi Olatunji None
    Overnight, okay. Will it be finished by the morning? Our people start early.
  35. Hamza Akhtar
    Hamza Akhtar None
    The nightly refresh is meant to be complete by seven in the morning on business days. The very first load can take longer because it's pulling history, so I'd treat the first one as a bonus and the second one as the real test.
  36. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Good. Let me be concrete, then. Tuesday: credentials, Femi. Wednesday: tracker conversation, me. Tuesday or Wednesday: client list, me, today actually. Hamza: configuration and first refresh. Next call, we look at real data.
  37. Hamza Akhtar
    Hamza Akhtar None
    That's exactly my list as well. I'll put it in an email this afternoon so it's in writing, with owners.
  38. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Please. We close this today.
  39. Femi Olatunji
    Femi Olatunji None
    One question before we finish. Where do the permissions live? If complaints can see something onboarding shouldn't, is that managed in the brain or in Snowflake?
  40. Hamza Akhtar
    Hamza Akhtar None
    Good question. Both, really. The data sits in your Snowflake account, so your own roles apply underneath, and the brain adds access groups on top. I'd suggest we map those together on the next call rather than rush it now.
  41. Femi Olatunji
    Femi Olatunji None
    Fine by me. I'll draft who should see what and bring it.
  42. Tomasz Wiśniewski
    Tomasz Wiśniewski None
    Good. Hamza, thank you. Femi, thank you. Cheers, speak next week.
  43. Hamza Akhtar
    Hamza Akhtar None
    Thanks both. Have a good weekend. 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