Veldmaat Payments - Onboarding Plan
Documentfinal Veldmaat Payments: documents · onboarding_plan · final · 2026-01-07
Final onboarding plan dated 7 Jan 2026 for Veldmaat Payments on the Growth tier, subscription 5 Jan 2026 to 4 Jan 2027. It sets four phases to connect HubSpot, Zendesk and Exact Online and map merchants. It states no price, availability or response times.
What it says
What this says
Current to 11 Oct 26Final onboarding plan dated 7 Jan 2026 for Veldmaat Payments on the Growth tier, subscription 5 Jan 2026 to 4 Jan 2027. It sets four phases to connect HubSpot, Zendesk and Exact Online and map merchants. It states no price, availability or response times.
What it is: a BB-Demo working plan prepared by Yusuf Demir, Data Engineer, in four phases. The goal is "one trusted view of each merchant across HubSpot, Zendesk and Exact Online".
Commits: BB-Demo to report row counts after each first load, report a failed load with the source and the last good load time, and tell the customer success manager before the customer about any re-run. Exact Online "carries a go-live commitment in the order form".
Unusual: the plan names a go-live commitment but does not state its date or number of days. It is a plan, not a contract.
Not settled: price, availability, support response times and service credits are not stated. Only one person was using the brain at the plan date, and the plan flags a single champion on the customer side as a risk. The document does not show whether the phases were completed.
As found in this document
Current to 9 Oct 26- Date end4 Jan 2027Source: object_read:doc_003_009
- Date start5 Jan 2026Source: object_read:doc_003_009
- Row countsReport row counts per source back to the customer lead after each first load.Report row counts per source back to the customer lead after each first load. · Source: object_read:doc_003_009
- Failed loadA failed load is reported with the source named and the time of the last good load.A failed load is reported with the source named and the time of the last good load. · Source: object_read:doc_003_009
- Re-run of a loadAny re-run of a load is reported to the customer success manager before the customer is told.Any re-run of a load is reported to the customer success manager before the customer is told. · Source: object_read:doc_003_009
- Exact OnlineConnect Exact Online, which carries a go-live commitment in the order form.Connect Exact Online, which carries a go-live commitment in the order form. · Source: object_read:doc_003_009
- Nightly refreshCheck that the nightly refresh finishes before the start of the Amsterdam working day.Check that the nightly refresh finishes before the start of the Amsterdam working day. · Source: object_read:doc_003_009
The document
Body
Veldmaat Payments - Onboarding Plan
Final | Version one | 7 Jan 2026 | Prepared by Yusuf Demir, Data Engineer, BB-Demo
1. Summary
Veldmaat Payments is on the Growth tier. The subscription began on 5 Jan 2026 and runs to 4 Jan 2027. The goal of onboarding is one trusted view of each merchant across HubSpot, Zendesk and Exact Online, so that account managers and the merchant risk team work from the same picture.
At the date of this plan only one person is using the brain, which is expected in the first days. The Growth user allowance is available for the wider group as they are brought on.
2. Roles
| Role | Person | Responsibility |
|---|---|---|
| Account owner | Tom Ashdown | Commercial terms and the order form |
| Customer success manager | Elena Novak | Adoption, reviews and the renewal conversation |
| Data engineer | Yusuf Demir | Connectors, loads and row counts |
| Customer lead | Veldmaat's Head of Data | Access, data owners and sign-off of mappings |
3. Phases
Phase one: access and first connectors
Read the whole document (2,434 characters)
- Confirm access to Veldmaat's Snowflake account.
- Connect HubSpot and Zendesk.
- Report row counts per source back to the customer lead after each first load.
Phase two: Exact Online and merchant mapping
- Connect Exact Online, which carries a go-live commitment in the order form.
- Map each merchant consistently across the three sources.
- Review the mapping with the account managers and the merchant risk team.
Phase three: users and dashboards
- Invite the first group of account managers and merchant risk users.
- Build the first dashboards with the customer lead.
- Agree who in each team will ask questions of the brain first.
Phase four: review
- Check that the nightly refresh finishes before the start of the Amsterdam working day.
- Hold the first review with Elena Novak.
- Record anything outstanding against the order form.
4. Working rules
- Any re-run of a load is reported to the customer success manager before the customer is told.
- A failed load is reported with the source named and the time of the last good load.
- Questions about price or terms go to Tom Ashdown.
5. Risks to watch
- A single champion on the customer side: widen the group of users early.
- Source systems changing during the build: ask the data owners to flag changes.
- Connector delays: report them against the order form commitment as soon as they appear.
Unusual terms
Current to 9 Oct 26- Exact Online go-live commitment referenced but not dated
- Refresh check against Amsterdam working day