A free contract extension for a tool we had not used yet
The initiative slipped seven months. Rather than renewing capacity nobody had touched, the ask was for the time back.
The contract was roughly $90,000 a year for a tool bought to support an initiative that then slipped. By the time renewal came round, usage logs showed fewer than 20 sessions against an expectation of daily active use, and the revised launch date was seven months after the original one. The same review is offered as a fixed-price SaaS license audit.
Why the ask worked
The key was specifics: usage logs, and a documented internal timeline for the revised launch. That made the case a factual account of usage that had not happened yet, paired with a credible date for when it would, rather than a discount request dressed up as a fairness argument. A vendor can tell the difference between a genuine delay and a tactic, and bringing the real timeline upfront made this far easier to grant.
The outcome
The vendor extended the term by seven months at no additional charge: a 19-month term for the original 12-month price. The company paid roughly $90,000 for a full year of intended usage rather than a year that included seven months of dead time. Measured per month of real usage, that is an effective discount close to 37 percent.
The takeaway
Usage timing is a distinct lever from usage level, and an underused one. A vendor who understands why a tool sat unused, backed by actual data rather than a general claim, and believes the delay is genuine and time-bound, has real room to extend value at little cost to themselves. It preserves the relationship far better than a customer who lets the contract lapse in frustration or renews reluctantly at full price.
When to ask for time instead of money
The ask works when the vendor can see that usage is genuinely near zero, because a renewal at full price on an untouched deployment is a churn risk they would rather not create. Extending the term costs them nothing in cash, keeps the logo, and pushes the real commercial conversation to a point where the tool might actually be embedded. Two things make it more likely to land. Bring evidence of the delay rather than a general claim, an internal project timeline works well. And name the length you want; open-ended requests get met with an open-ended offer. Where it does not work is a tool with healthy usage, where the same request signals hesitation without giving the vendor a reason to concede.
Common questions
Keep reading
What an account team sees when a renewal lands on an account with idle seats, why unused licences survive, and how to right-size before the vendor call.
In-depth GuideRight Sizing SaaS Contracts With Real Usage DataWhy seat count and real usage are two different numbers, and how involving the business users unlocks savings that spend data alone misses.