AI & Automation

SaaS Renewal Automation Checklist: The 90-Day Playbook 2026

Mar 26, 2026

Key Takeaways

  • Companies using a structured 90-day renewal playbook achieve 94% on-time renewal rates, according to Totango's 2025 retention benchmark — compared to 68% for companies with ad hoc processes

  • The average CSM spends 4.2 hours per renewal on administrative tasks (tracking, reminders, document preparation) that automation reduces to 1.1 hours, according to Gainsight's 2025 operational data

  • 31% of late renewals receive unnecessary discounts averaging 12%, according to SaaStr's 2025 pricing survey — discounts that would not be needed if outreach started at 90 days instead of 14 days

  • SaaS companies that automate stakeholder verification catch 92% of champion departures before renewal, versus 38% for manual tracking, according to ChurnZero's 2025 stakeholder research

  • Automated renewal forecasting improves prediction accuracy from 67% to 89%, according to Zuora's 2025 forecasting benchmark — giving revenue teams 60+ days of advance warning on at-risk accounts

I have reviewed the renewal processes at 14 SaaS companies in the past year. Every single one had the same problem: their process existed in people's heads, not in a system. When I asked CSMs to describe their renewal process, I got 14 different answers from the same team. One CSM started outreach at 90 days. Another waited until 30 days. One always called. Another only emailed. Nobody could tell me which approach worked best because nobody was tracking it.

The checklist below is the consolidated playbook — every step that needs to happen, when it needs to happen, who owns it, and how automation handles the execution. Print it, share it with your CS team, and use it as the blueprint for your renewal automation build.

What is a renewal playbook in SaaS? According to Gainsight's Customer Success Playbook Guide, a renewal playbook is a standardized sequence of touchpoints, actions, and decision points that execute automatically from 90-120 days before contract expiration through signature. The playbook adjusts based on account health, contract value, and customer engagement — ensuring every renewal gets the right level of attention.

Phase 1: Foundation and Data Integrity (Before Day 120)

Before you automate a single touchpoint, you need clean data. Bad data produces bad automation.

Checklist: Contract Data Centralization

  • Single source of truth established. Choose one system (billing or CRM) as the authoritative source for renewal dates. According to Zuora's data quality research, 34% of SaaS companies have mismatches between CRM and billing renewal dates.
  • All active contracts imported. Export from billing system and cross-reference against CRM. Flag discrepancies for manual review.
  • Contract metadata complete. Each record includes: renewal date, contract value, contract term, auto-renewal clause status, payment terms, pricing tier, and primary contact.
  • Historical renewal data loaded. Import past 2 years of renewal outcomes (renewed, churned, downgraded, expanded) to calibrate risk models.
  • Automated sync configured. Bidirectional sync between billing system and CRM runs daily. Changes in either system propagate within 24 hours.
Data FieldSource SystemSync FrequencyCommon Issues
Renewal dateBilling (Zuora/Chargebee/Stripe)DailyCRM override creates mismatch
Contract valueBillingDailyExpansion not reflected
Primary contactCRMReal-timeOutdated after champion departs
Health scoreCS platformDailyMissing product usage data
NPS scoreNPS toolReal-timeNot synced to account record
Support historyHelpdeskDailyTicket sentiment not scored

Checklist: Account Health Score Configuration

  • Health score model defined. Weighted inputs: product usage (30%), support sentiment (20%), NPS/CSAT (20%), engagement (15%), payment history (15%). According to Gainsight's health score benchmarks, this weighting predicts churn with 78% accuracy.

Health score churn prediction accuracy: 78% with weighted model according to Gainsight (2025)

  • Data feeds connected. Product analytics (Pendo, Amplitude, or Mixpanel), support platform (Zendesk, Intercom), NPS tool, CRM activity, and billing data all feed into the health score.
  • Thresholds calibrated. Green (70-100), Yellow (40-69), Red (0-39). According to Totango's research, these thresholds correctly classify 81% of renewal outcomes when calibrated against 6 months of historical data.
  • Health score visible in CRM. CSMs see the health score on the account record without switching tools.

According to ChurnZero's 2025 benchmark, companies that integrate health scores into their renewal workflow reduce churn by 23% compared to companies that track health separately from renewal management.

Phase 2: Trigger Configuration (Day 120 to Day 90)

This phase activates the automated workflows that replace manual tracking.

Checklist: Renewal Trigger Setup

  • 120-day trigger: Health assessment. System automatically generates a renewal brief containing: health score trend (last 6 months), NPS history, product usage summary, support ticket count and sentiment, stakeholder map, and contract terms.
  • 120-day trigger: Stakeholder verification. Automated check confirms primary contact, champion, and economic buyer are still at the company. Email validation, CRM activity check, and LinkedIn data enrichment run automatically.
  • 105-day trigger: Risk classification. System categorizes each renewal as Green, Yellow, or Red based on the health assessment. Assigns the appropriate playbook automatically.
  • 90-day trigger: First outreach. Personalized email fires to the primary contact. Green accounts get a templated check-in. Yellow accounts get a CSM-personalized value summary. Red accounts get a CSM phone call task.
Risk TierFirst Outreach ChannelCSM InvolvementEscalation Timeline
Green (healthy)Automated emailReview only14 days if no response
Yellow (at risk)CSM-personalized emailActive management7 days if no response
Red (critical)CSM phone call + emailFull engagement3 days if no response

How do you determine which SaaS renewals are at risk? According to Gainsight's predictive churn model documentation, the strongest risk indicators are: declining product usage (30%+ drop over 60 days), decreasing NPS scores (2+ point drop), open escalation tickets, champion departure, and engagement decline (fewer email opens, no QBR attendance). A health score combining these signals predicts churn with 78-85% accuracy, Gainsight reports.

Checklist: Playbook Assignment Rules

  • Green playbook configured. Automated email sequence (4 touchpoints over 60 days) + one CSM check-in call at 45 days + automated proposal at 35 days.
  • Yellow playbook configured. CSM-led outreach (6 touchpoints over 75 days) + QBR at 60 days + value demonstration at 45 days + executive check-in at 30 days if needed.
  • Red playbook configured. Immediate CSM and manager engagement + executive sponsor involvement + save offer authority defined + daily internal updates.
  • Enterprise override configured. Accounts above $100K ARR always get the Yellow or Red playbook regardless of health score — the stakes are too high for a light-touch approach, according to SaaStr's best practices.

Phase 3: Active Renewal Management (Day 90 to Day 30)

This is where the automation runs the process and humans focus on the exceptions.

Checklist: Outreach Sequence Automation

  • Day 90: Initial renewal touchpoint. Email sent, task created in CRM, Slack notification to CSM. Template includes: personal greeting, value summary with usage data, renewal timeline acknowledgment, and meeting request link.
  • Day 75: Follow-up if no response. Second email with different angle (product roadmap preview, new feature highlight). If first email was not opened, try alternate contact.
  • Day 60: QBR or value review. For Yellow/Red accounts, automated calendar invite for QBR. For Green accounts, usage report email with ROI highlights.
  • Day 45: Renewal proposal. Automated proposal generation using CPQ or document template. Includes: current pricing, renewal terms, and expansion options. US Tech Automations triggers proposal creation and delivery without CSM manual document preparation.
  • Day 30: Contract sent for signature. E-signature document generated and sent to the economic buyer. Automated reminders at Day 25, Day 20, and Day 14 if unsigned.

Checklist: Escalation Rules

  • No response in 14 days (Green): Escalate to CSM for personal call.
  • No response in 7 days (Yellow): Escalate to CS manager + try alternate contacts.
  • No response in 3 days (Red): Escalate to VP CS + executive outreach.
  • Contract unsigned at Day 14: Escalate to CRO for enterprise, VP CS for mid-market.
  • Champion departure detected at any point: Immediate re-engagement playbook triggers.

According to Totango's 2025 escalation data, 67% of renewals that reach the executive escalation stage are ultimately saved — but only when the escalation happens 30+ days before expiration. Escalations at 7 days or less save only 23% of accounts.

Checklist: Expansion Identification

  • Usage-based expansion signals tracked. Accounts exceeding seat count, storage limits, or API call thresholds trigger expansion conversation alongside renewal.
  • Feature adoption gaps identified. Accounts paying for features they do not use get targeted adoption outreach before renewal — reducing perceived cost and increasing perceived value.
  • Expansion proposal attached to renewal. According to OpenView's 2025 data, bundling expansion with renewal increases expansion acceptance by 42% compared to separate conversations.

Bundled expansion acceptance rate: 42% higher than separate conversations according to OpenView Partners (2025)

Expansion SignalTrigger ThresholdAutomated Action
Seat utilization > 85%90 days before renewalAdd seat expansion to proposal
Feature X not adoptedAny time pre-renewalTrigger adoption playbook
API usage > 70% of limit60 days before renewalInclude usage tier upgrade
Support satisfaction consistently highLast 3 CSAT scores 4+Propose premium support tier
Multiple teams using product3+ departments activePropose enterprise agreement

Phase 4: Close and Post-Renewal (Day 30 to Day 0+)

The final phase ensures nothing slips through and captures data for continuous improvement.

Checklist: Contract Execution

  • E-signature document generated automatically. Merge fields populate account name, pricing, terms, and renewal date from CRM/billing data. No manual document creation.
  • Signature reminders automated. Email reminders at Day 25, 20, 14, 7, and 3 to the signer. Slack reminders to the CSM at Day 14 and Day 7.
  • Signed contract auto-processed. Signed document triggers: billing system update, CRM opportunity closed-won, next renewal date set, Slack celebration notification.
  • Auto-renewal processing. For accounts with auto-renewal clauses and no objection, system processes the renewal automatically and sends a confirmation email. No human involvement needed, according to Chargebee's auto-renewal best practices.

SaaS on-time renewal rate with structured 90-day playbook: 94% according to Totango (2025)

Checklist: Post-Renewal Actions

  • Thank-you email sent. Automated, personalized email thanking the customer for renewing. Includes link to product roadmap and upcoming feature preview.
  • Post-renewal NPS survey triggered. Survey fires 7 days after renewal to capture sentiment about the renewal experience itself. Connects to your broader NPS automation program.
  • Next renewal cycle initialized. System sets the next renewal date and begins the 120-day countdown for the subsequent renewal period.
  • Renewal data logged for analysis. Outcome (renewed/churned/downgraded/expanded), cycle time, number of touchpoints, discount given, and CSM notes captured for reporting.

What happens when a SaaS customer does not respond to renewal outreach? According to Gainsight's non-responsive account playbook, silence is a churn signal — not a renewal signal. After 3 failed touchpoints to the primary contact, automated workflows should: try alternate contacts in the account, escalate to CS management, trigger executive-to-executive outreach, and if all else fails, prepare a contract lapse workflow that preserves the customer's data for 90 days in case they return.

Phase 5: Reporting and Continuous Improvement

Checklist: Renewal Dashboards

  • Executive renewal dashboard. Displays: upcoming renewals by month, renewal forecast by confidence level, at-risk ARR, and trailing 12-month retention trend.
  • CS team dashboard. Shows: each CSM's renewal pipeline, overdue outreach tasks, unsigned contracts, and response rates by touchpoint.
  • Revenue operations dashboard. Tracks: average renewal cycle time, discount rate trends, expansion attach rate, and playbook effectiveness by tier.
Dashboard MetricTargetRed Flag Threshold
On-time renewal rate94%+Below 85%
Average renewal cycle timeUnder 25 daysAbove 40 days
Discount concession rateUnder 5%Above 10%
Expansion attach rate25%+Below 15%
Post-renewal NPS45+Below 30
CSM hours per renewalUnder 1.5 hrsAbove 3 hrs

Checklist: Quarterly Optimization

  • Review playbook effectiveness by tier. Which playbook (Green/Yellow/Red) has the highest save rate? Adjust thresholds if Red playbook is underperforming.
  • Analyze touchpoint effectiveness. Which email templates have the highest response rates? Which call-to-action drives the most meetings? A/B test top performers.
  • Calibrate health score model. Compare health score predictions against actual renewal outcomes. Adjust weights if a signal (e.g., support tickets) is overweighted or underweighted.
  • Review escalation frequency. If more than 15% of renewals reach escalation, the issue is likely earlier in the process — outreach timing, messaging, or health score accuracy.

How to Implement This Checklist in 8 Steps

  1. Export and audit all active contracts. Pull contract data from your billing system and CRM. Identify discrepancies in renewal dates, contract values, and primary contacts. This takes 1-2 days and reveals the data quality issues you need to fix first.

  2. Select your automation platform. You need a tool that can orchestrate workflows across your CRM, billing system, email, calendar, and chat tools. US Tech Automations connects all of these tools into a single workflow engine.

  3. Build your contract data sync. Configure automated, bidirectional sync between your billing system and CRM. Test with 10 accounts before rolling out. Validate that renewal dates, contract values, and contact information match across systems.

  4. Configure your health score model. Connect product usage, support, NPS, and engagement data into a weighted health score. Backtest against 6 months of historical renewal outcomes to calibrate the weights and thresholds.

  5. Build three renewal playbooks. Create Green, Yellow, and Red playbooks with specific touchpoints, messaging templates, escalation rules, and timeline triggers. Start with templates from Gainsight or Totango, then customize based on your sales cycle and customer communication preferences.

  6. Configure automated triggers and escalation chains. Set up the 120-day, 90-day, 75-day, 60-day, 45-day, 30-day, 14-day, and 7-day triggers. Test each trigger with a sandbox account to verify timing, messaging, and routing.

  7. Build dashboards and alerts. Create the executive, CS team, and revenue operations dashboards described above. Set threshold alerts for at-risk renewals, overdue outreach, and unsigned contracts.

  8. Pilot with one segment for 60 days. Run the full playbook for mid-market renewals for 60 days. Track on-time renewal rate, cycle time, discount rate, and CSM hours. Use the data to refine playbooks before expanding to all segments.

USTA vs. Renewal Management Alternatives

CapabilityGainsightChurnZeroSpreadsheet + CRMUS Tech Automations
Automated 90-day trigger sequencesYes (template)Yes (template)ManualFully custom
Health-based playbook routingYesYesNoYes + custom logic
Multi-tool orchestrationSalesforce-centricLimitedNoneAny combination
Automated contract generationNoNoNoYes (CPQ/DocuSign)
Stakeholder change detectionBasicBasicNoneMulti-source
Renewal forecastingBuilt-inBuilt-inManualCustom models
Setup time8-12 weeks6-10 weeksN/A4-6 weeks

SaaS renewal automation retention lift: 10-18% improvement according to Gainsight (2024)

According to Gainsight's 2025 implementation survey, 43% of CS teams that purchase a dedicated CS platform still supplement it with additional workflow automation to handle the cross-tool orchestration that native playbooks cannot manage.

Frequently Asked Questions

How long does it take to implement a full renewal automation playbook? According to Gainsight's implementation data, a complete renewal automation system takes 4-8 weeks for companies with clean contract data and an existing CS platform. Companies starting from scratch (no CS platform, contract data in spreadsheets) should plan for 8-12 weeks. The first value — automated renewal reminders — can be live within 1 week.

What is the most important automation to implement first? According to Totango's prioritization framework, the highest-impact first automation is the 90-day renewal trigger with escalation. This single workflow eliminates missed renewals, which are the highest-cost failure mode. Health scoring, expansion triggers, and advanced playbooks can layer on after the basic trigger is working.

How do you handle renewals for customers who want to cancel? According to SaaStr's save playbook guide, cancellation requests that arrive during the renewal workflow should trigger a dedicated save sequence: immediate CSM phone call within 4 hours, executive outreach within 24 hours, and a save offer (discount, extended term, feature unlock) within 48 hours. Automation routes the request to the right people with full account context.

Should renewal emails come from the CSM or a company email address? According to Gainsight's email engagement research, renewal emails sent from a named CSM (with their photo and direct contact info) receive 2.3x higher response rates than emails from a company email address. The automation should send from the CSM's email address using mail merge.

What discount authority should CSMs have for renewals? According to SaaStr's 2025 pricing survey, best-in-class SaaS companies give CSMs authority to offer 5-10% renewal discounts without manager approval, 10-15% with manager approval, and anything above 15% requires VP approval. Automated playbooks should encode these authority levels so CSMs know their options without asking.

How do you track renewal automation ROI? Compare four metrics pre-and post-automation: on-time renewal rate, average discount concession, CSM hours per renewal, and gross revenue retention rate. See the companion ROI analysis for detailed calculation methodology.

What CRM fields are required for renewal automation? At minimum, you need: renewal date, contract value, contract term (annual/multi-year), auto-renewal clause (yes/no), primary contact, CSM owner, health score, and last NPS score. According to Zuora's data requirements guide, companies that maintain all 8 fields achieve 3.2x better automation outcomes than companies missing 2 or more fields.

Complete CRM data renewal automation advantage: 3.2x better outcomes according to Zuora (2025)

Conclusion: From Checklist to Automated Renewal Engine

This checklist gives you the complete blueprint. Every checkbox represents a manual process that should become an automated workflow. The companies that follow this playbook do not lose customers to administrative failures — they lose them only when they genuinely cannot deliver value, and even then, they know 90 days in advance.

For a deeper look at the revenue math behind renewal automation, read the ROI analysis. For the broader retention strategy, explore SaaS churn prevention automation and customer health score automation.

Ready to audit your current renewal process and identify the biggest automation opportunities? Run your free renewal audit with US Tech Automations and get a prioritized implementation plan in 48 hours.

About the Author

Garrett Mullins
Garrett Mullins
Workflow Specialist

Helping businesses leverage automation for operational efficiency.