What it says
What this says
As at Fri 9 Oct 2026BG-Demo's onboarding plan for Vellacott Payments, prepared by Hamza Akhtar on 15 Jul 2025 and marked Final. It lists a contract of 10 Jul 2025 to 9 Jul 2026 with contracted ARR of £99k and 150 licensed users. It states no availability or P1 figures.
What it is: a delivery plan in four phases, covering foundations, connect and index, bringing the teams on, and go-live and handover. It is written for the customer's programme sponsor and hands over to Daniel Okafor for adoption, quarterly reviews and the renewal conversation.
Commits: the contract summary table gives the tier as Enterprise, the contract end as 9 Jul 2026 and the licensed users as 150. Phase two includes "Set up single sign-on and user provisioning for the Enterprise tier."
Not settled: it is a plan, not an order form, so it does not set service levels, credits, billing or payment terms. The £99k is the figure this plan labels as contracted annual recurring revenue; it should be checked against the executed order form.
Stale: the contract end of 9 Jul 2026 is before the as-of date, and the plan does not say what happened at renewal. Its "Current position" section reflects July 2025 only.
As found in this document
As at Fri 9 Oct 2026- Date end9 Jul 2026Source: the AI read of this record
- Date start10 Jul 2025Source: the AI read of this record
- Price£99,000Source: the AI read of this record
- TierEnterpriseSource: the AI read of this record
- Contract start10 Jul 2025Source: the AI read of this record
- Contract end9 Jul 2026Source: the AI read of this record
- Annual recurring revenue (contracted)£99,000Source: the AI read of this record
- Licensed users150Source: the AI read of this record
Body
Vellacott Payments - Onboarding Plan
Status: Final Prepared by: Hamza Akhtar, Implementation Consultant, BG-Demo Date: 15 Jul 2025
Purpose
This plan sets out how BG-Demo will bring Vellacott Payments onto B-Glass, running inside your own Snowflake account. The aim is simple: your partnerships, merchant onboarding and complaints teams should be able to see each client together, in one place, rather than reconciling separate systems by hand.
Contract summary
| Item | Detail |
|---|---|
| Customer | Vellacott Payments |
| Tier | Enterprise |
| Contract start | 10 Jul 2025 |
| Contract end | 9 Jul 2026 |
| Annual recurring revenue (contracted) | £99k |
| Licensed users | 150 |
| Account owner | Sophie Ling |
| Customer success manager | Daniel Okafor |
| Implementation lead | Hamza Akhtar |
Phases
Phase one: foundations
- Confirm the Snowflake environment and the access the brain needs.
- Complete any remaining security review support so your risk and compliance colleagues are comfortable with how data is handled.
- Agree the list of source systems to connect first, starting with the CRM and the helpdesk.
Phase two: connect and index
Read the whole document (3,016 characters)
- Connect the agreed sources and check the first full load of records.
- Review the nightly refresh with your IT contact so freshness is understood from the start.
- Set up single sign-on and user provisioning for the Enterprise tier.
Phase three: bring the teams on
- Partnerships first, then merchant onboarding, then complaints.
- A short working session with each team on its own data, so the first questions asked are ones the team actually cares about.
- Name admins on your side who can manage users and connectors after handover.
Phase four: go-live and handover
- Review usage and questions asked with your sponsor.
- Hand over to Daniel Okafor for adoption, quarterly reviews and the renewal conversation.
- Capture lessons and any extra sources for a later phase.
Owners and responsibilities
| Area | BG-Demo owner | Vellacott Payments owner |
|---|---|---|
| Plan and delivery | Hamza Akhtar | Programme sponsor |
| Commercial terms | Sophie Ling | Finance contact |
| Adoption and reviews | Daniel Okafor | Team leads |
| Security questions | Hamza Akhtar | Risk and compliance |
Current position
Only a small group of early users has logged in so far, which is expected at this stage. Nothing is outstanding on support or invoicing.
Risks and how we will handle them
- Source system changes: if a connected system is reconfigured, tell us early so we can check that records still load.
- Key-person dependence: we will encourage a spread of askers across the three teams, not one champion.
- Stale data: the nightly refresh will be reviewed together before go-live.
Next steps
- Confirm the first connectors with your IT contact this week.
- Book the first working session with the partnerships team.
- Hamza Akhtar to share a short status note after the first load.