Veldmaat Payments / BG-Demo – Demo
Callcompleted
Veldmaat Payments · 27 Oct 2025 10:00
Demo for Veldmaat Payments on 27 Oct 2025. Femke Jansen saw her Monday merchant list produced in seconds. Joost Verbeek wants payout data scoped as a separate option and a dated proposal.
What was said
What this says
As at Fri 9 Oct 2026Demo for Veldmaat Payments on 27 Oct 2025. Femke Jansen saw her Monday merchant list produced in seconds. Joost Verbeek wants payout data scoped as a separate option and a dated proposal.
What happened: Tom Ashdown and Hannah Lowe demoed the brain on a test extract for Joost Verbeek, Sanne Bakker and Femke Jansen on 27 Oct 2025. Femke took a live merchant question on payouts during the call.
Customer view: Femke said the list of merchants with a ticket, a late invoice and no recent contact is what she builds by hand on Mondays, taking half the morning. Sanne asked that each account manager sees only their own merchants.
Commercial: Payout timing lives in a platform outside the three systems, so it would need a fourth connector as separate scope. Joost wants it in the proposal as an option, with no surprise.
Watch: Joost pushed back on "a couple of weeks" and Tom promised a date by the end of the following day. The evidence does not show who decides or signs. Notes written after the last refresh are not visible until the next one.
Themes
As at Fri 9 Oct 2026Theme
Demo, payouts scope, proposal
Importance
upsell
Sentiment
positive
Voice
champion
Who was there
BG-Demo
CRMmade from
Them
CRMmade from
Follow-up
Next steps
As at Fri 9 Oct 2026- Tom Ashdown to send Joost Verbeek a proposal date by the end of the following day.
- Hannah Lowe to put the HubSpot ownership mapping and permissions in writing for Sanne Bakker.
- Tom Ashdown to list the duplicate-ticket filter as a mapping preference.
Risks
As at Fri 9 Oct 2026- Payout timing is outside the three systems, so the brain cannot answer Femke's main merchant question without a fourth connector.
- Nightly refresh means same-day notes are not visible, which Femke noticed and may weigh against value.
Opportunities
As at Fri 9 Oct 2026- A fourth connector for payout data can be offered as a separate, clearly scoped option in the proposal.
- The risk team does similar work by hand, which points to a wider use case.
Transcript
Tom AshdownMorning, all. We've got a full house today. Femke, welcome, have I got your name right?
Femke JansenYes, Femke. Good morning. Sorry, one minute, a merchant is waiting for an answer on payouts. I have the call open.- Tom AshdownNo bother, you do what you need to. Hannah's got the data up, so actually that might be a nice place to start.
Hannah LoweGood morning, everyone. Femke, I'll ask my usual: what do you most need to know? And if there's a merchant you're dealing with right now, give me the name and I'll show you what the brain says about it.- Femke JansenA webshop merchant. They say their payouts arrived late twice this month, and they ask if it is us or their bank. Just to be clear, I do not need the answer for the contract. I need it for the call.
- Hannah LoweUnderstood. This is the test extract again, so I'll use one of the merchants in it. Let me type: show me this merchant's recent tickets, open invoices and the last notes from the account manager.
Joost VerbeekFemke, tell her if the page has what you look for. Do not be polite.- Femke JansenI am never polite when it is work. Ha. Okay. I see the tickets, good. Where is the HubSpot note I wrote last Thursday?
- Hannah LoweRight, the short answer is that it's only as fresh as the last refresh. The extract we're using was taken before that date. In a live setup the nightly load would have brought your note in by 07:00 the next business day.
- Femke JansenNext business day. So if I write a note at four o'clock and the merchant calls at five, the brain does not know.
- Hannah LoweCorrect, to be precise, it won't have that note until the next refresh. You'd still have it in HubSpot, of course. I'd rather you hear that now than discover it later.
- Femke JansenGood. Thank you. Can you check one more thing please? The ticket count in Zendesk for this merchant. I want to see if it matches.
- Hannah LoweSure. The brain says three tickets in the period. Sanne, you know the Zendesk side. Is three what you'd expect for this merchant?
Sanne BakkerI check. In Zendesk I see three. One is closed as duplicate. So three, but two real.- Hannah LoweThat's a useful catch. The brain keeps the duplicate flag from Zendesk, so I can filter it out. Watch. There, two.
- Femke JansenGood. That matches what I see. Please do that by default, the duplicates out.
- Tom AshdownNoted, I'll put that on the list as a mapping preference.
- Hannah LoweNow the invoices. This section is the accounting system. Open, paid, overdue, per merchant. Femke, for your merchant, does the payment status help with their question about payouts?
- Femke JansenNot for payouts. That is on the payment side, and that is another system. But I use this for fees. If the merchant has an overdue fee invoice, I say it before they say it.
- Joost VerbeekThe payout data is in the platform, not in the three systems. This is a thing to decide. It is a phase two, perhaps. I do not want a surprise.
- Hannah LoweAgreed, and I'd prefer to be clear. With the three sources we've discussed you'd get the relationship, the tickets and the invoices. Payout timing would need a fourth connector to wherever that lives. It's doable, but it's separate scope, and I'd put it on paper as such.
- Tom AshdownAnd that's the sort of thing that goes in the proposal as an option, so there's no confusion about what's in and what's out.
- Femke JansenOkay. Another question. This merchant is waiting. I can say to them, I will come back within the hour. Can I say that, because the brain gives me the answer?
- Hannah LoweI'd be careful there, and I think you were already thinking it. What you tell your merchants is your call. What I can say is that it gives you the answer to the questions in those three systems in seconds rather than days.
- Femke JansenYes. Just to be clear, I do not promise a merchant something that depends on someone else. But seconds is good. This is much better than now.
- Hannah LoweLet me show you the last piece, then, which is asking it in your own words. Type whatever you'd ask a colleague.
- Femke JansenOkay. Which of my merchants had a ticket and a late invoice, and did not talk to me in the last month. Typing. Send.
- Hannah LoweThere. Four merchants, with the reason against each. And at the side it shows the fields it used.
- Femke JansenThat is exactly the list I make by hand on Mondays. It takes me half the morning.
- Joost VerbeekThis is the point. Femke, you can say it to Tom in the next step, honest. The risk team, they do the same by hand.
- Sanne BakkerOne thing from me. The access. Femke sees her merchants only? Not all merchants.
- Hannah LoweIt follows the permissions you set. We can mirror the HubSpot ownership so an account manager sees their own book. I'll confirm exactly how that mapping works and put it in writing, because I don't want to overstate it.
- Sanne BakkerGood. In writing.
- Tom AshdownRight, let's land this. Joost, what would you like from us before the next step?
- Joost VerbeekA proposal. With what is in, what is out, and the options we discussed. The payout data, the risk data. And a clear timeline. So what is the plan, Tom, and when?
- Tom AshdownYou'll have it within a couple of weeks, and I'll get a call in the diary to walk you through it so it's not just a PDF landing in your inbox.
- Joost VerbeekA couple of weeks is not a date. Please give me a date.
- Tom AshdownFair. Leave that with me, I'll send you the day by the end of tomorrow.
- Femke JansenSorry, I must go, the merchant. Thank you, Hannah. Groeten.
- Hannah LoweThanks, Femke. Thanks, everyone, I'll send the notes on mapping and permissions.
- Tom AshdownCheers, all. Speak soon.
Callsmade from