SaaS renewals: what to do in the year before the term ends

Reference article · 5 min read

A subscription renewal is negotiated on a schedule the contract sets, not one the agency picks. By the time a renewal notice arrives with a new price and a signature deadline, most of the leverage is gone. The notice window is short, the budget request is already submitted, and the practical alternative to signing is an interruption in a system staff use every day. The work that changes the outcome happens about a year earlier, while nothing is urgent.

What follows is that year as a sequence of tasks. It assumes a software as a service agreement where the vendor hosts the application and the contract continues in terms rather than ending at a delivery. Budget calendars differ, so treat the months as a shape to adapt rather than a fixed rule.

Build the renewal calendar from the documents

Pull the executed agreement, every amendment, the order form listing what was purchased, and the cooperative or master agreement the purchase rode on. Record five things: the current term end, the deadline for notice of non-renewal, whether renewal happens automatically or requires an affirmative action, how many renewal options remain, and when the underlying purchasing vehicle expires.

Notice deadlines run backward from the term end, so a ninety day notice period on a June 30 term means the decision is effectively due at the end of March. Put that date in a calendar the agency watches, set a reminder well ahead of it, and name a responsible person rather than a shared mailbox.

Twelve to nine months out: inventory what is in service

Renewal quotes are built from the order form, not from reality. Reconcile the two, and compare recent invoices to what the contract authorizes.

Licensed versus assigned. Count the named users or devices actually provisioned, and separate active accounts from ones left behind by turnover.
Modules purchased versus modules in production. Agencies commonly pay for components bought during implementation and never configured.
Consumption elements. Storage tiers, non-production environments, transaction volumes, and interface counts often carry separate fees and growth curves.
Expiring credits. Training hours and professional services blocks may lapse at term end. Use them or negotiate carryover.

Nine to six months out: read the renewal and pricing language

Auto-renewal. Identify whether the term extends by itself. Evergreen language interacts poorly with public appropriation rules, and many jurisdictions limit an agency's ability to obligate future budgets. Requirements vary by state and change over time, so confirm the treatment with your procurement office and counsel.
Notice. Confirm the required form, delivery method, and address. A notice sent to the wrong contact can fail even when it is timely.
Escalation. Determine whether increases are capped at a fixed percentage, tied to a published index, or unaddressed. Silence generally means the vendor may quote current list price.
Non-appropriation. Confirm the clause exists, and that termination under it obligates the vendor to return agency data.
Fee triggers. Note what moves the price outside of escalation: user growth, record counts, added interfaces, or support tier changes.

Six to four months out: assemble the service record

Price is easier to discuss when the agency can describe performance precisely.

Support ticket volume by severity, with time to first response and time to resolution.
Availability against the service level commitment, including credits earned and whether they were claimed.
Open defects, and roadmap commitments from the last renewal that have not shipped.
Security posture: the current independent audit report, the subprocessor list, and incident notifications.
A short question set for staff who use the system daily. Keep it brief so people answer it.

Decide: extend, recompete, or restructure

A recompete takes far longer than a renewal, so decide while there is still time to run one. Weigh the service record, the price trajectory, the availability of comparable products, and the real cost of switching, including data conversion, retraining, and interface rework.

Confirm the authority separately from the business decision. Renewal options remaining, the expiration of the cooperative or master agreement, cumulative spend against the approved amount, thresholds that trigger governing body action, and state limits on contract length all constrain what the agency may sign. An extension the program wants is unavailable if the vehicle underneath it has lapsed.

Keep exit readiness current either way

Maintain these whether or not the agency ever leaves. They also protect against vendor insolvency, acquisition, and product end of life.

A current export. Request a full extract in a documented, non-proprietary format, and open it. Include attachments, audit history, and the field definitions needed to read it.
Configuration documentation. Workflows, security roles, forms, templates, and business rules, recorded outside the application.
An integration inventory. Every interface, its direction, its owner on each end, and what breaks if it stops.
Retention alignment. Confirm that retention and deletion behavior matches the applicable records schedule.
Administrative ownership. Domains, tenant accounts, certificates, and app store listings should be held by the agency, not by the vendor.

What to ask before signing

What is the proposed price for each line item, and what drove any increase?
What would the price be for the two terms after this one?
Which purchased modules are unused, and what credit applies to removing them?
What is the standard export format, and what transition assistance is included?

In the amendment, seek a capped escalation with a stated ceiling, a notice period long enough for the agency to act on, a defined transition assistance period after termination, and written confirmation that data is returned at no additional charge.

HQT works with state and local agencies on system evaluations, data migration, and integration work of the kind renewal decisions depend on.

Frequently asked questions

How much notice do we have to give to cancel a SaaS contract before it auto-renews?

The notice period is whatever the executed agreement says, and it is measured backward from the term end date rather than from the day the vendor sends a quote. Many agreements also specify the form of the notice and the exact address it must go to, and a notice delivered elsewhere may not count. Read the original agreement and every amendment, because a later amendment often changes the original notice language.

Can a state or local agency agree to an automatically renewing subscription?

It depends on the jurisdiction. Many public agencies cannot obligate funds beyond the current appropriation, so evergreen renewal language is commonly paired with a non-appropriation clause or replaced with renewal options the agency must affirmatively exercise. Rules vary by state and change over time, so confirm the treatment with your procurement office and your attorney before signing.

How do we keep price increases under control at renewal?

Negotiate an escalation cap into the contract, expressed either as a fixed maximum percentage or as a published index with a stated ceiling, and make it apply to every remaining term rather than only the next one. If the current agreement says nothing about escalation, the vendor is generally free to quote current list price at renewal. The best time to add a cap is at initial award, and the next best is at a renewal where the agency is genuinely prepared to compete the work.

When should we start preparing for a SaaS renewal?

About a year before the term ends for any significant system, and earlier if a recompete is realistic, because a solicitation, evaluation, award, and implementation take far longer than a renewal does. Starting a year out leaves time to inventory actual usage, collect the service record, and confirm purchasing authority before the notice deadline arrives. It also means the agency can discuss price while it still has a credible alternative.

What should we have on hand in case we leave the vendor?

A recent full data export in a documented, non-proprietary format that someone has actually opened, configuration documentation covering workflows, roles, forms, and business rules kept outside the application, and an inventory of every integration with its owner on each end. Confirm that the agency, not the vendor, holds domains, tenant accounts, and certificates. These items are worth maintaining even if you never leave, since they also protect against vendor insolvency and product retirement.