Vellacott Payments / BB-Demo – Onboarding
Callcompleted
Vellacott Payments: documents · 2025-09-05 09:00
First onboarding call with Vellacott Payments. Tomasz wants one view of each client across partnerships, onboarding and complaints. Network policy approval is the open blocker; owners and dates were agreed for each action.
What was said
What this says
Current to 11 Oct 26First onboarding call with Vellacott Payments. Tomasz wants one view of each client across partnerships, onboarding and complaints. Network policy approval is the open blocker; owners and dates were agreed for each action.
What happened: Hamza Akhtar reviewed three actions with Tomasz Wiśniewski and Femi Olatunji. Access to the Snowflake warehouse is mostly done, with the network policy still awaiting security approval.
Customer view: Tomasz wants one place to ask about a client and see partnerships, merchant onboarding and complaints together. He wants the minimum fields indexed first because of compliance.
Commercial: The customer is licensed for a hundred and fifty users and starts with a handful. Adoption is early, so value depends on a clean first connector and training.
Watch: A stuck approval or a CRM field rename could stall a connector. Femi agreed to warn BB-Demo before changing a system.
Themes
Current to 9 Oct 26Theme
Onboarding access and connectors
Importance
neutral
Sentiment
positive
Voice
decision-maker
Who was there
BB-Demo
CRMmade from
Them
CRMmade from
Follow-up
Next steps
Current to 9 Oct 26- Femi Olatunji attaches the network policy the same day and sends the helpdesk field list by Wednesday.
- Hamza Akhtar configures the first connector by the end of the week and runs a test load on one client.
- Tomasz Wiśniewski sends the team leads list so Hamza can book training.
Risks
Current to 9 Oct 26- Network policy approval by the customer's security team could delay access to the warehouse.
- A CRM field rename could stop a connector loading unnoticed.
- Only a handful of users are active, so early value depends on the first connector and training.
Opportunities
Current to 9 Oct 26- A joined-up client view across partnerships, merchant onboarding and complaints gives a clear value case.
- Team leads and wider staff are planned next, which would grow usage within the licensed seats.
Transcript
Hamza Akhtar NoneMorning, Tomasz. Can you hear me alright?
Tomasz Wiśniewski NoneLoud and clear. Morning, Hamza. Femi is just joining, I think he is fighting with the link.
Femi Olatunji NoneHi, sorry, the meeting room booking clashed with my own calendar. Morning both.- Hamza Akhtar NoneNo problem at all, we're all here now. Good week so far?
- Tomasz Wiśniewski NoneBusy. Always busy. Let me be concrete and start with the three actions from last time. One, Femi sorts the access to our warehouse in Snowflake so you can create the brain's schema. Two, I send you the list of marketplace clients and how we group them. Three, you send us the connector plan. What's the owner for each, and where are we?
- Hamza Akhtar NoneGood, that's the right order. I'll take the third one first because it's mine. The plan went over on Tuesday, a short document, and it lists the sources in the order I'd suggest we connect them.
- Tomasz Wiśniewski NoneI saw it. I have comments, but later. Femi, access.
- Femi Olatunji NoneYeah, so that's done, mostly. The role is created and the warehouse is assigned. What I haven't done is the network policy, because our security team wanted to look at it again before I attach it.
- Tomasz Wiśniewski NoneMostly is not done. What's the owner of the network policy?
- Femi Olatunji NoneMe, and a colleague in security approves. I'll chase them today. They already signed off the review when we bought, so this should be a formality.
- Hamza Akhtar NoneThat's right, nothing in the policy changes what we agreed in the security review. Everything runs inside your Snowflake account, so there's no data leaving. It's really just a matter of the role being able to read the schemas you choose.
- Tomasz Wiśniewski NoneGood. We close this today. Femi, tell Hamza when it's attached, same day.
- Femi Olatunji NoneSame day, yes.
- Hamza Akhtar NoneBrilliant. So on to the second action. Tomasz, the client list. I got it yesterday, thank you. It's very clear how you group by marketplace and by payroll bureau.
- Tomasz Wiśniewski NoneThat grouping is the whole point for us. Partnerships, merchant onboarding, complaints. Each team sees a piece of a client today. I want one place where I ask about a client and I see all three.
- Hamza Akhtar NoneUnderstood, and that's what we'll build the first pages around. So here's what I'd propose for the order. First the CRM, because it has your client records and your partnership owners. Second the helpdesk, which is where complaints land. Third the call recorder, then the mailboxes later once we've seen the first two working.
- Femi Olatunji NoneCan I ask something on the helpdesk? Some of our complaints tickets carry regulated fields. Customer names, sometimes more. Do we have to bring all of those in?
- Hamza Akhtar NoneNo, you choose. Each connector has a field list, and you can leave out anything you don't want indexed. My suggestion is we start with the minimum, look at the answers, and add fields if a question needs them.
- Tomasz Wiśniewski NoneYes. Minimum first. I don't want to explain to compliance why we indexed something we never used.
- Femi Olatunji NoneFine by me. I'll write the field list for the helpdesk and send it to you, Hamza. Give me until Wednesday.
- Hamza Akhtar NoneWednesday works. Then I can have the first connector configured before the end of the week, and we do a test load into a small slice.
- Tomasz Wiśniewski NoneA slice of what? Be concrete.
- Hamza Akhtar NoneSorry, yes. One marketplace client and its records. If the picture looks right for that one, we widen it to the rest. It's much easier to check one client by eye than the whole book.
- Tomasz Wiśniewski NoneGood. Take the biggest marketplace client, because it has the most mess, and mess will tell us the most. Femi, you know which one.
- Femi Olatunji NoneI do. I'll put the name in the email with the field list.
- Hamza Akhtar NoneNow users. You're licensed for a hundred and fifty, which is plenty for what you described, so there's no pressure on that. I'd like to start with a small group, the people who will test the pages, and widen in a few weeks.
- Tomasz Wiśniewski NoneRight now it's a handful of us. Me, Femi, a couple of people from complaints, someone from merchant onboarding. I want the team leads in next, and the rest when we've trained them. Which brings training.
- Hamza Akhtar NoneYes. Once the first connector is loading, I'll set up a session for the group, walking through search, chat and the pages on your own data. Not slides. Daniel will join as your customer success manager so he knows what you've been shown.
- Tomasz Wiśniewski NoneGood. I like that Daniel is there. Last point from me. What can go wrong in the first month? Tell me honestly.
- Hamza Akhtar NoneHonestly, two things. One, access gets stuck waiting on an approval, which we've just talked about. Two, a source changes shape, say someone renames a field in the CRM, and a connector stops loading until we notice. So tell us before you change a system, and we'll tell you if a connector stops.
- Femi Olatunji NoneThat's fair. We do change the CRM fields from time to time. I'll tell you before, it's easier.
- Tomasz Wiśniewski NoneGood. Let me summarise so nothing floats. Femi: network policy today, helpdesk field list by Wednesday, name of the first client. Hamza: configure the first connector by the end of the week, test load on one client, then book the training. Me: team leads list. Correct?
- Hamza Akhtar NoneCorrect, and I'll send that as a short note after the call so it's written down.
- Tomasz Wiśniewski NonePerfect. Thanks both. Cheers, Tomasz.
- Femi Olatunji NoneThanks, speak soon.
- Hamza Akhtar NoneCheers, both. Speak soon.
Callsmade from