Usage and need
Who uses the capability, how much, which features matter, and what can be reduced without degrading the outcome.
How we negotiate
Evidence strengthens the ask.
We compare pricing and terms where reliable sources exist, account for the renewal window, test usage and capability, and build an alternative only when you would genuinely consider it.
Current evidence shapes the ask. Contract structure, timing, usage, market context, and your actual alternatives all matter.
What supports the ask
Three inputs shape the negotiation.
Terms and timing
Renewal date, notice window, seat floors, ramp, overages, support tier, price protections, and commitment structure.
Credible alternatives
Consolidation, an owned capability, a smaller product, or a replacement candidate you would genuinely consider.
Client control
You set the boundary.
- You approve any binding commercial change.
- We use credible alternatives, never a fabricated competitive process.
- Recommendations carry no vendor referral fee or reseller commission.
- We count operating and migration cost before calling a replacement a saving.
- Sometimes Keep is the right answer.
AI-tied renewals
Evidence still comes first. The asks change.
Usage, terms, and a credible alternative still shape the ask. When the uplift is an AI SKU, metered credits, or an outcome fee, add the AI-specific moves on the AI tax at SaaS renewals playbook: an AI-free SKU in writing, a separable premium, and a hard credit cap.
Agent vs review
Negotiation capacity is not the same as a portfolio decision.
This page is how a Renegotiate ask is built. If the live question is whether to adopt an AI negotiation agent or hire an independent Keep/Cut/Renegotiate/Replace review, use the agent vs independent review decision instead of stretching this playbook into a software buy.
Evidence without a platform
Peer pricing is an input, not a dataset you have to buy.
This page is where evidence fits in the ask. If the live question is how to get usable SaaS pricing or renewal evidence without buying Tropic, Vendr/Vertice, or Zip, use SaaS pricing benchmarks without a platform instead of stretching this playbook into a product buy.
Seat reduction
Rightsizing seats is a specific ask, not the whole method.
Usage, terms, and a credible alternative still shape the ask. When the money question is cutting seats at renewal on true-up-only paper, add the true-down and rightsizing moves on the true-up vs true-down playbook instead of stretching this page into a seat-reconciliation tutorial.
Usage evidence without an SMP
Unused-seat proof is a pack you assemble, not a dashboard you have to buy.
This page is where evidence fits in the ask. If the live question is how to assemble unused-seat and rightsizing proof from invoices, SSO, and admin exports without buying Torii, Zylo, or CloudEagle first, use renewal usage evidence without a platform instead of stretching this playbook into a discovery-product buy.
AI minimum commitment
The commit line is a specific ask, not the whole method.
Usage, terms, and a credible alternative still shape the ask. When the money question is sizing or refusing an AI minimum commitment, unused-credit rollover, or breakage, add the floor and ceiling moves on the AI SaaS minimum commitments playbook instead of stretching this page into a commit-line tutorial.
Packaging and successor SKUs
Cap survival is a specific ask, not the whole method.
Usage, terms, and a credible alternative still shape the ask. When the vendor retires a tier, renames a SKU, or quotes a successor package that would reset a price cap, add successor-SKU and packaging-neutral language from the forced SKU migration playbook instead of stretching this page into a packaging tutorial.
Annual increase ceiling
Locking the rate cap is a specific ask, not the whole method.
Usage, terms, and a credible alternative still shape the ask. When the fight is an uncapped or ambiguous renewal increase, add formula choice and drafting-trap moves from the price uplift / escalation caps playbook instead of stretching this page into a ceiling tutorial.
Notice of non-renewal
Valid notice is a send-and-proof job, not the whole method.
Usage, terms, and a credible alternative still shape the ask. When the live question is how to find the notice deadline, send a clause-cited letter that keeps renegotiation open, and keep proof of receipt, use the SaaS notice of non-renewal playbook instead of stretching this page into a letter tutorial.