Vellacott Payments / BB-Demo – Demo
Callcompleted
Vellacott Payments: documents · 2025-03-27 15:00
Demo for Vellacott Payments. Tomasz Wiśniewski liked sourced answers and the handover use case. Femi Olatunji probed Snowflake permissions and freshness. Pricing sits with Philippa Gore, who was not on the call.
What was said
What this says
Current to 11 Oct 26Demo for Vellacott Payments. Tomasz Wiśniewski liked sourced answers and the handover use case. Femi Olatunji probed Snowflake permissions and freshness. Pricing sits with Philippa Gore, who was not on the call.
What happened: Anya Petrova demonstrated a sample marketplace client with complaints, onboarding and partnership history on one page. Tomasz and Femi Olatunji tested Snowflake permissions, freshness, access groups and connectors.
Customer view: Tomasz liked answers that show their sources and named handover from onboarding as a key use. A day-old refresh suits complaints review; fraud holds are out of scope.
Commercial: Priya restated the Enterprise tier at £129,000 total, implementation included. Tomasz said pricing is Philippa's and he will ask her for a call, probably late April.
Watch: Permissions detail is owed before the proposal. A custom payments ledger connector needs scoping with a committed live date.
Themes
Current to 9 Oct 26Theme
Enterprise demo, Snowflake fit
Importance
neutral
Sentiment
positive
Voice
champion
Who was there
BB-Demo
CRMmade from
Them
CRMmade from
Follow-up
Next steps
Current to 9 Oct 26- Anya Petrova sends the Snowflake permissions detail, the nightly refresh note and the access groups document.
- Femi Olatunji sends the ledger table description without sensitive columns.
- Tomasz Wiśniewski confirms a proposal call date with Philippa Gore, and Priya Raman then sets out the proposal.
Risks
Current to 9 Oct 26- Philippa Gore owns the commercial decision and was not on the call, so Tomasz must carry the case to her.
- A nightly refresh may fall short for fraud holds, which Tomasz placed out of scope.
- The payments ledger is a custom source and needs schema review before a live date can be committed.
Opportunities
Current to 9 Oct 26- Handover from onboarding to partnerships was named a key use, strengthening the Enterprise case.
- Single sign-on and SCIM answered the access question, supporting the Enterprise tier.
Transcript
Priya Raman NoneHello, hello. Can everyone hear me alright? Good afternoon.
Tomasz Wiśniewski NoneYes, we hear you. Good afternoon, Priya.
Anya Petrova NoneHi all, Anya here. Is the audio okay on my side as well?- Tomasz Wiśniewski NoneFine, yes. Femi will join in a minute. He is finishing a data load, so he is a little late.
- Priya Raman NoneNo problem at all. How's the week been, Tomasz? Still raining over there?
- Tomasz Wiśniewski NoneRaining, yes. And busy. Complaints are up this month, so this is good timing, honestly.
- Priya Raman NoneRight, that's useful context. So, quick recap of where we are, just to keep momentum. We did discovery with you a few weeks back, today is the demo, and the next step is a proposal. The date we have pencilled in for getting this over the line is 26 Jun 2025, and I'm happy to make that easy, so shout if the timing is wrong.
- Tomasz Wiśniewski NoneOkay. Let me be concrete about what we want to see today. One, a single marketplace client seen whole: onboarding, partnership notes, complaints, all together. Two, how fast a question gets an answer. Three, how it sits in our Snowflake. What's the owner for the Snowflake part? That will be Femi.
- Priya Raman NonePerfect. Anya, over to you, you've got all three covered.
- Anya Petrova NoneYes. Let me share my screen. Bear with me a second. Can you see the browser window?
- Tomasz Wiśniewski NoneYes, we see it.
Femi Olatunji NoneSorry, sorry, I'm here. Femi. I missed the start, carry on.- Anya Petrova NoneHi Femi, no worries. I'll start with the part that probably matters most to you. The brain is built and run inside your own Snowflake account. Nothing is copied out to us. The data stays where it is, and we sit on top of it.
- Femi Olatunji NoneOkay. So which role does it use? Does it need write access to our existing schemas?
- Anya Petrova NoneGood question. It gets its own schema and its own role. Read access to what you point it at, and it writes only into its own space. I'd rather show you the permissions screen in the security review than wave my hands now.
- Femi Olatunji NoneFine. Yes. We will need that in writing anyway.
- Tomasz Wiśniewski NoneFemi, write that down. Action, permissions detail, owner Anya, before the proposal. Yes?
- Anya Petrova NoneYes, I'll send it after the call.
- Anya Petrova NoneRight, so this is a sample marketplace client in the demo environment. Think of it as one of yours. On the left you see the connected sources: the CRM, call recordings, the email threads, the support tickets, and finance. Everything about this one client is on one page.
- Tomasz Wiśniewski NoneThis is the part. Show me the complaints next to onboarding. Because now my team opens three systems and still guesses.
- Anya Petrova NoneSure. So here, the timeline. Onboarding steps, then the partnership calls, then the complaints as they came in. And I can just ask it. Let me type: which complaints from this client mention delayed payouts, and what did we tell them?
- Anya Petrova NoneThere. You get the answer, and under it the sources it used, so you can click through to the actual ticket or the actual email. It does not just assert.
- Tomasz Wiśniewski NoneMm. That I like. Sources, yes. Our compliance people will insist on that.
- Priya Raman NoneAnd that's the regulatory conversation Philippa will want to have, so it's good you're seeing it now.
- Tomasz Wiśniewski NonePhilippa will ask about the regulatory angle first, yes. Always. But the detail she delegates to me.
- Femi Olatunji NoneCan I ask about freshness? If a ticket is closed at four in the afternoon, when does the brain know?
- Anya Petrova NoneThere's a nightly refresh, finished before seven in the morning your time on business days. So the brain is a day behind at worst. It's not live streaming. If you need something fresher for a particular source we'd talk about it in scoping.
- Femi Olatunji NoneA day is okay for complaints review. Maybe not for fraud holds. But that's not this project.
- Tomasz Wiśniewski NoneCorrect. Not this project. Let me be concrete, fraud is out of scope.
- Anya Petrova NoneNoted. Out of scope.
- Anya Petrova NoneOkay, next. Dashboards. This is the builder. Say you want, for each marketplace client, open complaints, onboarding stage and last partnership contact. You drag those in, name it, and it's shared with whoever you choose.
- Tomasz Wiśniewski NoneWho can see which client? Merchant onboarding should not see everything. What's the owner of access?
- Anya Petrova NoneAccess follows teams. On Enterprise there's single sign-on and SCIM, so groups come from your identity provider. Femi would set it up with us, and your side owns who is in which group.
- Femi Olatunji NoneOkay. That works. I would own the groups, yes.
- Tomasz Wiśniewski NoneGood. Femi owns groups.
- Priya Raman NoneCan I just jump in, Anya? Tomasz, from what you've seen so far, is there a gap, anything you'd want to see that we haven't shown?
- Tomasz Wiśniewski NoneOne. A handover. When a client moves from onboarding to the partnerships team, we lose context. Can the brain show what was promised during onboarding?
- Anya Petrova NoneIt can. Let me try with the sample. Give me a moment, I'll ask: what commitments were made to this client during onboarding?
- Anya Petrova NoneSo it pulls from the call notes and the emails. It lists three things, with the dates, and again the sources. It's not perfect, I'd always want a person to check it, but it's a much better starting point than a blank page.
- Tomasz Wiśniewski NoneA better starting point is what I need. Good. We close this today: yes, handover is a key use.
- Femi Olatunji NoneOne more technical. Connectors. How long does it take to bring a new source in? Say our payments ledger.
- Anya Petrova NoneDepends on the source. Standard ones, days. A custom ledger, I'd want to look at the schema first. That goes into the plan with a committed live date, so it's not a vague promise.
- Femi Olatunji NoneOkay. I can send you a description of the ledger tables. Without sensitive columns.
- Anya Petrova NonePlease do. That helps a lot.
- Priya Raman NoneWhile you're on that, I'll say where the commercial side is heading, so there's no surprise. We're talking the Enterprise tier for you, and the deal value is £129,000 in total, implementation included. I'll set it all out in the proposal. Tomasz, I know pricing is Philippa's, so I'll take that with her.
- Tomasz Wiśniewski NoneYes. I don't argue the commercial terms. That's Philippa. But I will tell her what I saw today.
- Priya Raman NoneGreat. Would a short call with her in a few weeks work, to walk through the proposal?
- Tomasz Wiśniewski NoneI will ask her. Probably late April. I'll come back to you by Monday. Owner, me.
- Anya Petrova NoneLet me stop sharing there and recap. Three things on my side: the permissions detail for the Snowflake role, a note on the nightly refresh timing, and a short document on how access groups work with single sign-on. Femi sends the ledger table description.
- Femi Olatunji NoneYes. Tomorrow.
- Tomasz Wiśniewski NoneAnd I confirm the date with Philippa by Monday. That's the three actions plus one. Good.
- Priya Raman NoneBrilliant, thanks everyone. Really useful. Speak soon.
- Tomasz Wiśniewski NoneThank you. Cheers, all.
- Anya Petrova NoneBye, all.
Callsmade from