Veldmaat Payments - Onboarding Plan
Documentfinal Veldmaat Payments: documents · onboarding_plan · final · 2026-01-10
Final onboarding plan dated 10 Jan 2026, prepared by Elena Novak for a Growth tier customer since 5 Jan 2026. It sets six phases to connect HubSpot, Zendesk and the accounting system. It states no price, service levels or connector dates.
What it says
What this says
Current to 11 Oct 26Final onboarding plan dated 10 Jan 2026, prepared by Elena Novak for a Growth tier customer since 5 Jan 2026. It sets six phases to connect HubSpot, Zendesk and the accounting system. It states no price, service levels or connector dates.
What it is: a BB-Demo-authored delivery plan to bring the brain live in Veldmaat's own Snowflake account, with the aim of "one view of each merchant". It lists six phases, each with an owner and milestone.
Commits: BB-Demo to written actions after every call and written confirmation of any scope change before work starts. The plan states that the current term ends 4 Jan 2027 and that the executed order form "remains the reference for price and terms".
Not settled: licensed users, subscription price, connector go-live dates and service levels are all left to the order form, which is not in this document. No dates are set for the phases.
Risks named: inconsistent merchant names across the three systems, low early usage, and reliance on a single administrator. The plan asks for at least two administrators on the Veldmaat side.
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 changesI will make sure that any change to scope is confirmed in writing before work starts.I will make sure that any change to scope is confirmed in writing before work starts. · Source: object_read:doc_003_010
- Price and termsThe contracted licensed users and the annual subscription are set out in the executed order form, which remains the reference for price and terms.The contracted licensed users and the annual subscription are set out in the executed order form, which remains the reference for price and terms. · Source: object_read:doc_003_010
The document
Body
Veldmaat Payments - Onboarding Plan
Status: Final Prepared by: Elena Novak, Customer Success Manager, EU, BB-Demo Date: 10 Jan 2026 Account owner: Tom Ashdown
Purpose
This plan sets out how BB-Demo 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 BB-Demo 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 | BB-Demo 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