Turn renewal dates, notice periods, contract value, ownership, and usage evidence into a real decision runway—without inventing a universal “risk score” or estimating exposure from unrelated stack averages.
01 · Contract runway
The important date is not always the renewal date. When a contract has a notice period, the practical decision deadline can arrive earlier. This desk keeps the two dates separate.
Analyze one subscription using the terms you actually know.
02 · Renewal economics
Test a known or hypothetical price change. The output is contract-value scenario math only; it does not predict the vendor’s offer or your negotiation outcome.
Modeled next-term value
Analyze the current contract, then add a quoted or hypothetical price change.
03 · Renewal register
Add each analyzed contract. The register sorts by the earliest decision deadline so a distant renewal with a long notice period does not disappear behind a nearer renewal.
| App | Decision deadline | Renewal | Annual value | Auto-renew | Owner | Usage | Action |
|---|---|---|---|---|---|---|---|
| No contracts added yet. | |||||||
04 · Evidence desk
The calculation engine uses your entered dates and values. These sources explain why renewal metadata, contract terms, ownership, and usage visibility matter.
FinOps describes SaaS management as understanding vendor-specific licensing terms, use rights, pricing options, organizational agreements, contract terms, renewals, and true-up/down parameters.
Open FinOps source ↗The FOCUS contract-commitment dataset explicitly models contract cost, contract ID, contract-period start/end, commitment-period start/end, quantity, type, unit, and related provider fields.
Open FOCUS specification ↗Zylo reports an average of 211 SaaS renewals annually in its 2026 enterprise context and says 87% of total software spend is tied to renewals. These figures are not used to estimate your own renewal volume or contract value.
Open Zylo source ↗05 · Methodology
Authority comes from transparent date arithmetic, user-provided contract fields, explicit evidence categories, and refusing to convert missing information into fake precision.
06 · Portable result
Copy or print a review note that separates contract inputs, derived dates, evidence readiness, scenario economics, and the decision boundary.
07 · Continue only where the evidence points
The renewal result should route into the next evidence question: inventory completeness, license usage, broader stack review, or cluster-level cost control.
FAQ
A universal score would imply that the same weights and thresholds apply across different contracts, vendors, industries, business-critical systems, and notice clauses. This tool keeps timing, auto-renewal, ownership, usage, seats, overlap, and criticality visible as separate evidence.
It is the renewal date minus the notice period you enter. It is a planning calculation, not a legal interpretation. Signed contract language can include special delivery methods, holidays, amendments, jurisdictions, or other conditions.
They sum the annualized values of contracts you added whose next renewal date falls inside each display window. They do not predict savings, and each contract is counted once by its next renewal event.
No. A close deadline means the review window deserves attention. Continuity, security, compliance, workflow dependency, migration effort, business criticality, and negotiated rights can matter more than cost reduction.
This HTML tool calculates in your browser. The register exists in the current page session unless you export it yourself. External source links open separately.
Yes. CSV exports the working register, and the calendar export creates an ICS file containing decision-deadline and renewal events for contracts with dates.
ToolRelief source review: September 19, 2026. Re-check material contract terms and external evidence before a financial, procurement, access-control, security, or contractual decision.
