Adoption
Customer success plans
Build a customer success plan around an agreed outcome, meaningful milestones, clear ownership and evidence that supports the next decision.
A customer success plan is a shared working record of the customer’s desired result, the milestones towards it and the next decisions each side must make. Start with a customer-confirmed outcome, then add evidence, owners and dates. Revisit it when progress or priorities change.
Give the plan a clear job
The plan answers three questions for both sides: What are we trying to achieve? What needs to happen next? How will we know whether it worked? It can guide work after onboarding without copying the implementation checklist, and inform a business review without becoming its presentation.
Keep internal sales strategy and private account notes in their appropriate records. A shared plan should contain commitments and observations both parties can recognise and discuss.
Build from the customer's outcome
Ask the customer’s outcome owner what they want to change in their work and who is affected. Record the starting position, the intended improvement and how the customer will check it. If the result cannot yet be measured reliably, name the evidence that must be gathered rather than substituting a convenient product count.
For example, a hypothetical customer using an approvals product might want regional managers to complete eligible approvals within its own target window. Accounts created and training delivered may help, but they do not show whether approvals meet that target. The customer should confirm the wording, population and measure before either side treats the statement as agreed.
Connect the result to a short route
Choose milestones that represent a meaningful decision, completed workflow or verified change. For each one, name the accountable person, a target date, the evidence that will establish completion and any dependency that could move the date. Confirm assignments with the named people. An unaccepted task beside a date is not a commitment.
A compact plan can use these fields:
| Field | What to record |
|---|---|
| Outcome | The result in the customer's terms, with its scope and success condition |
| Starting position | The agreed baseline or an explicit evidence gap |
| Milestones | The few steps that show progress towards the result |
| Owners and dates | Who accepts each step, when it is due and what it depends on |
| Evidence and review | What both sides will inspect and when they will decide what to do next |
| Open issue | A material obstacle, its response owner and the next update |
This is a suggested format. A complex account may need a separate delivery schedule; a simple account may need only a brief shared record. The test is whether the customer can find its goal and the next action without decoding an internal task system.
If the team uses a plan template, treat it as a starting structure rather than proof that every listed task applies. Gainsight NXT allows users to add tasks manually or apply a predefined template, while administrators configure plan types, templates, sharing settings and automation rules. Available options can therefore vary between organisations.
Before adopting a platform’s fields or workflow, check which settings are available and who can change them. Keep the shared plan focused on the customer-confirmed result and the actions that remain relevant, rather than preserving template tasks simply because they were included.
Keep the working record coherent
Some customer success platforms bring plan details, actions and updates into one workspace. Gainsight NXT, for example, separates plan information from assigned actions and provides Gantt Chart and Timeline views for tracking. This can make it easier for both sides to find the current plan rather than relying on scattered task lists and messages.
A plan record can also hold its purpose, owner, timeline and status. Keep these plan-level details distinct from the work assigned to individual people, so a change to an action does not obscure the overall direction of the plan.
Use comments, sharing controls or an activity timeline to keep relevant updates with the plan. Gainsight NXT allows activities and updates to be logged on a plan timeline; the specific sharing options and fields available depend on how administrators configure the platform.
Review the plan while a decision is still possible
At each agreed check point, inspect the milestone evidence and ask the customer what it means for the intended result. Mark a milestone complete only when its completion condition is met. If a task is blocked, record the cause, the person who can resolve it and the next update. If the evidence is inconclusive, keep that uncertainty visible.
When the customer’s priorities change, confirm the new goal with the appropriate owner. Decide which milestones remain useful, which should stop and which dates or measures need revision. Keep a brief record of what changed so an old target is not presented as a missed current commitment.
A plan earns its place when it prompts a timely action, exposes a dependency or helps both sides recognise a result. If a field or routine never helps either side make a decision, simplify it.
In this guide
- Writing success outcomes in the customer's languageEdit a success-plan outcome in the customer's terms, then confirm its people, task, intended change and evidence.
- Linking each success milestone to an owner and dateMake an ongoing success-plan milestone actionable with a completion condition, accepted owner, feasible date, dependency and evidence.
- Updating a success plan after customer priorities changeConfirm what changed, revise the success outcome and dependent milestones, and preserve a clear record of the customer's new commitments.
- Keeping success plans useful rather than administrativeUse a simple decision test to trim success-plan fields, updates and meetings while preserving customer goals and clear accountability.
