Veenendrecht Payments / BG-Demo – Kickoff
Callcompleted
Veenendrecht Payments · 10 Feb 2026 09:30
Kickoff for the Growth tier signed on 5 Feb 2026. Security Officer Fleur Jansen needs permissions, a data flow description and an incident contact before approving the first connector. A high priority ticket waits on her decision.
What was said
What this says
As at Fri 9 Oct 2026Kickoff for the Growth tier signed on 5 Feb 2026. Security Officer Fleur Jansen needs permissions, a data flow description and an incident contact before approving the first connector. A high priority ticket waits on her decision.
What happened: Laura Penhaligon confirmed the Growth term to 4 Feb 2027 and forty licensed users. Elena Novak set four actions: names, permission list, data flow description and Fleur's review.
Customer view: Eline Bakker wants each merchant's disputes, tickets and volumes on one page, with the helpdesk connector the priority. Fleur needs to explain the setup to the supervisor and wants to be told in writing when BG-Demo's named list changes.
Commercial: Nothing is live yet, so early value depends on Fleur's approval. The open high priority ticket is the access request for the service role, waiting on her permissions decision.
Watch: Pieter, who covers outsourcing, is not on the call and Eline will not commit anything for him.
Themes
As at Fri 9 Oct 2026Theme
Kickoff and security approval
Importance
neutral
Sentiment
positive
Voice
champion
Who was there
BG-Demo
CRMmade from
Them
CRMmade from
Follow-up
Next steps
As at Fri 9 Oct 2026- Eline Bakker sends the four names for first access on the day of the call.
- Elena Novak sends Fleur the permission list with a reason for each permission.
- Laura Penhaligon drafts the data flow description for Fleur and Eline to correct.
Risks
As at Fri 9 Oct 2026- The first connector cannot go live until Fleur Jansen has the permissions, data flow description and incident contact.
- The high priority access ticket stays open until her permissions decision.
- Outsourcing sign-off by Pieter is not committed.
Opportunities
As at Fri 9 Oct 2026- Helpdesk tickets beside disputes can show value early within what Growth includes.
- Forty licensed users leave room for merchant success and merchant risk together.
Transcript
Elena NovakGood morning, everyone. Thank you for joining. Can everyone hear me?
Eline BakkerGood morning, Elena. Yes. Laura, Fleur, hello.
Fleur JansenGood morning. I can hear you. My camera is slow, but it should arrive.
Laura PenhaligonMorning all. Laura here, from the implementation side. Nice to finally put faces to names.- Elena NovakThank you. As I wrote in the agenda I sent beforehand, we have four items. One, the scope and the people. Two, the connectors and the order we connect them. Three, security and access. Four, the next steps and owners. To confirm, we have about an hour.
- Eline BakkerBefore the agenda, let me check last time's actions. We said we would name who from my team gets access first. I have that. Four names, and I will send them today.
- Elena NovakThank you, Eline. As agreed, I will record that as the first action.
- Laura PenhaligonGood, that's helpful. So, scope. Veenendrecht signed on Thursday 5 February 2026 for the Growth tier, and the term runs to 4 Feb 2027. That gives you forty licensed users and the connectors that come with Growth. Does that match what you expected?
- Eline BakkerYes. Forty users is enough for merchant success and merchant risk together, with some room. What I need is practical: each merchant's disputes, tickets and volumes on one page.
- Laura PenhaligonRight, and that's what we build towards. Which sources hold those three things today? Disputes and volumes, I assume, come from the payments platform. Tickets from your helpdesk?
- Eline BakkerYes. Tickets from the helpdesk, and merchant records from the CRM. Disputes and volumes sit in our own platform, and that is already in Snowflake.
- Laura PenhaligonThat's good news. If the platform data is already in your Snowflake account, that one is the easiest, because the brain runs inside that account. We don't copy anything out.
- Fleur JansenCan I stop you there? That is my first question. When you say inside our account, who can see what? I need to be able to explain it to the supervisor.
- Laura PenhaligonOf course. The brain is deployed in your Snowflake account, under your roles. We use a service role that you create and control. You decide which schemas it can read, and you can remove it at any time.
- Fleur JansenSo we create the role, not you.
- Laura PenhaligonCorrect. We give you the list of permissions we need, and you grant them. Nothing is granted by us.
- Elena NovakTo confirm, I will make sure that the permission list reaches Fleur in writing, with the reason for each permission. I will send it after this call.
- Fleur JansenGood. And the list of people on your side who can touch our environment. I will want names, and I will want to know when somebody leaves.
- Elena NovakAs agreed, we will provide the names, and we will tell you in writing when the list changes. I will make sure that this is in the onboarding notes.
- Eline BakkerFleur, let's make it practical. What do you need before the first connector goes live? A list of what, and by when?
- Fleur JansenI need the permissions, the data flow description, and the incident contact. If I have those, I can approve the first connector. Without them, I cannot.
- Laura PenhaligonThen those go first, ahead of any connector work. I'd rather you approved the setup than found out afterwards.
- Elena NovakItem two, then. The connectors. Laura, could you propose an order?
- Laura PenhaligonYes. I'd start with the platform data, since it's already in Snowflake. Second, the helpdesk, because tickets beside disputes is the thing Eline asked for first. Third, the CRM for the merchant records. After that we add whatever else you want, within what Growth includes.
- Eline BakkerAgreed. The helpdesk is the one I care about most. We have one ticket open with you already, about getting access set up. Is that linked?
- Laura PenhaligonIt is. That's the one marked high priority, and it's the access request for the service role. It's waiting on Fleur's permissions decision, which is exactly why those go first.
- Fleur JansenUnderstood. So that ticket is waiting for me. I will take that.
- Eline BakkerGood. Who owns the next step? Fleur has the permissions. Who has the data flow description?
- Laura PenhaligonI do. I'll draft it from what we've just said and send it to Fleur and Eline for correction. Better that you tell me what's wrong than that I guess.
- Fleur JansenYes. Please include where the answers are stored, and for how long.
- Laura PenhaligonWill do. If I can't answer something precisely, I'll say so in the note and come back to you.
- Elena NovakItem four, then. To confirm, the actions are as follows. One: Eline sends the four names today. Two: I send Fleur the permission list with reasons. Three: Laura sends the data flow description. Four: Fleur reviews both and tells us what she needs changed. Is that correct?
- Eline BakkerYes. And Pieter should see the outsourcing side. I will not commit anything for him, but I will tell him where we are.
- Elena NovakThank you. I will send written actions within the hour, and we will review them together at the start of the next call.
- Fleur JansenThat works for me. Thank you, both.
- Eline BakkerThanks everyone. Groetjes.
- Laura PenhaligonThanks all. Speak soon.
- Elena NovakThank you. Kind regards from us both.
Callsmade from