Most decisions a CEO makes are reversible, and the good ones treat them that way. You try a vendor, a market, a pricing change, a hire, and if it does not work you unwind it at a cost you can live with. The reversibility is what lets you move fast. When the downside of being wrong is "we change it back," you should decide quickly, because deliberating at length over a choice you can cheaply undo is just expensive caution.

A small number of decisions do not have this property. They are the ones where being wrong is not a matter of changing it back, because changing it back has become prohibitively expensive by the time you would want to. Your core operating and financial platform, the system your company actually runs on, is one of these, and treating it like the reversible kind is one of the more costly category errors a CEO can make.

Reversibility is the property that should decide how you decide

The reason this matters is not that platform decisions are important. Plenty of important decisions are also easy to reverse, and you can afford to make those quickly and correct course later. The reason platform decisions demand a different kind of attention is that their reversibility decays over time, and it decays in one direction only. Every year you run on a system, leaving it gets harder, never easier.

That single asymmetry should change how the decision gets made. A choice you can walk back cheaply can be evaluated on this quarter's price and this year's feature list, because if you are wrong, you correct it. A choice that becomes more expensive to reverse every year cannot be evaluated that way, because the thing you are really deciding is not "which system serves us best now" but "which system are we willing to be unable to leave in five years." Those are different questions, and the second one is the one that actually binds. A platform that wins on price today and traps you tomorrow is not a good deal. It is a deferred bill.

Why leaving gets harder every year

It is worth being concrete about what accumulates, because the growing switching cost is not abstract. It is made of specific things that pile up whether or not anyone is watching.

Data accumulates. Every month adds history, and history is both the hardest thing to migrate and the thing you can least afford to lose or corrupt. Migrating a platform is, at its core, a data migration, and the data is reliably the part that turns a clean plan into a multi-month or multi-year effort. The failure statistics here are sobering and consistent: Gartner has been cited putting the share of data migration projects that fail outright or significantly overrun their budgets and timelines at around 83%, and Bloor Research has independently placed the failure-or-overrun rate near 75%, with average schedule slippage over 40%. This is why serious migrations are run with rollback plans in hand, because failure is common enough to plan for rather than hope against.

Customization accumulates. The configurations, the fields, the reports, the workflows you built to fit your operation are also the things a new system will not replicate without effort. The better a system is molded to how you work, the more of that molding you would have to redo elsewhere. This is one reason customization discipline and reversibility are linked: the more deeply you tailor a platform, the more expensive it becomes to ever leave, a connection explored in the companion piece on the customization trap.

Habit accumulates. Your people learn the system. Their daily competence is built on top of it, and moving platforms means moving all of that competence too, through a period where experienced people are temporarily slow and error-prone in the tool they use all day.

And dependency accumulates. Other systems get wired to this one. Integrations, reports, downstream tools, and outside parties all come to assume its presence, so leaving it means unpicking not one system but a web that grew around it. Each of these grows every year, and together they are why the door you walked through easily becomes one you can barely fit back through later.

Property compounds all of it

This gets heavier faster in a property company, for the same reason so many of these questions do: the entities and the history multiply. A property operator does not just accumulate more transactions on one set of books. It accumulates more entities, each with its own history, its own structure, its own accumulated data and customization, often added through acquisition. The switching cost is not rising along one line. It is rising along many at once, which means the window in which the platform decision is still cheaply reversible closes earlier for an acquisitive property company than the unit count alone would suggest.

The honest tension: you will be locked into something

Here is where this argument has to be careful, because the easy version of it is wrong. The lesson is not "avoid lock-in," because lock-in is not avoidable. Any platform you commit to deeply enough to get value from is a platform you become dependent on. Deep commitment and switching cost are the same thing viewed from two angles, so a system you could leave effortlessly is usually one you never really relied on. Refusing to commit in order to stay flexible is its own failure, the kind that leaves a company running shallow, disconnected tools it never trusted enough to build on.

So the real question is not how to stay free. It is which dependency you would least regret. You are going to be locked into something. The discipline is to choose the platform you would still be glad to be committed to in five years, under conditions you cannot fully predict now, rather than the one that merely looked cheapest or most impressive at the moment of signing. Choose the lock-in you can live with, deliberately, instead of backing into one you did not examine.

What this asks of a CEO

Practically, this means the platform decision deserves a different evaluation than most vendor decisions get, and specifically a longer time horizon. Not "does this win the demo and the price comparison," but "if we are wrong about this, how bad and how expensive is that in year three, and can we live with the answer." A useful test is to ask, before signing, what leaving this system would cost you three years from now, and whether that future exit cost is one you are comfortable handing to your later self. If the honest answer is that leaving would be ruinous and you have not thought hard about whether you would ever want to, you are making a low-reversibility decision with high-reversibility casualness, which is the exact mismatch this whole argument is about.

None of this is a reason for paralysis. It is a reason for proportion. Make your reversible decisions quickly and your irreversible ones deliberately, and know at all times which kind you are making. The platform your company runs on is the irreversible kind, getting more so every year you wait to take it seriously. Decide it like what it is.

FAQs

Q1. Isn't every software decision reversible if you're willing to spend enough?
Technically yes, and that is exactly the point. The question is never whether you can leave a platform, but at what cost, and for a core system that cost rises every year until it becomes large enough to change your behavior. A decision that is reversible only at ruinous expense is, for practical purposes, one you make once.

Q2. Doesn't this argument just favor whichever platform is biggest or most established?
No. It favors whichever platform you would be most comfortable being committed to over a long horizon, which is not always the biggest one. The argument is about matching the evaluation to the reversibility of the decision, not about defaulting to scale. A smaller platform you would happily still be on in five years can be the better low-regret choice.

Q3. If lock-in is unavoidable, why does the choice matter so much?
Because being locked into a platform that continues to serve you well is entirely different from being locked into one you have outgrown or come to distrust. The inevitability of dependency raises the stakes on choosing well rather than lowering them. You cannot avoid the commitment, so the quality of what you commit to is the whole game.

Q4. How do I evaluate a platform on a five-year horizon when I can't predict five years out?
You cannot predict the specifics, but you can ask which platform gives you the most room to be wrong about them: which one adapts across a range of futures rather than only the one you are planning for today. Judging on flexibility under uncertainty, rather than fit to a single forecast, is how you make a durable choice without a crystal ball.

Q5. Why is this worse for property companies specifically?
Because property operators accumulate not just transaction history but entities, often through acquisition, and each entity brings its own data, structure, and customization. The switching cost therefore rises along several dimensions at once, so the point at which changing platforms becomes prohibitively expensive arrives sooner than the raw size of the business would imply.

Q6. Doesn't waiting to decide carefully just delay value we could be getting now?
There is a real cost to deliberation, which is why reversible decisions should be made fast. The argument here is narrower: the platform decision is not the reversible kind, so the usual bias toward speed does not apply to it. Careful is the correct speed for a decision that gets more expensive to undo every year.

Q7. What if we already made this decision and suspect it was wrong?
Then the reversibility clock is the thing to think about honestly. Switching cost only grows, so if a change is truly warranted, the cheapest time to make it is always now rather than later, weighed against the disruption of the move itself. The worst outcome is drifting for years on a platform you have already concluded is wrong, letting the exit cost compound while you avoid the decision.

Q8. Is this an argument against ever switching platforms?
Not at all. It is an argument for switching deliberately and rarely, with a clear view of the cost, rather than either churning through systems casually or clinging to a bad one out of inertia. The goal is to make the irreversible decision consciously and infrequently, and to make it well the small number of times you make it.