B-Glass
Elena Novak

Veldmaat Payments / BG-Demo – QBR

Callcompleted

Veldmaat Payments logo Veldmaat Payments · 29 May 2026 13:15

At the quarterly review, Veldmaat reported two missed 07:00 refreshes in a month and an invoice dispute still open. Joost Verbeek will not discuss renewal until both are answered in writing.

What was said

What this says

As at Fri 9 Oct 2026

At the quarterly review, Veldmaat reported two missed 07:00 refreshes in a month and an invoice dispute still open. Joost Verbeek will not discuss renewal until both are answered in writing.

What happened: Elena Novak held the quarterly review with Joost Verbeek and Sanne Bakker. Active users have nearly doubled and merchant risk now starts from the merchant view.

Customer view: Sanne reported the refresh not complete at 07:00 twice this month, with two linked high priority tickets. Joost called yesterday's data in a payments company not acceptable and said the refresh is everything.

Commercial: The invoice of £50k against the £45k order form is still open after weeks, and Joost said he would write to Elena's director if he did not hear on Monday. Elena said Growth credits cover availability only, subject to checking the order form.

Watch: Joost said he does not discuss renewal while the refresh is late. The contract runs to 4 Jan 2027, with renewal on 5 Jan 2027.

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

Themes

As at Fri 9 Oct 2026
Theme
Late refresh, open invoice
Importance
complaint
Sentiment
negative
Voice
decision-maker

Who was there

BG-Demo

Them

Follow-up

Next steps

As at Fri 9 Oct 2026
  • Elena Novak speaks to engineering on Monday and writes to Joost the same day with the cause of both late mornings.
  • Elena speaks to the head of finance on Monday about the invoice and writes the same day.
  • Elena checks the executed order form on service credits and confirms in writing.

Risks

As at Fri 9 Oct 2026
  • Two late refreshes in a month put the 5 Jan 2027 renewal at risk, since Joost will not discuss renewal until they are answered.
  • The invoice dispute is unresolved after weeks, and Joost has said he will escalate to Elena's director.
  • If the refresh stays late, merchant risk may revert to the old manual way of working.

Opportunities

As at Fri 9 Oct 2026
  • Active users have nearly doubled against 40 licensed, so adoption is growing without needing more seats.
  • Sanne's draft dashboard could become a standard view once the refresh is stable.

Transcript

  1. Elena Novak
    Elena Novak
    Good afternoon, Joost. Good afternoon, Sanne. Can you both hear me?
  2. Joost Verbeek
    Joost Verbeek
    Yes. Good afternoon.
  3. Sanne Bakker
    Sanne Bakker
    Yes. Hear you.
  4. Elena Novak
    Elena Novak
    Thank you for joining. To confirm, the agenda in my email has five points for this quarterly review. One, usage and who is using the brain. Two, the reliability of the morning refresh. Three, value for the teams. Four, the open question on the invoice. Five, written actions and the renewal timeline.
  5. Joost Verbeek
    Joost Verbeek
    Before that, the last actions. Were they done? The one-page summary for my director, the dashboards walk-through for Sanne, the visit to merchant risk.
  6. Elena Novak
    Elena Novak
    The summary was sent to you, and you corrected two lines, which I changed. The merchant risk visit took place and I will report on it under value. The walk-through for Sanne, to be honest, we have not held yet. It is on my list for this quarter.
  7. Joost Verbeek
    Joost Verbeek
    So one action open. Recorded.
  8. Elena Novak
    Elena Novak
    Recorded. And I will make sure it gets a date today.
  9. Elena Novak
    Elena Novak
    Let me share the usage page. Can you see it now?
  10. Sanne Bakker
    Sanne Bakker
    Yes.
  11. Elena Novak
    Elena Novak
    So, usage. Compared with the previous quarter, active users have nearly doubled. On a typical day it is now between seven and eight people. You are licensed for 40, so you are far from the limit.
  12. Joost Verbeek
    Joost Verbeek
    That is better than I expected. In April it was still around six, I think.
  13. Elena Novak
    Elena Novak
    Yes, it has continued to grow. More account managers, and from the meeting I attended, more of merchant risk. They told me they now start from the merchant view, and use the accounting system only to confirm a figure.
  14. Joost Verbeek
    Joost Verbeek
    I heard the same. Good. That is what I wanted.
  15. Sanne Bakker
    Sanne Bakker
    More users means more people seeing a late refresh. That is the problem.
  16. Elena Novak
    Elena Novak
    Yes, that is a fair way to put it. Let us go to the refresh, then. Sanne, please.
  17. Sanne Bakker
    Sanne Bakker
    Refresh not complete at 07:00 again. Twice this month. Once on a Tuesday, once on a Thursday. See ticket from Thursday. Both times the account managers saw yesterday's data until later in the morning.
  18. Joost Verbeek
    Joost Verbeek
    In a payments company, merchant risk looking at yesterday's picture is not acceptable. To be honest, this is the main thing for me today.
  19. Elena Novak
    Elena Novak
    Understood, and I do not want to soften it. To confirm, the nightly refresh should be complete by 07:00 on business days. That applies to every tier, including Growth. Two misses in a month is a miss against that.
  20. Joost Verbeek
    Joost Verbeek
    So what is the plan?
  21. Elena Novak
    Elena Novak
    I will not give you a vague answer. I have asked engineering for the cause of both mornings, and I do not have a written explanation yet. I will tell you as soon as I have one, and I will not promise a fix date before they have confirmed it to me.
  22. Joost Verbeek
    Joost Verbeek
    Not good enough as a timeline. When do I hear?
  23. Elena Novak
    Elena Novak
    Fair. I will speak to engineering on Monday and write to you the same day with what they say and when you will hear again. That is the commitment from me.
  24. Joost Verbeek
    Joost Verbeek
    Monday, in writing. Good. I record it.
  25. Sanne Bakker
    Sanne Bakker
    I want the cause, not just a restart. Did a source change on our side? Tell me what to check. I will check.
  26. Elena Novak
    Elena Novak
    That is a good question, and it belongs in the written note. I will ask them what you should look at on your side as well, so you are not guessing.
  27. Sanne Bakker
    Sanne Bakker
    Good.
  28. Joost Verbeek
    Joost Verbeek
    Next. Credits. If the refresh is late, what do I get? I am asking so that I know, not because I want the money.
  29. Elena Novak
    Elena Novak
    To confirm, under the standard terms for Growth, service credits relate to availability only. A brain that answers on stale data was available, so a late refresh on its own is not credited. Freshness credits exist on Enterprise. But the executed order form can change standard terms, so I will check the order form itself and confirm in writing.
  30. Joost Verbeek
    Joost Verbeek
    I signed it. I will read it too. But as I said, credits are not what I want. I want the data on time.
  31. Elena Novak
    Elena Novak
    Agreed. I mention it so you have the full picture. There is also an add-on for Premium support with a named engineer, which I am not trying to sell you today. I only want you to know it exists.
  32. Joost Verbeek
    Joost Verbeek
    I would rather the standard service worked as described. Noted that it exists.
  33. Elena Novak
    Elena Novak
    Understood.
  34. Elena Novak
    Elena Novak
    Let me move to value, if you are content with that. Joost, what are the teams getting?
  35. Joost Verbeek
    Joost Verbeek
    Account managers prepare merchant calls in much less time. They told me, not me asking. Merchant risk can see Zendesk history next to HubSpot notes, so a flagged merchant is no longer a three-system exercise.
  36. Elena Novak
    Elena Novak
    And the reconciliation with the accounting system, the thing they still did by hand?
  37. Joost Verbeek
    Joost Verbeek
    Better. Not gone. They still want to see the source figure for payouts. Maybe that stays.
  38. Sanne Bakker
    Sanne Bakker
    That one is not a connector gap. They do not trust a number until they see it in source. That is a habit. It will change when the refresh is reliable.
  39. Joost Verbeek
    Joost Verbeek
    Yes. Which is why the refresh is everything. If it is late, they go back to the old way, and then the value is gone.
  40. Elena Novak
    Elena Novak
    That is clear, and I think it is the right link to make. Reliability first, then adoption follows.
  41. Elena Novak
    Elena Novak
    Sanne, on the dashboards builder. You said last time there were questions asked repeatedly. Did you start on anything?
  42. Sanne Bakker
    Sanne Bakker
    A little. One view for merchants with open tickets and a change in activity. It is rough. I do not want to spend more time until I know the refresh is stable. Otherwise I build on sand.
  43. Elena Novak
    Elena Novak
    Reasonable. Then I propose the walk-through after the refresh answer, so your time is well used. I will suggest two slots in writing.
  44. Sanne Bakker
    Sanne Bakker
    Fine.
  45. Joost Verbeek
    Joost Verbeek
    Now the invoice. Did Finance come back to you?
  46. Elena Novak
    Elena Novak
    I have to be precise. I wrote to our finance team after our last call and I sent you my note. I do not yet have a written answer from them that I can give you, and I will not describe their work or date it before I have checked with them.
  47. Joost Verbeek
    Joost Verbeek
    So it is still open. The order form says £45,000. The invoice says £50,000. What was agreed was £45,000. It has been weeks.
  48. Elena Novak
    Elena Novak
    Yes, it is still open, and you are right that it has taken too long. To confirm, the executed order form is the document we work from. I will speak to the head of finance on Monday as well, together with the engineering question, and I will write to you the same day.
  49. Joost Verbeek
    Joost Verbeek
    Both on Monday. Good. If I do not hear on Monday I will write to your director.
  50. Elena Novak
    Elena Novak
    That is fair, Joost. I will make sure you hear.
  51. Sanne Bakker
    Sanne Bakker
    One more thing on the tickets. Two tickets this month, both high priority, both the refresh. I want them linked so nobody treats them as separate.
  52. Elena Novak
    Elena Novak
    Yes, I will ask support to link them and mention both in the engineering question. Thank you for raising it.
  53. Sanne Bakker
    Sanne Bakker
    Good.
  54. Elena Novak
    Elena Novak
    Let me say a word about the contract, and then actions. The contract runs to 4 Jan 2027 and the renewal date is 5 Jan 2027. I would like to begin that conversation in the autumn, in writing first. I do not want to push it before the refresh and the invoice are settled.
  55. Joost Verbeek
    Joost Verbeek
    Correct order. First fix, then renewal. I do not discuss renewal while the refresh is late.
  56. Elena Novak
    Elena Novak
    Understood. I will not raise it before you have the written answers.
  57. Joost Verbeek
    Joost Verbeek
    And the number of users. Do we need more?
  58. Elena Novak
    Elena Novak
    Not at this level. You are licensed for 40 and well below it. If merchant risk and the account managers all join, we can look at it again. There is no reason to buy anything now.
  59. Joost Verbeek
    Joost Verbeek
    Good. I like to hear that from a supplier.
  60. Elena Novak
    Elena Novak
    Then the actions, numbered, so we agree. One, on Monday I speak to engineering, ask for the cause of both late mornings and what Sanne should check on your side, and write to you the same day. Two, on Monday I also speak to the head of finance about the invoice and write the same day. Three, I check the executed order form on service credits and confirm in writing. Four, support links the two tickets. Five, I propose two slots for the dashboards walk-through for Sanne, after the refresh answer. Is that complete?
  61. Joost Verbeek
    Joost Verbeek
    Add: nothing about renewal until one and two are answered.
  62. Elena Novak
    Elena Novak
    Added as six. Thank you.
  63. Sanne Bakker
    Sanne Bakker
    And I send you the exact times of the misses. So the log matches yours.
  64. Elena Novak
    Elena Novak
    Yes please, Sanne. That is seven, for you. I will include it in the written actions.
  65. Joost Verbeek
    Joost Verbeek
    One last question. This is a quarterly review. Next one is when?
  66. Elena Novak
    Elena Novak
    Next quarter. I will propose a date in the same email as the actions, and I will check it with your diary before I fix it.
  67. Joost Verbeek
    Joost Verbeek
    Good. Then I have nothing more.
  68. Sanne Bakker
    Sanne Bakker
    Nothing.
  69. Elena Novak
    Elena Novak
    Thank you both. The usage is moving the right way, and I take your point that it does not count if the morning data is late. Written actions follow this afternoon. Kind regards, and a good weekend.
  70. Joost Verbeek
    Joost Verbeek
    You too. Tot ziens.
  71. Sanne Bakker
    Sanne Bakker
    Bye.

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