Start every customer the same way
The first ninety days decide the renewal. Make them a play with owned steps rather than a checklist somebody keeps privately.
The job
“I want to give every new customer the same start, and know when one is drifting.”
- Customer success managers
- CS leaders
- RevOps
Onboarding quality is the strongest predictor of a renewal and the least standardised process in most customer success teams. Each CSM has a way of doing it, the good ones have a very good way, and none of it is visible until a renewal goes badly and somebody asks what happened in the first month.
The reason it stays private is that the artefact is a checklist, and checklists live in the tool the individual prefers. Making the first ninety days a motion changes who can see it, which changes whether it can be improved.
What it moves
- Time to first value
- Gross revenue retention
- Handoff completeness
The division of labour
What RevTech does, and where you decide
In the product
How to do it
- Step 1 of 5
Start from the handoff, not from the kickoff call
The seller’s handoff arrives drafted when the deal closes. Read it before the kickoff rather than during it — the questions you want to ask the seller are the ones you will otherwise ask the customer, which is the first impression worth avoiding.
- Step 2 of 5
Make the ninety days a play
A play whose eligibility is accounts that have just entered the customer lifecycle enrols every new customer automatically. Its timeline carries the steps, each with an owner and an instruction, and they arrive as work in the right queue rather than as a document nobody opens.
- Step 3 of 5
Regenerate the account plan for the new lifecycle
The plan built to win the deal is not the plan to keep the account. Regenerating it produces one framed around adoption and growth, and it becomes the document the first quarterly review is built from.
- Step 4 of 5
Set the health baseline early
A health score is most useful as a trend, and a trend needs a starting point. Reading health at day thirty tells you what normal looks like for this account, which is what makes the reading at day seventy mean something.
- Step 5 of 5
Watch for the enrolment that stalls
A stalled or blocked enrolment arrives with the signals and the wait time attached. In onboarding this is the earliest reliable indicator you have: an account that stops moving through its first ninety days rarely starts again on its own.
What arrives
What this puts in your Action Center
| Item | What is prepared | How it resolves |
|---|---|---|
| WonDeal | The drafted customer success handoff | The deal |
| RevPlayActionInstance | The instruction, objective and account context for one step of the onboarding motion | Opens the account; completion goes through the play |
| EnrollmentAttention | The signals and the elapsed wait time behind a stalled enrolment | The account, on its Signals tab; the owner can also complete the current step |
| EnrollmentOutcome | The outcome summary when the motion completes or exits | Acknowledge |
Where this is today
A stalled enrolment card points at the account’s Signals tab, which is not switched on for production tenants yet. The card, its signals and the ability to complete the current step all work; the dedicated tab does not.
What to take away
- Read the handoff before the kickoff. The questions you skip there get asked of the customer.
- A private checklist cannot be improved because nobody can see it. A play can.
- Regenerate the account plan — winning and keeping are different documents.
- Baseline health at day thirty, or the day-seventy reading means nothing.
Go deeper
The material behind this
Try the demo.
See agents carry the repeatable work of GTM across sales, marketing, customer success, and RevOps. Every action prepared, reviewed, and recorded. Fictional data, real product.
Explore the demo