Fairhallow Travel: documents logo

Fairhallow Travel - Onboarding Plan

Documentfinal

Fairhallow Travel: documents logo Fairhallow Travel: documents · onboarding_plan · final · 2025-01-01

Final 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 says

What this says

Current to 11 Oct 26

Final 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.

AI · claude-sonnet-5-5 · 11 Oct 2026

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

ItemDetail
CustomerFairhallow Travel, Manchester
TierGrowth
Licensed users40
Annual recurring revenue (contracted)£39,600
Term1 Jan 2025 to 31 Dec 2025
HostingInside 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.

StepOwnerOutput
Confirm the sources to be connected under the order formCallie Brennan with your project leadAgreed source list
Provide credentials for the booking system, the helpdesk and the CRMFairhallow Travel ITWritten access
Confirm who will be your administratorsFairhallow TravelNamed admins
Kickoff callCallie BrennanAgreed 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

PersonOrganisationRole in onboarding
Callie BrennanBB-DemoRuns implementation, connectors and handover
Marcus BellBB-DemoCustomer success manager after handover
Tom AshdownBB-DemoAccount owner, commercial questions
Your project lead and administratorsFairhallow TravelAccess, 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

Documentsmade from

Unusual terms

Current to 9 Oct 26
  • Contracted figure £39,600 sits below v1 Growth list
  • Refresh deadline stated without a clock time

BB-Demo is a fictional company; every organisation and person here is invented. B-Brain is the tool. Built by site/build_site.py from the site tree, data as of Fri 9 Oct 2026. Help & Support

Help & Support

Open as a page

Help & Support

B-Brain is one place to read everything the company knows about its customers: the CRM, calls, emails, support tickets, product usage, invoices, documents, news and HR. Every page is built from those systems and the data is current to Fri 9 Oct 2026.

How to use the site

How to ask

Press Ask Brain in the header. Type a question, or pick one of the examples.

The site itself does not call an AI model; answers in Claude come from the same figures you see here.

What the data covers

DataRecords
Organisations150
People at customers573
BB-Demo staff48
Calls1,382
Email threads2,122
Support tickets789
Documents850
Deals217
Invoices187
Events49
News items84

Data as of Fri 9 Oct 2026. Text marked AI was written by the brain from the records listed in its made-from link; an AI output that cannot cite its evidence is refused and the previous text kept. Where two systems disagree (for example a contract and the CRM), the key facts show both values and mark the difference.

BB-Demo is a fictional company: every organisation, person and figure here is invented for this demonstration. B-Brain is the tool that reads its data.

Who to contact

Email support@b-brain.example or talk to your B-Brain account team. Tell us the page address and what looked wrong; a screenshot helps.

HelpAsk B

Ask B

B-Brain · read-only