Get a renew-or-not verdict on every renewal before the meeting.
Combines adoption, champion stability, support sentiment, and competitive signals into one per-deal verdict.
Inside: The adoption / champion / sentiment inputs and the renewal verdict.
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.
accounts, renewal dates and value, contacts, and the renewal opportunity, live.
which features the customer actually uses and how often, the signal that predicts a renewal best and is hardest to paste by hand.
Your product-usage signal is the part most worth mapping carefully. Decide how your analytics tool expresses adoption per feature, and name the features the way your customers would recognize them.
| Set this | What it is | Default / Example |
|---|---|---|
| CRM | The system of record for the account and the renewal | A CRM with accountcontactopportunity objects |
| Renewal date field | The field holding the renewal close or period-end date | A "renewal end date" field |
| Renewal value field | The current ARR up for renewal | An "open renewal ARR" field |
| Product-usage signal | The adoption read per feature or capability | A per-feature usage tier from your analytics tool |
| Champion field | The contact marked as the primary relationship owner | A "primary champion" field |
| Renew threshold | Confidence floor above which you call it a likely renewal | 70% |
| Champion-stale threshold | Days of champion silence that downgrade the verdict | 90 days |
| Engagement-floor threshold | Active weeks below which the relationship reads thin | Customer median |
Everything the skill does, in full.
This skill reads one customer and returns a renewal verdict you can act on. It combines product adoption, champion stability, support sentiment, and any competitive signals into a single per-deal call: will this renew, at what value, and under what conditions. It then hands you the pitch material: the adoption story, the commercial levers you can pull, and the checklist of things that must happen before the renewal call. It is built for depth on one renewal at a time, not portfolio rollups.
- 1- Per-renewal verdict. Combine product adoption, champion stability, support sentiment, and competitive intel into a verdict and a confidence number: renew yes/no, a predicted value (flat, upsell, downgrade), and the conditions attached.
- Champion-stability check. Confirm the named champion is still active: record valid, title still a buyer, recent engagement. Flag single-thread risk when the only real relationship runs through one person.
- Adoption story for the pitch. Group product usage by depth: deeply used, established, emerging, untouched. State it in features the customer recognizes. The untouched group becomes the expansion narrative.
- Commercial-lever inventory. Term length, discount headroom, expansion add-ons, multi-year incentives, prepay. Attach a number to each and mark the strongest.
- Save-play prerequisites. A sequenced checklist of what must happen before the renewal call, with branch logic for responds, ghosts, and rejects.
- No renewal verdict without a champion check. If the champion left or has not engaged within the stale threshold, the verdict downgrades automatically.
- The adoption story is named-capability, not "good usage."
- Save plays are sequenced (Day 0 / Day 7 / Day 14) with branch logic for responds, ghosts, rejects.
EXAMPLE CO RENEWAL · Closes 2026-08-15 VERDICT: RENEW + EXPANSION POSSIBLE · Confidence 78% Champion stability: - Champion still at the company (profile verified this month) - Engaged 6 of the last 12 weeks (above customer median) - Second-thread contact left in March, single-thread risk Adoption story (for the pitch): Deeply used: Sequencing, Smart Send Established: Templates, Meeting Recording Emerging: AI Compose Untouched: Calendar features, Auto Follow-ups Story: "Core outreach is fully adopted. Calendar is your next step." Commercial levers: - Multi-year at flat rate (strongest) - Add calendar bundle (expansion) Save-play prerequisites: [ ] Re-thread to a second champion [ ] Run a calendar-feature demo [ ] Pre-position the multi-year offer 30 days out
The thresholds are defaults, not laws. The renew threshold (70%) is the confidence floor for calling a renewal likely. The champion-stale threshold (90 days) is the silence window that downgrades a verdict. The engagement floor defaults to your own customer median, so it self-calibrates once you have enough accounts. Re-tune all three after you watch a few renewals land against the verdicts the skill gave you.
Where an operator takes this next.
The single-account read proves the model works. Here is the version that runs it on every renewal.
The verdict stops being a snapshot and starts updating itself as the signals move.
Schedule a Claude task off your CRM's renewal-date field so every account gets a verdict 90 days out automatically, not when a CSM remembers to ask.
Connect Gong or your email tool so a champion going quiet past 90 days downgrades the verdict the moment it happens.
Wire the sequenced prerequisites into Salesforce tasks so "re-thread to a second champion" shows up as an assigned to-do, not a line in a doc.
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.