How to measure what you’re actually paying for staying — and how to stop paying more
By Steele Consulting
Every CFO at a growing company has had this exact meeting. It’s annual renewal season for a core vendor — a CRM, an ERP, a data platform, a payment processor. The quote comes in. The price has gone up 25%, or 40%, or sometimes more. Somebody asks the question everybody is thinking: “Can we leave?”
And somebody else answers, with less confidence than they’d like: “We’re already on their platform. We don’t really have a choice.”
That sentence — “we don’t really have a choice” — is the sound of a lock-in tax arriving. The money you pay above what a competitive market would charge isn’t a renewal increase. It’s the tax a vendor collects when they know you can’t leave.
In our 24 years at Steele Consulting building custom software and advising growing businesses on their vendor relationships, we’ve watched this exact pattern play out hundreds of times. The lock-in tax is almost always invisible on the way in — nobody signs a vendor contract thinking “we’ll never be able to leave this.” It becomes visible at the second or third renewal, when the vendor has quietly realized you can’t.
This post is about the five forms the tax takes, how to measure how much you’re paying today, and how to design new vendor relationships to pay less of it tomorrow.
Why the tax is hidden
Three structural reasons the lock-in tax stays invisible until it’s expensive:
- It doesn’t appear on an invoice. You pay the renewal price. You don’t see a line item called “lock-in surcharge.” The tax is embedded in the increase.
- The alternative cost is theoretical. You can’t easily see what you’d pay in a free market because you’re not in one. Vendors know this. Their pricing team definitely does.
- The switching cost is cumulative. You accumulated lock-in one small decision at a time — a plugin here, an integration there, a workflow shaped by the tool. No single decision looks expensive. The sum of them does.
The tax reveals itself in specific moments. Price increases that outpace inflation and your business growth. New feature pricing structures that make previously-included things cost extra. Terms that quietly got worse at your last renewal. Vendors adding “value-based pricing” components that align with your revenue. All of these are tax events — the vendor collecting on their knowledge that leaving is harder than paying.
The 5 forms of lock-in
Vendor lock-in isn’t one thing. It’s five different kinds of entanglement that compound into the overall tax.
1. Data lock-in
Your data lives in their system, in their format, often in their proprietary data model. Getting it out is possible, but it requires engineering effort — sometimes substantial — and the exported data arrives in a shape that needs to be re-mapped to work anywhere else. For some vendors, “export” delivers you a CSV that doesn’t actually represent the full structure of what you had.
The cost: when the vendor raises prices, extracting and migrating your data could take 3–6 months of engineering effort — enough that the price increase stays cheaper.
2. Integration lock-in
Other systems in your business depend on this vendor. Your CRM has webhooks to it. Your accounting system pulls from it. Your custom tools authenticate through it. Moving the vendor doesn’t just mean moving one thing — it means rebuilding every integration that touches it.
The cost: multiplied by the number of integrations, this is often the single largest form of lock-in for a growing business. We wrote about one specific symptom of this in What to Do When Two Reports Say Different Things — those reconciliation gaps are usually built on top of integration lock-in.
3. Workflow lock-in
Your team has shaped their processes around the tool. The sales workflow matches the CRM’s stages. The finance close matches the accounting system’s reporting cycle. Switching the tool means retraining the team, rebuilding playbooks, and absorbing a productivity hit for a quarter.
The cost: real but underestimated. The retraining and productivity hit on 50 people switching tools is usually larger than the one-time software migration cost.
4. Contract lock-in
The formal, legal version. Multi-year commitments. Early termination fees. Automatic renewal clauses. Volume discounts that lock pricing to minimum commits you’ll be penalized for not meeting. Change-of-control clauses that trigger renegotiation on sale.
The cost: this is the only form of lock-in that’s visible in the contract itself — which means it’s the only one most buyers negotiate. The irony is that the other four forms are usually larger.
5. Platform lock-in
You built on their proprietary APIs, features, or extensions. Your custom work only runs on their platform. Portable alternatives would require rewriting. This is lock-in that your own engineering team created — usually in good faith, following the vendor’s documentation.
The cost: the most expensive form of lock-in when it’s present, because moving requires rebuilding software you’ve already paid to build once.
How to measure your current lock-in exposure
A simple audit any CFO can run with the IT or ops leader, in about four hours total, across your top five vendors by spend.
For each vendor, ask three questions and score 1–5 (where 1 = easy to leave, 5 = effectively impossible):
- If this vendor doubled their price tomorrow, how long would it take us to switch? (Measures the real cost of leaving.)
- What percentage of our business workflow would need to change if we left? (Measures workflow lock-in.)
- Do we own our data in a form a replacement vendor could use directly? (Measures data lock-in.)
Add the three scores. Any vendor scoring over 9 is high-exposure lock-in — they can raise prices meaningfully at renewal and you’ll pay it. Any vendor scoring over 12 is critical exposure — they can raise prices substantially and you have no real leverage.
Most growing businesses discover two or three critical-exposure vendors they didn’t know they had. Those are where the lock-in tax lives.
How to design new vendor relationships to reduce future exposure
The best time to reduce lock-in is before you sign. Four moves that help:
- Negotiate data portability into the contract. Explicit terms about export format, frequency, completeness, and your ongoing right to extract. If the vendor won’t contract to it, that’s a signal.
- Prefer standard interfaces. Pick vendors who use widely-supported APIs and data formats over those who use proprietary ones. Lock-in is lower when alternatives speak the same language.
- Cap the contract term. Three-year deals get better pricing. One-year deals get better leverage at renewal. Pick based on which matters more for this specific vendor.
- Avoid building on proprietary platform features when a standard would do. Platform lock-in is usually self-inflicted. If a vendor’s standard API would work for your use case, don’t use their proprietary extension just because it’s slightly nicer.
When lock-in is actually fine
Not every vendor relationship needs to be portable. Some lock-in is a reasonable price to pay for depth of integration, ecosystem benefits, or specialized capability.
Lock-in is fine when: the vendor is foundational and the business is unlikely to need to leave; the alternative options are worse enough that the lock-in cost is dominated by the capability gain; and the vendor has a track record of good-faith pricing that doesn’t exploit the lock-in relationship.
Lock-in is a problem when: the vendor has started treating renewals as a profit center; the alternatives have caught up or passed the incumbent; or your business has evolved to where the vendor’s constraints are now the binding constraint on your growth.
The audit above tells you where you are on this spectrum for each vendor. The decision — accept the tax, negotiate it down, or plan an exit — follows from the diagnosis.
How this connects to the other decisions you’re making
Vendor lock-in sits downstream of several patterns we’ve written about. The Bend option in Build, Buy, or Bend accumulates lock-in — every workaround and plugin deepens the entanglement. The 47 Software Tools SaaS audit is where you find out which vendors you’re locked into without realizing. The DRIFT framework’s Friction Cost usually hides significant integration lock-in. Read in sequence, the posts give you a complete view of where vendor tax exposure sits in your business.
Book a call
Twenty-four years of building custom software. Both sides of the table on more decisions than we can count. And a track record of telling clients honestly when the answer is us and when it isn’t.
If you’re sitting in the middle of this decision right now, that’s the conversation we’re built for. Book a 30-minute call and we’ll walk through it with your specific situation. No pitch. No pressure. You’ll leave with a clearer picture of what to do — whether you work with us or not.