Systems Lab

Agent skill

renewal-save-motion

The defensive counterpart to expansion: a structured save motion for at-risk customers and a renewal runbook that starts at T-120, not the week the contract ends.

activeReaches the webInstructions only1,782 words

Filed under Onboarding, retention and expansion.

From NEON-Rutger/B2B-revops-skills · 45 skill entries · 51 · pushed 2026-10-05

What it does when it runs

The defensive counterpart to expansion: a structured save motion for at-risk customers and a renewal runbook that starts at T-120, not the week the contract ends. Triggers on 'renewal at risk', 'customer went quiet', 'churn save', 'save play', 'they stopped using the product', 'champion left the account', 'renewal coming up', 'GRR is slipping', 'downgrade request', 'cancellation notice', or any account where a health signal fired and the only play on the table is a discount. Entry condition: a risk flag already exists (health scan, usage drop, champion departure, blocked expansion). BOUNDARY: health scanners detect risk across the base; this skill runs the intervention on one flagged account. Expansion is the offense on healthy accounts and never runs on the same account at the same time. cs-operations owns CS org design; this is one motion inside it.

Automated analysis of the skill and the 2 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply
None found.
Hosts it reaches
  • hbr.org
  • info.sapphireventures.com
  • neontriforce.com
  • www.benchmarkit.ai
  • www.iconiq.com
  • www.saas-capital.com
Tool permissions it declares
No allowed-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files
None. Instructions only.

Ask about renewal-save-motion

Opens your assistant with this page's recorded context. Check the linked sources before relying on it.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah
git clone --depth 1 --filter=blob:none --sparse https://github.com/NEON-Rutger/B2B-revops-skills.git /tmp/B2B-revops-skills
git -C /tmp/B2B-revops-skills sparse-checkout set "renewal-save-motion"
mkdir -p ~/.claude/skills/renewal-save-motion
cp -R "/tmp/B2B-revops-skills/renewal-save-motion/." ~/.claude/skills/renewal-save-motion/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

Reproduced in full from NEON-Rutger/B2B-revops-skills/blob/03a61da783c6c4a686da3f5ba97e832319663571/renewal-save-motion/SKILL.md, which is licensed MIT (repository). 1,782 words, 9 headings.

Renewal Save Motion: Defense Is a System, Not a Discount

Median gross revenue retention for private B2B SaaS runs 84% to 91% depending on the survey, with top-quartile companies at about 91% and enterprise-grade (ACV above $250K) at a 95% median (Benchmarkit 2026, CY2025 data; SaaS Capital 2025). The distance between those two numbers is rarely product quality. It is whether the company runs renewals as a managed motion with an early-warning save play, or discovers churn in the cancellation email. Retaining revenue also costs a fraction of re-acquiring it; the 5x-and-up cost gap between acquisition and retention has been replicated across studies for a decade (Bain & Company research cited in Harvard Business Review, 2014: 5x to 25x depending on study and industry).

Expansion gets the attention because it is offense. But a dollar of churn cancels a dollar of expansion at par, and the save window closes silently: by the time a customer tells you they are leaving, they finished evaluating alternatives weeks ago.

Entry condition: this skill runs on a FLAGGED account. Detection is upstream (health scans, usage monitoring, champion-move detection). If nothing is flagged and no renewal sits inside 120 days, you do not need this skill yet; you need detection.


Stage check: do this before anything else in this skill

This skill was written for a company that already has a repeatable motion and named owners. Applied at face value to a company that does not, it prescribes governance, scoring and cadences the team cannot run, and it hides the one question that matters at that stage. Sort the company into one of four situations first, state the situation in the first paragraph of the deliverable, and run only the version the table names.

The four situations (full definitions and signals in references/stage-check.md):

  1. Start-up, pre product-market fit: fewer than roughly 30 comparable customers, wins from the founders' network, no measured win rate, cycle time or retention, nobody on quota. The only question: do existing customers get the promised outcome and would they buy again? Run the minimum version, or do not run it.
  2. Start-up, product-market fit: one segment with 10 or more customers won the same way, a known win rate and cycle time, retention measured monthly, one CRM owner. Run the skill for that one motion; thresholds are guidance, not rules.
  3. Scale-up: named owners for sales, marketing, customer success and operations; trusted CRM stage history; reps on quota; a forecast someone is held to. Run the full skill.
  4. Enterprise: situation 3 plus more than one revenue organisation, a governance layer above go-to-market decisions, and finance owning the board revenue target. Run the full skill with the enterprise deltas in the table.

If the evidence is thin, ask three yes or no questions: Is there a segment with 10 or more customers won the same way? Is retention measured monthly? Does someone own the CRM as part of their job? Three no answers means situation 1. One or two yes answers means situation 2. Three yes answers means situation 3 or 4; then ask three more: Is there more than one business unit or region with its own revenue plan and leader? Do go-to-market decisions pass through a formal governance layer? Does finance own the revenue target for board reporting? Two or more yes answers means situation 4; otherwise situation 3.

The full skill applies to both scale-up and enterprise. Not every skill applies at every stage; the table below says what this skill does at each, and "do not run" is a valid answer.

What this skill does per situation:

SituationWhat this skill does
Start-up, pre product-market fitRun monthly check-ins only. Document whether value persists, whether they would stay, and what causes departure. Skip the renewal clock and triage logic. Focus on understanding customer satisfaction at a basic level without formal processes.
Start-up, product-market fitRun failure-mode triage on risk signals. Test commercial levers in priority order. Log account name, mode, lever used, outcome, and time to resolution. Skip the T-120 renewal timeline; your constraint is understanding which accounts are at risk.
Scale-upRun full skill. Assign a named owner. CRM tracks renewal dates and health scores. Segment by failure mode; measure save rate per mode. Execute the commercial levers in sequence and track which ones work for your customer base.
EnterpriseSame as scale-up plus account governance model for multi-region or multi-product customers, with cross-functional account teams and renewal ownership matrices tied to regional or divisional profit and loss. Steering committee escalation protocol for strategic at-risk accounts, and formal executive sponsor re-engagement for accounts above renewal value thresholds.

Skip before product-market fit: The Renewal Clock; Scorekeeping; Diagnostic Questions.

Entry condition

If no account is flagged, stop. This skill saves a flagged account. Use customer-health-audit first if you need to identify at-risk accounts.

The Renewal Clock

Every renewal runs the same clock, regardless of health. Healthy accounts move through it in minutes per checkpoint; flagged accounts trigger the save motion.

CheckpointAction
T-120Renewal owner named. Health verdict pulled (usage trend, support pattern, champion status, sponsor status). Verdict: CLEAN, WATCH, or AT-RISK.
T-90AT-RISK accounts enter the save motion below. WATCH accounts get a value-recap touch and a re-verdict at T-60. CLEAN accounts get the renewal packet drafted.
T-60Commercial terms on the table for CLEAN and recovered accounts. No surprises inside 60 days: if the price is changing, the customer heard it by now.
T-30Signature logistics only. If substantive objections first appear here, the motion failed upstream; log that as the lesson, not "late-stage save."

The clock exists because renewal risk is visible in behavior (login decay, feature abandonment, sponsor silence) long before it is audible in words. Practice-based rule of thumb, not a study: if you first learn about risk inside 60 days, your detection layer, not this account, is the real problem.

Risk Triage: Name the Failure Mode First

A save play aimed at the wrong failure mode accelerates the churn. Classify before acting:

  1. Value gap (they use it and cannot prove it is worth the money): the missing artifact is an impact story in their numbers. Save play: build the value recap FROM their system data, walked through with the economic buyer, not the daily user.
  2. Adoption gap (they stopped using it, or never really started): the honest question is whether the problem still exists for them. Save play: shrink to the one workflow that hurt when they bought, relaunch that, and only that. A re-onboarding of everything convinces no one.
  3. Champion loss (your person left, silence followed): treat as a NEW SALE at the same account. Save play: map who inherited the problem, brief them as a stranger who is inheriting a paid solution, never as someone who owes you continuity. Also route the departed champion to your revival lane; one event, two plays.
  4. Sponsor shift (reorg, new exec, strategy change; your product is now someone else's decision): save play: executive-to-executive re-anchor on the new agenda. A feature demo cannot fix a political change.
  5. Competitive displacement (an alternative is actively in the building): save play: the switching-cost case plus a roadmap commitment with a date, delivered by someone senior. If you discover this one at T-30, assume you are negotiating an exit, and optimize for a dignified door left open.

Commercial Levers, In Order

The discount is the last lever, not the first, because a discount buys silence, not adoption, and it reprices every future renewal at this account and every account that hears about it.

  1. Scope right-sizing: fewer seats or modules at defensible value beats a discount on unused shelf-space. A smaller true contract retains more revenue over two years than a larger resented one.
  2. Term restructure: shorter renewal with success criteria attached, or multi-year with protection, depending on which side is uncertain.
  3. Service injection: implementation help, training, an owned success plan. Costs you margin once; a discount costs you margin forever.
  4. Pause over cancel where the platform allows it: preserves data, relationship, and the reactivation path.
  5. Price concession, last, always exchanged for something real (case study, term length, expansion option, reference), never given for free.

When the Save Fails

Some accounts should churn: wrong-fit customers bought in an over-eager quarter, companies that pivoted away from the problem. Fighting every churn teaches the team that retention is begging.

  • Decide save-versus-release explicitly at triage: fit still right, problem still real, economics still sensible. Two of three or better: fight. Otherwise: release well.
  • A released account gets a clean exit, data handover, and a standing re-entry premise ("if [the trigger that broke this] changes, here is the door"). Churned-well accounts are a revival lane later; churned-badly accounts are a review on a site your prospects read.
  • Every loss, fought or released, gets an autopsy in the same loss-pattern library your closed-lost motion uses (see closed-lost-revival): failure mode, first detectable signal, days between signal and action. The library is how next quarter's saves start earlier.

Scorekeeping

  • Save rate BY FAILURE MODE, not blended: a 60% save rate on value-gap accounts and 10% on competitive displacement are two different businesses hiding in one metric.
  • Signal-to-action lag: days from first risk signal to first human intervention. This is the number the whole motion exists to shrink.
  • Concession cost per saved dollar, so finance can see that the service-injection lever beats the discount lever on evidence, not philosophy.
  • GRR quarterly against the 84-91% median band / 91% top-quartile line (Benchmarkit 2026; SaaS Capital 2025), segmented the way your board segments it.

Benchmark provenance, vintages, and which rules are practice-based rather than studied: read references/retention-benchmarks.md.

Diagnostic Questions

  1. List renewals due in the next 120 days. Who owns each one, by name, today?
  2. For your last five churns: on what date was the risk FIRST visible in system data, and on what date did a human first act? The gap is your motion's real latency.
  3. What percentage of at-risk saves in the last year used a discount as the first lever, and what did those accounts do at the following renewal?
  4. When a champion leaves a customer account, what happens automatically today? Anything?
  5. Can your team produce a value recap in the customer's own numbers for your top ten accounts within one day? If not, the value-gap save play has no ammunition.

Built by Neon Triforce

Files bundled with it

These load only when the skill asks for them, so they cost nothing until it runs.

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what renewal-save-motion does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.

Build my GTM engine

Tell us what you want to improve. Fedor reviews the workflow and replies by email when there is a useful fit.

Fedor reviews every request personally. If there is a useful fit, he will reply by email.