Vellacott Payments / BB-Demo – Kickoff
Callcompleted
Vellacott Payments: documents · 2025-07-17 14:30
Kickoff for Vellacott Payments' Enterprise build. Tomasz Wiśniewski wants complaints data first and a staged rollout. Samuel Adeyemi, the CISO, wants role definitions in writing, SSO via their identity provider and free text left out.
What was said
What this says
Current to 11 Oct 26Kickoff for Vellacott Payments' Enterprise build. Tomasz Wiśniewski wants complaints data first and a staged rollout. Samuel Adeyemi, the CISO, wants role definitions in writing, SSO via their identity provider and free text left out.
What happened: Hamza Akhtar confirmed the contract started on 10 Jul 2025 with a licence for up to 150 users. The call agreed six actions, each with an owner.
Customer view: Tomasz wants complaints first so he hears of an unhappy marketplace client before the account manager does. He also said his people are "curious, not yet convinced", so early trust depends on loaded data.
Security: Samuel set conditions: role definitions in writing before creation, SSO through their identity provider, and no free text until the data protection lead replies. Nothing is switched on until he has answered.
Commercial: Staged rollout leaves seat headroom under Enterprise and shows who owns adoption. The call does not show what happened at the 9 Jul 2026 subscription end date.
Themes
Current to 9 Oct 26Theme
Enterprise kickoff and security
Importance
neutral
Sentiment
neutral
Voice
champion
Who was there
BB-Demo
CRMmade from
Them
CRMmade from
Follow-up
Next steps
Current to 9 Oct 26- Hamza Akhtar sends role definitions to Samuel Adeyemi before anything is created.
- Hamza Akhtar sends the connector plan with dates to all attendees by the following Monday.
- Daniel Okafor reports back to Samuel Adeyemi by the end of the following week on the open retention question.
Risks
Current to 9 Oct 26- A half-loaded brain opened too widely could cost early trust, which Tomasz named himself.
- Security sign-off by the CISO gates every connector, so delays on role definitions or SSO stall the build.
- Free-text complaints fields stay out until the data protection lead replies, which limits the first load.
Opportunities
Current to 9 Oct 26- Complaints data first gives the fastest visible value for the partnerships team.
- A phased rollout across teams leaves room to use more of the 150 Enterprise seats.
Transcript
Daniel Okafor NoneGood afternoon, everyone. Thank you all for making the time. Let me just check who's here. Tomasz, I can see you. Samuel, is that you coming in now?
Samuel Adeyemi NoneYes, hello. Sorry, I was finishing a call. I can hear you fine.
Hamza Akhtar NoneHello, both. Hamza here, I'm the implementation consultant, so I'll be the one living in your Snowflake account for the next few weeks. Daniel's your customer success manager and will be with you after that.
Tomasz Wiśniewski NoneGood afternoon. Let me be concrete, so we don't waste time. Three things I want out of today. One, which sources go first. Two, who owns each one. Three, what the security team needs before you touch anything. Yes?- Daniel Okafor NoneThat's a perfect frame, Tomasz. Hamza, shall we use those as the agenda?
- Hamza Akhtar NoneYes, let's do that. Before we start, just to confirm where we are. The contract started on 10 Jul 2025, Enterprise, so you have the licence for up to 150 users, and the subscription runs to 9 Jul 2026. Today is the start of the build.
- Tomasz Wiśniewski NoneGood. We know the date. What's the first source?
- Hamza Akhtar NoneThat's for you to tell me, really. From the sales conversations, the idea is that partnerships, merchant onboarding and complaints each see one client in one place. So I'd think the CRM first, then the helpdesk, then the call recorder. Does that match?
- Tomasz Wiśniewski NoneMostly. Complaints first, actually. Honestly. If a marketplace client is unhappy, I want to know before the account manager does. Then the CRM, then onboarding records.
- Daniel Okafor NoneI like that. It starts with the thing that hurts most, which usually gets people using it fastest. How is the team finding the sandbox, by the way? Sorry, I mean the early access. A few of your people have already logged in.
- Tomasz Wiśniewski NoneYes, a handful. They're curious, not yet convinced. They don't have data in it, so what do they see? Nothing. That's why I want the complaints data in first.
- Hamza Akhtar NoneFair. That's exactly what I'd expect. So, let's treat complaints as the first connector. Who owns the helpdesk on your side? Someone I can ask for access and for a view of the fields.
- Tomasz Wiśniewski NoneThe head of complaints owns the helpdesk. I'll introduce you today, by email. And what's the owner on your side for that connector? I want a name.
- Hamza Akhtar NoneMe. I own the connector until it's live and you've signed it off. Then it passes to Daniel for the ongoing running.
- Tomasz Wiśniewski NoneGood. That's an owner.
- Samuel Adeyemi NoneCan I come in on that? Before any connector, I need to be clear about access. The service account. What does it read, what can it write?
- Hamza Akhtar NoneRead only on the source systems. Nothing is written back. The brain itself runs inside your Snowflake account, so the data doesn't leave your environment. The roles and the warehouse are yours to approve.
- Samuel Adeyemi NoneThat was the point in the review, yes. But I want to see the role definitions in writing before they are created. Not afterwards.
- Daniel Okafor NoneOf course, Samuel. Just to close the loop on that: Hamza will send the role definitions to you before anything is created, and nothing is switched on until you've replied. Is that right, Hamza?
- Hamza Akhtar NoneYes, absolutely. I'd rather wait a day than have you find out later.
- Samuel Adeyemi NoneGood. That's how I'd like to run it.
- Samuel Adeyemi NoneSecond thing. Single sign-on. Enterprise includes it, I believe. We will not issue passwords to staff, it must go through our identity provider.
- Hamza Akhtar NoneYes, SSO and SCIM are both part of Enterprise. I'll need someone from your IT team to work through the setup with me. It's a short session, usually.
- Samuel Adeyemi NoneA colleague in IT will do that. I'll name them by the end of the week.
- Tomasz Wiśniewski NoneSamuel, 'by the end of the week' is fine, but give me a day. Which day?
- Samuel Adeyemi NoneFriday. You'll have the name on Friday.
- Tomasz Wiśniewski NoneThank you. We close this today.
- Daniel Okafor NoneTomasz, can I ask about the users? You have up to 150 seats, but I'd guess you won't open it to everyone at once. How were you thinking of rolling it out?
- Tomasz Wiśniewski NoneNot everyone. Partnerships operations first, then complaints, then merchant onboarding. Maybe the account managers last. I don't want a hundred people asking questions of a brain that has half the data. They'll lose trust in a week.
- Daniel Okafor NoneThat's wise, and it matches what I've seen elsewhere. Trust is quite fragile in the first month. We could also agree a few questions in advance that you know the answer to, so people can test it against what they already know.
- Tomasz Wiśniewski NoneYes. Yes, good. Let me write ten of them. Sorry, a short list. I'll send it to you and Hamza.
- Hamza Akhtar NoneThat would be really useful, I can check the data against them as I go.
- Samuel Adeyemi NoneOne more, then I'll stop. Retention. Complaints data has personal information in it. What happens to that inside the brain?
- Hamza Akhtar NoneIt stays in your account under your own policies. I'd suggest we don't copy free-text fields in the first load, and add them once you've told us what the rules are. Is that sensible?
- Samuel Adeyemi NoneYes, that's sensible. Leave the free text out for now. I'll ask our data protection lead to look at it and come back.
- Daniel Okafor NoneThank you, Samuel. I'll note that as open and I'll come back to you by the end of next week with where we are.
- Tomasz Wiśniewski NoneGood. Hamza, can you read back the actions, with owners? I want them in the room.
- Hamza Akhtar NoneYes. Tomasz introduces me to the head of complaints today. Samuel names the IT colleague for single sign-on on Friday. Samuel receives the role definitions from me before anything is created. Tomasz sends the short list of test questions. Free-text fields are left out of the first load until your data protection lead has replied. And I'll send a connector plan, with dates, to all of you by Monday.
- Tomasz Wiśniewski NoneGood. That's six, each with an owner. Thank you, Hamza.
- Daniel Okafor NoneThank you all, really. I'll be in touch next week. Enjoy the rest of your afternoon.
- Samuel Adeyemi NoneThank you. Goodbye.
Callsmade from