What it says
What this says
Current to 13 Oct 26BB-Demo's onboarding plan, version 1 (Final) dated 2 Sep 2023, for a Starter subscription with 15 licensed users and £20k shown as the contracted figure. It runs from 30 Aug 2023 to 29 Aug 2024. It states no availability or P1 response commitments.
What it is: a delivery plan written by Callie Brennan, Implementation Consultant, for the client-relationship team. It sets out four phases from kickoff to handover, with an owner and a done-when test for each step.
Commits: the subscription is stated as "Subscription start | 30 Aug 2023" to "Subscription end | 29 Aug 2024", Starter tier, 15 licensed users. Callie says "I do not start a connector without written access" and will flag late credentials the same day.
Unusual: nothing off the standard terms. The plan names no connector list, service levels or service credits, and points to the signed order form for connectors.
Not settled: it is not the order form, so contracted terms must be checked there. It dates from 2023 and says nothing about the later term, renewal outcome or price change, so treat it as historic. The evidence does not show whether a second person was ever shown the setup note.
As found in this document
Current to 9 Oct 26- Date end29 Aug 2024Source: object_read:doc_159_007
- Date renewal29 Aug 2024Source: object_read:doc_159_007
- Date start30 Aug 2023Source: object_read:doc_159_007
- Price£19,500Source: object_read:doc_159_007
- TierStarterSource: object_read:doc_159_007
- Licensed users15Source: object_read:doc_159_007
- Subscription termSubscription start 30 Aug 2023, Subscription end 29 Aug 2024Subscription start 30 Aug 2023, Subscription end 29 Aug 2024 · Source: object_read:doc_159_007
- Connector accessI do not start a connector without written access.I do not start a connector without written access. · Source: object_read:doc_159_007
- Late credentialseach late source moves the first refresh back by the same amount. I will flag it the same day.each late source moves the first refresh back by the same amount. I will flag it the same day. · Source: object_read:doc_159_007
- Renewalrenewal will be raised ahead of that daterenewal will be raised ahead of that date · Source: object_read:doc_159_007
The document
Body
Ardenmore Pension Administration - Onboarding Plan
Version: 1 (Final) Prepared by: Callie Brennan, Implementation Consultant, BB-Demo Date: 2 Sep 2023
1. Purpose
This plan sets out how we get Ardenmore Pension Administration from signed order form to a working company brain for its client-relationship team. It lists the phases, who owns each step, and what I need from your side before we switch on the refresh.
2. Contract at a glance
| Tier | Starter |
| Licensed users | 15 |
| Annual recurring revenue (contracted) | £20k |
| Subscription start | 30 Aug 2023 |
| Subscription end | 29 Aug 2024 |
| BB-Demo account owner | Tom Ashdown |
| BB-Demo customer success manager | Marcus Bell |
| Implementation lead | Callie Brennan |
The Starter tier covers one team, with a fixed number of connectors. The connectors we set up are the ones named in the signed order form.
3. Phases
Phase 1: Access and kickoff (week one)
Read the whole document (3,789 characters)
| Step | Owner | Done when |
|---|---|---|
| Kickoff call to agree scope and the order of connectors | Callie Brennan, Customer sponsor | Connector order agreed in writing |
| Connector credentials supplied | Customer IT contact | Written access received for each source |
| Named admin confirmed | Customer sponsor | One admin named and invited |
What I need from your side is the credentials before the kickoff where possible. I do not start a connector without written access.
Phase 2: Connect and map (weeks two and three)
| Step | Owner | Done when |
|---|---|---|
| Connect each source inside your Snowflake account | Callie Brennan | Source loads and record counts look right |
| Map fields to the brain's data model | Callie Brennan, Customer admin | Each mapping checked against sample records |
| Review of mapped fields | Customer admin | Mappings signed off |
I check each mapping against real records before moving on. Anything that does not map cleanly goes on the open points list rather than being assumed.
Phase 3: First refresh and checks (final week)
| Step | Owner | Done when |
|---|---|---|
| First refresh run | Callie Brennan | Refresh lands with no failed sources |
| Spot checks on answers with the client-relationship team | Callie Brennan, Customer team lead | Team confirms the answers match what they know |
| User invitations sent, up to the licensed number | Customer admin | Users can sign in |
Phase 4: Handover
| Step | Owner | Done when |
|---|---|---|
| Setup note written and shared | Callie Brennan | Note covers connectors, mappings and open points |
| Admin walk-through | Callie Brennan, Customer admin | Admin can run a refresh check alone |
| Handover to customer success | Callie Brennan, Marcus Bell | Marcus confirmed as day-to-day contact |
4. What I need from your side
- Written access for each source system, supplied before kickoff.
- One named admin who can make decisions on mappings.
- A short list of the questions the client-relationship team asks most often, so we can test the brain against them.
- A contact in IT for permissions and any change to a source system during the build.
5. Risks and how we handle them
- Late credentials: each late source moves the first refresh back by the same amount. I will flag it the same day.
- Source system changes mid-build: please tell us before changing a connected system, as a changed source can stop a connector loading.
- Single admin: we recommend a second person is shown the setup note so the brain does not depend on one person.
6. After go-live
Marcus Bell takes over adoption and check-ins. Tom Ashdown remains the contact for commercial questions. The subscription runs to 29 Aug 2024, and renewal will be raised ahead of that date.
Thanks, Callie