Brimscombe Energy - Onboarding Plan
Documentfinal Brimscombe Energy · onboarding_plan · final · 2025-01-18
Final version one of the onboarding plan prepared by Callie Brennan on 18 Jan 2025 for an Enterprise implementation starting 10 Jan 2025. It sets five phases, owners and done-when tests. It states no availability or P1 figures; the contracted figure is £115k.
What it says
What this says
Current to 13 Oct 26Final version one of the onboarding plan prepared by Callie Brennan on 18 Jan 2025 for an Enterprise implementation starting 10 Jan 2025. It sets five phases, owners and done-when tests. It states no availability or P1 figures; the contracted figure is £115k.
What it is: a delivery plan from BB-Demo's Implementation Consultant for three customer teams (key-account, collections, complaints). It runs five phases from access and security to handover, each with an owner and a done-when test.
Commits: the plan says "nothing is connected until access is in writing" and that handover needs a setup note and "at least two" admins. It lists 180 licensed users, a contract end of 9 Jan 2026 and the contracted figure of £115k.
Unusual: the executive sponsor is still "To be agreed with Brimscombe Energy during phase one". No phase dates or connector delivery dates are given.
Not settled: price and terms sit in the executed order form, which this plan says it does not change. The plan does not state a renewal trigger, service levels or notice terms, and it was prepared as a plan, so it does not show whether the phases were completed.
As found in this document
Current to 9 Oct 26- Date end9 Jan 2026Source: object_read:doc_154_008
- Date start10 Jan 2025Source: object_read:doc_154_008
- Price£115,000Source: object_read:doc_154_008
- Licensed users180Source: object_read:doc_154_008
- Contract end9 Jan 2026Source: object_read:doc_154_008
- Accessnothing is connected until access is in writingnothing is connected until access is in writing · Source: object_read:doc_154_008
- HandoverI do not hand over without a setup noteI do not hand over without a setup note · Source: object_read:doc_154_008
- Admins before handoverat least twoSource: object_read:doc_154_008
The document
Body
Brimscombe Energy - Onboarding Plan
Status: Final, version one Prepared: 18 Jan 2025 Prepared by: Callie Brennan, Implementation Consultant, BB-Demo Customer: Brimscombe Energy, Gloucester Tier: Enterprise Account owner: Tom Ashdown Customer success manager: Daniel Okafor
Purpose of this plan
Brimscombe Energy supplies business gas and electricity to SME and corporate sites and is licensed by Ofgem. The company bought the Enterprise tier so that the key-account, collections and complaints teams can see each business customer's sites, contracts, calls and bills together in one place.
This plan sets out how we get from the start date of 10 Jan 2025 to a brain that those three teams use day to day, running inside your own Snowflake account. It covers the phases, who owns each step, what I need from your side and how we agree each step is done.
Commercial summary
| Item | Detail |
|---|---|
| Tier | Enterprise |
| Annual recurring revenue (contracted) | £115k |
| Licensed users | 180 |
| Customer since | 10 Jan 2025 |
| Contract end | 9 Jan 2026 |
Read the whole document (5,807 characters)
The executed order form remains the reference for price and terms. This plan does not change either.
Teams in scope
- Key-account team: one view of each business customer, with sites, contracts, recent calls and the latest bills.
- Collections team: billing history and contact history side by side, so a call to a customer starts with the full picture.
- Complaints team: every complaint set against the contract, the calls and the emails that led to it.
Phases
Phase one: access and security
Before we switch on the refresh, nothing is connected until access is in writing. What I need from your side is:
- written confirmation of which source systems are in scope for the first wave
- a named technical contact who can issue connector credentials
- the security review questions from your information security team, so we can answer them early (security review support is part of the Enterprise implementation)
- the Snowflake account details and the agreed role for BB-Demo to build in
Owner: Brimscombe Energy technical contact, with Callie Brennan Done when: credentials are received in writing and the security review has no open questions.
Phase two: connect and map
We connect each source one at a time and map the fields to the brain's model of a customer, a site and a contract. I check each mapping against real records before I call it done, and I will tell you where a field does not map cleanly rather than guess.
- connect the CRM and the billing and accounting data first, since collections depends on them
- connect the call recorder and mailboxes next, for the key-account and complaints views
- connect the helpdesk or complaints log last
- agree a short list of test records, drawn from each team, to check against
Owner: Callie Brennan Done when: each connected source has a signed-off mapping and the test records match.
Phase three: first refresh and validation
The first full refresh runs only when phases one and two are complete. After it lands we review the results together with one person from each team.
- check the record counts against the source systems
- ask a set of real questions from each team and compare the answers with what they know to be true
- log anything that does not match and fix it before the wider launch
Owner: Callie Brennan, with a nominated lead from each team Done when: each team lead confirms their test questions are answered correctly.
Phase four: access, SSO and rollout
Enterprise includes SSO and SCIM, so users are provisioned from your identity provider rather than by hand. We then bring the 180 licensed users on in stages, team by team, starting with the key-account team.
- configure SSO and SCIM with your IT team
- run a training session for each team, using their own data
- name at least two admins on your side who can run the brain without us
Owner: Brimscombe Energy IT and the three team leads, supported by Callie Brennan Done when: all three teams have been trained and have admins in place.
Phase five: handover
I do not hand over without a setup note. It will list every connector, every mapping decision, the refresh schedule and who to contact for what. Daniel Okafor then takes over as the day-to-day contact for adoption and reviews.
Owner: Callie Brennan, then Daniel Okafor Done when: the setup note is accepted by your admins and the handover call has taken place.
Roles
| Role | Person | Responsibility |
|---|---|---|
| Implementation Consultant | Callie Brennan | Delivery of phases one to five, setup note |
| Customer success manager | Daniel Okafor | Adoption after handover, reviews, renewal conversation |
| Account owner | Tom Ashdown | Commercial terms and escalation |
| Executive sponsor | To be agreed with Brimscombe Energy during phase one | Sponsorship and decisions on scope |
Risks and how we manage them
- Access arrives late. Nothing starts without written access, so late credentials move the plan. I will chase in week, not at the end.
- A source system changes during the build. Tell me before it happens and I will re-check that mapping.
- Too few admins. One admin is a single point of failure. We will not hand over until there are at least two.
- Teams disagree on a definition. For example, what counts as an open complaint. We agree one definition per term in phase two and write it into the setup note.
What happens next
- Brimscombe Energy confirms the first-wave source list and the technical contact.
- Callie Brennan sends the access checklist for each source.
- The first working session is held once credentials are in hand.
Thanks, Callie
Unusual terms
Current to 9 Oct 26- Executive sponsor not yet named
- No phase dates given