Onboarding kickoff & first-win plan
Builds on Topic 4.
What you'll produce
The kickoff meeting and first-win execution layer that turns Deliverable 1's plan into a customer commitment — not a second copy of that plan. Deliverable 1 already produced Brightline's success criteria, stakeholder map, and the 90-day phased plan with its deliberate fast first win. This deliverable does the three things a static plan document cannot do for you:
- A timed 45-minute kickoff agenda that gets the room — Maya, the CFO's proxy, the dispatch lead — to agree out loud to D1's outcome, baseline, and plan, so onboarding starts from a shared commitment instead of your assumptions.
- A day-by-day execution playbook for D1's Phase 1 first-win window only (the ~21 days where most onboardings quietly die) — the run sheet, the data read, and the go/no-go gate that D1 named but did not schedule.
- The honest-expectations script and live-objection responses — the exact words you say when a skeptical buyer or a wary dispatcher pushes back in the room, which a plan on paper never has to survive.
You do not rewrite D1's success criteria, re-map stakeholders, re-author the 90-day phases, or re-invent the early win. You import them by reference and prove you can run the meeting and the first 21 days that make them real. This is the Topic 4 skill a hiring manager can't see from a planning doc: facilitating the kickoff, contracting on expectations, and executing time-to-value under live pushback.
Instructions
Carry forward from Deliverable 1 (do not restate, cite): the bought-for outcome (empty-mile rate 27% → <20%, worth ~$90–120k/yr ≈ 2× the contract), SC-1 (empty-mile rate) and SC-2 (≥12 of 15 dispatchers active — Maya's oversight seat excluded), the stakeholder map, the Phase 1 fast first win (worst deadhead lane re-planned, 31% → 18% on one run, by ~Jun 21), and the "done = value, not setup" exit line. Reference them by their D1 names; spend your effort on the meeting and the execution, not on re-deriving the plan.
- Open the kickoff by getting the room to ratify D1's outcome — not by presenting a new one. Your first agenda segment confirms, in Maya's words, that the outcome you wrote in D1 (empty miles down, real-time visibility) is still the outcome, and surfaces anything sales got wrong. If the room edits the outcome here, that edit flows back into D1 — kickoff is the moment the plan stops being yours and becomes theirs.
- Build the kickoff agenda as a timed, 45-minute meeting with named owners. Cover, in order: re-confirm why they bought (Maya speaks), lock SC-1's baseline with the data owner present, walk D1's 90-day plan at headline level (don't re-teach it — point to it and get a nod), assign the pilot group, schedule the first-win read date, and close on expectations + support + a booked next meeting. End with one concrete action item per side.
- Lock the baseline live — this is the one number D1 left open. D1 cites a 27% baseline "to verify wk 1." Your kickoff is week 1. Put the data owner (Priya) in the room and walk out with either a confirmed baseline or a dated commitment to deliver the history that produces one. A QBR argument three months from now is almost always a baseline you never nailed down at kickoff.
- Write the first-win execution run sheet for D1's Phase 1 window — day by day, not phase by phase. D1 named the first win (one lane, 31%→18%, by ~Jun 21). Your job is to make it happen: lay out Days 0–21 with the specific action, owner, and artifact for each step (configure the lane → train the pilot dispatchers → run RouteIQ-dispatched loads → read the result), ending in a dated go/no-go gate. State the read date, the data source, and what you do if the number doesn't move — diagnosing on 3 dispatchers before scaling to 15 is the whole point of a pilot.
- Script honest expectations as spoken lines, not a policy list. Write 3–5 plain-language statements you will say out loud at kickoff: what RouteIQ will and won't do in 90 days, what's required of Brightline (data, dispatcher time), how support works, and one thing you are deliberately not doing yet so you don't overwhelm them (Topic 4 pitfall). These are quotes, in your voice, ready to deliver.
- Prepare live-objection responses for the two people most likely to push back in the room. A plan can't be heckled; a kickoff can. Write the exact response to (a) the ROI-skeptical CFO/proxy who asks "why should I believe this moves a number?" and (b) a wary dispatcher who says "I already have a system that works." Each response should redirect to the first win — the fast, visible result that answers skepticism with evidence rather than promises.
- Define the kickoff's own success — did the meeting do its job? Separate from D1's onboarding-exit criteria, write 3–4 checkable conditions that mean this kickoff succeeded: the outcome was ratified, the baseline was locked (or dated), the pilot group and read date are committed, and the room left with aligned expectations and a next meeting booked. This is how you grade the meeting, not the 90 days.
- Name the one risk to the kickoff/first-win window specifically, with a mitigation. Not the program-level churn risk (D1 owns that) — the risk to getting the first win on time: e.g. the dispatch lead stalls on picking pilot dispatchers, or the history needed for the baseline slips. Name the most likely first-21-days blocker and the move you'll make in the room to de-risk it.
Worked example
(Account: Brightline Logistics · Product: RouteIQ · CSM: you · Contract: $48k/yr, 12 months · Renewal: 12 months out · Champion: Maya, Head of Operations · Economic buyer: the CFO, ROI-skeptical · End users: 15 dispatchers, currently in spreadsheets. All targets, SCs, the 90-day plan, and the first win are imported from Deliverable 1 — restated here only as pointers.)
What D1 already committed (carried forward, not re-authored): outcome = empty-mile rate 27% → <20% in 90 days (~$90–120k/yr ≈ 2× the contract); SC-1 empty-mile rate, SC-2 ≥12/15 dispatchers active; Phase 1 first win = Brightline's worst deadhead lane re-planned in RouteIQ, 31% → 18% on one run, by ~Jun 21. This deliverable runs the meeting and the 21 days that make those real.
Kickoff agenda — 45 minutes (Day 3 after handoff)
Attendees: you (CSM), Maya (champion), dispatch lead Dev, ops analyst Priya (owns the data → present specifically to lock SC-1's baseline). CFO invited, optional — send him the recap regardless.
| Min | Segment | Owner | Job of this segment |
|---|---|---|---|
| 0–5 | Welcome + my role | You | "I'm your partner for the year, judged on whether Brightline gets the result it bought." |
| 5–12 | Ratify the outcome — confirm D1's "why you bought": empty miles down, dispatcher visibility up | Maya | Maya says it in her words; any correction here updates D1. The plan becomes theirs. |
| 12–18 | Lock SC-1's baseline — confirm the 27% figure against Brightline's own data, with Priya | You + Priya | Close the one number D1 left open ("to verify wk 1"). Walk out with a baseline or a dated commitment to one. |
| 18–24 | Walk the 90-day plan at headline level — point to D1's phases, get a nod | You | Don't re-teach the plan — show the path (pilot → all 15), confirm they're bought in. |
| 24–32 | Commit the first-win window — pilot group + read date for D1's Phase 1 win | Shared | Dev names the 3 most open-minded dispatchers; you book the Day-21 read. |
| 32–40 | Expectations + objections — say the honest-expectations lines; handle pushback live | You | Deliver the scripted scope/support lines; answer the CFO-proxy and dispatcher objections (below). |
| 40–45 | Close — action items, support path, next meeting | You | One action per side; book the Day-30 checkpoint. |
Action items out of kickoff: You — configure RouteIQ for Brightline's worst deadhead lane (the D1 first-win lane) by Day 7. Brightline (Priya) — deliver 90 days of historical dispatch data by Day 5 so the empty-mile baseline is real, not the sales estimate. Next meeting booked: Day 30 checkpoint.
First-win execution run sheet — D1's Phase 1, day by day (Days 0–21)
D1 named this win and its target (31% → 18%, by ~Jun 21). Below is how it actually gets done — the run sheet, owners, and the go/no-go gate D1 didn't schedule.
| Day | Action | Owner | Artifact / proof |
|---|---|---|---|
| 0–5 | Priya delivers 90-day history; confirm the lane baseline = 31% empty (worst lane, picked because it's easy to move and visible to Maya) | You + Priya | Confirmed baseline in writing |
| 5–7 | Configure that single lane in RouteIQ; Dev names the 3 pilot dispatchers | You + Dev | Lane live; 3 pilots named |
| 7–10 | 90-min hands-on training for the 3 pilots — framed "fewer clicks than your spreadsheet," not "new system" | You + Dev | Pilots dispatch the lane themselves |
| 10–20 | Run RouteIQ-dispatched loads on the lane; collect the mileage data | Pilots | RouteIQ mileage report accruing |
| 21 | Read the result + GO/NO-GO gate | You + Priya | Empty-mile % on the lane vs. 31% baseline |
- Target (from D1): the lane drops toward 18% empty on RouteIQ-dispatched runs — a result the pilot dispatchers can see for themselves, weeks before any fleet-wide number.
- Data source: RouteIQ's mileage report, cross-checked against Priya's historical dispatch log for the same lane.
- GO (number moved): lead the Day-30 checkpoint with it; pilots become peer coaches for the Phase 2 rollout (peer proof beats vendor proof).
- NO-GO (number didn't move): do not scale. Diagnose with the 3 pilots — bad data, wrong lane, training gap, tool gap — and fix before touching the other 12. Finding this out on 3 dispatchers on Day 21 instead of on 15 at renewal is exactly why D1 made this a pilot.
Honest expectations — the lines I'll actually say at kickoff
- "In 90 days you'll have a measurable empty-mile reduction and your team dispatching in real time — that's the result you bought, per our plan. Not every feature. The result."
- "This needs your data and your dispatchers' time: the ~90 days of history Priya is sending, and 90 minutes of training per dispatcher. RouteIQ can't optimize what it can't see."
- "We're starting with 3 dispatchers and one lane on purpose. Onboarding all 15 at once is how tools get rejected. We earn the rollout with a win you can see in three weeks."
- "We are not touching billing integration or the driver mobile app in these 90 days — important, but later. First we prove the core result."
- "Support: I'm your direct line for anything strategic; in-app help and our support team handle day-to-day questions, usually within a few hours."
Live-objection responses (the part a plan can't rehearse for you)
CFO/proxy — "Why should I believe this actually moves a number?" "Fair — you've been sold software before. So I'm not asking you to believe a projection. In three weeks we'll re-run your single worst lane through RouteIQ and show you the empty-mile change on that lane against your own historical data. If it doesn't move, we find out on one lane and three dispatchers, not on your whole fleet at renewal. I'd rather earn the renewal on a number than argue for it."
Wary dispatcher — "I already have a system that works." "Then I don't want to slow you down. The deal is this: 90 minutes, on one lane you already run, and you judge it on whether it saves you clicks — not on what it does for management. If it's slower than your spreadsheet, that's my problem to fix, not yours to live with. The three of you go first precisely so the other twelve don't get something half-baked dropped on them."
Did the kickoff do its job? (grade the meeting, not the 90 days)
This kickoff succeeded when all four are true — distinct from D1's onboarding-exit criteria, which grade the program:
- Outcome ratified: Maya re-stated the bought-for outcome in her own words and corrected anything sales got wrong (any edit fed back into D1).
- Baseline closed: the 27% empty-mile baseline is either confirmed against Brightline's data or has a dated commitment (history by Day 5) to make it real.
- First-win window committed: the 3 pilot dispatchers are named, the worst lane is the target, and the Day-21 read is on calendars.
- Aligned + booked: the room heard the honest-expectations lines, the two live objections got real answers, and the Day-30 checkpoint is booked with one action item per side.
Contrast — a kickoff that failed its job: everyone nodded, no baseline got locked, "we'll figure out the pilot group later," and no read date. That's a friendly meeting that changed nothing — and it's how a $48k account drifts past its value window.
Top risk to the first-win window + mitigation
Risk: the first win slips its date — most likely because Dev stalls on naming pilot dispatchers, or Priya's 90-day history is late, so there's no clean baseline to read against on Day 21. A late first win means no proof before doubt sets in. Mitigation: get both committed in the room: Dev names the 3 pilots before the kickoff ends (or commits to a name-by date with me on the hook to chase it), and Priya's data delivery becomes a written Day-5 action item, not a vague "she'll send it." I protect the Day-21 read date the way I'd protect the renewal — because it's the cheapest proof I'll ever get that this account will renew.
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.
- Builds on D1 instead of restating it — 1: re-authors D1's content — re-derives the outcome, re-maps stakeholders, or rewrites the 90-day plan/first win as if D1 didn't exist · 2: references D1's outcome, SCs, and plan and adds the kickoff/execution layer on top · 3: cleanly imports D1 by name (outcome, SC-1/SC-2, Phase 1 first win) and spends its effort entirely on running the meeting and the first 21 days — no duplicated planning, and any kickoff edits explicitly flow back into D1.
- Timed kickoff agenda that ratifies the plan and locks the baseline — 1: a vague topic list, no owners/timing, or just re-presents the plan · 2: a structured, timed 45-min agenda with owners that confirms why-they-bought and walks the plan · 3: timed segments with named owners where the room ratifies the outcome in the customer's words, SC-1's baseline is locked live with the data owner present, the pilot group and read date are committed, and action items + next meeting are booked.
- Day-by-day first-win run sheet with a go/no-go gate — 1: just repeats D1's phases, or a generic "early win" with no schedule · 2: a Days 0–21 sequence for D1's Phase 1 win with actions and owners · 3: a dated run sheet (configure → train → run → read) with owner and artifact per step, a Day-21 data read against the lane baseline, and an explicit NO-GO branch (diagnose on 3 before scaling to 15).
- Honest-expectations script + live-objection responses — 1: over-promises, or a dry policy list with no spoken lines · 2: 3–5 plain-language expectation statements including what's required of Brightline · 3: expectations written as spoken lines (scope, what's required, support, one deliberate "not yet") plus rehearsed responses to a skeptical-buyer and a wary-dispatcher objection that redirect to the first win as evidence.
- Grades the meeting, with a window-specific risk — 1: success = "we had a kickoff," or borrows D1's onboarding-exit criteria wholesale · 2: states 3–4 kickoff-success conditions and a risk · 3: 3–4 checkable conditions that grade the meeting (outcome ratified, baseline closed, window committed, expectations aligned), explicitly distinct from D1's program-exit criteria, plus a named first-21-days risk with an in-the-room mitigation.