B-Brain
Yusuf Demir

Veldmaat Payments / BB-Demo – Onboarding

Callcompleted

Veldmaat Payments logo Veldmaat Payments · 2026-02-02 10:00

Joost Verbeek said the third connector is late and that the merchant risk team and account managers will not use the brain until the refresh is reliable. Two people use a 40-user contract: not the value they bought.

What was said

What this says

Current to 13 Oct 26

Joost Verbeek said the third connector is late and that the merchant risk team and account managers will not use the brain until the refresh is reliable. Two people use a 40-user contract: not the value they bought.

What happened: Yusuf Demir reported on the connectors and the refresh with Joost Verbeek and Sanne Bakker. The accounting connector is not built because the service user is still with the customer's IT.

Customer view: Joost said this is not what he expected by now and that two users on 40 is not the value bought. Sanne counted three misses in two weeks and said two good mornings is not a pattern.

Commercial: Joost stated for the record that adoption waits on a reliable refresh. Yusuf changed the page size and moved the Zendesk load earlier.

Watch: Joost is escalating with IT and wants the accounting mapping within a few working days of the service user existing. Yusuf declined to discuss commercial matters.

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

Themes

Current to 9 Oct 26
Theme
Value doubt, unreliable refresh
Importance
complaint
Sentiment
negative
Voice
decision-maker

Who was there

BB-Demo

Them

Follow-up

Next steps

Current to 9 Oct 26
  • Joost Verbeek escalates the service user with the customer's IT on 2 Feb 2026.
  • Yusuf Demir builds the accounting mapping within a few working days of the service user existing.
  • Yusuf checks the merchant duplicates after that night's load and Elena Novak sends the written actions.

Risks

Current to 9 Oct 26
  • Joost Verbeek said two users on a 40-user contract is not the value bought, which puts the renewal case at risk.
  • Refresh misses at 07:00 keep the merchant risk team and account managers away from the brain.
  • The accounting connector is late and depends on the customer's IT creating a service user.

Opportunities

Current to 9 Oct 26
  • A reliable refresh and the third connector would open the way to rolling out to account managers and merchant risk.

Transcript

  1. Yusuf Demir
    Yusuf Demir None
    Hello. Yusuf here. Can you hear me?
  2. Sanne Bakker
    Sanne Bakker None
    Yes.
  3. Joost Verbeek
    Joost Verbeek None
    Good morning, Yusuf. I can hear you. Sanne is with me in the room, so you may get a little echo.
  4. Yusuf Demir
    Yusuf Demir None
    No echo on my side. Thanks for making time. I will start with where things are. The HubSpot connector, last good load was this morning, finished before seven. Zendesk, last good load also this morning. Row count is higher than last week, because of the history.
  5. Joost Verbeek
    Joost Verbeek None
    Before we go on. Were the actions from the last call done? I would like to know that first.
  6. Yusuf Demir
    Yusuf Demir None
    Some. Hannah sent the field list. I wrote to Sanne about the late refresh. The accounting connector is not done, because the service user is not there yet.
  7. Joost Verbeek
    Joost Verbeek None
    So the third connector is not live. To be honest, that is not what I expected by now. What was agreed was that all three would be in the first weeks. So what is the plan?
  8. Yusuf Demir
    Yusuf Demir None
    I can only speak to my part. Once the service user exists, I need a short window to build and test the mapping. I won't give you a date without Sanne's side. I also don't talk about the commercial side, that is Elena and the account owner.
  9. Sanne Bakker
    Sanne Bakker None
    The service user. My finance team approved the scope last week. The request is with IT. They are slow.
  10. Joost Verbeek
    Joost Verbeek None
    I will push IT today. Sanne, send me the ticket reference from your side and I will escalate it. Yusuf, once it is created, how long?
  11. Yusuf Demir
    Yusuf Demir None
    A few working days to get a clean load. Maybe sooner. I'd rather say a few days and be right.
  12. Joost Verbeek
    Joost Verbeek None
    A few days. Good. That is something I can write down.
  13. Yusuf Demir
    Yusuf Demir None
    Second thing, the refresh. Sanne, can you read me the mornings you logged?
  14. Sanne Bakker
    Sanne Bakker None
    Last Tuesday. Refresh not complete at 07:00. Again on Thursday. Friday was fine. This morning fine. Three misses in two weeks, counting the one in the ticket.
  15. Yusuf Demir
    Yusuf Demir None
    Right. I looked at those. The source returned a very large page of Zendesk tickets on both mornings. The load waited on it. It finished at around twenty past seven on Tuesday and a little later on Thursday.
  16. Joost Verbeek
    Joost Verbeek None
    A little later. How much later.
  17. Yusuf Demir
    Yusuf Demir None
    Thursday, about half past seven. I don't have the exact minute in front of me and I'd rather not guess.
  18. Joost Verbeek
    Joost Verbeek None
    Fine. So what has changed so that it does not happen again?
  19. Yusuf Demir
    Yusuf Demir None
    I changed the page size and I moved the Zendesk load earlier in the run. I've re-run Tuesday's load to check the counts, and I told Elena before I did it. Row count matched the source.
  20. Sanne Bakker
    Sanne Bakker None
    Friday and this morning were fine. Two is not a pattern. I will keep logging.
  21. Yusuf Demir
    Yusuf Demir None
    Please do. If it misses again I want the timestamp straight away.
  22. Joost Verbeek
    Joost Verbeek None
    I want to be clear for the record. Our merchant risk team will not use the brain until the refresh is reliable. Account managers the same. The contract is for 40 users and today we have two people. That is not the value we bought.
  23. Yusuf Demir
    Yusuf Demir None
    Understood. That is fair, and I'll make sure it is in the notes for Elena.
  24. Sanne Bakker
    Sanne Bakker None
    There is another thing. The duplicate merchants in HubSpot. I fixed most. Four are left. Can you check after tonight's load that they are merged?
  25. Yusuf Demir
    Yusuf Demir None
    Yes. I'll check the merchant count after tonight's load and tell you what it is. Numbers first.
  26. Joost Verbeek
    Joost Verbeek None
    Good. Then let me summarise, so nobody can say later it was unclear. One. I escalate the service user with our IT today. Two. Yusuf builds the accounting mapping within a few working days of that. Three. Yusuf checks the merchant duplicates after tonight. Four. Sanne keeps her log and sends any miss. Five. Elena sends written actions. Yes?
  27. Yusuf Demir
    Yusuf Demir None
    Yes. I'll pass this to Elena straight after the call.
  28. Sanne Bakker
    Sanne Bakker None
    Yes.
  29. Joost Verbeek
    Joost Verbeek None
    Good. Thank you, Yusuf. Met vriendelijke groet.
  30. Yusuf Demir
    Yusuf Demir None
    Thanks, both. Speak soon.

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
Organisations225
People at customers862
BB-Demo staff58
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 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.

Help

Ask B

B-Brain · read-only