There is a sentence that quietly governs the IT budget of almost every large organisation: "We're not sure what happens if we touch that."
The tax nobody puts on the invoice
That uncertainty is a tax. It is paid in padded estimates, in change windows that stretch to absorb the unknown, in incidents traced back to a dependency nobody knew existed, and in modernization programmes that slip because the as-is picture was never trustworthy. None of it appears as a line item — but all of it is real, and all of it compounds.
Where the uncertainty comes from
- The people who wrote the system are retiring.
- The documentation, if any, drifted out of date long ago.
- The authoritative behaviour lives only in the source — and reading it by hand, at scale, is slow and error-prone.
Replacing archaeology with a query
The way to retire the sentence is to make the answer cheap to obtain. When the behaviour of a system is captured deterministically and made queryable, the question "what breaks if I change this?" stops being a research project and becomes a single query — answered in seconds, with every affected program, interface and dependency surfaced, and every hidden dependency flagged.
The compounding upside
When the truth about a system is cheap, everything downstream gets cheaper: maintenance, audits, migration, outsourcing transitions, and AI-assisted change. The organisations that win the next decade of modernization will be the ones that stopped paying the uncertainty tax — and started answering their two hardest questions with facts.