The Renewal Shakedown: How SaaS Companies Double Your Bill

Every SaaS vendor runs the same playbook. It's not a conspiracy — it's just what happens when you combine per-seat pricing, indefinite renewal clauses, and an MSA drafted by a lawyer who got paid for it.

The four-year curve

Year one: Discounted entry. "Let's get you started at 30% off the list rate so we can prove value." You sign a 12-month contract.

Year two: Renewal at list. The "discount" evaporates — plus an "annual index adjustment" of 8–12%. You're now paying 1.5x what you paid last year for the same thing.

Year three: List + inflation + a new required tier. They "consolidated the product line"; your plan is now legacy. The migration path is to the Enterprise tier at 1.8x. You negotiate to 1.4x.

Year four: You're paying 2.1x what you paid in year one. You've added three integrations, trained 60 people, and connected it to six other systems. You won't leave; they know it.

Why the playbook works

Because switching costs are huge and non-obvious. Migration is 3–6 months, costs tens of thousands in migration services, and breaks every integration in your stack. Even when the renewal ask is unfair, it's cheaper than leaving.

This is the definition of vendor power: the software is worse than the alternative, but the cost to act on that knowledge is too high.

How to refuse the shakedown

You cannot refuse a shakedown while paying rent. You have to own the building. In software terms: you have to move to a model where the vendor's leverage evaporates.

• Own the code. If you can hire any developer to maintain it, your vendor can't extort a renewal.
• Flat monthly. A fee that doesn't grow with headcount kills the per-seat inflation vector.
• No switching cost. When you own the git repo, you can always switch who builds without switching what runs.

When your renewal conversation is "we'd like to continue the current arrangement at the current price" and the vendor has no leverage to respond — you've exited the playbook.