Before the Contract Renews Itself

About This Post

By Greg Margolin · August 20, 2026

An IT director is asked whether to renew 250 licenses for a design application. Procurement has the contract. Finance has the invoices. IT has the assignment records. Department managers know which projects are coming. And the contract says any change must be requested well before the renewal date.

By the time the information is gathered, the deadline has often passed, and the renewal happens by default at the same size, or bigger.

A quick word on terms. Software asset management (SAM) is the practice of tracking what software you own and how it's used. Three numbers matter and are easy to confuse: entitlement (what you bought), assignment (what's been given to people or installed) and usage (what's actually used). Shelfware is software you pay for but don't use. A true-up is a periodic count where you pay for growth. FinOps is the practice of managing variable cloud spend.

The Deadline Is Earlier Than You Think

Many contracts renew automatically unless you give notice of non-renewal a set number of days before the term ends. Some subscription programs are stricter still. Under Microsoft's New Commerce Experience, for example, annual subscriptions can generally be cancelled or reduced only within a short window after purchase or renewal (currently seven days), after which the seat count is fixed until the next anniversary. The moment to right-size is right around renewal, not halfway through the year.

Why "Low Usage" Isn't Enough

It's tempting to pull a usage report and cut everything that looks idle. Be careful:

  • Seasonal users may only need the software at year-end, audit time or for an annual project.
  • Legal and records holds can require keeping a departed employee's account or data.
  • Service, testing and disaster-recovery accounts look idle until you need them.
  • Departed employees are a different case: Microsoft's own offboarding steps treat blocking sign-in, removing the license and deleting the account as separate actions. A license freed up this way can be reassigned, but it only stops costing money when the subscription itself is reduced.

Low usage is a reason to ask a question, not an answer.

What a Good Renewal Looks Like

  • A renewal calendar keyed to notice dates, not just end dates.
  • Entitlement, assignment and usage side by side, with the gaps explained.
  • Questions routed to the people who can answer them, well before the deadline.
  • A short decision brief: current commitment, key dates, what's known and what still needs a decision.
  • The reasoning kept, so next year's renewal starts from this year's answers.

The same discipline applies to cloud spend, where the FinOps Foundation describes FinOps as creating “financial accountability through collaboration between engineering, finance, and business teams.”

How GQP Helps

Our Fractional Agentic AI Team builds and runs renewal and spend workflows that keep the calendar, reconcile entitlements with assignments and usage, flag the differences and prepare the decision brief in time to act. Procurement confirms the terms, department managers judge future demand, and your authorized people decide what to buy. We take on the gathering and the follow-up.

How You'd Know It's Working

  • No renewal passes its notice date unreviewed.
  • Every renewal has a written brief and a recorded decision.
  • Licenses assigned to departed employees are found and dealt with.
  • Next year's renewal starts from this year's answers.

Ready to Talk?

Start with a 15-minute conversation. We'll ask how renewals are handled today, then tell you honestly whether AI would help.

Prefer the phone? Call us at 888-477-5580, or 888-GQP-5580. Alternatively, complete our Contact Us form here.

Sources: Microsoft Partner Center, “New commerce license-based subscriptions: cancellation policy.” Microsoft Learn, “Remove a former employee from Microsoft 365.” ISO/IEC 19770-1:2017, IT asset management. FinOps Foundation, “What is FinOps?”