What goes in it
- The business outcome, in the customer's words.
- How it will be measured, with today's baseline.
- Milestones, each with a date and an owner on both sides.
- Risks and dependencies, such as an integration or a data migration.
- When you'll review it together, for example at each QBR.
Worked example
A finance software customer's goal is to close the books in 5 working days instead of 9 by the end of Q2. The plan has 8 milestones due before the first QBR, such as "bank feeds connected" (customer IT, February 14) and "controllers trained" (CSM, February 28). By the QBR, 6 were met on time. (Example numbers.)
Month-end close is down from 9 days to 7, so the customer has 2 of the 4 days it wanted. That's the progress to report, in the customer's own measure.
How CS leaders use it
Ask for a plan on every high-touch account and review a sample in account reviews. At renewal, the plan is the record of value delivered against goals the customer set, which is stronger than a usage chart. A plan whose milestones keep slipping is an early renewal risk.
Common mistakes
- Writing it alone. If the customer didn't help write it, it isn't mutual.
- Goals in feature terms ("use dashboards") when they should be outcomes.
- No owner on the customer's side.
- Writing it once and never opening it again.
More on this topic: renewals, definitions, guides and tools.
Updated November 3, 2026