Buying guide / Renew

SaaS renewal checklist: usage, cost and decisions

A renewal review starts with the current contract and a named service owner. Establish when a decision must be made, then work backwards far enough to obtain a quote, review evidence and test an alternative if needed. The timeline depends on your agreement and the effort required to move; a generic reminder thirty days before expiry may arrive too late for either.

By SaaS Ranking · Reviewed 2026-10-02

Download the checklist (CSV)

Build a renewal record from documents

Capture the purchased entity, product, edition, term dates, payment schedule and quantity commitment from the signed documents. Record notice requirements exactly and ask your contract owner to confirm the action date. Keep that date separate from an internal review deadline. Add the person who can approve spending and the person who can authorise a change. Where the documents disagree with an account screen or a sales message, leave the discrepancy open until the responsible owner resolves it.

Compare assigned seats with the work being done

Ask for a usage export covering a period that represents your workflow. Separate purchased seats, assigned seats and evidence of actual use. A single login is not necessarily useful work, and an occasional account may support an important seasonal task. Let the business owner explain low use before removing access. Check service accounts, integrations, guests and privileged roles separately. Record the measure you use, its date range and any missing coverage so a future reviewer can reproduce the conclusion.

Request a like-for-like renewal quote

Send the intended quantity, required features and support scope with the request. Ask for a line-by-line explanation of changes from the existing offer. Put a reduced-quantity option and the unchanged-scope option side by side if both are permitted. Identify one-time credits and expiring discounts so they do not hide the ongoing rate. Use the cost calculator for a shared planning period, but keep its estimate separate from payment dates and cash-flow planning. A lower total is a budget result, not proof of product fit.

Reopen evidence that the purchase depends on

Check whether the service scope, hosting arrangement, integration or your own use has changed. Review the dates of documents in the procurement file and ask for replacements where needed. A fresh web measurement can help locate public evidence, but the date of our visit does not tell you when a vendor last changed the document. Record both dates when available. If an unresolved item was accepted temporarily, check whether its condition was actually completed rather than carrying the exception forward automatically.

Choose a path and preserve the reason

Record one of four actions in your own file: renew unchanged, renew with a changed scope, run an alternative trial or prepare an exit. Name the person who owns the next step and the evidence supporting the decision. If you are testing an alternative, budget the overlap and confirm how long the current service must remain usable. When the new agreement is final, update the next review date, retain the old baseline and check the first invoice against the approved scope.

Your working checklist

The download contains these questions plus blank fields for your answer, evidence URL, review date, owner, due date and decision. Complete it in your own spreadsheet.

Ownership
Who owns the service, budget and renewal decision?
Ask for: Named internal owners.
Dates
What are the term end, notice requirement and internal decision date?
Ask for: Confirmed contract record.
Commitment
Which seats, usage or minimum spend are committed?
Ask for: Current order form.
Use
What work was completed during the representative review period?
Ask for: Dated usage export and owner explanation.
Scope
Which required features and integrations must remain available?
Ask for: Current workflow inventory.
Quote
What changes in rate, quantity, support or discount at renewal?
Ask for: Itemised renewal offer.
Evidence
Which approval conditions or documents need review?
Ask for: Procurement file and follow-up record.
Alternative
What trial and transition would an alternative require?
Ask for: Trial plan and cost scenario.
Decision
Who approved the chosen action and what happens next?
Ask for: Decision, owner and due date.

Source and scope

The FinOps Foundation includes usage analysis and collaboration during licence and SaaS renewal in its capability guidance. The workflow and worksheet here are our own practical review structure.

FinOps Foundation: Licensing & SaaS. Reviewed 2026-10-02.