Veldmaat Payments / BG-Demo – Onboarding
Callcompleted
Veldmaat Payments · 2 Feb 2026 10:00
Joost Verbeek said the third connector is late and that the merchant risk team and account managers will not use the brain until the refresh is reliable. Two people use a 40-user contract: not the value they bought.
What was said
What this says
As at Fri 9 Oct 2026Joost Verbeek said the third connector is late and that the merchant risk team and account managers will not use the brain until the refresh is reliable. Two people use a 40-user contract: not the value they bought.
What happened: Yusuf Demir reported on the connectors and the refresh with Joost Verbeek and Sanne Bakker. The accounting connector is not built because the service user is still with the customer's IT.
Customer view: Joost said this is not what he expected by now and that two users on 40 is not the value bought. Sanne counted three misses in two weeks and said two good mornings is not a pattern.
Commercial: Joost stated for the record that adoption waits on a reliable refresh. Yusuf changed the page size and moved the Zendesk load earlier.
Watch: Joost is escalating with IT and wants the accounting mapping within a few working days of the service user existing. Yusuf declined to discuss commercial matters.
Themes
As at Fri 9 Oct 2026Theme
Value doubt, unreliable refresh
Importance
complaint
Sentiment
negative
Voice
decision-maker
Who was there
BG-Demo
CRMmade from
Them
CRMmade from
Follow-up
Next steps
As at Fri 9 Oct 2026- Joost Verbeek escalates the service user with the customer's IT on 2 Feb 2026.
- Yusuf Demir builds the accounting mapping within a few working days of the service user existing.
- Yusuf checks the merchant duplicates after that night's load and Elena Novak sends the written actions.
Risks
As at Fri 9 Oct 2026- Joost Verbeek said two users on a 40-user contract is not the value bought, which puts the renewal case at risk.
- Refresh misses at 07:00 keep the merchant risk team and account managers away from the brain.
- The accounting connector is late and depends on the customer's IT creating a service user.
Opportunities
As at Fri 9 Oct 2026- A reliable refresh and the third connector would open the way to rolling out to account managers and merchant risk.
Transcript
Yusuf DemirHello. Yusuf here. Can you hear me?
Sanne BakkerYes.
Joost VerbeekGood morning, Yusuf. I can hear you. Sanne is with me in the room, so you may get a little echo.- Yusuf DemirNo echo on my side. Thanks for making time. I will start with where things are. The HubSpot connector, last good load was this morning, finished before seven. Zendesk, last good load also this morning. Row count is higher than last week, because of the history.
- Joost VerbeekBefore we go on. Were the actions from the last call done? I would like to know that first.
- Yusuf DemirSome. Hannah sent the field list. I wrote to Sanne about the late refresh. The accounting connector is not done, because the service user is not there yet.
- Joost VerbeekSo the third connector is not live. To be honest, that is not what I expected by now. What was agreed was that all three would be in the first weeks. So what is the plan?
- Yusuf DemirI can only speak to my part. Once the service user exists, I need a short window to build and test the mapping. I won't give you a date without Sanne's side. I also don't talk about the commercial side, that is Elena and the account owner.
- Sanne BakkerThe service user. My finance team approved the scope last week. The request is with IT. They are slow.
- Joost VerbeekI will push IT today. Sanne, send me the ticket reference from your side and I will escalate it. Yusuf, once it is created, how long?
- Yusuf DemirA few working days to get a clean load. Maybe sooner. I'd rather say a few days and be right.
- Joost VerbeekA few days. Good. That is something I can write down.
- Yusuf DemirSecond thing, the refresh. Sanne, can you read me the mornings you logged?
- Sanne BakkerLast Tuesday. Refresh not complete at 07:00. Again on Thursday. Friday was fine. This morning fine. Three misses in two weeks, counting the one in the ticket.
- Yusuf DemirRight. I looked at those. The source returned a very large page of Zendesk tickets on both mornings. The load waited on it. It finished at around twenty past seven on Tuesday and a little later on Thursday.
- Joost VerbeekA little later. How much later.
- Yusuf DemirThursday, about half past seven. I don't have the exact minute in front of me and I'd rather not guess.
- Joost VerbeekFine. So what has changed so that it does not happen again?
- Yusuf DemirI changed the page size and I moved the Zendesk load earlier in the run. I've re-run Tuesday's load to check the counts, and I told Elena before I did it. Row count matched the source.
- Sanne BakkerFriday and this morning were fine. Two is not a pattern. I will keep logging.
- Yusuf DemirPlease do. If it misses again I want the timestamp straight away.
- Joost VerbeekI want to be clear for the record. Our merchant risk team will not use the brain until the refresh is reliable. Account managers the same. The contract is for 40 users and today we have two people. That is not the value we bought.
- Yusuf DemirUnderstood. That is fair, and I'll make sure it is in the notes for Elena.
- Sanne BakkerThere is another thing. The duplicate merchants in HubSpot. I fixed most. Four are left. Can you check after tonight's load that they are merged?
- Yusuf DemirYes. I'll check the merchant count after tonight's load and tell you what it is. Numbers first.
- Joost VerbeekGood. Then let me summarise, so nobody can say later it was unclear. One. I escalate the service user with our IT today. Two. Yusuf builds the accounting mapping within a few working days of that. Three. Yusuf checks the merchant duplicates after tonight. Four. Sanne keeps her log and sends any miss. Five. Elena sends written actions. Yes?
- Yusuf DemirYes. I'll pass this to Elena straight after the call.
- Sanne BakkerYes.
- Joost VerbeekGood. Thank you, Yusuf. Met vriendelijke groet.
- Yusuf DemirThanks, both. Speak soon.
Callsmade from