Veldmaat Payments / BB-Demo – Demo
Callcompleted
Veldmaat Payments: documents · 2025-10-17 10:15
Hannah Lowe demoed the brain to Joost Verbeek and Sanne Bakker using Veldmaat's own sandbox data. Joost liked answers that name their source. Sanne tested refresh timing and failure visibility. Proposal and second session were agreed.
What was said
What this says
Current to 10 Oct 26Hannah Lowe demoed the brain to Joost Verbeek and Sanne Bakker using Veldmaat's own sandbox data. Joost liked answers that name their source. Sanne tested refresh timing and failure visibility. Proposal and second session were agreed.
What happened: Hannah Lowe ran the 17 Oct 2025 demo for Joost Verbeek and Sanne Bakker on sandbox data shared by Joost's team. Joost's three questions were where the data lives, how connectors fail and what an account manager sees.
Customer view: Joost said it was the first time he had seen an answer with the source named. Sanne pressed on refresh timing and flat records indexed, and liked that Hannah would not promise an alert beyond the contract.
Commercial: Hannah described Growth implementation as about eight weeks. Risk data as a further connector goes into the proposal as a question, not a promise.
Watch: Sanne's own pipeline had missed 07:00 twice, so freshness is her test of BB-Demo. The evidence does not show whether the proposal or second session followed.
Themes
Current to 9 Oct 26Theme
Growth demo, data trust
Importance
neutral
Sentiment
positive
Voice
champion
Who was there
BB-Demo
CRMmade from
Them
CRMmade from
Follow-up
Next steps
Current to 9 Oct 26- Hannah Lowe sends the architecture diagram, role definition and outline plan in one email by the end of the week.
- Tom Ashdown sends dates for a second demo for the account managers.
- Joost Verbeek's team sends its questions, and the proposal states risk data as an open question.
Risks
Current to 9 Oct 26- Sanne Bakker is sensitive to missed 07:00 refreshes, so any freshness miss early in an implementation would damage trust.
- Hannah Lowe would not promise proactive alerts for flat records beyond the contract, which may fall short of what Sanne expects.
- The evidence does not show who signs or holds the budget, only a Head of Data and a Data Engineer.
Opportunities
Current to 9 Oct 26- A Growth subscription with its implementation fits the three connectors named: HubSpot, Zendesk and the accounting system.
- Merchant risk data as a further connector could be scoped as a phase two or day-one item.
- A second session with Femke and other account managers could widen the buying group.
Transcript
Tom Ashdown NoneHello all. Joost, Sanne, can you see my screen yet? No, I haven't shared it, hang on. Hannah, you're muted.
Hannah Lowe NoneSorry, thank you. Good morning, everyone. Can everyone hear me now?
Joost Verbeek NoneGood morning. Yes, we hear you both.
Sanne Bakker NoneMorning. Refresh not complete at 07:00 on Tuesday and again on Thursday last week. Our own pipeline, I mean. I will say why this matters to me, later.- Hannah Lowe NoneThat's helpful to know up front, Sanne, thank you. Before I share anything, what do you most need to know from this session? I'd rather spend the time on your questions than on my slides.
- Joost Verbeek NoneThree things. Where the data lives and who can touch it. How the connectors work and what happens when one fails. And what an account manager sees, one merchant, one page. In that order.
- Hannah Lowe NoneGood, that's a clean order, we'll follow it. Tom, I'll take it from here if that's alright.
- Tom Ashdown NoneAll yours, Hannah. I'll keep quiet and take notes. No drama.
- Hannah Lowe NoneSo, the short answer on where the data lives is: in your Snowflake account, nowhere else. The longer answer is that we deploy into a schema you own, with a role that you grant and can revoke. Let me show you the diagram. This is your account on the left, the sources on the right, and the arrows go into your account, never out.
- Joost Verbeek NoneAnd your staff. Who from BB-Demo can see our data?
- Hannah Lowe NoneTo be precise, only what the role you grant allows, and only the engineers who work on your account. You can see every query they run in your own query history. I'll put the exact role definition in writing, so your compliance people have it.
- Joost Verbeek NoneGood. That I want in writing, yes.
- Hannah Lowe NoneNext, the connectors. For you that's HubSpot, Zendesk and the accounting system. Sanne, you'd be the one setting these up, so tell me if I'm describing something you wouldn't do. Each connector authenticates with a credential you create. We pull on a schedule, land the records in your Snowflake, and index them for the brain.
- Sanne Bakker NoneSchedule. When? What time is the refresh complete.
- Hannah Lowe NoneNightly, and it's complete by 07:00 your local time on business days. That's the commitment on every tier.
- Sanne Bakker NoneAnd when it is not. Again, I mean. What do I see.
- Hannah Lowe NoneFair question. Let me show you the connector status page. You see here, per connector, the time of the last good load, the number of records indexed, and if a load fails, it says what failed. The source returned an error, or the credential expired, that kind of thing. It doesn't just say failed.
- Sanne Bakker NoneRecords indexed. If it is flat for days, do you tell me or do I find out.
- Hannah Lowe NoneHonestly, you'd see it on that page and our engineers watch it too, but I'd rather not promise a proactive alert beyond what's in the contract. I'll check exactly what's covered and put that in writing.
- Sanne Bakker NoneGood. Not saying it is fine when it is not. I like that.
- Hannah Lowe NoneHa, that's my job. Right, let me show you the merchant page. This is built from a copy of your sandbox data that Joost's team shared last week, so it's your merchants, not invented ones.
- Joost Verbeek NoneWhich merchant is this?
- Hannah Lowe NoneOne of the test merchants from the extract. Here at the top you have the HubSpot side, owner, notes, last conversations. Below that the Zendesk side, open and recent tickets. And down here the accounting side, what's been invoiced and what's still open.
- Joost Verbeek NoneOne page. Okay. And the merchant risk team, do they see this also, or something different?
- Hannah Lowe NoneThey can see the same page, that's rather the point. If you want to bring in your risk data later, it's another connector, and it lands in the same layer. We'd scope that rather than do it live today.
- Tom Ashdown NoneSorry to jump in. Joost, that's one for the proposal, whether risk data is in from day one or a phase two. We'll look at it with you.
- Joost Verbeek NoneYes. Put it in the proposal as a question. Not as a promise.
- Hannah Lowe NoneNow the part people usually like. Let me ask it a question in plain language. Which merchants have had more than one ticket this month and also have an open invoice? I'll type it just as I'd say it.
- Sanne Bakker NoneHow does it know what is a ticket this month. Which date field.
- Hannah Lowe NoneGood, the answer shows its working. Look, here it states the field it used, the created date on the ticket, and the filter it applied. If that's not the field you'd use, you can say so and it reruns. It's not a black box.
- Joost Verbeek NoneTo be honest, this is the first time I see an answer with the source named. Others, they give you a number and you must believe.
- Hannah Lowe NoneWhich is exactly what we try to avoid. Anything else you'd like me to show on this, or shall we look at how it would be set up on your side?
- Joost Verbeek NoneSet up. What is the work for my team, and how long.
- Hannah Lowe NoneFor Growth the implementation runs about eight weeks. Your side mainly grants access, names an owner per source, and reviews the mapping with us. Sanne would carry most of that. I'd rather give you the week-by-week plan in writing than guess here.
- Sanne Bakker NoneFine. Send it and I read it. If it is vague I tell you.
- Hannah Lowe NoneI'd expect nothing less. I'll send the architecture diagram, the role definition, and the outline plan, all in one email, by the end of the week.
- Tom Ashdown NoneAnd I'll sort a second session with Femke and whoever else you want, Joost, so the account managers see the merchant page themselves. Leave that with me, I'll send some dates.
- Joost Verbeek NoneGood. So what is the plan, then. Hannah sends three things by Friday, Tom sends dates for the second demo. And we, we send the questions.
- Tom Ashdown NoneSpot on. Thanks, all. Really good session.
- Hannah Lowe NoneThanks, everyone. Speak soon.
- Sanne Bakker NoneSanne out. Bye.
Callsmade from