Kanaalpoort Payments / BB-Demo – Discovery
Callcompleted
Kanaalpoort Payments: documents · 2026-09-08 10:00
Kanaalpoort Payments has merchant data split across payments, CRM, help desk and its own platform. Lotte Vermeulen wants to see which merchants are at risk. They want something in place by January and run Snowflake.
What was said
What this says
Current to 11 Oct 26Kanaalpoort Payments has merchant data split across payments, CRM, help desk and its own platform. Lotte Vermeulen wants to see which merchants are at risk. They want something in place by January and run Snowflake.
What happened: On the 8 Sep 2026 discovery call, Lotte Vermeulen and Erik Dijkstra described four disconnected cloud systems and manual report matching. Several thousand merchants are affected.
Customer view: The first question they would ask is which merchants are at risk and why. Erik said retention is everything in their business.
Commercial: They run Snowflake and prefer to keep control of the data, which fits the brain running inside their own account. Matteo Ricci proposed an early October demo, then scope and timing.
Watch: The evidence does not show budget, tier or a decision process. Erik is the most senior voice and set the January timeline, but no buying commitment was made. Any October demo is a plan, not a held call.
Themes
Current to 9 Oct 26Who was there
BB-Demo
Them
Follow-up
Next steps
Current to 9 Oct 26- Matteo Ricci to set up a demo in early October with sample data.
- Matteo Ricci to agree scope and timing with Lotte Vermeulen and Erik Dijkstra after the demo.
Risks
Current to 9 Oct 26- No budget, tier or decision process was discussed, so the opportunity is unqualified.
- The January target leaves limited time if scope and security steps run long.
Opportunities
Current to 9 Oct 26- A clear use case of merchant churn risk maps directly to what the brain answers.
- Existing Snowflake and cloud-only systems fit the brain running in the customer's own account.
Transcript
Matteo Ricci NoneGood morning, Lotte and Erik. Thank you for making the time. I know you're evaluating data solutions for merchant operations. We have a few weeks to explore whether we're a fit, so I want to focus on your biggest pain points today. Does that work?
Lotte Vermeulen NoneYes, that makes sense. We have a lot of merchant data scattered across systems: payments, help desk, our platform, and nobody can see the whole picture.- Matteo Ricci NoneThat's a common place to start. Walk me through your stack. What systems are involved?
Erik Dijkstra NoneWe have our core payment system, a CRM for merchant management, a help desk, and our own platform that tracks merchant activity. They're largely disconnected.- Matteo Ricci NoneAnd when you say disconnected, what does that look like in practice? What's the work you're doing today?
- Lotte Vermeulen NoneMy team spends time pulling reports from each system, matching them up manually. If we want to know which merchants are at risk of leaving, we have to combine data from the help desk, platform usage, and the CRM. It's slow.
- Matteo Ricci NoneHow many merchants are we talking about?
- Erik Dijkstra NoneSeveral thousand. It's a lot of data to manually reconcile.
- Matteo Ricci NoneAnd this affects how many people in your business?
- Lotte Vermeulen NoneRight now, my operations team directly, maybe a dozen people. But the insights feed back to finance and the executive level, so it's broader.
- Matteo Ricci NoneUnderstood. So if you had a tool that could answer questions about your merchants instantly, combining all that data, what would be the most valuable question you'd ask first?
- Lotte Vermeulen NoneProbably: which merchants are at risk, and why. Then we could intervene before they leave.
- Erik Dijkstra NoneAnd that feeds straight to the bottom line. Retention is everything in our business.
- Matteo Ricci NoneThat makes sense. And on the technical side: you mentioned a CRM, help desk, payment system, and your own platform. Are those cloud-based or on-premises?
- Erik Dijkstra NoneAll cloud now. We're running on cloud infrastructure.
- Matteo Ricci NoneGood. And do you have a data warehouse or any kind of central data layer?
- Erik Dijkstra NoneWe have Snowflake.
- Matteo Ricci NonePerfect. That's actually important to mention, the brain runs inside your Snowflake account, so the data stays with you. We would connect your systems into the brain, and your team would query from there. Does that feel aligned with how you work?
- Lotte Vermeulen NoneYes, we prefer to keep control of the data.
- Matteo Ricci NoneExcellent. And one more question before we close: what's your timeline for needing something like this?
- Erik Dijkstra NoneWe'd like to have something in place early in the new year. By January, ideally.
- Matteo Ricci NoneThat's feasible. What I'll do is set up a demo for early October where we'll show you the brain working with some sample data, and then we can talk about scope and timing. Does that work?