Renewal Playbook on a Revenue Operating System
Why renewals break on fractured graphs
- Contract value in billing — does not match CRM ARR field
- Delivery pain invisible — tickets spiked; AM focused on upsell deck
- Negotiation in mail — not on account; successor AM starts blind
- Expansion opps orphan — no link to parent renewal motion
- QBR fiction — pretty slides; no trace to mail or usage
A revenue operating system does not eliminate hard conversations — it makes them earlier and evidence-based.
90-day renewal radar
| Window | Actions | Artifacts on graph |
|---|---|---|
| T-90 | Create renewal opp; confirm bill-to and stakeholders | Opp linked to parent account; contract end date field |
| T-60 | Health check: mail + delivery summary | Internal note; MCP read brief archived |
| T-45 | QBR or executive touchpoint scheduled | Calendar + Workspace deck linked |
| T-30 | Pricing / expansion proposal if qualified | Quote in mail on account |
| T-14 | Commit or escalate churn risk | Stage + blocker fields honest |
| T-0 | Closed won renewal or save plan active | Signed terms on account |
Roles on the renewal graph
| Role | Owns | Needs on account |
|---|---|---|
| Account manager | Relationship, QBR, renewal opp | Mail, contract value, delivery summary |
| CS / success | Adoption, risk signals | Tickets, health notes — not full forecast |
| Finance | Invoice, terms, credit | Read-only pipeline; AR notes |
| Sales (expansion) | New modules / seats | Child opp linked to renewal parent |
Permission design prevents CS from editing commit while still surfacing churn risk — see MSP guide for services-heavy orgs.
Expansion vs renewal (do not merge blindly)
Create linked opps: parent renewal at contract value; child expansion for new modules, seats, or sites. Forecast rolls up; narratives stay legible. AM runs renewal; AE or specialist runs expansion with shared mail thread on the logo.
- Expansion qualified — usage or ticket pattern supports upsell
- Renewal at risk — delivery or sponsor change; pause expansion pitch
- Land-and-expand timing — expansion close after renewal secures base
MCP renewal brief (read-only)
For [ACCOUNT], summarize: contract/renewal opp details, last 60 days mail themes, open support or delivery notes, and expansion opps. Flag churn risk (low engagement, negative mail, ticket spikes) in five bullets with evidence.
AM edits deck; agent does not send customer mail. Governance: MCP key policy.
QBR without archaeology
- Deck outline in Workspace — linked from renewal opp
- Metrics slide from CRM + finance fields — not screenshot from billing portal
- Mail recap — decisions and open items from account threads
- Forward plan — next 90 days with named owners
- Post-QBR note on account — agents read it next cycle
Sector-specific reminders
- MSP — ticket volume and license true-up on renewal; MSP playbook
- Commercial trades — quote versions and field handoffs; quote-to-cash guide
- Logistics — credit, accessorials, invoice status; prospect-to-invoice guide
Metrics for internal discipline
Track privately: time to renewal brief, percent renewals with mail on account, expansion opps with delivery context, forecast traceability for renewal commit. Skip public hero stats — use for your own operating review.
Save motions when risk appears late
T-14 churn signals are not rare — they are usually ignored until too late. A save motion on the graph includes:
- Executive sponsor map updated — who left, who replaced them
- Delivery recovery plan — ticket backlog, owner, customer-visible timeline
- Commercial option set — term extension, module concession, or honest churn forecast
- Mail trail on account — no side-channel apologies leadership cannot see
Agents can draft internal save summaries from mail + tickets; only humans negotiate concessions.
Post-renewal: close the loop for next cycle
Won renewal is not the end — log what worked on the account note, archive QBR deck in Workspace, and set T-90 for next term immediately. Teams that skip this rebuild from zero next year. Linked expansion opps that closed should note attach rate and implementation status so MCP revenue workflows stay accurate.