Grisedale Search & Selection - Onboarding Plan
Documentfinal Grisedale Search & Selection · onboarding_plan · final · 2024-05-01
Final version 1 onboarding plan by Callie Brennan, dated Wed 1 May 2024, taking Grisedale from signature to a working brain on Starter. It states a contracted figure of £20k, 15 licensed users and a term from 1 May 2024 to 30 Apr 2025.
What it says
What this says
Current to 11 Oct 26Final version 1 onboarding plan by Callie Brennan, dated Wed 1 May 2024, taking Grisedale from signature to a working brain on Starter. It states a contracted figure of £20k, 15 licensed users and a term from 1 May 2024 to 30 Apr 2025.
What it is: an onboarding plan prepared by Callie Brennan, Implementation Consultant. It sets four weeks of phases from kickoff to handover to Marcus Bell, the customer success manager.
Commits: the contract summary lists "Annual recurring revenue (contracted)" of £20k, "Licensed users" of 15, and a term from 1 May 2024 to 30 Apr 2025. The plan states the first refresh lands in week three.
Unusual: nothing off standard terms. The only constraint is that connectors "must stay within the Starter connector allowance", and extra sources go to a check-in.
Not settled: the plan states no service levels, no connector go-live dates and no renewal mechanism. The term end is 30 Apr 2025, so it says nothing on what followed, and it is not a contract: the executed order form decides price and terms.
As found in this document
Current to 9 Oct 26- Date end30 Apr 2025Source: object_read:doc_082_007
- Date start1 May 2024Source: object_read:doc_082_007
- Price£19,500Source: object_read:doc_082_007
- Licensed users15Source: object_read:doc_082_007
- Term1 May 2024 to 30 Apr 2025Source: object_read:doc_082_007
- Connectorsmust stay within the Starter connector allowancemust stay within the Starter connector allowance · Source: object_read:doc_082_007
- HostingInside Grisedale's own Snowflake accountInside Grisedale's own Snowflake account · Source: object_read:doc_082_007
The document
Body
Grisedale Search & Selection - Onboarding Plan
Status: Final, version 1 Prepared by: Callie Brennan, Implementation Consultant, BB-Demo Plan date: Wednesday 1 May 2024 Account owner: Priya Raman Customer success manager: Marcus Bell
1. Purpose
This plan sets out how we get Grisedale Search & Selection from signature to a working company brain on the Starter tier. Grisedale is a Manchester recruiter for finance, legal and HR roles across the North West. The aim is that consultants and the operations manager can see client accounts, open roles and client complaints in one place, and ask questions of it without reconciling systems by hand.
2. Contract summary
| Item | Detail |
|---|---|
| Tier | Starter |
| Annual recurring revenue (contracted) | £20k |
| Licensed users | 15 |
| Term start | 1 May 2024 |
| Term end | 30 Apr 2025 |
| Hosting | Inside Grisedale's own Snowflake account |
The connectors we connect must stay within the Starter connector allowance. If Grisedale wants more sources than that later, we will raise it at a check-in rather than squeeze them in.
3. What I need from your side
Read the whole document (3,567 characters)
Before we switch on the refresh, what I need from your side is the following, in writing:
- Named admin access to the CRM and to the system that holds client complaints.
- Credentials for each source, sent before the kickoff, not after.
- A Snowflake account contact in IT who can confirm where the brain will run.
- One person from the operations team who owns the field definitions for open roles and client accounts.
I do not start a connector without written access, so these items set the pace of everything below.
4. Phases and owners
| Phase | Activity | Owner | Timing |
|---|---|---|---|
| Kickoff | Walk through this plan, confirm users and sources | Callie Brennan | Week one |
| Access | Collect credentials and confirm written access | Grisedale operations manager | Week one |
| Connect | Set up connectors and map fields; that maps cleanly only once each field is checked | Callie Brennan | Week two |
| First refresh | Run the first nightly refresh and review what landed | Callie Brennan | Week three |
| Training | Short sessions for consultants and the operations manager | Callie Brennan | Week three |
| Hand to success | Meet the customer success manager and agree the first check-in | Marcus Bell | Week four |
5. Milestones
- Access confirmed: all credentials received in writing and tested.
- Fields mapped: client account, open role and complaint fields agreed with the operations manager.
- First refresh landed: data visible in pages, chat and search, with the nightly refresh complete before the working day starts.
- Admin able to run it alone: the Grisedale admin can add a user, check a refresh and raise a request without me.
6. Risks and how we handle them
- Late credentials. The refresh does not start until access is in writing. I will chase a few days before each step.
- Unclear field meanings. If two systems disagree on what a client status means, the operations manager decides and I record it in the setup note.
- Low early usage. Usage will be near zero until the first refresh lands. We review it at the first check-in with the customer success manager.
7. Handover
I will leave a setup note covering every connector, every mapped field and the refresh schedule, so that Grisedale's admin and the customer success manager have the same picture. Priya Raman remains the commercial contact for the account.
Thanks, Callie