Veldmaat Payments - Onboarding Plan
Documentfinal Veldmaat Payments: documents · onboarding_plan · final · 2026-01-10
Final onboarding plan prepared by Elena Novak on 10 Jan 2026 for Veldmaat Payments' Growth tier. It sets phases, owners and milestones to connect HubSpot, Zendesk and the accounting system. Price and terms sit in the executed order form, not here.
What it says
What this says
Current to 11 Oct 26Final onboarding plan prepared by Elena Novak on 10 Jan 2026 for Veldmaat Payments' Growth tier. It sets phases, owners and milestones to connect HubSpot, Zendesk and the accounting system. Price and terms sit in the executed order form, not here.
What it is: a B-Brain onboarding plan, marked Final, covering six phases from kick-off to hand over. Teams in scope are account management and merchant risk, with a merchant view as the aim.
Commits: B-Brain to send written actions after every call and to confirm any scope change in writing before work starts. Veldmaat is asked for a named administrator per source system and a single point of contact for access and security.
Not settled: the plan states that "The contracted licensed users and the annual subscription are set out in the executed order form", so no price, user number or connector dates appear here. No go-live date is given.
Risks: merchant names may differ across the three systems, needing a clean-up step. Early usage will be low, and success is judged by questions asked.
As found in this document
Current to 9 Oct 26- Date end4 Jan 2027Source: object_read:doc_003_010
- Date start5 Jan 2026Source: object_read:doc_003_010
- Written actionsI will send written actions after every call, as agreed.I will send written actions after every call, as agreed. · Source: object_read:doc_003_010
- Scope changesany change to scope is confirmed in writing before work startsany change to scope is confirmed in writing before work starts · Source: object_read:doc_003_010
- Customer administratorsA named administrator for each of the three source systems.A named administrator for each of the three source systems. · Source: object_read:doc_003_010
The document
Body
Veldmaat Payments - Onboarding Plan
Status: Final Prepared by: Elena Novak, Customer Success Manager, EU, B-Brain Date: 10 Jan 2026 Account owner: Tom Ashdown
Purpose
This plan sets out how B-Brain and Veldmaat Payments will bring the company brain live inside Veldmaat's own Snowflake account. The aim, as agreed during the sale, is one view of each merchant, so that account managers and merchant risk work from the same picture.
Agreement at a glance
| Item | Detail |
|---|---|
| Customer | Veldmaat Payments, Amsterdam |
| Tier | Growth |
| Customer since | 5 Jan 2026 |
| Current term ends | 4 Jan 2027 |
| Sources to connect | HubSpot, Zendesk and the accounting system |
| Teams in scope | Account management and merchant risk |
The contracted licensed users and the annual subscription are set out in the executed order form, which remains the reference for price and terms.
Phases, owners and milestones
Read the whole document (2,989 characters)
| Phase | What happens | Owner | Milestone |
|---|---|---|---|
| Kick-off | Confirm scope, success measures and the people involved on both sides | Elena Novak | Agenda and written actions issued after the call |
| Access and security | Agree how B-Brain is given access to the three source systems inside the Snowflake account | Veldmaat's IT lead, with Elena Novak | Access granted and recorded |
| Connect | Load HubSpot, Zendesk and the accounting system, one at a time | B-Brain implementation team | Each connector live and indexing records |
| Model the merchant | Agree how a merchant is identified consistently across the three systems | Veldmaat's head of merchant operations, with Elena Novak | One merchant view signed off |
| Train | Short sessions for account managers and for merchant risk | Elena Novak | Both teams asking real questions of the brain |
| Hand over | Review usage, agree the first check-in and the quarterly review rhythm | Elena Novak and Tom Ashdown | Handover note issued |
What we need from Veldmaat
- A named administrator for each of the three source systems.
- A single point of contact for access and security questions.
- A small group of early users from each team who will test the merchant view and say plainly what is missing.
Risks to watch
- Source quality. If merchant names differ between the CRM, the helpdesk and the accounting system, the merchant view will need a clean-up step. To confirm, we will flag this early rather than late.
- Early adoption. Usage will start low while access is being set up. We will judge success by questions asked once the connectors are live, not by logins in the first days.
- Key people. We will ask for at least two administrators on the Veldmaat side so that one absence does not stall the work.
Communication
I will send written actions after every call, as agreed. I will make sure that any change to scope is confirmed in writing before work starts. Questions about commercial terms go to Tom Ashdown.
Kind regards, Elena