Renewal Negotiation Playbook: Keep Customers, Raise Prices, Don't Lose to "We're Switching"

Most founders treat renewal as a rubber stamp. Customer signed annual; the contract auto-renews; the team logs $X of "renewal revenue" without thinking. Six months in, a renewal is "at risk" — customer hints at switching to a competitor, demands deep discount to stay, or just goes silent. The team scrambles, often gives 30% off to "save" the deal, and walks away with a customer who now expects that discount permanently.

A working renewal-negotiation playbook does specific work. It starts 90+ days before renewal date, identifies risk early, runs a structured negotiation with prepared trades, and either closes a stronger renewal (price increase + multi-year + reference) or walks away gracefully. Done well, renewals are the highest-margin revenue you have — Net Revenue Retention compounds. Done badly, every renewal is a fire drill, prices erode each year, and 20% silently churn.

This guide is the playbook for renewal as a deliberate sales motion — different from initial sale, distinct from churn save-offers, more strategic than auto-renew. Companion to Annual Contract Negotiation (initial signing), Reduce Churn, First Customer Success Hire, and Discount & Promotion Strategy.

What Done Looks Like

By end of the exercise:

Renewal motion starting 90 days before contract end
Tiered renewal-risk classification (green / yellow / red)
Standard playbook per risk level
Price-increase strategy at renewal
Multi-year and expansion paths planned
Net Revenue Retention (NRR) tracked
Quarterly renewal-cohort review

This pairs with Annual Contract Negotiation (initial signing), Reduce Churn, First Customer Success Hire, Expansion Revenue, Discount & Promotion Strategy, Customer References, Customer Case Studies, B2B Procurement Process Navigation, Sales Playbook, Self-Serve vs Sales-Led, Activation Metric Definition (renewal predictors), and Win/Loss Analysis (lost-renewal patterns).

Renewal Is Different from Initial Sale

Don''t treat renewal like new business.

Help me understand the differences.

The contrasts:

| Aspect | Initial Sale | Renewal |
|---|---|---|
| Buyer mindset | Skeptical; comparing | Knows you; weighing fit |
| Decision drivers | Promised value | Realized value |
| Key question | "Will this work?" | "Did it work?" |
| Champion role | Convert skeptic | Defend internally |
| Pricing leverage | We have less | We have more (data on usage) |
| Risk | They don''t buy | They leave (and we lose ARR) |

**Strategic implications**:

**Initial sale**:
- Pitch what we''ll do
- Optimize for closing
- Champion-driven

**Renewal**:
- Show what we did (data)
- Optimize for expansion + price
- Outcome-driven

**The "renewal is a sale" reframe**:

Many teams treat renewal as administrative. It''s a sale.

- Buyer can choose to leave
- Buyer can negotiate
- Buyer''s perception of value matters
- Sales motion required (not auto-renew alone)

Treat it like a sale; you''ll renew more, expand more, and discount less.

**The NRR (Net Revenue Retention) goal**:

Healthy SaaS NRR:
- 100%: customers paying same as last year (flat; not great)
- 110-120%: small expansion (decent)
- 120-130%: strong expansion (excellent)
- 130%+: best-in-class (best PLG SaaS)

NRR > 100% means cohort revenue grows even with churn.
NRR < 100% means churn outpaces expansion (warning sign).

Renewal is half of NRR (the other half: expansion within term).

For my company:
- Current NRR
- Renewal-management state (auto-pilot vs deliberate)
- The opportunity

Output:
1. The current NRR
2. The renewal-as-sale assessment
3. The "we''re leaving renewals on the table" diagnosis

The biggest unforced error: letting renewals auto-pilot. Customer signs annual; auto-renew enabled; team forgets about it; renewal date passes; they didn''t advocate; customer churns OR pays same flat price for 3 years (no expansion). The fix: every renewal is a structured motion. Calendar trigger; assigned owner; playbook executed.

Start the Renewal 90 Days Out

Renewal-day arrives faster than you think. Build the runway.

Help me build the renewal timeline.

The standard 90-day timeline:

**Day -90: Initial review (CSM)**

- Pull customer health data
- Usage trend (growing / stable / declining)
- Stakeholder map (champion + others)
- Recent issues / escalations
- Classify risk: green / yellow / red

**Day -75: Internal alignment**

- CSM + AE meet (if multi-team)
- Pricing review (any changes?)
- Multi-year strategy
- Expansion opportunities identified

**Day -60: Reach out to customer**

- Casual message: "renewal coming up; want to chat about how things are going"
- Schedule QBR / strategic review
- Don''t lead with "renewal"; lead with value

**Day -45: Quarterly Business Review (QBR) call**

- Review last 12 months value delivered
- Specific outcomes, metrics, cases
- Listen for signals (issues, expansion needs, leadership changes)
- Tee up renewal conversation

**Day -30: Send renewal proposal**

- Pricing for next term
- Multi-year option
- Expansion modules / tiers
- Clear date by which to confirm

**Day -20: Negotiate**

- Address customer concerns
- Trade discount for terms (multi-year / expansion / case study)
- Get to yes (or escalate / walk)

**Day -10: Sign**

- Contract execution
- Procurement / legal if needed
- Buffer days for delays

**Day 0: Renewal date**

- Already done (signed earlier)
- Or: at-risk if not signed

**Day +30: Re-engage if not yet signed**

- Some customers slip past renewal date
- Don''t auto-extend forever; address head-on

**The "starting 30 days out" mistake**:

Founders / CSMs often start renewal 30 days before. By then:
- Customer''s already evaluated alternatives
- No time for procurement on customer side
- Pressure-cooker negotiation

90 days is the right runway. 60 if you can''t do 90.

**The QBR is the heart**:

For sales-led customers, QBR (Quarterly Business Review) is the renewal-precursor.

Structure:
- 30-60 minute meeting
- Slides: outcomes delivered, usage, roadmap
- Open: feedback, concerns, future needs
- Close: renewal teeing, next steps

Per [first-customer-success-hire](first-customer-success-hire.md): CSM owns the QBR.

For my system:
- Current renewal timeline
- Gaps
- Standardization plan

Output:
1. The 90-day timeline
2. The QBR template
3. The standardization plan

The biggest renewal-timing mistake: starting too late. 30 days before renewal: customer has decided; you''re reactive. The fix: 90-day runway; review at 90; QBR at 45; proposal at 30; negotiate at 20; sign at 10. Calendar-based, not vibes.

Classify Renewal Risk

Not all renewals are equal. Triage.

Help me classify renewals.

The three-color system:

**Green (low risk; ~70% of renewals)**

Signals:
- Healthy usage (steady or growing)
- Champion engaged
- No support escalations
- Recent positive feedback / NPS
- Renewal date plenty of runway

Action:
- Routine QBR
- Renewal proposal at standard pricing or modest increase
- Expansion conversation (if growing)
- Likely closes without drama

**Yellow (moderate risk; ~20% of renewals)**

Signals:
- Usage stagnant or slightly declining
- Champion left or changed roles
- One or two escalations
- Mixed sentiment (some positive, some negative)
- Less engaged in product

Action:
- Earlier outreach
- Diagnose: what changed? what''s the issue?
- Address specific concerns before renewal date
- May need pricing flexibility OR scope change
- 50/50 odds without intervention

**Red (high risk; ~10% of renewals)**

Signals:
- Usage dropping significantly
- Champion gone; no replacement
- Active dissatisfaction (escalations, complaints)
- Talked to competitors
- Pricing concerns vocal
- Decision-maker changing

Action:
- Founder / CEO involvement
- Recovery plan (specific issues addressed)
- Possibly: deeper discount; scope change; pause
- Likely to lose if no intervention
- Plan for "graceful loss" if can''t save

**The risk-classification cadence**:

Every 30 days: refresh classification per active renewal.

- Some yellow becomes green (issues resolved)
- Some yellow becomes red (issues escalate)
- Catch trajectory early

**The data inputs**:

Health-scoring system (per [VibeWeek customer-health-scoring](https://www.vibeweek.com/6-grow/customer-health-scoring-chat)):

- Usage score
- Engagement score
- Sentiment score
- Support load
- Champion status

Combine into a renewal-risk score automatically. Manual review on top.

**The "deflection vs save" decision**:

For yellow / red:
- Can we save with intervention? (deflection)
- Or is this fundamentally not the right customer?
- Some customers shouldn''t renew (low-fit; high cost)

Decide deliberately. Saving the wrong customer is worse than losing them.

For my customers:
- Risk classification system
- Data inputs available
- Refresh cadence

Output:
1. The classification framework
2. The data inputs
3. The cadence + responsibility

The biggest classification mistake: treating all renewals the same. Green renewals get over-managed (customer annoyed); red renewals get under-managed (lost). The fix: triage; differentiate effort; spend time where it matters.

The Renewal Proposal: Price Increase as Default

Don''t default to flat-renewal. Plan price increases.

Help me design the renewal proposal.

The principles:

**1. Price increase is the default**

Costs go up; product improves; market pricing rises. Without price increases:
- Real (inflation-adjusted) revenue declines
- Per-customer LTV underperforms
- Pricing power erodes

Default annual increase: 5-10% on renewal.

Communicate: "your subscription will renew at the new pricing tier as scheduled. Here''s why..."

**2. Customers expect some increase**

In 2026, B2B SaaS customers expect 5-10% annual increase. It''s not surprising; they''ve seen it from every vendor.

Surprise is when:
- 20%+ increase (justify carefully)
- 0% increase (signals weakness; missed opportunity)
- Big increase without explanation

**3. Tied to product / value**

Justify the increase:
- "We''ve added [X features] in the last 12 months"
- "We''ve doubled the limits / capabilities"
- "Industry pricing for this category is now [Y]"

Don''t apologize. Frame as "you''re getting more for similar relative cost."

**4. Multi-year option (carrot)**

Offer:
- 1-year renewal: standard new pricing
- 2-year renewal: lock in current pricing (no increase year 2)
- 3-year renewal: lock in + small additional discount

Multi-year benefits both:
- You get extended customer commitment
- Customer locks in price (insurance against future increases)

Many customers prefer 2-3 year contracts to avoid recurring negotiations.

**5. Expansion options**

Renewal is the natural moment to upsell:
- "We see you''re using 80% of your seat allocation; want to upgrade to higher tier?"
- "You''re heavy on [feature]; new tier includes [more]"
- "Your team has grown; let''s right-size your plan"

Expansion + renewal in same conversation = higher NRR.

**6. The proposal structure**

Subject: [Customer] Renewal Proposal — [Date]

Hi [Champion],

Coming up to your renewal date of [Date]. Here''s the proposal:

Option 1: 1-year renewal

Pricing: $X/yr ([+5%] from current)
Features: same plan, all current capabilities
New: [list of features added in last 12 months]

Option 2: 2-year renewal

Pricing: $X/yr (current pricing locked)
2-year commitment
Bonus: [small expansion or feature]

Option 3: Upgrade to [Higher Tier]

Pricing: $Y/yr
Includes: [new capabilities]
1-year or 2-year option

Let''s discuss what fits best. Available [dates / times].

[Name]


Three options. One usually fits.

**7. The "no proposal" approach for green**

For low-risk renewals, sometimes silence is fine:

- Auto-renew enabled
- Mention upcoming renewal once at QBR
- Renewal happens; you communicate post-renewal

Use only for: clearly engaged customers; small accounts; risk-free renewals.

**The "what if they push back?"**:

- "We can''t pay 5% more": offer 2-year at flat (trade)
- "We''ll need to evaluate alternatives": fair; help them find the data
- "We need to reduce scope": pause / reduce-tier (better than churn)
- "Procurement is delayed": extend renewal date 30 days

For my proposals:
- Standard increase amount
- Multi-year structure
- Expansion paths

Output:
1. The proposal template
2. The pricing-increase strategy
3. The multi-year option

The biggest proposal mistake: flat renewal as default. Year over year, prices stay same; effective revenue declines (inflation); pricing power erodes. The fix: 5-10% annual increase as default; justify with value; offer multi-year as alternative.

The Negotiation Itself

Anticipate customer pushback; have responses ready.

Help me handle renewal negotiation.

Common asks + responses:

**Ask 1: "We can''t pay more next year"**

Response options:
- "Tell me about the budget situation; we have multi-year pricing options"
- "Multi-year at current price (2-3 year commit)?"
- "Reduce-scope tier (smaller plan; lower price)?"

Don''t just discount. Trade the discount for something.

**Ask 2: "We''re evaluating alternatives"**

Response:
- "Help me understand what you''re looking for; I''d rather lose a deal than waste your time"
- "What''s working / not working with us?"
- Address concerns; offer to demo competitive features
- Don''t panic-discount

**Ask 3: "We need 30% off to stay"**

Response:
- "What changed in your situation that makes this critical?"
- "30% would require a structural change; can we discuss multi-year or scope?"
- Walk-away criteria: 30% is below your floor; walk

Per [discount-and-promotion-strategy](discount-and-promotion-strategy.md): save-offer discounts trained into "demand discount or threaten to leave." Don''t encourage.

**Ask 4: "Champion left; new team is reviewing"**

Response:
- "Happy to do a fresh demo for the new team"
- "Can I help with the internal review?"
- "Meet with new champion"
- Time may help (new champion needs to learn)

**Ask 5: "Our team isn''t using it as much"**

Response:
- "Help me understand what changed"
- "Want to schedule a re-onboarding session?"
- "Maybe a smaller tier fits better"
- Sometimes: "no judgment; let''s talk about pause / cancel" (if not fitting)

**Ask 6: "We need [feature] at this price; otherwise we''re switching"**

Response:
- "When is [feature] on our roadmap? Can I confirm dates?"
- "Multi-year at current price + roadmap commitment?"
- "If not feasible, we understand"

**Ask 7: "Annual contract is too long; want to go monthly"**

Response:
- Monthly typically priced higher (per [pricing-strategy](../1-position/pricing-strategy.md))
- "Monthly available; pricing is X (no annual discount)"
- Typically 20-30% premium

**Ask 8: "Can we delay the renewal?"**

Response:
- "30-day extension to handle [internal process]"
- Don''t extend indefinitely; sets bad precedent
- Document the new deadline

**Ask 9: "You''re cheaper at competitor X"**

Response:
- "What specifically about competitor X?"
- Know your differentiators (per [competitive-positioning](../1-position/competitive-positioning.md))
- Don''t price-match (race to bottom)
- "Different products; here''s the value math"

**Ask 10: "Sign me up — but we need [custom term]"**

Response:
- Per [annual-contract-negotiation](annual-contract-negotiation.md)
- Trade custom term for value
- Some asks justify; some don''t

**The trade-list**:

For every concession, get something:

| Customer wants | We get |
|---|---|
| Flat pricing | 2-year commit |
| 10% off | 3-year + reference |
| Custom feature | 30% price premium |
| Specific SLA | Monthly check-in calls |
| Extended payment terms | Higher price |

Never give without asking.

**The walk-away rehearsal**:

For some customers, the right answer is to walk:
- Demands below your floor
- Bad culture fit
- Constant complaining without paying full price

Walk-away script:
- "Based on the terms, this isn''t a fit anymore. Happy to revisit if circumstances change."
- Door open; respect intact

For my negotiation:
- Common asks playbook
- The trade-list
- Walk-away criteria

Output:
1. The objection-response playbook
2. The trade-list
3. The walk-away triggers

The biggest negotiation mistake: discounting reflexively. Customer pushes back; rep folds; 20% off; customer learned to push. The fix: every discount has a trade. Multi-year for flat pricing. Reference for discount. Rep can''t self-approve below floor.

Avoiding the Last-Minute Save Trap

When renewal date is in 7 days and customer says "I''m leaving"...

Help me handle the last-minute save scenario.

The pattern:

- Renewal date: 7 days
- Customer: "We''re leaving for [Competitor]"
- Founder''s reflex: "30% off to stay!"
- Customer stays at 30% off
- 12 months later: same conversation; now expects 40% off

This is how pricing erodes.

**Diagnose first**:

Before discounting, ask:

- Why are you leaving?
- What specific issue?
- Who decided?
- Is this final or negotiable?

Often the "real" issue is:
- Specific feature gap (not just price)
- Champion left; new team unfamiliar
- Bad onboarding earlier; never recovered
- One bad incident never resolved
- Real budget cut at customer

Each has different responses.

**Match the response to the cause**:

| Cause | Response |
|---|---|
| Feature gap | Roadmap commitment; partial workaround |
| Champion change | Re-onboard new team; demo |
| Bad onboarding | CSM intervention; training |
| Bad incident | Post-mortem + commitment to improve |
| Real budget cut | Reduced-scope tier (not discount) |
| "Competitor is shinier" | Differentiation conversation |
| Genuine bad fit | Allow churn; learn for future |

Discount alone fixes none of these.

**The "pause" alternative**:

For genuine budget-cut:
- Pause subscription instead of cancel
- Lower-tier or 50% scope reduction
- Re-engage when budget returns

Better than full discount; preserves pricing integrity.

**The "controlled save" rules**:

If you decide to save:
- Don''t exceed pre-set floor (e.g., 15% max discount)
- Tie to specific terms (multi-year; no escalation rights)
- Document as exception (not standard)
- One-time-only ("we can''t do this again at next renewal")
- Quarterly check-in to address root cause

**The "graceful loss" approach**:

Sometimes the right answer is: let them go.

- "We''re sorry to see you leave. Is there anything I should know that''ll help us improve?"
- Offer help with transition (data export)
- Keep the relationship clean
- Some come back 6-12 months later

Never burn the bridge; never beg either.

**The renewal-postmortem**:

After every lost renewal:
- Document why
- Pattern-match across losses (per [win-loss-analysis](win-loss-analysis.md))
- Adjust playbook

For my saves:
- Save-criteria documented
- Discount floor
- Postmortem cadence

Output:
1. The save-or-graceful-loss decision tree
2. The discount floor + terms
3. The postmortem template

The biggest save mistake: discounting to save EVERY at-risk renewal. Some customers shouldn''t be saved; some saves train discount-extraction; the cumulative effect erodes pricing. The fix: diagnose before discounting; not all saves are right; sometimes graceful loss is better.

Multi-Year Strategy

Multi-year contracts compound. Use them strategically.

Help me design multi-year strategy.

The benefits:

**For you**:

- Predictable revenue (years out)
- Higher retention (locked in)
- Lower CAC payback (longer tenure)
- Cash upfront sometimes (annual prepay × N years)

**For customer**:

- Price lock (insurance against increases)
- Reduced negotiation overhead
- Sometimes: better terms

**The structure**:

| Term | Discount / Benefit |
|---|---|
| 1 year | Standard pricing |
| 2 year | 10% off Year 2 (or flat at Year 1 price) |
| 3 year | 15% off + locked SLA |

**The "lock pricing" trade**:

Customer signs 2-year at current pricing; you don''t raise prices in Year 2.

Math:
- Year 1: $100K
- Year 2: $100K (would have been $105K + 5% increase)
- 2-year total: $200K
- Vs annual: $205K
- "Cost" to you: $5K (the increase you didn''t do)
- Benefit: 2-year commitment; 50% lower churn risk

Usually worth it.

**The "auto-renew" with multi-year**:

3-year contract with annual auto-increase:
- Year 1: $100K
- Year 2: $103K (3% increase)
- Year 3: $106K
- 3-year total: $309K

Customer gets predictable; you get programmed price increases.

**Be careful**:

- Don''t lock in too low for too long
- Include scope-protections (volume increase = pricing change)
- Allow exit clauses for major scope changes

**The multi-year sales pitch**:

Don''t lead with multi-year. Lead with annual; offer multi-year as "if you''re committed; here''s a better deal."

Option 1: 1-year renewal at $X Option 2: 2-year at $Y/yr (locked; no increase Year 2) Option 3: 3-year at $Z/yr (locked + 5% off Year 1)

Which fits your budget cycle?


**Customer hesitation: "3 years feels long"**

Response:
- "Most enterprise customers go 2-3 year"
- "We can do 2-year if 3 feels long"
- "Cancellation provisions if needed"

**The "every customer should be on multi-year" target**:

For mature SaaS:
- 60-80% of revenue on multi-year
- Reduces churn
- Stabilizes growth

Push toward this over time.

For my strategy:
- Multi-year offering
- Pricing structure
- Push criteria

Output:
1. The multi-year structure
2. The pricing
3. The push strategy

The biggest multi-year mistake: flat-discount multi-year that locks your pricing power away. "30% off for 3 years" — sounds great; you can''t raise prices for 3 years; customer effectively got 30% off forever. The fix: trade for time-bounded benefit (Year 1 price for Year 2; not "30% off Year 1, 2, 3"). Programmed price increases preferred.

Track NRR and Run the Quarterly Review

Renewal management without measurement is invisible.

Help me measure renewal effectiveness.

The key metrics:

**Net Revenue Retention (NRR)**:

- (Starting ARR + expansion + upsell - churn - downgrade) / Starting ARR
- Reported: month / quarter / year cohort
- Goal: > 110%

**Gross Revenue Retention (GRR)**:

- (Starting ARR - churn - downgrade) / Starting ARR
- Excludes expansion
- Goal: > 95% for B2B SaaS

**Renewal rate**:

- (# renewed accounts) / (# accounts up for renewal)
- Goal: > 90%

**Logo retention**:

- Same as renewal rate; sometimes called "logo retention"

**Expansion revenue**:

- Upsell + cross-sell revenue
- Goal: 20-30% of base ARR annually

**At-risk-saved rate**:

- (# at-risk that renewed) / (# at-risk total)
- Effectiveness of save motion

**Average discount on renewal**:

- % discount given to retain
- Track: declining over time?

**The quarterly renewal review**:

Each quarter:
- Cohort coming up for renewal: count, ARR
- Risk classification breakdown
- Past quarter''s renewal results
- Wins / losses analysis
- Playbook adjustments

Look for patterns:
- "We lose customers who started in Q2 of last year — why?"
- "Renewals stall when champion changes — fix?"
- "Multi-year takes 30% — should we push more?"

**The renewal pipeline view**:

Like sales pipeline, but for renewals:

| Customer | Renewal Date | ACV | Risk | Status | Owner |
|---|---|---|---|---|---|
| Acme | 2026-06-15 | $50K | Green | Proposal sent | Sarah |
| Beta | 2026-07-01 | $25K | Yellow | QBR scheduled | Mike |
| Gamma | 2026-07-15 | $100K | Red | At-risk plan | Founder |

Visibility = accountability.

**The "lost renewal" debrief**:

For every lost renewal:
- 30-min debrief
- Root cause
- Was it preventable?
- Pattern across losses?
- Update playbook

This is win/loss analysis applied to renewals.

For my system:
- NRR tracked
- Renewal pipeline visible
- Quarterly cadence

Output:
1. The KPI dashboard
2. The renewal-pipeline view
3. The quarterly review template

The biggest measurement mistake: NRR not tracked. Founder doesn''t know if cohort revenue grows or shrinks; can''t tell if renewals are healthy. The fix: NRR / GRR / renewal-rate dashboard; quarterly review; actionable signals.

Avoid Common Pitfalls

Recognizable failure patterns.

The renewal mistake checklist.

**Mistake 1: Auto-pilot renewals**
- No motion; missed expansion
- Fix: every renewal = structured sale

**Mistake 2: Flat-renew default**
- Pricing erosion over time
- Fix: 5-10% increase as standard

**Mistake 3: Starting too late**
- 30 days; reactive
- Fix: 90-day runway

**Mistake 4: One-size-fits-all motion**
- Green over-managed; red under-managed
- Fix: tiered playbook

**Mistake 5: Discount-reflex on at-risk**
- Saves with deep discount; trains gaming
- Fix: diagnose before discount

**Mistake 6: No champion management**
- Champion leaves; nobody''s the relationship owner
- Fix: stakeholder map + maintenance

**Mistake 7: No multi-year push**
- All annual; missed locking opportunity
- Fix: multi-year as default offer

**Mistake 8: No NRR tracking**
- Don''t know if program works
- Fix: dashboard + cadence

**Mistake 9: No graceful-loss framework**
- Burn bridges; or save bad customers
- Fix: walk-away criteria

**Mistake 10: No postmortem**
- Don''t learn from losses
- Fix: 30-min debrief per loss

**The quality checklist**:

- [ ] 90-day renewal motion
- [ ] Risk classification (green / yellow / red)
- [ ] Tiered playbook per risk
- [ ] Standard 5-10% renewal increase
- [ ] Multi-year option offered
- [ ] Expansion identified
- [ ] NRR / GRR tracked
- [ ] Quarterly renewal review
- [ ] Save criteria documented
- [ ] Graceful-loss process

For my system:
- Audit
- Top 3 fixes

Output:
1. Audit
2. Top 3 fixes
3. The "v2 renewal program" plan

The single most-common mistake: renewals are an afterthought. Sales focus on new business; CSM does what they can; renewals just happen — until they don''t. The fix: treat renewal program as core revenue motion. Calendar-based; structured; measured. The compounding (NRR > 100%) is too valuable to ignore.

What "Done" Looks Like

A working renewal program in 2026 has:

90-day renewal motion (calendar-triggered)
Risk classification with tiered playbook
Standard 5-10% annual increase
Multi-year option offered (60-80% of revenue ideally)
Expansion identified at QBR
Renewal pipeline visible (CSM-owned)
NRR / GRR / renewal-rate tracked
Save-criteria documented (with floors)
Graceful-loss process
Quarterly cohort review

The hidden cost of weak renewal management: NRR < 100%. Customers cumulatively pay less year-over-year (churn outpaces expansion); growth becomes expensive (need more new acquisitions); investors see the leak. NRR is the leading indicator of SaaS health; renewal is half of NRR. Spend the time; build the playbook; the compound returns are massive.