Define the first result in the customer's words
Ask a recent happy customer: "When did you first feel this was working?" Write down their answer. It is usually specific: the first report sent, the first lead routed, the first invoice paid on time.
That moment is your activation milestone. Write it as a sentence a customer would say, with a number or a date in it. For example: "Our first campaign report went out on Friday without anyone building it by hand."
Work backwards to the shortest path
List every step between "signed" and the milestone. Cross out any step that does not move them closer. What remains is the minimum path. Most plans have too many steps, such as data imports nobody needs yet. Move those to week four.
Aim to reach the milestone in the shortest time that is realistic for your product. Write the target down as a number of days.
Hand over from sales with a one-page brief
Customers hate repeating themselves. Before the kickoff, the salesperson writes a one-page brief:
- Why they bought, in their words.
- The result they expect and by when.
- The people involved and their roles.
- Anything promised during the sale.
- Known risks, such as a tight deadline or a sceptical colleague.
Store it on the account record in your CRM, such as HubSpot, where everyone can find it.
Run a kickoff of 45 minutes
Use the kickoff to agree the plan, not to demo. Cover four things: the result they want, the milestone and its date, who does what on each side, and when you will next speak. End with a short written summary within a day.
Build a 30, 60 and 90 day map
Lay out the plan in three blocks:
- Days 1 to 30: setup and the activation milestone. Weekly contact.
- Days 31 to 60: second use case, wider team, first review of results.
- Days 61 to 90: a results review with numbers, and a conversation about the next goal.
Each block has an owner, a date and a visible outcome. Share the map with the customer.
Schedule the check-ins before you need them
Add check-ins to the calendar at day 3, 7, 14 and 30. Keep them short. At each, ask: what has happened, what is stuck, what is next. A message is enough where a call would be too heavy. Triggered messages can be sent from tools such as Customer.io or Userpilot.
Define the warning signs
Pick two or three signals that mean the customer is drifting: no login in seven days, the milestone date passed without progress, or the main contact has stopped replying. Agree who acts on each and within how many days. Where this feeds the wider system, see How to monitor customer health.
Fix drop-off with data
When customers stall at the same step, treat it as a design problem, not a customer problem. Improve onboarding completion rate covers how to analyse where they stop and what to change.
Common mistakes
- Treating onboarding as training on every feature.
- Starting without a handover from sales.
- Leaving the milestone vague, such as "getting comfortable".
- Doing everything for the customer so they never learn to use it.
- Letting the plan sit in one person's head.
- Waiting for the first renewal to find out how it went.
How you know it works
A rising share of new customers reach the milestone within your target number of days. Fewer customers go quiet in the first 30 days. The first results review is a meeting about numbers, not a rescue. When you ask new customers if they know what happens next, they can tell you.
On Monday morning: pick your last three happy customers and ask each when they first felt it worked.
