What it says
What this says
Current to 11 Oct 26Final version 1 onboarding plan prepared by Callie Brennan on 1 Jan 2025 for a Growth tier customer with 40 licensed users. It sets four phases from access to handover and states a contracted figure of £39,600 for the term 1 Jan 2025 to 31 Dec 2025.
What it is: a customer-facing plan for connecting booking data, service tickets and account reviews inside the customer's own Snowflake account. It runs from access and kickoff through connect and map, first refresh and validation, then training and handover to Marcus Bell.
Commits: BB-Demo to a validated first refresh and handover. The plan says "Confirm the nightly refresh is complete before the start of your business day". It does not give a clock time.
Unusual: the plan lists a contracted annual figure of £39,600, which is below the v1 Growth list price of £44,000 in the company brief. The plan does not say why, so a discount cannot be assumed.
Not settled: the plan names no connector count or go-live dates. It is a plan, not an order form, so the executed order form decides price and terms. It also covers only the 2025 term, so it says nothing about renewal.
As found in this document
Current to 9 Oct 26- Date end31 Dec 2025Source: object_read:doc_020_008
- Date start1 Jan 2025Source: object_read:doc_020_008
- Price£39,600Source: object_read:doc_020_008
- Nightly refreshConfirm the nightly refresh is complete before the start of your business day.Confirm the nightly refresh is complete before the start of your business day. · Source: object_read:doc_020_008
- Licensed usersLicensed users are set at 40 for this term.Licensed users are set at 40 for this term. · Source: object_read:doc_020_008
- Term1 Jan 2025 to 31 Dec 2025Source: object_read:doc_020_008
- HostingInside your Snowflake accountSource: object_read:doc_020_008
- Handover success checksEvery connector in the order form live and loading.Every connector in the order form live and loading. · Source: object_read:doc_020_008
The document
Body
Fairhallow Travel - Onboarding Plan
Status: Final, version 1 Prepared by: Callie Brennan, Implementation Consultant, BB-Demo Customer success manager: Marcus Bell Account owner: Tom Ashdown Plan date: 1 Jan 2025
Purpose
This plan sets out how we bring Fairhallow Travel onto the company brain. The aim is simple: your client bookings, service tickets and account reviews should sit in one place, inside your own Snowflake account, so your teams can ask one question instead of reconciling three systems by hand.
Contract summary
| Item | Detail |
|---|---|
| Customer | Fairhallow Travel, Manchester |
| Tier | Growth |
| Licensed users | 40 |
| Annual recurring revenue (contracted) | £39,600 |
| Term | 1 Jan 2025 to 31 Dec 2025 |
| Hosting | Inside your Snowflake account |
Outcomes we are working towards
Read the whole document (3,940 characters)
- A first nightly refresh that lands cleanly and completes before the start of your business day.
- Client bookings, service tickets and account reviews searchable together in pages, chat and search.
- A first set of dashboards built by your own team using the Growth dashboards builder.
- Your administrators able to run the brain without us in the room.
Phases
Phase one: access and kickoff
What I need from your side is written access to each source before we start. I do not begin a connector without it.
| Step | Owner | Output |
|---|---|---|
| Confirm the sources to be connected under the order form | Callie Brennan with your project lead | Agreed source list |
| Provide credentials for the booking system, the helpdesk and the CRM | Fairhallow Travel IT | Written access |
| Confirm who will be your administrators | Fairhallow Travel | Named admins |
| Kickoff call | Callie Brennan | Agreed plan and dates |
Phase two: connect and map
We connect each source one at a time and map fields before switching on any refresh. Each mapping is checked against a sample of your real records, not assumed.
- Booking data mapped to client and account.
- Service tickets mapped to the same client records.
- Account reviews linked so a client's history reads in one view.
- Any field that does not map cleanly is logged and agreed with you before we move on.
Phase three: first refresh and validation
Before we switch on the refresh for everyone, we run it once and review the result with your project lead.
- Check record counts against the source systems.
- Spot-check a handful of client accounts end to end.
- Fix any mapping gaps and re-run.
- Confirm the nightly refresh is complete before the start of your business day.
Phase four: training and handover
- Short sessions for your account managers, service team and managers on asking questions and reading pages.
- A working session with your administrators on users, connectors and refresh checks.
- A written setup note covering every connector, mapping decision and credential owner.
- Handover to Marcus Bell, who will run adoption reviews from there.
Roles
| Person | Organisation | Role in onboarding |
|---|---|---|
| Callie Brennan | BB-Demo | Runs implementation, connectors and handover |
| Marcus Bell | BB-Demo | Customer success manager after handover |
| Tom Ashdown | BB-Demo | Account owner, commercial questions |
| Your project lead and administrators | Fairhallow Travel | Access, decisions and sign-off of the first refresh |
Dependencies and risks
- Credentials arriving late is the most common cause of delay. Please send them before kickoff.
- If a source system changes during onboarding, tell us so we can re-check the mapping.
- Licensed users are set at 40 for this term. We will invite users in groups so adoption is steady.
Success checks at handover
- First refresh landed and validated with your project lead.
- Every connector in the order form live and loading.
- Administrators named and trained.
- Setup note delivered and acknowledged.
Thanks, Callie
Unusual terms
Current to 9 Oct 26- Contracted figure £39,600 sits below v1 Growth list
- Refresh deadline stated without a clock time