B-Glass
Matteo Ricci

Veenendrecht Payments / BG-Demo – Discovery

Callcompleted

Veenendrecht Payments logo Veenendrecht Payments · 22 Oct 2025 12:00

Eline Bakker, Head of Merchant Success, described hand-built merchant views taking half a day each. Matteo Ricci floated Growth at fifty-nine thousand five hundred including implementation, with a decision targeted for 22 Jan 2026.

What was said

What this says

As at Fri 9 Oct 2026

Eline Bakker, Head of Merchant Success, described hand-built merchant views taking half a day each. Matteo Ricci floated Growth at fifty-nine thousand five hundred including implementation, with a decision targeted for 22 Jan 2026.

What happened: Veenendrecht is a supervised payment service provider. Eline said support, risk, finance and sales each hold a piece of a merchant, and she or her team pull it together by hand.

Customer view: Success and risk would be the first two teams, with finance maybe later. She wants one timeline of disputes, tickets and volumes, and the ability to ask questions without waiting for anyone.

Commercial: Matteo suggested the Growth tier and gave a first figure of fifty-nine thousand five hundred including the one-off implementation. Eline said Pieter decides the budget, was not on the call, and she will not commit before him.

Watch: Compliance questions and a sample extract are still to come. Daan, head of merchant risk, will want to know who can see risk data.

AI · claude-sonnet-5-5 · as at Fri 9 Oct 2026

Themes

As at Fri 9 Oct 2026
Theme
Discovery, merchant data consolidation
Importance
upsell
Sentiment
positive
Voice
champion

Who was there

BG-Demo

Them

Follow-up

Next steps

As at Fri 9 Oct 2026
  • Matteo Ricci sends a written summary and a note on how data stays in the customer's Snowflake account.
  • Matteo Ricci proposes a demo date with Hannah and Daan.
  • Eline Bakker sends the compliance question list and asks about a sample extract.

Risks

As at Fri 9 Oct 2026
  • Pieter, who decides the budget, was not on the call and Eline will not commit before him.
  • Regulatory and compliance questions on data access are not yet known and could slow the decision.
  • The decision date of 22 Jan 2026 may move, as Eline said.

Opportunities

As at Fri 9 Oct 2026
  • Growth tier for success and risk, with possible extension to finance later.
  • A demo on the customer's own merchant data, supported by Hannah and Daan's involvement.

Transcript

  1. Matteo Ricci
    Matteo Ricci
    Hello Eline, good afternoon. Can you hear me all right?
  2. Eline Bakker
    Eline Bakker
    Yes, I hear you. Hello Matteo. Good afternoon. Sorry, one second, I am in a different room today, the other one has a meeting.
  3. Matteo Ricci
    Matteo Ricci
    No problem at all. Take your time. How is the week going so far?
  4. Eline Bakker
    Eline Bakker
    Busy. Quarter planning. Everybody wants everything. But fine. Let's make it practical, I have the full time until the end of the slot.
  5. Matteo Ricci
    Matteo Ricci
    Good. Let me just restate where I think we are, so we start from the same place. You would like to have a decision on something like this by Thursday 22 January 2026, and today is about me understanding your world before I show you anything. Is that still right?
  6. Eline Bakker
    Eline Bakker
    Yes. That is the date we have. Maybe it moves a bit, but that is the plan. My CFO wants it settled before the new budget year really starts.
  7. Matteo Ricci
    Matteo Ricci
    Understood. So, to begin, tell me about Veenendrecht in your own words. I have read the website, but I would rather hear it from you.
  8. Eline Bakker
    Eline Bakker
    We are a payment service provider. Mostly for subscription businesses and software companies. Recurring payments, the cards, direct debits, the whole flow. We are in Utrecht, and we are supervised, so the regulator is always somewhere in the room.
  9. Matteo Ricci
    Matteo Ricci
    Right. And your role sits where, exactly?
  10. Eline Bakker
    Eline Bakker
    Merchant success. I look after the merchants once they are live. Are they growing, are they happy, do they have problems. I also own the data side of that, which is how I came to look at your product.
  11. Matteo Ricci
    Matteo Ricci
    Mm. So what is the pain, today? When something goes wrong with a merchant, what happens?
  12. Eline Bakker
    Eline Bakker
    Okay. Honest answer. Everybody has a piece. Support has the tickets. Risk has the disputes and chargebacks. Finance has the volumes. Sales has the contract and the story from when we signed them. And nobody has all of it in one place.
  13. Matteo Ricci
    Matteo Ricci
    And when a merchant is, let's say, worrying you. Who pulls it together?
  14. Eline Bakker
    Eline Bakker
    Me. Or one of my team. By hand. We export, we paste into a sheet, we ask risk for their numbers. It takes half a day for one merchant. Sometimes more. And then the sheet is old the next week.
  15. Matteo Ricci
    Matteo Ricci
    Half a day for one merchant. How many merchants would you say you have to do this for in a typical month?
  16. Eline Bakker
    Eline Bakker
    The ones we really look at? A handful, a dozen when it is bad. But the real problem is the ones we do not look at. We find out too late. The merchant's story is already finished when we see it.
  17. Matteo Ricci
    Matteo Ricci
    That is a clear way to put it. Who else is affected? Is it only success, or is risk living the same problem?
  18. Eline Bakker
    Eline Bakker
    Risk is living it more. Daan, he is the head of merchant risk, he sees a merchant with rising disputes and he does not know that the same merchant opened a lot of angry tickets last month. Or that their volume is dropping. So he decides with half a picture.
  19. Matteo Ricci
    Matteo Ricci
    And the other direction, I imagine. You see a happy merchant and do not know that risk is already nervous.
  20. Eline Bakker
    Eline Bakker
    Exactly. Yes. That happened. I will not say which one. We were talking to the merchant about growth and risk was about to put limits on them. Not good.
  21. Matteo Ricci
    Matteo Ricci
    Understood. I would like to ask about systems now, just so I know what we are connecting to. Where do the tickets live, where is the contract and customer record, and where do the payment numbers sit?
  22. Eline Bakker
    Eline Bakker
    Tickets are in the helpdesk. The customer record is in our CRM. The payments and disputes are in our own platform, and a copy goes to the warehouse every night. We do use Snowflake for the analytics team, yes.
  23. Matteo Ricci
    Matteo Ricci
    Good, that helps a lot, because the brain is built and run inside your own Snowflake account. Nothing leaves your environment. I know that matters for you. What does your regulator need to see, if you put something like this in front of merchant data?
  24. Eline Bakker
    Eline Bakker
    Where the data sits. Who can see what. Logging. And that we can explain it. Our compliance team will have a long list. I do not want to guess, I will ask them for the exact questions.
  25. Matteo Ricci
    Matteo Ricci
    That is the right way. Let me confirm that in writing afterwards, and when we get to the demo my colleague Hannah, who is our solutions engineer, can answer the technical side properly. I would rather she did that than I improvise.
  26. Eline Bakker
    Eline Bakker
    Good. Yes. Please bring her. And bring something for Daan, he will have questions about who can see risk data.
  27. Matteo Ricci
    Matteo Ricci
    Noted. Now, what does good look like? If this works, six months from now, what is different on a Tuesday morning?
  28. Eline Bakker
    Eline Bakker
    I open one place. I type the merchant name. I see disputes, tickets, volumes, in one timeline. And I can ask a question, like, which merchants have rising disputes and falling volumes. Without waiting for anybody.
  29. Matteo Ricci
    Matteo Ricci
    And how many people would use that, in your picture? Just your team and risk, or wider?
  30. Eline Bakker
    Eline Bakker
    Start with success and risk. Two teams. Maybe finance later. I do not want to promise more, I need Pieter to agree first, and I do not commit budget before him.
  31. Matteo Ricci
    Matteo Ricci
    Of course. Is Pieter the person who signs, then?
  32. Eline Bakker
    Eline Bakker
    He decides the budget, yes. He is not on this call. He will want the business case in a few clear lines. Who owns the next step, what does it cost, what do we get.
  33. Matteo Ricci
    Matteo Ricci
    Then I will help you write those lines. The shape I have in mind is our Growth tier, because you have several teams and you want dashboards. As a first view, the deal comes to fifty-nine thousand five hundred, and that includes the one-off implementation. But let me not get ahead of myself. I would like the demo to come first, on your own data if possible.
  34. Eline Bakker
    Eline Bakker
    Fifty-nine five, all in. Okay. Noted. Not a problem for a first number. Pieter will ask what is inside, so the demo has to show it.
  35. Matteo Ricci
    Matteo Ricci
    Agreed. What would you need from your side to prepare a demo on real merchants? Even a small sample, anonymised if you prefer.
  36. Eline Bakker
    Eline Bakker
    I can ask our data team for a small extract. Maybe tickets and disputes for a few merchants. I need to check with compliance first. Give me a week.
  37. Matteo Ricci
    Matteo Ricci
    Perfect. So, actions. You will ask compliance for their question list and about the sample extract. I will send you a short written summary of today, a note on how the data stays in your Snowflake account, and propose a date for the demo with Hannah and with Daan.
  38. Eline Bakker
    Eline Bakker
    Good. And I will talk to Daan about the date. Who owns the next step? You send the summary, I send the compliance questions. Yes.
  39. Matteo Ricci
    Matteo Ricci
    Exactly that. Thank you, Eline, this was very clear. Speak soon.
  40. Eline Bakker
    Eline Bakker
    Thank you Matteo. Goodbye.

BG-Demo is a fictional company; every organisation and person here is invented. B-Glass is the tool. Data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Glass is one place to read everything the company knows about its customers: the CRM, calls, emails, support tickets, product usage, invoices, documents, news and HR. Every page is built from those systems and the data is current to Fri 9 Oct 2026.

How to use the site

How to ask

Press Ask B (the speech bubble) in the header, or open the Ask B page. Type a question, or pick one of the suggestions.

What the data covers

DataRecords
Organisations225
People at customers862
BG-Demo staff records (in post and leavers)58
Calls1,995
Email threads3,013
Support tickets1,159
Documents1,218
Deals315
Invoices285
Events49
News items119

Data as of Fri 9 Oct 2026. Text marked AI was written by the AI from the records listed in its made-from link; an AI output that cannot cite its evidence is refused and the previous text kept. Where two systems disagree (for example a contract and the CRM), the key facts show both values and mark the difference.

BG-Demo is a fictional company: every organisation, person and figure here is invented for this demonstration. B-Glass is the tool that reads its data.

Who to contact

Email info@b-glass.uk or talk to your B-Glass account team. Tell us the page address and what looked wrong; a screenshot helps.

Help

Ask B

B-Glass · read-only