Copperwick Logistics - Onboarding Plan
Documentfinal Copperwick Logistics: documents · onboarding_plan · final · 2026-06-06
Final version 1 onboarding plan, prepared 6 Jun 2026 by Laura Penhaligon, for an eight-week Growth implementation in the customer's Snowflake account. Contract runs 1 Jun 2026 to 31 May 2027 with 40 licensed users. It states no availability, P1 response or service credit terms.
What it says
What this says
Current to 11 Oct 26Final version 1 onboarding plan, prepared 6 Jun 2026 by Laura Penhaligon, for an eight-week Growth implementation in the customer's Snowflake account. Contract runs 1 Jun 2026 to 31 May 2027 with 40 licensed users. It states no availability, P1 response or service credit terms.
What it is: a delivery plan, not a contract. It sets five phases over eight weeks, from kick-off and access through source connection, shipper view, dashboards and training, to handover.
Commits: it restates the contract summary: "Annual recurring revenue (contracted)" of £50,000, 40 licensed users, start 1 Jun 2026, end 31 May 2027. It asks the customer for "A named project sponsor and at least two admins".
Unusual: the plan labels £50,000 as contracted annual recurring revenue. It is a figure quoted from a plan, so check it against the executed order form. No connector delivery dates are stated.
Not settled: it gives no service levels, payment terms or renewal mechanics. Milestones carry no calendar dates beyond the contract start, and the evidence does not show who signed the order form.
As found in this document
Current to 9 Oct 26- Date end31 May 2027Source: object_read:doc_030_008
- Date start1 Jun 2026Source: object_read:doc_030_008
- Price£50,000Source: object_read:doc_030_008
- Licensed users40Source: object_read:doc_030_008
- Implementation lengtheight weeksSource: object_read:doc_030_008
- Contract start1 Jun 2026Source: object_read:doc_030_008
- Contract end31 May 2027Source: object_read:doc_030_008
- Customer adminsA named project sponsor and at least two adminsA named project sponsor and at least two admins · Source: object_read:doc_030_008
The document
Body
Copperwick Logistics - Onboarding Plan
Status: Final Version: 1 Prepared: Saturday 6 June 2026 Prepared by: Laura Penhaligon, Implementation Consultant, BB-Demo
1. Purpose
Copperwick Logistics is a truckload and intermodal freight brokerage serving Midwest shippers. It has bought the company brain to get one view of each shipper across Salesforce, its transport management system and support. This plan sets out how we get from contract start to a brain the commercial and operations teams use every day.
2. Contract summary
| Tier | Growth |
| Annual recurring revenue (contracted) | £50,000 |
| Licensed users | 40 |
| Contract start | 1 Jun 2026 |
| Contract end | 31 May 2027 |
| Account owner | Jordan Pike |
| Customer success manager | Hollie Grieve |
| Implementation lead | Laura Penhaligon |
The implementation is the Growth package: eight weeks, delivered inside the customer's Snowflake account.
3. Phases
Read the whole document (3,679 characters)
| Phase | Timing | Focus | BB-Demo owner | Copperwick owner |
|---|---|---|---|---|
| 1. Kick-off and access | Week one | Agree goals, confirm Snowflake access, name the project sponsor and admins | Laura Penhaligon | Operations lead |
| 2. Connect sources | Weeks two to four | Connect Salesforce, the transport management system and the support system; confirm nightly refresh | Laura Penhaligon | IT contact |
| 3. Shipper view | Weeks five and six | Build the single view of each shipper; check records against what account managers know | Laura Penhaligon | Sales operations lead |
| 4. Dashboards and training | Weeks seven and eight | Build first dashboards with the customer; train users and admins | Laura Penhaligon | Operations lead |
| 5. Handover | End of week eight | Hand over to customer success; agree the first review | Hollie Grieve | Project sponsor |
4. Milestones
- Kick-off held: contract started on 1 Jun 2026, so kick-off follows in the first week.
- First source loading: Salesforce records visible in the brain.
- All agreed sources live: the transport management system and support data indexed and refreshing nightly.
- First shipper questions answered: account managers ask the brain about their own shippers.
- Handover complete: users trained, admins named, dashboards in place.
5. What we need from Copperwick
- A named project sponsor and at least two admins, so the brain does not depend on one person.
- Read access to Salesforce and the other agreed sources.
- Time from a colleague in IT to confirm how each system is set up.
- A short list of the shippers and questions that matter most, so we test against real work.
6. How we will measure success
- Records indexed rising week on week as sources come online.
- The number of people asking questions, across more than one team.
- Admins named and trained.
- Dashboards built by the customer's own team.
The Growth tier includes the dashboards builder and quarterly business reviews, so Hollie Grieve will set the first review once handover is complete.
7. Risks and how we handle them
| Risk | Mitigation |
|---|---|
| A source system changes during the build | Tell Laura Penhaligon before any change so connectors can be re-checked |
| Only one person asks questions | Train users across sales, operations and support early |
| Access delayed | Agree access owners at kick-off and review progress weekly |
8. Communication
- A short weekly check-in between Laura Penhaligon and the Copperwick sponsor.
- Any blocker is raised straight away, not held until the check-in.
- Jordan Pike stays in touch on commercial matters throughout.