We are three years away from selling, and our core operating software is outdated, but upgrading it will cost hundreds of thousands of dollars and consume significant team focus. How do we use a strategic real options framework to determine if we should pay this lump-sum cost now or let the buyer discount our purchase price?

Question

Tyler Smith · Accepted Answer

When deciding whether to upgrade outdated core operating systems before a sale, you can evaluate the decision using a strategic real options framework. This method helps you weigh the flow cost of waiting against the hidden, lump-sum cost of upgrading your systems now. If you wait, the flow cost includes operational inefficiencies, data silos, and a higher risk of customer churn, all of which drive up your capitalization rate. However, a major software implementation introduces significant execution risk. If the upgrade is unfinished or buggy when you go to market, buyers will use this operational friction to re-trade and discount your purchase price. The rule of thumb is timeline-dependent. If you have a three-year runway, complete the upgrade. It gives you eighteen months to implement the system and another eighteen months to prove its stability and efficiency. This timing allows you to present a fully systemized, low-risk platform to buyers. If your runway is less than eighteen months, do not start the upgrade. Instead, document the exact upgrade plan, obtain vendor quotes, and let the buyer handle the implementation, accepting a calculated, minor discount rather than risking a failed migration during due diligence.