Tom Ashdown

Veldmaat Payments / BB-Demo – Proposal

Callcompleted

Veldmaat Payments: documents logo Veldmaat Payments: documents · 2025-11-05 12:00

Joost Verbeek, Head of Data, heard the Growth proposal and wants one page on data location, a two-line price and connector commitments in the order form. He wants to decide by 16 Dec 2025.

What was said

What this says

Current to 10 Oct 26

Joost Verbeek, Head of Data, heard the Growth proposal and wants one page on data location, a two-line price and connector commitments in the order form. He wants to decide by 16 Dec 2025.

What happened: Tom Ashdown walked Joost through the Growth proposal for HubSpot, Zendesk and the accounting system, built inside Veldmaat's own Snowflake account. The call was held on 5 Nov 2025.

Customer view: Joost's main concern is where the data sits and who can see it, because his risk team will ask. He also refused a vague number and wants implementation and subscription on separate lines.

Commercial: Tom quoted a deal value of fifty-seven thousand covering implementation plus the first year's subscription. He did not give the yearly subscription or the user allowance on the call, and promised both in writing.

Watch: Finance closes the budget in December, so a decision after 16 Dec 2025 slips to next year.

AI · claude-sonnet-5-5 · 10 Oct 2026

Themes

Current to 9 Oct 26
Theme
Growth proposal and pricing clarity
Importance
neutral
Sentiment
neutral
Voice
decision-maker

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Tom Ashdown sends the written proposal with implementation and subscription on separate lines.
  • Tom Ashdown has the solutions engineer write a one-page, non-marketing note on where the data sits.
  • Tom Ashdown sends written actions with owners and dates, and books a call after Joost's security review.

Risks

Current to 9 Oct 26
  • The headline figure could be read by Veldmaat finance as a yearly price rather than a total including implementation.
  • A decision after 16 Dec 2025 moves into next year's budget.
  • The data-location question could stall the security review if the one-page note is weak.

Opportunities

Current to 9 Oct 26
  • Growth tier for several teams, with account managers and merchant risk working from one picture.
  • Extra blocks of users can be added if Veldmaat outgrows the allowance.

Transcript

  1. Tom Ashdown
    Tom Ashdown None
    Joost, hello. Can you hear me alright? I've got a bit of an echo this end.
  2. Joost Verbeek
    Joost Verbeek None
    Yes, I hear you well. Hello Tom. First, the actions from last time. Did you send the connector list?
  3. Tom Ashdown
    Tom Ashdown None
    Yeah, that went over yesterday afternoon. Did it land? Sorry, I should've asked how your week's going before diving in.
  4. Joost Verbeek
    Joost Verbeek None
    Busy. The merchant-risk team has a review coming. But yes, I have the list, and it is correct. So, the proposal.
  5. Tom Ashdown
    Tom Ashdown None
    Right, so what I want to do, no drama, is walk you through what's in it, then we get something in the diary for the decision. Is that alright?
  6. Joost Verbeek
    Joost Verbeek None
    That is alright. Go.
  7. Tom Ashdown
    Tom Ashdown None
    So you're looking at the Growth tier. That's the one built for several teams, so your account managers and merchant risk working off the same picture. You get chat and search and pages, plus the dashboards builder, and a review with us every quarter.
  8. Joost Verbeek
    Joost Verbeek None
    What was agreed was three sources. HubSpot, Zendesk and the accounting system. Is that still the scope?
  9. Tom Ashdown
    Tom Ashdown None
    Those three, yes. Exactly those. And the whole thing gets built inside your own Snowflake account, so the data stays with you. Nothing leaves.
  10. Joost Verbeek
    Joost Verbeek None
    To be honest, this is the main point for me. The risk team will ask me this in the first minute. Where does the data sit, who can see it.
  11. Tom Ashdown
    Tom Ashdown None
    Sure. It's your Snowflake, your access rules. We run inside it. I can get our solutions engineer to write that up properly if it helps you with the risk team.
  12. Joost Verbeek
    Joost Verbeek None
    Please do. One page. Not marketing.
  13. Tom Ashdown
    Tom Ashdown None
    One page, not marketing. Leave that with me.
  14. Joost Verbeek
    Joost Verbeek None
    So what is the number?
  15. Tom Ashdown
    Tom Ashdown None
    Right. I don't like quoting from memory, so I'll confirm it in writing today, but the deal value on the proposal is fifty-seven thousand. That's the total, all-in, so the one-off implementation is in there with the first year's subscription.
  16. Joost Verbeek
    Joost Verbeek None
    So the fifty-seven is not what I pay every year.
  17. Tom Ashdown
    Tom Ashdown None
    No, no. It's the whole deal value for the start. The subscription then carries on annually, and I'll put the yearly figure on its own line so there's no confusion.
  18. Joost Verbeek
    Joost Verbeek None
    Good. I do not accept a vague number. If finance sees fifty-seven and thinks it is a yearly price, I have a problem.
  19. Tom Ashdown
    Tom Ashdown None
    Completely fair. Two lines. Implementation, then subscription. You'll be able to point at each.
  20. Joost Verbeek
    Joost Verbeek None
    Okay. Now the delivery. What is the plan after signature? Who does what?
  21. Tom Ashdown
    Tom Ashdown None
    So the proposal has the timeline set out, and I'd rather you read it than I paraphrase it from memory. Broadly, we connect your three sources, check the data lands properly, and then your people start asking it questions. Our customer success lead for you, Elena Novak, runs that side.
  22. Joost Verbeek
    Joost Verbeek None
    And if a connector is late? What was agreed was that connectors are live within a number of days. I want it in the order form.
  23. Tom Ashdown
    Tom Ashdown None
    Yeah, that's how we do it. The connectors you name in the order form carry a commitment to be live within a set number of days. It's written in, not a handshake.
  24. Joost Verbeek
    Joost Verbeek None
    Good. Then I will read that part carefully.
  25. Tom Ashdown
    Tom Ashdown None
    I'd expect nothing less, to be fair.
  26. Joost Verbeek
    Joost Verbeek None
    How many users is in Growth? I do not want a surprise when the account managers all want to log in.
  27. Tom Ashdown
    Tom Ashdown None
    Growth comes with a decent number of users and room on connectors, and if you grow past that you can add blocks of users on top. I'll put the exact allowance in the written proposal rather than say it off the top of my head.
  28. Joost Verbeek
    Joost Verbeek None
    So the plan is: you write the numbers, I check, then we talk again.
  29. Tom Ashdown
    Tom Ashdown None
    That's the plan. Now, timing. You mentioned before that you'd like this settled before the year end?
  30. Joost Verbeek
    Joost Verbeek None
    Yes. Our finance team closes the budget in December. I would like to decide by 16 Dec 2025. Later than that, it moves to next year, and I do not want that.
  31. Tom Ashdown
    Tom Ashdown None
    Then let's pencil 16 Dec 2025 as the target for signature, and work backwards. If I get you the written proposal tomorrow, and the data page, what do you need from your side to get through security and finance?
  32. Joost Verbeek
    Joost Verbeek None
    Security is a short review, one colleague in IT. Finance wants the document with the two lines. I can have both by the end of the month, I think. I will say it plainly if it is not possible.
  33. Tom Ashdown
    Tom Ashdown None
    Brilliant, that's all I'd ask. So I'll send the proposal and the one pager tomorrow, and I'll book a short call after your review so we can pick up anything that's come up.
  34. Joost Verbeek
    Joost Verbeek None
    Good. And the list of actions, please. In writing. Who, and by when.
  35. Tom Ashdown
    Tom Ashdown None
    Will do. You'll have it in the same email. Cheers, Joost, speak soon.
  36. Joost Verbeek
    Joost Verbeek None
    Thank you, Tom. Until then.

BB-Demo is a fictional company; every organisation and person here is invented. B-Brain is the tool. Built by site/build_site.py from the site tree, data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Brain 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 Brain in the header. Type a question, or pick one of the examples.

The site itself does not call an AI model; answers in Claude come from the same figures you see here.

What the data covers

DataRecords
Organisations75
People at customers290
BB-Demo staff40
Calls784
Email threads1,169
Support tickets449
Documents477
Deals117
Invoices101
Events49
News items56

Data as of Fri 9 Oct 2026. Text marked AI was written by the brain 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.

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

Who to contact

Email support@b-brain.example or talk to your B-Brain account team. Tell us the page address and what looked wrong; a screenshot helps.

Ask B

Ask B

B-Brain · read-only