Account handoff & success plan
Builds on Topic 4.
What you'll produce
A one-page Account Handoff & Success Plan for Brightline Logistics — the single artifact that converts a thin sales handoff into a CSM's operating plan for the account. It captures why the customer bought, who the champion and economic buyer are, the success criteria and target outcome that will define renewal, a stakeholder map of who you must influence, and a phased onboarding plan with milestones, owners, dates, and a deliberate fast first win that drives time to value. This is the most important document a CSM creates, because everything downstream — onboarding, the QBR, the health score, the renewal — is judged against the outcome you commit to here. Get the success criteria wrong (vague, unmeasurable, or not the buyer's actual goal) and you'll do twelve months of good work that the CFO can still call worthless at renewal. This deliverable proves the Topic 4 skills: reading a handoff, anchoring on the customer's goal, mapping stakeholders, and planning an onboarding that reaches a measurable early win — not just "set up."
Instructions
- Mine the handoff for the "why they bought." Sales sells a promise; your job is to restate it as an outcome you can be measured on. Write one sentence: the business pain Brightline had, and the specific result RouteIQ was sold to deliver. If your "why" is a feature ("they bought route optimization"), rewrite it as a business outcome ("they bought a lower empty-mile rate and real-time dispatcher visibility").
- Name the people and their stakes, individually. Identify the champion (who fought for the budget and what they personally need to be proven right) and the economic buyer (who controls the renewal money and what they need to see). Add the end users whose adoption makes or breaks value. For each, write what they care about and how they'd judge success — these are different people with different fears.
- Convert the promise into 2–4 measurable success criteria. Each must have a baseline (where they are today), a target (where "success" is), and a measurement source (where the number comes from). "Improve efficiency" is not a success criterion. "Cut empty-mile rate from 27% to under 20%, measured in RouteIQ's mileage report" is. If you don't have a baseline number, your first onboarding task is to capture one — write that in. For any adoption criterion, define the denominator explicitly and defensibly. Brightline has 16 licensed seats but only 15 of them are route-planning dispatchers; Maya's seat is for oversight, not daily route work. Counting her would let you hit "12 of 16" while a real dispatcher quietly never logs in — inflating adoption and hiding the exact risk this metric exists to catch. State who counts as an active seat (the 15 dispatchers) and who is licensed-but-excluded (Maya), and keep that denominator identical everywhere downstream — the QBR, the health score, and the renewal all report against this one number, so a denominator that drifts from 15 to 16 between documents is a credibility hole at renewal.
- State the one target outcome the renewal hangs on. Above the individual criteria, write the single headline result the CFO will use to decide renew/cancel. Tie it to money if you can — empty miles are fuel, labor, and lost loads, so a percentage reduction has a dollar figure behind it.
- Build the stakeholder map. For each person: name, role, relationship to the deal (champion / economic buyer / user / blocker / coach), their attitude (supporter / neutral / skeptic), and your engagement plan (how often, in what format). Flag risks explicitly — a skeptical CFO you never meet is the #1 renewal risk, so name it.
- Plan the phased onboarding with a fast first win. Lay out onboarding in 2–3 phases across the 90-day window, each with named milestones, owners (you, the customer, or shared), and dates. Deliberately design one fast first win in the first ~2 weeks — small enough to ship quickly, real enough that a dispatcher or Maya feels value — and write how you'll measure it. This is your time-to-value lever (Topic 3).
- Define what "onboarding done" means — value, not setup. Write the explicit exit criteria: the line that separates "they're configured and logged in" from "they're getting measurable value and using it confidently." This is what you're really driving toward.
- Keep it to one page and make it usable. This is an operating document you'll reread before every Brightline touchpoint, not an essay. Tables and tight bullets beat paragraphs. Use real dates, real numbers, and real names from the scenario.
Worked example
(Account: Brightline Logistics · 12-month, $48k/year RouteIQ contract · CSM assigned Day 0 · 90-day value window · renewal in 12 months)
Account snapshot
| Field | Detail |
|---|---|
| Customer | Brightline Logistics — 120-employee regional freight carrier |
| Product | RouteIQ — SaaS route-optimization & real-time dispatch |
| Contract | $48,000/yr, 12-month term · signed Jun 1, 2026 · renewal Jun 1, 2027 |
| Seats / users | 16 licensed seats = 15 dispatcher seats (the adoption population) + 1 oversight seat for Maya (Head of Operations). Maya is the champion, not a route-planner — her seat is for visibility/reporting and is not counted in the adoption denominator. Adoption is always measured against the 15 dispatchers. |
| Value window | 90 days to prove ROI (by ~Aug 30, 2026) |
| CSM | [You] — assigned at handoff, Day 0 |
Why Brightline bought (the promise, restated as an outcome)
Brightline's dispatchers run the fleet out of spreadsheets, so routes are planned by gut and trucks run too many empty miles (deadhead) — burning fuel and labor on every mile a truck rolls without freight. They bought RouteIQ to cut the empty-mile rate and give dispatchers real-time visibility so they stop reacting blind. The renewal will be decided on one number: did empty miles go down enough to pay for the tool, and can the CFO see it?
Target outcome (the headline the CFO will judge)
Reduce Brightline's empty-mile rate from a baseline of ~27% to under 20% within 90 days, and sustain it — a reduction worth roughly $90–120k/yr in fuel and labor, i.e. ~2x the contract. If the CFO can see that on one chart at the QBR, renewal is easy. If not, $48k looks like a line item to cut.
(Note: 27% baseline is the figure cited in the sales handoff; confirming the true baseline from Brightline's own data is onboarding task #1 — see the plan below. Never carry a sales number into the QBR unverified.)
People & stakes
| Person | Role | Why they bought / what they need | How they judge success |
|---|---|---|---|
| Maya Chen | Head of Operations — champion (licensed oversight seat, not in the adoption denominator) | Fought internally for the budget; her credibility is on the line. Needs the tool to work and her dispatchers to actually use it. She watches the live board and reports, but she doesn't plan routes — so her usage proves nothing about whether the team adopted. | Dispatchers stop complaining; empty miles drop; she looks right for pushing it. |
| The CFO | Economic buyer — skeptic | Controls renewal money. Wasn't sold on it; wants proof of ROI, in dollars, before signing again. | A clear, credible ROI number tied to fuel/labor savings vs. the $48k cost. |
| 15 dispatchers | End users — wary | Live in spreadsheets; tired of new tools dumped on them. Their daily adoption is the value. | The tool makes their shift easier, not harder; visible early on real routes. |
| Lead dispatcher (TBD) | Potential coach / power user | Identify in week 1 — the respected dispatcher whose buy-in pulls the other 14. | Becomes the internal go-to; champions the tool peer-to-peer. |
Success criteria (baseline → target → source)
| # | Success criterion | Baseline (today) | Target (success) | Measured from |
|---|---|---|---|---|
| SC-1 | Empty-mile rate | ~27% (to verify wk 1) | < 20% sustained | RouteIQ mileage report vs. Brightline historicals |
| SC-2 | Dispatcher adoption | 0 of 15 active | ≥ 12 of 15 dispatchers planning routes in RouteIQ weekly (denominator = the 15 dispatcher seats; Maya's oversight seat is excluded) | RouteIQ login/usage data |
| SC-3 | Real-time visibility in use | Spreadsheets, no live view | Dispatchers using the live dispatch board on every shift | Product usage + dispatcher feedback |
| SC-4 | ROI Maya can defend to the CFO | None | A one-page $ savings vs. $48k cost read, agreed with Maya | QBR (Deliverable 3) |
Stakeholder map & engagement plan
| Stakeholder | Relationship | Attitude | My engagement plan | Risk |
|---|---|---|---|---|
| Maya | Champion | Supporter | Weekly 30-min sync through onboarding; co-own the metrics story. | Over-relying on her alone; she burns out defending the tool. |
| CFO | Economic buyer | Skeptic | Get a 15-min intro by week 3; invite to the 90-day QBR; send Maya ROI ammo monthly. | #1 renewal risk — a CFO I never meet decides renewal on a vague feeling. |
| Dispatchers (15) | Users | Wary | Group kickoff + train the lead dispatcher first as coach; collect friction weekly. | Adoption stalls; spreadsheets win; SC-1 never moves. |
| Lead dispatcher | Coach (TBD) | Neutral→ | Identify wk 1, make them the power user, let them sell peers. | None identified = no internal momentum. |
Phased onboarding plan (90-day window)
| Phase | Window | Milestones | Owner | Date |
|---|---|---|---|---|
| Phase 0 — Handoff & baseline | Days 0–7 | Confirm goals with Maya; capture true empty-mile baseline from Brightline's data; account & 16 seats provisioned (15 dispatcher seats + Maya's oversight seat); identify lead dispatcher. | Shared | by Jun 8 |
| Phase 1 — Kickoff & FAST FIRST WIN | Days 7–21 | Kickoff call (goals + plan + expectations); train lead dispatcher; optimize ONE high-deadhead lane in RouteIQ and show the empty-mile saving on that lane to Maya + that dispatcher. | CSM-led | by Jun 21 |
| Phase 2 — Roll out & adopt | Days 21–60 | Train all 15 dispatchers; live dispatch board on every shift; weekly friction check-ins; drive toward SC-2 (≥12/15 weekly active). | Shared | by Jul 30 |
| Phase 3 — Prove value | Days 60–90 | Pull fleet-wide empty-mile trend; build the ROI read with Maya; book the 90-day QBR with Maya + CFO. | CSM-led | by Aug 30 |
Fast first win (Phase 1, by ~Jun 21): pick Brightline's worst single deadhead lane, re-plan it in RouteIQ, and show the dispatcher and Maya the concrete empty-mile drop on that one lane — e.g. "this lane went from 31% empty to 18% on today's run." Small, fast, real, and it makes a wary dispatcher and a champion feel the value weeks before the fleet-wide number lands. That felt win is the seed of adoption.
"Onboarding done" — value, not setup
Onboarding is not complete when all 16 seats are provisioned and everyone has logged in. It's complete when ≥ 12 of the 15 dispatchers are planning routes in RouteIQ every week, the live board is used on every shift, and we have a verified empty-mile trend heading toward <20% that Maya can show the CFO. Note the denominator: the adoption bar is 12 of 15 dispatchers — Maya's oversight seat is excluded, because she manages the operation rather than planning routes, so adding her would mask a missing dispatcher. Setup is "they can log in." Done is "they're getting measurable value and rely on it." We drive to the second.
Rubric
The app's AI scores the learner's submission against these criteria and gives feedback. Levels: Needs work (1) / Solid (2) / Excellent (3). Passing = every criterion at Solid or above.
- "Why they bought" as an outcome, not a feature — 1: restates the feature ("they bought route optimization") or is missing · 2: names the business pain and the promised result · 3: crisp business outcome tied to dollars, framed as the thing you will be measured on at renewal.
- Champion vs. economic buyer distinguished — 1: lumps stakeholders together or misses one · 2: both named with their roles · 3: captures their different fears (champion's credibility vs. CFO's ROI proof) and what each must personally see to call it a win.
- Measurable success criteria with baseline + target + source — 1: vague ("improve efficiency") or no numbers · 2: specific, measurable targets · 3: each criterion has a baseline, a target, and a named measurement source — and flags any baseline that must be captured before it's trusted.
- Adoption denominator stated and consistent — 1: the adoption metric's denominator is ambiguous or drifts (e.g. provisions 16 seats, then bars "12 of 16" in one place and "12 of 15" in another) · 2: picks one denominator and uses it consistently · 3: explicitly distinguishes licensed seats (16) from the adoption population (the 15 dispatchers), justifies excluding Maya's oversight seat (she doesn't plan routes, so counting her would mask a non-adopting dispatcher), and uses the same "of 15" denominator everywhere it appears.
- Target outcome the renewal hangs on — 1: missing or buried in feature talk · 2: a single clear headline outcome · 3: one headline result tied to a dollar value and explicitly framed for the economic buyer's renew/cancel decision.
- Stakeholder map with attitudes, engagement, and named risk — 1: just a list of names · 2: roles + an engagement plan per person · 3: includes attitudes (supporter/skeptic), a per-person engagement cadence, and names the top renewal risk (e.g. the unmet skeptical CFO).
- Phased onboarding with a deliberate fast first win — 1: a generic setup checklist, no dates/owners, or no early win · 2: phased milestones with owners and dates plus an early win · 3: tight phases with named owners/dates and a deliberately small, fast, measurable first win designed to drive time to value and seed adoption.
- "Done = value, not setup" exit criteria — 1: defines done as "set up / logged in" or omits it · 2: states value-based exit criteria · 3: a sharp, measurable line separating "configured" from "getting measurable value and relying on it," tied back to the success criteria.