Onboarding Cliff Rescue Playbook 2026
Your best customers show you what the first 90 days after go-live look like. This play checks every new account against them at the same stage each week, confirms the slip is real, and puts the move on the account in your CRM: an unblock call on the missed step, a note for the champion, a self-serve nudge – or no move, with the reason noted.
Onboarding has an end date on the project plan. Whether the account actually builds a habit shows up a few weeks later.
Your best customers show you what that looks like – how many seats were active by day 30, which steps they'd taken by day 60, where weekly use settled by day 90. A new account that's behind that pattern for its stage has a gap you can still close while it's small – a skipped step, or a team that never got invited.
This play checks every new account against that benchmark weekly, from day 30 to day 90. Each check ends with a move your team decides on, or a note on why there isn't one. Measure it on the share of new accounts at peer level by day 90, weeks from go-live to peer level, and first-renewal rate.
How it works11 steps
01SignalCompare every new account with peers at the same stage
An account enters the check once your CRM marks onboarding complete and it's past day 30 from go-live; it leaves at day 90. The first 30 days belong to the handoff play. Build the benchmark once, refresh it quarterly:
- Comparison customers: same segment (plan tier, size band), went live in the last two years, renewed their first term. Aim for 20; with fewer, label it low confidence.
- Checkpoints: day 30, 60 and 90 after go-live. Between checkpoints, compare with the last one passed (default).
- At each checkpoint, the median of: weekly usage (the one action that means real work – the report runs, the invoice sends), the share of seats active in three of the last four weeks, and the milestones hit by then. Your CS lead approves it.
Not the account's own onboarding weeks: setup work and kickoff calls inflate those, so an account can look like it's sliding when it isn't.
Say an account is at day 60 with 6 of 20 seats active (30%) and no data import; peers at day 60 have 70% of seats active and imported by week three. (The numbers are illustrative.)
Run it as a weekly saved query in PostHog, Amplitude or Mixpanel, or a spreadsheet. Under about a hundred accounts, do it by hand.
02ScoreCheck the records before calling it a slip
A slip, by default: two weeks in a row below 70% of peers' weekly usage or share of seats active, or a milestone peers had hit by now still missing. Then check:
- Phased rollout? If the onboarding notes bring seats in by team, judge each wave on its own dates.
- Pause or holiday: a project on hold, a budget freeze, a holiday – anything with an end date in the CRM notes.
- Champion still active? If the person who led onboarding has gone quiet or left, use the champion-departure play.
03DecisionDecide whether there's a move worth making now
- On track: no slip by the rule above.
- Leave alone: the records explain the slip – a wave not due yet, a pause with an end date, a departed champion, or patchy tracking.
- Yes: a slip the records don't explain.
04ActionHand on-track accounts to the second-value play
Set Recommended move to On track and let the second-value play pick up the next use case.
05ActionLeave it alone, and write down why
Set Recommended move to No move, write the reason in one line, and set Review date to when it could change – the end of the pause, the next rollout wave. More in Leave It Alone.
06DecisionPick the move the evidence supports
- Self-serve: ARR under $10,000 or no named CSM (default). The nudge, on the missed step or, if the steps are done, on inviting the team. It runs on its own – a lane your team chose to automate.
- Missed step: a milestone peers had hit by now is still missing. Unblock call.
- Few users: the steps are done, but seats active trail peers. Champion note.
If both a step and seats are behind, the missed step comes first: new users won't stay if setup isn't finished.
07ActionDraft an unblock call on the missed step
A task for the CSM with the evidence and the email below. Name the step: "your team hasn't imported data yet" beats "how's it going?".
08ActionDraft a note that helps the champion invite their team
The person who ran onboarding is your best route to the other seats: give them something to forward.
09ActionSend a self-serve nudge on the step they skipped
One Customer.io email, linking straight to the step – or to the invite page if the steps are done. Suppress it as soon as the step shows up in their usage, and log the send on the HubSpot record.
10Human stepThe CSM decides and runs the move
The CSM runs it as drafted, changes it, or passes, within a week of the flag (default). Before acting, record the success measure and the review date. After a quarter, the Missed milestone field shows which part of onboarding marks accounts complete too early.
11OutcomeReview what changed, then sharpen the benchmark
On the review date, record three answers in Review result: is usage at peer level for its stage, did the missed step happen, and what else played a part? Sending the nudge is activity; the step done and usage at peer level is progress; the first renewal is the result. If nothing moved, change the move, stop it, or give it time. Each quarter, update the benchmark – and if one skipped step keeps showing up, make it part of onboarding.
Setup and templates
Data sources: usage and milestone events from your analytics tool or event table; seats and plan from billing or the CRM; go-live date, onboarding notes and champion from the CRM. Account-level numbers need your analytics tool's account add-on (group analytics in PostHog, Accounts in Amplitude, Group Analytics in Mixpanel) and a group call in your app. Save the query, then subscribe to it (in Amplitude, add it to a dashboard and subscribe to that) so the result lands in your inbox or Slack on the schedule you set. By hand: one row per new account, with its go-live date, share of seats active, milestones done and weekly usage, beside the peer median for its checkpoint.
Company properties in HubSpot (Starter or above; free HubSpot allows 10 custom properties in total), or your CRM's account object:
| Property | Type | Filled by |
|---|---|---|
| Go-live date | Date picker | Onboarding owner |
| Checkpoint | Dropdown select: Day 30 · Day 60 · Day 90 | Weekly check |
| Usage vs peers | Number (%) | Weekly check |
| Seats active vs peers | Single-line text, e.g. 30% vs 70% | Weekly check |
| Missed milestone | Single-line text | Weekly check |
| Recommended move | Dropdown select: Unblock call · Champion note · Self-serve nudge · On track · No move | Weekly check |
| Move reason | Single-line text | Weekly check |
| Success measure | Single-line text | Account owner |
| Review date | Date picker | Weekly check, then account owner |
| Review result | Dropdown select: At peer level · Step done, usage not yet · No change · Stopped | Account owner |
The automation here uses HubSpot workflows (any Professional hub). On Free or Starter, run the same saved view and create the tasks by hand. The weekly list is a saved view: Go-live date is in the last 90 days, Recommended move is known and Review date is this week or overdue. In HubSpot that's two filter groups: Review date is This week, or Review date is before Today. Unblock calls and champion notes create a task for the CSM, "New account: [move]", with the draft in the body. HubSpot's Slack app sends the owner task notifications; custom messages need a workflow (Professional or Enterprise). The record stays where the work lives.
Send the step's usage event to Customer.io and set it as the automation's exit condition. If you use message limits, turn off auto-retry for this automation. Customer.io writes each send to HubSpot with a webhook step that calls HubSpot's API. If the From address belongs to a HubSpot user, a BCC to your HubSpot logging address also works. Apply these checks to marketing emails sent by hand or automatically: permission to send, accurate sender details, required address information, an easy unsubscribe and shared suppression checks. Keep required service notices separate from marketing. Only include a "teams like yours usually" line if your benchmark supports it; otherwise, describe what you saw on their account.
Unblock call (Missed step):
Hi [name] – I noticed [milestone] hasn't happened yet. Teams like yours usually do it by week [n], and when it stalls it's often [common blocker]. Would 20 minutes on [day] help? We'll do it together.
Champion note (Few users):
Hi [name] – [n] people on your team are using [product] each week so far. Would a short invite note and a two-minute video help you bring in [team or role]? Happy to draft both.
Self-serve nudge:
Subject: The step most teams take by week [n]
Hi [name] – teams like yours usually [milestone, or: invite their team] in their first [n] weeks. It's what makes [result] work. It takes about [time]: [link]. Reply if something's in the way.
No move: "No move – [reason]. Recheck [date]."
How Accoil fits
Accoil is a customer-success consultancy with our own tooling, and this is a play we run with you, not for you. We build the benchmark with your team, and you approve it. Every week we check every new account in the agreed segment, and the recommended move and its evidence land on the account record in your CRM – we recommend HubSpot – at a pace your team can actually run. Your team makes every call, including which moves run on their own. Nobody from Accoil contacts your customers. After the agreed window we review what changed together, and you keep the playbook, the benchmark and the analysis.
Running it yourself? Swap HubSpot for Salesforce or Pipedrive, and Customer.io for Ortto or Userlist. The play stays the same. On Salesforce, the field writes need API access (Enterprise and up, or an add-on on Professional). On Pipedrive, automations and date triggers need the Growth plan.
Thirty minutes with Kate, Simon or Peter on one example segment: what a successful customer looks like, where the gaps are, and whether there's work worth doing this quarter.
Talk to a founder →Keep reading
Trial Activation Playbook 2026
Your converted customers show you what a good first week looks like. This play checks every trial against that pace each day, confirms a trial is really stuck before anyone acts, and puts the move on the account in your CRM: personal outreach for high-fit trials, an unblock message or check-in your team chose to automate – or no move, with the reason noted.
Sales to CS Handoff Playbook 2026
Start while the deal is fresh. This play puts the deal's promises on the CRM record at closed-won, gets kickoff done inside a week, and at day 14 compares the account with customers who onboarded well. On track, it's left alone with a note; stalled, the CSM gets a drafted setup session or re-plan to run.
Second-Value Seeding Playbook 2026
Your best customers show you which feature comes after the first. This play checks every account against them each week, finds the feature customers like it added next and kept, and puts the move on the account in your CRM: an in-app prompt and a short story, the CSM on the next call – or no move, with the reason noted.
Every playbook, one download
All 32 workflows as print-ready playbooks — diagrams included. Plus every new workflow as we publish it.