Fenmoor Specialty Underwriting - Onboarding Plan
Documentfinal Fenmoor Specialty Underwriting: documents · onboarding_plan · final · 2024-07-07
Onboarding plan prepared by Callie Brennan on 7 Jul 2024 for Fenmoor Specialty Underwriting's Growth subscription. It sets out five phases over eight weeks, owners per step and two open items: written access and named administrators.
What it says
What this says
Current to 10 Oct 26Onboarding plan prepared by Callie Brennan on 7 Jul 2024 for Fenmoor Specialty Underwriting's Growth subscription. It sets out five phases over eight weeks, owners per step and two open items: written access and named administrators.
What it is: a customer-facing onboarding plan, stored as final, covering five phases from access through handover. It states a subscription start of 1 Jul 2024 and an initial term ending 30 Jun 2025.
Commits: B-Brain to a fixed-fee implementation of "eight weeks, up to eight connectors", a progress note at the end of each phase and a handover to the customer success manager in week eight. The customer is asked for written access and a primary and back-up administrator.
Unusual: Callie states "I will not begin a connector without it", so the timeline depends on written access from the customer.
Not settled: the plan is not an order form and states no price. It lists written access and administrator names as still to be confirmed, and does not show whether they were later provided.
As found in this document
Current to 9 Oct 26- Date end
- 30 Jun 2025
- Date start
- 1 Jul 2024
- Implementation
- Fixed fee, eight weeks, up to eight connectors
- Progress reporting
- A short written progress note from me at the end of each phase.
- Connector start
- I will not begin a connector without it.
The document
Body
Fenmoor Specialty Underwriting - Onboarding Plan
Status: Final Prepared by: Callie Brennan, Implementation Consultant, B-Brain Prepared on: 7 Jul 2024
Purpose
This plan sets out how we get Fenmoor Specialty Underwriting from a signed order form to a brain that your underwriting operations team uses every day. It covers the phases, who owns each step, and what I need from your side before we switch on the refresh.
Starting point
| Item | Detail |
|---|---|
| Customer | Fenmoor Specialty Underwriting, London |
| Tier | Growth |
| Subscription start | 1 Jul 2024 |
| Initial term ends | 30 Jun 2025 |
| Implementation | Fixed fee, eight weeks, up to eight connectors |
| B-Brain account owner | Priya Raman |
| B-Brain customer success manager | Daniel Okafor |
| B-Brain implementation lead | Callie Brennan |
The brain is built and run inside your own Snowflake account, so your IT colleagues are involved from the first phase.
What success looks like
Read the whole document (5,459 characters)
Your underwriting operations team can answer capacity providers' oversight questions from one view, without reconciling submissions, bordereaux queries, claims tickets and CRM activity by hand. By the end of the eight weeks:
- every connector promised in the order form is live and refreshing overnight;
- the licensed users on the Growth tier have been invited, starting with underwriting operations;
- at least one of your colleagues can run the brain's administration without us;
- you have a setup note that records every source, mapping and credential owner.
Phases
Phase one: access and preparation (first week)
| Step | Owner | Done when |
|---|---|---|
| Confirm your Snowflake account details and the role B-Brain will use | Your IT contact | Written confirmation received |
| Name a primary and a back-up administrator | Your operations lead | Both named in writing |
| Provide written access for each source system | Your IT contact | Access confirmed per connector |
| Agree the list of sources and their order of priority | Callie Brennan with your operations lead | Priority list signed off |
What I need from your side is written access before any connector is started. I will not begin a connector without it.
Phase two: connect and map (weeks two to five)
| Step | Owner | Done when |
|---|---|---|
| Connect the CRM and map accounts, contacts and activity | Callie Brennan | Mapping reviewed with your operations lead |
| Connect the helpdesk and map claims tickets | Callie Brennan | Ticket categories agreed |
| Connect submissions and bordereaux sources | Callie Brennan with your IT contact | Sample records checked against source |
| Connect remaining mailboxes, calls and shared documents as agreed | Callie Brennan | Each connector loading records |
Every mapping is checked against sample records before it is accepted. Where a field does not map cleanly I will raise it with your team rather than guess.
Phase three: first refresh and checks (weeks five and six)
| Step | Owner | Done when |
|---|---|---|
| Run the first full refresh | Callie Brennan | Refresh completes without errors |
| Check record counts against each source | Callie Brennan and your administrator | Differences explained |
| Test the first set of oversight questions | Your underwriting operations team | Answers judged usable |
| Fix anything the checks turn up | Callie Brennan | Issues closed |
Phase four: users and training (weeks six and seven)
| Step | Owner | Done when |
|---|---|---|
| Invite users up to the licensed number, starting with underwriting operations | Your administrator | Invitations accepted |
| Walk through pages, chat and search with the first group | Callie Brennan | Session held |
| Build the first dashboards with your team | Callie Brennan and your operations lead | Dashboards in use |
| Show your administrators how to add a user and check a connector | Callie Brennan | Administrators confident |
Phase five: handover (week eight)
| Step | Owner | Done when |
|---|---|---|
| Deliver the setup note covering sources, mappings and credential owners | Callie Brennan | Note accepted by your administrator |
| Hand over to the customer success manager | Callie Brennan and Daniel Okafor | Handover meeting held |
| Agree the date of the first quarterly business review | Daniel Okafor | Date in diaries |
Risks and how we handle them
- Credentials arrive late. Connectors cannot start without written access, so the plan moves with the access. I will flag any slip to Priya and Daniel straight away.
- A source system changes during the build. Tell us before you change a system we are connected to, so we can adjust the mapping rather than find a broken connector later.
- Only one administrator is trained. The plan asks for a primary and a back-up so that the brain does not depend on one person.
- Few people use it at the start. Active use will start small. We widen the invitation list once the first answers have been checked.
Communication
- A short written progress note from me at the end of each phase.
- A call with your operations lead at the start and end of each phase.
- Anything blocking progress goes to Priya Raman and Daniel Okafor the same day.
Open items at the date of this plan
- Written access for the first connectors is still to be confirmed.
- The names of your primary and back-up administrators are still to be confirmed.
Thanks, Callie
Unusual terms
Current to 9 Oct 26- no connector starts without written access