Veldmaat Payments / BG-Demo – Check In
Callcompleted
Veldmaat Payments · 7 Apr 2026 15:15
On 7 Apr 2026 Joost Verbeek pressed for a plan on late refreshes before the third connector goes live. A Thursday test load was agreed, go-live holds unless it fails, and he wants the whole merchant team using the brain.
What was said
What this says
As at Fri 9 Oct 2026On 7 Apr 2026 Joost Verbeek pressed for a plan on late refreshes before the third connector goes live. A Thursday test load was agreed, go-live holds unless it fails, and he wants the whole merchant team using the brain.
What happened: Hannah Lowe walked through the connector design, joining HubSpot, Zendesk and the accounting system on the merchant identifier. Sanne Bakker pointed to two refreshes not complete at 07:00 and said the third connector adds load.
Customer view: Joost called an unproven expectation not a plan and said a late refresh is late whatever the reason. He accepted the test load and the summary of actions.
Commercial: Joost wants the whole merchant team in the brain, not only Femke Jansen and a few others, and said that is the value. Elena Novak will propose a wider session after go-live.
Watch: Go-live stays as set unless the test shows a problem, and Joost wants to hear that the same day, in writing. Tickets in the last month were two, both high priority and both about the refresh.
Themes
As at Fri 9 Oct 2026Theme
Connector go-live and refresh
Importance
complaint
Sentiment
mixed
Voice
decision-maker
Who was there
BG-Demo
CRMmade from
Them
CRMmade from
Follow-up
Next steps
As at Fri 9 Oct 2026- Hannah Lowe to send the run order note by Friday.
- Sanne Bakker and Hannah Lowe to run the test load on Thursday, with Elena Novak reporting to Joost the same day.
- Sanne Bakker to send Hannah one example of the blank field today.
Risks
As at Fri 9 Oct 2026- The third connector may lengthen the nightly run, and the timing of a full run is not yet measured.
- Two high priority refresh tickets in the last month show the 07:00 commitment is slipping.
- Joost wants usage beyond a few people, so low adoption may undermine the value case.
Opportunities
As at Fri 9 Oct 2026- A wider merchant team session after go-live could broaden adoption.
- Showing all three sources at once gives the customer a fuller picture of the brain's value.
Transcript
Elena NovakGood afternoon everyone. Can everybody hear me?
Joost VerbeekYes, afternoon Elena.
Sanne BakkerI hear you.
Hannah LoweHi all. Yes, fine here.- Elena NovakThank you. As in my email, there are three points. First, the connector review. Second, the go-live date. Third, usage and tickets since we last met. Hannah has the connector design ready to share.
- Joost VerbeekBefore that. Were the last actions done?
- Elena NovakTo confirm, two of three. Hannah's field mapping note was sent. Yusuf's notes on the re-runs were shared. The third is the connector review itself, which is today.
- Joost VerbeekOkay. What was agreed was a review before go-live. So let's do the review.
- Hannah LoweRight. Let me start with what you most need to know. Is the question the mapping, or the timing?
- Joost VerbeekTiming. The mapping I have read, it looks right. Timing is the problem.
- Hannah LoweFine, then I'll be brief on mapping. HubSpot and Zendesk are live and join on the merchant identifier. The accounting system connector uses the same identifier, so a merchant becomes one record across all three. That is the design.
- Sanne BakkerFine. But the nightly run. Refresh not complete at 07:00, last Tuesday, and the Thursday before. See tickets from those days. Third connector adds more to that run.
- Hannah LoweYes. To be precise, it would add to it. The short answer is, I expect the extra load to be small, because the accounting data changes less than tickets do. The longer answer is, I haven't seen the timings of a full run with all three, so I won't promise yet.
- Joost VerbeekTo be honest, that is not a plan. Account managers open the brain at the start of the day. A refresh that is late is a late refresh, whatever the reason. So what is the plan?
- Hannah LoweFair. The plan is this. Sanne and I run a test load of the accounting connector outside the nightly run, and measure it. Then I set the run order so the two connectors you rely on most go first. I'll put that in writing by Friday.
- Sanne BakkerTest load, fine. Which day?
- Hannah LoweThursday, if that works for you. Then we have the numbers before the go-live.
- Sanne BakkerThursday works.
- Elena NovakTo confirm the go-live. The date we set is next Tuesday. Joost, is that still right for you?
- Joost VerbeekNext Tuesday, yes. But if the test on Thursday shows a problem, I want to hear it the same day. Not on Monday.
- Elena NovakAs agreed. I will make sure that you hear it from me the same day, in writing.
- Joost VerbeekGood. Then that is what I will record.
- Hannah LoweOne more point on the connector review. Sanne, you raised a question about permissions on the accounting side. Is that settled?
- Sanne BakkerMostly. Read access only, I set it up. One field is still blank for some merchants. I will check the source before I say it is a mapping issue.
- Hannah LoweGood. Send me one example and I'll check it against the mapping. I'd rather see a real record.
- Sanne BakkerWill do. Today.
- Elena NovakThird point, usage and tickets. Active use is up a good deal on last quarter, which is encouraging. Tickets in the last month, two, both high priority, both about the refresh.
- Joost VerbeekUp is good. But still few people. I would like the whole merchant team in there, not only Femke and a few others. That is the value.
- Elena NovakUnderstood. Yusuf has trained Femke already. I will propose a session for the wider team after go-live, and send you the proposal in writing.
- Joost VerbeekFine. After go-live. Not before, they will see a half-finished picture.
- Hannah LoweAgreed. Better to show them all three sources at once.
- Sanne BakkerOne thing for the notes. If a refresh misses again before Tuesday, I raise a ticket as usual. No change.
- Elena NovakPlease do. Yes.
- Elena NovakLet me summarise. First, Hannah sends the run order note by Friday. Second, Sanne and Hannah run the test load on Thursday, and I report the result to Joost the same day. Third, Sanne sends Hannah the example of the blank field today. Fourth, go-live stays next Tuesday, unless the test says otherwise. I will send these in writing after the call.
- Joost VerbeekGood. That I can accept. Thank you all.
- Hannah LoweThanks, everyone. Speak Thursday.
- Sanne BakkerBye.
- Elena NovakThank you, goodbye.
Callsmade from