Veenendrecht Payments / BG-Demo – Demo
Callcompleted
Veenendrecht Payments · 11 Nov 2025 15:45
Demo to Eline Bakker and Daan Visser on an anonymised sample. Eline was happy with what she saw. Daan needs written answers on permissions and logging. Decision is wanted by Thu 22 Jan 2026, with Pieter still to see the price.
What was said
What this says
As at Fri 9 Oct 2026Demo to Eline Bakker and Daan Visser on an anonymised sample. Eline was happy with what she saw. Daan needs written answers on permissions and logging. Decision is wanted by Thu 22 Jan 2026, with Pieter still to see the price.
What happened: Hannah Lowe showed a merchant timeline, a plain-language question with sources, permissions by team and source, and the dashboards builder. Matteo Ricci confirmed the Growth deal as scoped at fifty-nine thousand five hundred, with the one-off implementation included.
Customer view: Eline wants one timeline and questions in normal words. Daan accepted nightly refresh for review but not for live blocking, and wants logging of who looked at which merchant.
Commercial: Pieter will need the implementation and the yearly part as two clear lines. The decision date is Thursday 22 January 2026.
Watch: the evidence does not show Pieter's view or any answer on the regulator list. Written security answers are promised but not yet sent.
Themes
As at Fri 9 Oct 2026Theme
Growth demo, compliance questions
Importance
praise
Sentiment
positive
Voice
champion
Who was there
BG-Demo
CRMmade from
Them
CRMmade from
Follow-up
Next steps
As at Fri 9 Oct 2026- Hannah Lowe sends written answers on permissions and logging and the architecture picture.
- Matteo Ricci sends the commercial summary with implementation and yearly part as two lines.
- Eline Bakker takes the commercial summary to Pieter and a follow-up call is set before Christmas if possible.
Risks
As at Fri 9 Oct 2026- Daan needs written answers on permissions and logging before compliance will be comfortable.
- Nightly refresh rules out live use, so the brain must not be positioned as a real-time control.
- Pieter has not been on a call and will judge on cost and contract.
Opportunities
As at Fri 9 Oct 2026- Growth tier with the dashboards builder fits both merchant success and merchant risk.
- More sources such as CRM and finance could later need connectors beyond the Growth set.
Transcript
Matteo RicciGood afternoon, everyone. Eline, hello. Daan, lovely to meet you properly. Hannah is with me.
Hannah LoweHello both. Can you see my screen, or is it still the waiting slide?
Daan VisserI see a slide. Hello. Daan here, risk. Eline told me a little about the first call.
Eline BakkerHello. Before we start, last time's actions. Matteo, you sent the summary, thank you. I asked compliance about the sample. They said yes for a small anonymised extract. So you have it, Hannah?- Hannah LoweYes, we received it and loaded it into a demo environment. To be precise, it is a small set of merchants, with their tickets and disputes and the volume figures, and nothing else. I will say what is real and what is only shaped for the demo as we go.
- Matteo RicciLet me restate the timeline quickly, so we all keep it in mind. Eline's team would like a decision by Thursday 22 January 2026. So today is the part where you decide whether this really answers your problem.
- Hannah LoweBefore I click anything, what do you most need to know from today? Eline, Daan, tell me and I will steer.
- Daan VisserFor me, two things. Can I see disputes and tickets for one merchant together. And who sees what. I am careful about who gets to see risk assessments.
- Eline BakkerMine is the story of the merchant. One timeline. And can I ask questions in normal words.
- Hannah LoweGood. Then I will do those two in that order. Starting with the timeline. This is a merchant page. At the top you see the basic record, the contract and the contact. Below that is one stream, ordered by date, with tickets, disputes and volume changes mixed in.
- Eline BakkerMm. So this is the half day of work. In one screen.
- Hannah LoweThat is the idea. Here is an example. This merchant has a run of tickets about failed payouts, and in the same fortnight the disputes tick up and the volume dips. Each of those lived in a different system. Here they sit side by side, and every line links back to the source record.
- Daan VisserSorry, the so-called link back. If I click a dispute line, it opens the original in our platform? Or it is a copy?
- Hannah LoweThe short answer is it shows the indexed record, and it carries the reference to the original. The longer answer is that the brain keeps its own indexed copy inside your Snowflake account, refreshed nightly, so what you see is as fresh as the last refresh, not live. I want to be clear about that.
- Daan VisserNightly. Okay. For a risk decision, that is fine for review. I would not use it for a live block.
- Hannah LoweRight, and I would not suggest it. It is for understanding and for review, not for real-time decisions.
- Matteo RicciI would rather you heard that from us now than found it later. It is a strength for the picture, not a replacement for your live controls.
- Eline BakkerFine. Clear. Let's make it practical. Show me a question.
- Hannah LoweOkay. I will type it as you would say it. Which merchants have rising disputes and falling volume over the last few months. And we wait a moment.
- Hannah LoweThere. Three merchants in the sample. Each has a short explanation, and the sources underneath. So not just an answer, the evidence for the answer.
- Eline BakkerAnd if the answer is wrong? What is the merchant's story, then. How do I know.
- Hannah LoweThat is exactly why the sources are there. You open them and check. And I would say, with a small sample, treat any answer as a lead to confirm, not as a verdict. The same applies with your full data.
- Daan VisserGood. Now permissions. If Eline's team and my team both use this, can I keep some things from her team?
- Hannah LoweYes. Access can be set by team and by source, so risk assessments can be visible to risk only while tickets are visible to both. To be precise, I will show you the settings page, and I will put the exact options in writing afterwards so your compliance team has them.
- Daan VisserYes please. In writing. They will want the logging, too. Who looked at which merchant.
- Hannah LoweUnderstood. For the formal security questions I will check details with our security lead before I answer anything I am not certain of, and send you the answers in writing.
- Matteo RicciAnd what does your regulator need to see, Daan? You know better than us. If you give us the questions, we answer in the same words.
- Daan VisserMostly where the data is and who can see it. I will send a list. It is not unusual.
- Hannah LoweGood. Let me show you dashboards next, because Growth includes the builder. Here is one built on your sample. Disputes against volume by merchant, with a filter by sector and a filter by size.
- Eline BakkerCan my team build their own? Or do you build it, every time.
- Hannah LoweYour team can. It is drag and choose, no code. We help with the first ones during the implementation, and then it is yours.
- Daan VisserAnd connecting more sources later? Today you have the tickets and disputes. We also have the CRM, finance. Does that mean more work, more cost?
- Hannah LoweGrowth comes with a set number of connectors, and your three or four main sources fit comfortably inside it. Anything beyond that is an add-on, and Matteo can go through it. Each connector takes design effort, so I plan them with you.
- Matteo RicciLet me confirm the commercial side, so there are no surprises. The Growth deal, as scoped, is fifty-nine thousand five hundred, with the one-off implementation included. I will put the breakdown in writing, because I do not want you to have to reconstruct it for Pieter.
- Eline BakkerYes. Pieter will ask for exactly that. What is the implementation, what is the yearly part. In the document, please. Two clear lines.
- Matteo RicciTwo clear lines. You will have them.
- Daan VisserOne more from me. If a merchant asks us why we made a decision, can we use what the brain shows as part of the explanation?
- Hannah LoweYou can use it as supporting material, because every statement links to a source record. But the decision record itself should stay in your own system. The brain helps you find and explain, it does not replace the formal record.
- Daan VisserThat is how I would want it. Good.
- Eline BakkerOkay. I am happy with what I saw. Who owns the next step? I would like a short list. What you send, what we send, with dates.
- Matteo RicciThen here it is. Hannah sends the written answers on permissions and logging, and the architecture picture for compliance. I send the commercial summary with the two lines. Daan sends his regulator list. Eline, you take it to Pieter. Does that sound right?
- Eline BakkerYes. And a follow-up call after compliance has read it. Before Christmas, ideally. Then we still make the date in January.
- Matteo RicciAgreed. I will send some options this week. Thank you all, this was a good session.
- Hannah LoweThanks, both. Speak soon.
- Daan VisserThank you. Goodbye.
- Eline BakkerGoodbye. Groetjes.
Callsmade from