Calderbrook Housing Group - Onboarding Plan
Documentfinal Calderbrook Housing Group: documents · onboarding_plan · final · 2024-09-07
Final onboarding plan issued 7 Sep 2024 by Callie Brennan for a Growth subscription running 2 Sep 2024 to 1 Sep 2025. States an annual recurring value of £44,000, 40 licensed users, eight connectors and a nightly refresh complete by 07:00.
What it says
What this says
Current to 11 Oct 26Final onboarding plan issued 7 Sep 2024 by Callie Brennan for a Growth subscription running 2 Sep 2024 to 1 Sep 2025. States an annual recurring value of £44,000, 40 licensed users, eight connectors and a nightly refresh complete by 07:00.
What it is: a four-phase plan from signature to a working brain, written by the implementation consultant. Phases run kickoff and access, connect and map, first refresh, then first questions and handover to Natalie Eze in Customer Success.
Commits: "The subscription began on 2 Sep 2024 and runs to 1 Sep 2025." The refresh "completes by 07:00 customer local time on business days", and scope is up to eight connectors and 40 licensed users. The plan states no availability percentage, P1 response time or connector go-live dates.
Unusual: the plan is a working document, not a contract. It refers to the order form for the connector limit but does not reproduce its terms.
Not settled: it does not say whether the onboarding finished or the brain went live, and it is two years old. The renewal date it names has passed, so it does not show the current term or price.
As found in this document
Current to 9 Oct 26- Date end1 Sep 2025Source: object_read:doc_007_008
- Date start2 Sep 2024Source: object_read:doc_007_008
- Price£44,000Source: object_read:doc_007_008
- Subscription termThe subscription began on 2 Sep 2024 and runs to 1 Sep 2025.The subscription began on 2 Sep 2024 and runs to 1 Sep 2025. · Source: object_read:doc_007_008
- Licensed users40 licensed usersSource: object_read:doc_007_008
- Connectorsup to the eight connectors in the order formup to the eight connectors in the order form · Source: object_read:doc_007_008
- Nightly refreshIt completes by 07:00 customer local time on business days.It completes by 07:00 customer local time on business days. · Source: object_read:doc_007_008
- Contracted annual recurring value£44,000Source: object_read:doc_007_008
The document
Body
Calderbrook Housing Group - Onboarding Plan
Status: Final Prepared by: Callie Brennan, Implementation Consultant, BB-Demo Issued: 7 Sep 2024
Purpose
This plan sets out how Calderbrook Housing Group goes from signature to a working company brain on the Growth tier. The aim is simple: your business-intelligence team can ask one question and get an answer that joins tenant calls, repairs tickets, complaints and rent arrears, in a form the board can use.
The subscription began on 2 Sep 2024 and runs to 1 Sep 2025. The contracted annual recurring value is £44,000, with 40 licensed users.
Who is involved
Read the whole document (4,876 characters)
| Role | Person | Responsibility |
|---|---|---|
| Implementation Consultant | Callie Brennan, BB-Demo | Runs the plan, connects sources, maps fields, writes the setup note |
| Account Executive | Tom Ashdown, BB-Demo | Commercial questions and scope changes |
| Customer Success Manager | Natalie Eze, BB-Demo | Adoption after go-live, quarterly reviews, renewal conversation |
| Business-intelligence lead | Calderbrook Housing Group | Day-to-day contact, priorities, sign-off on mappings |
| Systems administrator | Calderbrook Housing Group | Credentials and access for each source |
| Snowflake administrator | Calderbrook Housing Group | Access to the Snowflake account the brain runs inside |
What I need from your side is
- Written access for each source system, in place before we start that connector.
- A named Snowflake administrator who can grant the brain's roles.
- A business-intelligence lead who can answer mapping questions within a couple of days.
- A short list of the first questions the board and executive team want answered.
I will not start a connector without written access. That keeps the plan honest and your data safe.
Phases
Phase one: kickoff and access
- Walk through this plan with the business-intelligence lead.
- Confirm the list of sources, up to the eight connectors in the order form.
- Collect credentials and written access for each source.
- Confirm the Snowflake setup and the roles the brain needs.
Exit check: every source on the list has written access, and the Snowflake roles are agreed.
Phase two: connect and map
- Connect the sources in priority order, starting with tenant calls and repairs tickets.
- Map fields for each source to the brain's common model, and check each mapping against real records before moving on.
- Agree with the business-intelligence lead how complaints and rent arrears should join to a tenant and a property.
Exit check: each connector has loaded records, and the mappings are signed off by your lead.
Phase three: first refresh
- Before we switch on the refresh, run a dry load and review the counts together.
- Switch on the nightly refresh. It completes by 07:00 customer local time on business days.
- Review the first three mornings of refresh results and fix anything that did not land cleanly.
Exit check: the nightly refresh completes on its own, with no manual intervention, for a run of consecutive business days.
Phase four: first questions and handover
- Work through the starter questions from the board list and tune the answers.
- Train the business-intelligence team and the wider user group, up to the 40 licensed users.
- Show your administrator how to add a user, check a connector and read the refresh log, so the brain can be run without us.
- Hand over a written setup note covering every connector, mapping and credential owner.
Exit check: your administrator has run each of those tasks unaided, and the setup note is delivered.
Handover to Customer Success
Once phase four is complete, Natalie Eze takes over the relationship. She will set the review rhythm for the Growth tier, track which teams are asking questions and which are not, and keep the renewal in view well ahead of 1 Sep 2025.
Risks and how we handle them
| Risk | What we do |
|---|---|
| Source credentials arrive late | Start with the sources that are ready and keep the others in the plan |
| A source changes shape during the build | Pause that connector, re-check the mapping, and tell your lead the same day |
| Only one person on your side knows the sources | Name a second contact at kickoff and record them in the setup note |
| Questions are asked by only a few people | Run a second training session and share example questions by team |
Out of scope
Anything beyond the eight connectors in the order form, additional users, or new teams is a separate conversation with Tom Ashdown, agreed in writing before work starts.
How we will keep in touch
I will send a short written update at the end of each phase, covering what is done, what is next and anything I need from you. If something is blocked, you will hear about it that day rather than at the end of the week.
Thanks, Callie
Unusual terms
Current to 9 Oct 26- Connector not started without written access
- Work beyond scope agreed in writing first