Ask what needs to change.
Before the kickoff call, read the notes from the sale. Find the problem that made the customer look for a solution. Then ask the person doing the work whether that problem is still the priority.
“We spend most of Friday building invoices. We want to finish before lunch and catch the work we’ve been forgetting to bill.”
That gives you a result to plan around. Put it at the top of the document and ask the customer to confirm it. A founder might have this conversation directly; in a larger team, the account owner can prepare the draft with the person who sold the product.
Check the starting point before setting a target.
Choose one or two measures that show whether the customer’s problem is improving. In the example above, preparation time and the share of work invoiced within seven days tell us whether the new process helps.
Record a starting value, an agreed target, and a date. Add where the numbers come from and who will collect them. If nobody knows the current value, make measuring it an early task. Leave it marked “to measure” until you have evidence.
Keep the definition consistent. If you measure hours per week, compare weeks with a similar workload or record invoice volume beside the hours. For a percentage, agree which jobs count and use that definition at every review. A product login can help explain adoption, but it doesn’t tell you whether invoicing got faster.
Customer success goals: three examples.
These fictional examples show how to adapt the plan. Set each target with the customer, using their own starting values and workload.
- A support team using a help desk
Reduce median first-response time from 8 business hours to 4 within 60 days.
How to check itThe support lead checks the reply-time report each week, using the same support hours and excluding automated replies.
- A field service company using scheduling software
Reduce missed appointments from 12% to 5% within 90 days.
How to check itThe scheduling manager compares no-shows with scheduled appointments, excluding cancellations made in advance. Keep that definition the same each week.
- A team training new hires
Reduce the time needed to handle a client case independently from 20 working days to 12 by the next quarterly review.
How to check itThe training lead records start dates and manager sign-off. Compare new hires doing the same role.
Give each next step an owner.
Work backward from the first useful result. To send the first invoice batch, the customer needs to supply records, your team needs to import them, and someone needs to check the totals. Those are the first rows in the plan.
Name one person responsible for each action, even when several people will help. Agree on the dates together. Keep the next few actions detailed; add later work once you know what the first attempt reveals.
Write down the blocker and the next move.
Access permissions, a missing export, an absent decision maker, or a busy customer team can all delay the result. State what is blocked, what that changes, and who will act. “Waiting on data” leaves the responsibility unclear.
“Imports cannot start until the accounting export arrives. The finance lead will send it by 5 October and flag any delay that day.”
Keep this section current. Remove a resolved blocker or note when it was resolved. Raise urgent problems as they happen so the next review can focus on decisions.
Review the result as well as the work.
Book the next check-in before sharing the plan. Agree who attends, who brings the figures, and how you’ll communicate between meetings. A short review every week or two can work during setup; choose a schedule that fits the customer and the work.
At the review, keep the original baseline and add the latest result with its date. Mark each action as not started, in progress, or done. Record what you decided, any changed deadline, and the next action. In the example, invoicing is faster, but missing billing codes still hold up two jobs. The plan records who will fix that and when.
When the target is reached, confirm the result with the customer and agree on the next goal. Keep the old plan as a record. If you later discuss retention in an investor update, use company-level results and keep private customer details out of it.
Turn the milestones into a customer success roadmap.
The roadmap is a short view of the order of work. For the agency in our example, it could look like this:
- Days 1–15Run the first invoice batch.
Import the records, check the totals, and work through the process together.
- Days 16–30Find what still takes too long.
Review the time log and invoice dates. Fix the slowest remaining step.
- Days 31–60Check the result with the customer.
Compare against the starting values and agree on the next goal or adjustment.
Use dates that match the customer’s situation. A 30-, 60-, or 90-day outline is a way to organize the work; the targets still need to be achievable. Keep the detailed actions in the plan so there is one place to update them.
