B-Glass
Veldmaat Payments logo

Veldmaat Payments - Onboarding Plan

Documentfinal

Veldmaat Payments logo Veldmaat Payments · onboarding plan · final · 10 Jan 2026

Final version 1 onboarding plan, dated 10 Jan 2026, for bringing Veldmaat Payments live on the Growth tier. It states a contracted £45k and 40 licensed users, runs the contract 5 Jan 2026 to 4 Jan 2027, and sets four phases with no dates.

What it says

What this says

As at Fri 9 Oct 2026

Final version 1 onboarding plan, dated 10 Jan 2026, for bringing Veldmaat Payments live on the Growth tier. It states a contracted £45k and 40 licensed users, runs the contract 5 Jan 2026 to 4 Jan 2027, and sets four phases with no dates.

What it is: a BG-Demo onboarding plan written by Elena Novak, Customer Success Manager, EU, with Tom Ashdown as account owner. The aim is "one view of each merchant across HubSpot, Zendesk and the accounting system".

Commits: three connectors (HubSpot, Zendesk, the accounting system) loading with a first nightly refresh, then sign-off of the merchant view by account management and merchant risk. Training sessions follow, and the account then moves to "quarterly reviews".

Unusual: nothing off the standard Growth terms. The plan does not state service levels, availability or connector delivery dates.

Not settled: no dates are given for any phase, and the plan says dates depending on the finance team will be confirmed first. It says "very few people have signed in so far", and it does not name the customer sponsor or administrator. Accounting system access may depend on a colleague in IT.

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

As found in this document

As at Fri 9 Oct 2026
  • Date end4 Jan 2027Source: the AI read of this record
  • Date start5 Jan 2026Source: the AI read of this record
  • Price£45,000Source: the AI read of this record
  • TierGrowthSource: the AI read of this record
  • Contract start5 Jan 2026Source: the AI read of this record
  • Contract end4 Jan 2027Source: the AI read of this record
  • Annual recurring revenue (contracted)£45,000Source: the AI read of this record
  • Licensed users40Source: the AI read of this record
  • Phase two milestoneall three connectors loading, with the first nightly refresh completedSource: the AI read of this record
  • Usage reviewreviewed weekly until the core group is activeSource: the AI read of this record

Body

Veldmaat Payments - Onboarding Plan

Status: Final, version 1 Prepared by: Elena Novak, Customer Success Manager, EU, BG-Demo Account owner: Tom Ashdown, BG-Demo Date: 10 Jan 2026

1. Purpose

This plan sets out how BG-Demo will bring Veldmaat Payments live on B-Glass on the Growth tier. The aim, as agreed during the sale, is one view of each merchant across HubSpot, Zendesk and the accounting system, so that account managers and merchant risk work from the same picture.

2. Contract summary

ItemDetail
CustomerVeldmaat Payments, Amsterdam
TierGrowth
Contract start5 Jan 2026
Contract end4 Jan 2027
Annual recurring revenue (contracted)£45k
Licensed users40

3. Where we are today

The contract started on 5 Jan 2026 and the account is in onboarding. To confirm, very few people have signed in so far, which is expected at this stage. The first priority is therefore to connect the sources and to bring a core group of users in early.

4. Phases, owners and milestones

Phase one: Kick-off and access

Read the whole document (3,529 characters)
  1. Confirm the project team on both sides and the working agenda. Owner: Elena Novak.
  2. Agree who at Veldmaat Payments administers the brain. Owner: Veldmaat Payments sponsor, with Elena Novak.
  3. Confirm access to the Snowflake account in which the brain will run. Owner: Veldmaat Payments IT.

Milestone: access confirmed in writing.

Phase two: Connect the sources

  1. Connect HubSpot and confirm that merchant records load. Owner: BG-Demo implementation team.
  2. Connect Zendesk and confirm that tickets are linked to the right merchant. Owner: BG-Demo implementation team.
  3. Connect the accounting system and confirm that invoice data matches the merchant view. Owner: BG-Demo implementation team, with the Veldmaat Payments finance team.

Milestone: all three connectors loading, with the first nightly refresh completed.

Phase three: Validate the merchant view

  1. Walk through a small sample of merchants with account managers and compare the brain with what they know. Owner: Elena Novak.
  2. Log every mismatch in writing and agree who corrects it, the source system or the connector. Owner: Elena Novak.
  3. Review the same sample with merchant risk. Owner: Veldmaat Payments merchant risk lead.

Milestone: account management and merchant risk both sign off the merchant view.

Phase four: Training and adoption

  1. Run a first training session for account managers. Owner: Elena Novak.
  2. Run a second session for merchant risk. Owner: Elena Novak.
  3. Agree a short list of questions each team will ask the brain in their first weeks. Owner: team leads at Veldmaat Payments.

Milestone: a core group of users asking questions each week.

5. Risks and open points

  • Access to the accounting system may depend on a colleague in IT. I will make sure this is raised in the first week.
  • Any date that depends on the Veldmaat Payments finance team will be confirmed with that team before it is written down.
  • Because adoption starts from a very low base, usage will be reviewed weekly until the core group is active.

6. Communication

Elena Novak will send a written summary with actions after every working session. Commercial questions go to Tom Ashdown.

7. Hand-over to business as usual

Once phase four is complete, the account moves to the normal Growth rhythm of quarterly reviews. The first review will report on usage, value and any open issues.

Kind regards, Elena

Documentsmade from

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