I'm currently reviewing the renewal terms for our enterprise observability platform, and the proposed contract includes a standard clause allowing for annual price increases at the discretion of the vendor, tied to a "market rate" index. Given our annual spend is now in the mid-six figures and we've built significant data gravity within their ecosystem, this presents a substantial financial and operational risk.
My legal and procurement teams have drafted an amendment seeking to impose a hard cap on any year-over-year increase—specifically, a maximum of 5% or the percentage change in the Consumer Price Index, whichever is lower. The goal is to create predictability for our three-year budgeting cycles, especially as our data volumes grow predictably.
The vendor's initial pushback has been multifaceted and, in my analysis, follows a predictable pattern:
* **Claim of "Industry Standard":** They assert that such open-ended increase clauses are universal in SaaS agreements, which our own portfolio review shows is not entirely accurate, though it is common.
* **Vague "Cost of Service" Arguments:** They cite increased costs for their own infrastructure and R&D, but refuse to provide any transparency linking those costs to our specific price point.
* **Leverage of Ecosystem Lock-in:** The conversation subtly shifts to our high volume of custom dashboards, integrated alerts, and historical data, implying migration cost would be prohibitive. This is a classic vendor lock-in tactic.
* **Offering a "Discount" in Lieu of a Cap:** Their first counter-proposal was a 10% discount off the new list price at renewal, which, of course, does nothing to address the fundamental risk of an uncapped list price increase in future years.
I am interested in the community's experience with similar negotiations. Specifically:
* What specific contractual language have you successfully used to cap renewal increases? Did you tie it to a public index, a fixed percentage, or another mechanism?
* What was the most substantive pushback you received, and how did you counter it? For instance, when they cite their rising costs, has anyone had success requesting (even high-level) transparency to justify the "market rate" adjustment?
* In cases where a hard cap was rejected, were you able to negotiate alternative protections? Examples might include:
* A longer initial term at a fixed rate.
* Specific, pre-defined pricing tiers for anticipated usage growth.
* A right to terminate for convenience if the increase exceeds a certain threshold, with robust data portability and extraction assistance clauses.
The underlying technical concern here is that our monitoring data has become a critical system of record. The commercial terms must reflect that dependency and mitigate the risk of us being held hostage by exponential cost growth. I am preparing a detailed analysis of alternative platforms (despite the migration pain) to use as a BATNA, but I'm keen to learn from the contractual strategies others have employed.
Data over dogma
Your analysis of the predictable pushback is spot on. The 'industry standard' argument is a classic negotiation tactic, but your data point about your own portfolio review is the correct counter: it establishes that alternatives exist.
On the **vague "cost of service" arguments**, I've found it effective to reframe that refusal to provide detail as a shared business risk. In a recent renewal for a logging platform, we stated that without transparency into their cost drivers, we couldn't accurately model our own unit economics or forecast our consumption. This shifted the conversation from a pure price debate to one about partnership and predictable unit cost, which our FinOps team could engage with. They eventually provided a simplified cost model tied to their cloud provider regional pricing, which gave us the lever we needed to negotiate a capped increase based on that specific index, not a generic market rate. Their reluctance usually means the linkage is weak or the margin is higher than they want to admit.
Latency is a liability
That's a smart move with the 5% or CPI cap. I've seen that work, but you might find CPI itself becomes a point of contention. Vendors often argue it doesn't reflect their specific cost structure, like cloud region pricing or specialized labor. In our last negotiation, we settled on a hybrid: a hard cap of 5% *or* a specific, publicly available index for their primary cloud provider's price changes, whichever was lower. It gave them a cost-tied metric that was also transparent for us.
Your note about the "cost of service" pushback is key. When they refuse to detail it, you lose the ability to model your own growth. Framing it as a partnership issue - where both sides need predictable unit economics to plan - is the right angle. Have you considered asking for the cap to be coupled with a volume commitment on your end? Sometimes offering a multi-year commitment with defined growth tiers can make the cap more palatable for them, as it guarantees a baseline revenue stream.
api first
>given our annual spend is now in the mid-six figures
That's your leverage. Use it. The "industry standard" argument falls apart when you're spending that much. They need the deal more than you need to accept their boilerplate.
Your 5% or CPI cap is reasonable, but expect them to fight it. Push back harder on the "cost of service" vagueness. If they can't or won't open their books a little, they're asking for a blank check. Tell them you'll model your exit costs instead of your growth. That usually gets their attention.
Consider adding a right to terminate without penalty if increases exceed the cap. Makes your threat real.
slow pipelines make me cranky
Totally agree on using that spend as leverage. Mid-six figures means you're likely a top-tier customer for them, and they really don't want to lose the whole account over this clause.
One tactic I've seen work is to ask for the termination right, but frame it as a mutual "out" if their costs *truly* spike beyond the cap. It makes it feel less like a threat and more like shared risk management. If they balk, that tells you everything about how likely those "market rate" increases really are.
Also, be ready for them to counter with a higher cap, like 7-8%. Have your number, but know your walk-away number too. Good luck
ship it
Refuse to accept the "cost of service" line without detail. If it's their core justification, they should be able to model it.
I've forced this by requiring a shared spreadsheet model based on their primary cloud provider's pricing API. Their real cost driver is compute/storage, which has a public price trend. Tie your cap to that specific index, not CPI. If their costs jump 30% from AWS, you can have a real conversation. If not, they're bluffing.
Trust but verify, then don't trust.
That framing of the termination right as a "mutual out" is excellent. It turns a potential stalemate into a collaborative problem-solving discussion. I've used a similar approach by suggesting a *tiered* cap structure tied to verifiable events.
For example, we once negotiated a clause where the standard annual cap was 5%, but if their primary cloud provider announced a price increase above, say, 10% for their specific service SKUs, we'd agree to reopen the clause for that year only, with the requirement that they share the official provider notice. It protected them from true hyperinflation in their underlying costs, but prevented them from using vague "market rates" as a blanket excuse. It also built in the transparency everyone is asking for in this thread.
The right tool saves a thousand meetings.