Direct answer: do not start with a churn score. Start with a trustworthy renewal timeline. For every contract or subscription, record the contractual date, notice window, evidence cutoff, accountable owner, allowed actions, proposal deadline, and the event that confirms renewal, contraction, expansion, or loss. AI can summarize usage, support, and authorized conversations and expose missing evidence. Rules can open tasks and block incompatible actions. People retain authority over scope, price, and concessions. Measure renewed revenue and margin against the prior process without crediting every outcome to a score or outreach.
Many companies discover a renewal only when the CRM creates an opportunity near the end date. By then, the stakeholder changed, an incident remains open, procurement has frozen budget, or the contract required earlier notice. The automation ran, but it started after the economic decision. https://makinai.co/insights/en/ai-preventable-churn-early-warning-retention addresses preventable loss; https://makinai.co/insights/en/ai-customer-expansion-account-revenue-loop-b2b addresses account growth. This project is the operating path between contract clock, evidence, action, and confirmed outcome.
Write a Renewal Operating Contract
- Unit — contract, subscription, asset, account, or renewable line, with an explicit aggregation rule.
- Clocks — end date, notice, budgeting, proposal, internal approval, signature, and billing.
- Evidence — usage, delivered value, cases, payment, relationship, obligations, price, and margin, each with source and time.
- Owner — accountable person for the next decision, fallback, and capacity; no owner is not low risk.
- Allowed action — value review, service recovery, proposal, approval, wait, or no contact; discount is not the default.
- Decision — renew, change scope, expand, contract, end, or defer, with reason and authority.
- Outcome — accepted contract, signature, order, paid invoice, or another finance-validated event; a meeting is not revenue.
- Learning — preserve signal, action, decision, and realized result as separate tracks.
Salesforce documents configurable lead time for renewal notices and opportunities. HubSpot documents workflows that create tasks, deals, and quotes before renewal. Those features execute timing; they do not determine the right timing. A complex, regulated, or procurement-led agreement may need 180 days. A simple subscription may need 30. Work backward from the last moment when service, value, or approval can still change.
Let AI assemble evidence, not grant terms
AI can reduce context reconstruction by summarizing authorized cases and meetings, finding stakeholder changes, comparing obligations with evidence, and flagging missing sources. Every summary should link to originals, carry timestamps, and separate fact, inference, and absence. A positive email does not erase declining usage, and a high score does not prove renewal intent.
Hard rules protect decisions: invalid contract date, critical open case, disputed billing, missing permission, price beyond authority, unsupported country, or proposal below margin. Models can order review when history is adequate, but predicted risk is not cause or treatment effect. Microsoft documents material history and completeness prerequisites for churn predictions; that is a reason to repair the renewable population before buying a model.
Practical example: 240 annual contracts
Consider a B2B services company with 240 annual contracts. Customer success keeps dates in a spreadsheet, sales creates opportunities 45 days out, support owns incidents elsewhere, and finance sees only final value. A pilot selects 60 contracts for one offer and country.
At 120 days, the workflow confirms contract, notice, owner, and contacts. At 90, it assembles delivery, usage, support, payment, and commitment evidence. At 60, the owner records a strategy: renew as is, repair service, revise scope, expand, or make no approach. At 45, a proposal exists or a reason explains why it does not. At 15, approvals and risks escalate. After the end date, finance confirms the economic event and the reason closes. The figures are illustrative, not a benchmark or MAKINAI result.
HubSpot separates renewal, upgrade, and downgrade recurring-revenue events. That prevents expansion from hiding core contraction or an automatic renewal from receiving program credit. Stripe subscription and invoice events are technical evidence, not business truth by themselves. Created, sent, paid, and canceled can have different meanings under the agreement and accounting policy.
Run an eight-week implementation
- Weeks 1–2 — define population, clocks, economic event, baseline, owners, and exceptions; manually reconcile 30 cases.
- Weeks 3–4 — connect contract, CRM, support, usage, and billing; build the evidence dossier with visible sources and freshness.
- Week 5 — configure tasks, blocks, escalation, authority, and tests; run in shadow mode.
- Week 6 — release a small cohort with a comparator and preserve the prior process as fallback.
- Week 7 — review missing data, noisy alerts, delays, manual work, proposals, and owner decisions.
- Week 8 — keep, adjust, or stop; document runbook, cost, privacy, retention, audit, and expansion criteria.
Deliverables include renewable-population logic, clock map, operating contract, dossier, integrations, rules, templates, dashboard, runbook, and decision log. Cost grows with contracts and line items, term variability, countries, currencies, channels, identity quality, access to usage and support, latency, proposal customization, approvals, retention, and human review.
Measure process, economics, and effect
Track date and owner coverage; cases opened on time; complete dossiers; days of lead time; accepted tasks; critical cases resolved before proposal; time to strategy; proposals on time; renewal, contraction, and expansion; renewed revenue and margin; time to signature and payment; concessions; and cost per managed renewal. Guardrails include improper contact, unnecessary discounts, overload, stale alerts, inflated pipeline, and no-score cases.
Use a comparable cohort or phased rollout. Seasonality, mix, pricing, product quality, and seller action influence outcomes; CRM data alone does not establish causality. Lifecycle owns journey and communication; customer success or sales owns the relationship; operations owns clocks and queues; data and engineering own integration; finance validates event and margin; legal owns terms; commercial leadership owns authority.
Before buying renewal intelligence, verify identity and sources with https://makinai.co/insights/en/ai-customer-identity-resolution-crm-duplicates. If renewals appear late or require five systems to reconstruct, bring MAKINAI at https://makinai.co/services/en/crm-ecommerce-commerce-transformation ten recent cases, contractual clocks, and the current workflow. We can scope one-offer, one-market implementation with a verifiable economic outcome and no automated concessions.