• Vol. 2 · No. 23
  • ISSN 5269-2749
Full-text feed
The Quiet Ledger

The part of the decision nobody explains.

  • Independent reader-funded
  • Contributors 03 named

Corporate — Field report TQL-BUS-176

Renewal in Ninety Days? The Clauses That Decide What You Pay in Year Four

Software contracts inherited their shape from the perpetual license era, and the parts that cost you money three years out are not the parts people read first.

A printed multi-page software subscription agreement on a desk, open to a pricing and renewal section, with a wall calendar and a calculator beside it
A printed multi-page software subscription agreement on a desk, open to a pricing and renewal section, with a wall calendar and a calculator beside it

The expensive part of a software agreement is almost never the price on the order form. It is the arithmetic that price is subjected to over the next thirty-six months, and the date by which you had to object to it. I have read a few hundred of these. The same four or five mechanisms do nearly all the damage, and they do it quietly, in the third year, long after the person who signed is in a different job.

Knowing where those mechanisms came from helps, because they are not arbitrary. Each one is a scar from an earlier commercial model, carried forward into the current one.

The term became the product, and the paperwork never caught up

For a long stretch, business software was sold as a perpetual license: a large one-time fee for the right to run a version forever, plus an annual maintenance percentage for patches, support, and the right to upgrade. The license was the asset. Maintenance was the annuity. Vendors learned early that the annuity was the better business, because it compounded and because customers who had already capitalized the license rarely walked away from the support line.

When delivery moved to hosting, the two line items collapsed into one subscription. But the vendor's internal model did not change. They still think in terms of a base and an escalator. What used to be "license plus maintenance at a fixed percentage" became "subscription with annual uplift," and the uplift inherited the maintenance percentage's logic: automatic, modest-looking, applied to a growing base.

Auto-renewal came from the same place. Maintenance contracts renewed by default because nobody wanted an annual lapse in patch rights. That default survived into subscriptions, where its effect is far larger, because now lapsing means losing access to the system rather than losing access to updates. The Federal Trade Commission is the body responsible for how automatic renewal and negative option terms are presented to buyers, and the scrutiny there has pushed disclosure forward, but a negotiated business agreement is still governed mostly by what you signed.

So the structure you are reading was built for a world where the software was yours and the recurring fee was a service. It is now applied to a world where neither is true. That mismatch is where the money hides.

Find the notice window first, before you read anything else

I do not start at page one. I start with a text search for "notice," "renew," and "terminate," and I write three dates on the front of the folder: the end of the current term, the last day to give non-renewal notice, and the last day to give notice of a change in quantity if those are separate clauses. They often are.

Common shapes:

  • Evergreen with short notice. Renews for successive terms equal to the current one unless either party gives notice thirty or sixty days out. Manageable, as long as someone is watching.
  • Evergreen with long notice. Ninety days is common in enterprise agreements, and I have seen one hundred and eighty. On a twelve-month term, a ninety-day window means you must decide a quarter of the way through the year before the year you are deciding about.
  • Fixed term, express renewal. Ends unless you sign again. Rarer, better for you, and worth asking for.

Notice method matters as much as timing. If the contract requires written notice to a named legal address, an email to your account executive is not notice. I have watched a company lose a non-renewal because the person who sent it had a cordial reply from the rep and assumed the matter was closed.

Put the notice deadline in a shared calendar with a reminder six weeks ahead of it, owned by a role rather than a person. Roles outlast employees.

The price clause is usually three clauses pretending to be one

Read every sentence that touches money as a separate mechanism, because that is how the vendor's deal desk built it.

The uplift. A stated annual increase, sometimes capped at a fixed percentage, sometimes tied to an index, sometimes expressed as "not to exceed" language that tells you the ceiling and nothing about the floor. Compound it over the term before you agree. An increase that sounds small applied to a base that also grows with headcount is not small by year four.

The discount. Your first-term price is frequently a discount off a list price recorded somewhere in the document or in an attached schedule. If the discount is expressed as a percentage that applies only to the initial term, your renewal is not last year's price plus the uplift. It is list, plus the uplift. That gap has produced more surprised finance directors than any other clause I can name.

The reduction rights. Can you renew for fewer seats than you have now? Many agreements let quantities go up at any time and down only at renewal, and only with notice, and sometimes not below a floor set at your peak. If you grew fast and then flattened, this is the clause that determines whether you are paying for the company you used to be.

Count what you actually bought, not what you were sold

The second pass is about units. Every subscription has a billing metric: named users, active users, transactions, records, endpoints, gigabytes, API calls. Find the defined term, read the definition, then go measure your actual consumption against it.

Metric drift is the ordinary failure here. A company buys on named users, then builds an integration that counts as a user, then connects a second system, and three years later the overage line is a meaningful fraction of the base. True-up clauses let the vendor reconcile and bill the difference, often at list rather than your negotiated rate. Read whether overage is billed at contract price or list. It is a short sentence with a long tail.

Then check entitlements against modules. Products get repackaged. A feature included in your original tier can move into a higher tier at renewal, and the contract may permit that by reference to an online product description the vendor can edit. If something you depend on daily is not named in your order form, name it.

The questions that get answers before the window closes

Sixty to ninety days before the notice deadline, I send one short message with four asks: a written confirmation of the renewal price and how it was calculated, the current count on the billing metric, a list of entitlements by name, and confirmation of the notice address. Everything that follows gets easier once those four are on paper.

Leverage exists only before you renew, and only in proportion to how early you asked. A vendor facing a quarter-end with an open question about your account will discuss caps, co-terminus dates, and seat reductions. The same vendor, after an auto-renewal has fired, will discuss nothing until next year.

Read it with a calendar open and a calculator running. The clauses that matter are short, and they are the ones written in the language of time.

About the author

Cyrus MehrabianCorporate Desk

Cyrus writes about deferred maintenance and what waiting actually costs.