Veldmaat Payments: documents logo

Veldmaat Payments - QBR

Documentfinal

Veldmaat Payments: documents logo Veldmaat Payments: documents · qbr_deck · final · 2026-09-21

Growth tier QBR deck prepared by Elena Novak on 21 Sep 2026. Use is rising with headroom under the user allowance, one invoice is overdue, and the term ends on 4 Jan 2027. It states no price, availability or response-time figures.

What it says

What this says

Current to 11 Oct 26

Growth tier QBR deck prepared by Elena Novak on 21 Sep 2026. Use is rising with headroom under the user allowance, one invoice is overdue, and the term ends on 4 Jan 2027. It states no price, availability or response-time figures.

What it is: a customer success review written by Elena Novak, Customer Success Manager, EU, ahead of the renewal. It is a BB-Demo document, not a contract, and sets out usage, value, issues and a renewal plan.

Commits: it binds no one commercially. It assigns internal actions to Elena and Tom Ashdown, such as confirming the invoice position with Finance and agreeing a value case with Veldmaat's sponsor.

Unusual: usage is described only in words, with no figures. The deck notes "The point to watch is whether a small number of people are asking most of the questions."

Not settled: the overdue invoice is not identified or quantified. The one high priority ticket's cause and first response time are not stated, and the renewal conversation is "a plan, not yet held".

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

As found in this document

Current to 9 Oct 26
  • Date end4 Jan 2027Source: object_read:doc_003_012
  • Date renewal4 Jan 2027Source: object_read:doc_003_012
  • Date start5 Jan 2026Source: object_read:doc_003_012

The document

Body

Veldmaat Payments - QBR

Quarterly business review, Growth tier Prepared by Elena Novak, Customer Success Manager, EU, BB-Demo Date: 21 Sep 2026

Where we are

  • Veldmaat has been a customer since 5 Jan 2026 and the current term ends on 4 Jan 2027, so the renewal is now close.
  • The brain remains live over HubSpot, Zendesk and the accounting system.
  • Active use has grown again on the previous quarter, building on the earlier increase.
  • One invoice is currently overdue. I will confirm the position with Finance and share an update in writing, as agreed, before anything is discussed with Veldmaat's finance team.

Usage

MeasurePosition
Active usersHigher than last quarter and still rising
Licensed usersBelow the Growth user allowance, with headroom remaining
SpreadBoth account management and merchant risk are asking questions

To confirm, the growth is steady rather than sudden, which is the pattern we would hope for. The point to watch is whether a small number of people are asking most of the questions.

Value

Read the whole document (2,338 characters)
  • The merchant view is now part of how account managers prepare for conversations with merchants.
  • Merchant risk uses the same data as account management, so disagreements about whose figures are right have reduced.
  • Before the renewal conversation we should have a short, written value case agreed with Veldmaat, in their own words.

Issues

  • One ticket was raised in the last thirty days and it was marked high priority.
  • I will send the written summary of cause and resolution, checked against the Growth service level for first response.
  • The overdue invoice is a billing matter and not, as far as the evidence shows, a sign of dissatisfaction. We will check the facts with Finance before drawing a conclusion.

Plan for the renewal

ActionOwner
Confirm the invoice position with Finance and report back in writingElena Novak
Agree the value case with Veldmaat's sponsorElena Novak
Book the renewal conversation, including the renewal noticeElena Novak and Tom Ashdown
Discuss whether extra users or a further team are worth addingTom Ashdown

The renewal conversation is a plan, not yet held. I will make sure that its outcome is recorded in writing once it has taken place.

Kind regards, Elena

Documentsmade from

Unusual terms

Not yet analysedThe unusual terms of object_read:doc_003_012 are empty: the record found none.

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