Build the plan that predicts the renewal a year out.
Translates the customer's goals into measurable outcomes, time-to-value milestones, and the leading indicators that flag risk early.
Inside: The goal translation, the milestone sequence, and the leading-indicator set.
Install it in one line, or paste it in.
~/.claude/skills/ and runs automatically when it is relevant.Connect your context. Set it to your motion.
it reads the account, contacts, ARR, and renewal date automatically.
turns milestones into measured events instead of checkboxes.
tracks whether the owners are actually meeting the plan.
This was built for a B2B SaaS org onboarding named accounts to a renewal. Set these to your stack:
Build the plan around the goals this customer stated, not a template. A generic plan renews no one.
| Set this | What it is | Default / Example |
|---|---|---|
| GOALS source | where the stated goals live | order formhandoffdiscovery notes |
| ADOPTION source | where usage lives | product analyticsa usage export |
| FIRST_VALUE | the first real outcome that matters | first live workflowfirst report shipped |
| TTV target | days to first value you aim for | 30 (re-tune to your product) |
| INDICATOR set | the leading signals you trust | weekly active seatskey-feature usesponsor engaged |
| OWNERS model | how you name both-side owners | CSM + customer champion per milestone |
| RENEWAL field | the renewal date and ARR | Account.RenewalDateAccount.ARR |
Everything the skill does, in full.
Takes the goals a customer stated when they bought and turns them into a plan that drives to value: milestones with dates, an owner on your side and theirs for each one, and the leading indicators that predict the renewal long before the renewal date. The output is a working plan, not a wish list.
- 1Goal translation
Turn each stated goal into a measurable outcome. "Improve efficiency" becomes "one team running the core workflow live by day 30." A goal you cannot measure is a goal you cannot prove at renewal.
- 2Time-to-value milestones
Sequence the outcomes: first value fast, then breadth, then depth. Each milestone has a date anchored to the start, not to "someday." The first-value milestone is the one that matters most; protect its date.
- 3Owners on both sides
Every milestone names a your-side owner and a customer-side owner. A milestone with no customer owner is a task you will do alone and they will not value. Escalate any milestone that has no owner on their side.
- 4Leading indicators that predict renewal
Pick the few signals that move before the renewal does: weekly active seats trending up, the key feature in real use, the sponsor still engaged, a second use case emerging. These are the early-warning system. Lagging signals like the renewal date itself tell you too late.
- 5The renewal thesis
State, in one line, why this account renews if the plan holds, and what would break it. Revisit it every review. If you cannot write the thesis, the plan is not done.
- Every goal is measurable, or it is flagged and sent back for a metric.
- Every milestone has a date and an owner on both sides.
- Leading indicators are named and trackable, not vague "engagement."
- The plan states its renewal thesis and the single biggest risk to it.
SUCCESS PLAN · sample account · start day 0, renewal day 365 MILESTONE TARGET YOUR OWNER THEIR OWNER INDICATOR Kickoff + goals agreed Day 3 CSM Sponsor plan signed First workflow live Day 30 CSM Champion 1 team active Full team adopted Day 75 CSM Champion 8/9 seats weekly Second use case Day 120 CSM Sponsor new workflow live Value review Day 180 CSM Sponsor outcome measured Leading indicators: weekly active seats, key-feature use, sponsor engaged. Renewal thesis: renews if the second team adopts and the sponsor stays engaged. Biggest risk: single-threaded on one champion.
The day targets, seat counts, and indicators come from the data you paste or the tools you connect. Nothing above is a real customer number; it is illustrative. When the skill cannot measure a milestone, it marks it a checkpoint and names the input that would make it measured.
Where an operator takes this next.
The plan is drafted. Here is where an operator takes it once the manual version proves out.
The plan predicts the renewal; the automation is what keeps the prediction honest.
Wire product analytics (Amplitude) so "first workflow live" fires automatically off real usage, and the plan updates itself instead of waiting on a CSM check-in.
A scheduled Claude task re-reads the leading indicators weekly and flags the account in Salesforce the moment the sponsor goes quiet.
If the single-threaded flag trips, have Slack DM the CSM's manager automatically, so the second-contact gap gets worked while there's still runway.
One skill is the on-ramp.
A single skill does one job. Chained into a playbook, or run as a full build, it becomes a system. Here is where this one plugs in.