Almost every growing business has one. It started as a convenience — a quick way to track a handful of jobs, or orders, or stock levels — and it worked beautifully, which is exactly how it became load-bearing. Years later it holds pricing logic, customer history, and formulas nobody remembers writing. Sometimes only one person truly understands it, and everybody works around the parts they are afraid to touch.
The risk is not that spreadsheets are bad tools. They are outstanding tools, and their flexibility is why they spread. The risk is the mismatch between what the file has become and the protections it has. A system this important would normally have access controls, an audit trail, backups, validation on entry, and a defined owner. A shared file usually has none of these. One accidental sort, one overwritten column, one person on vacation, and an operational process stops.
There is a slower failure mode as well. Because a spreadsheet cannot easily be used by several people at once, teams create copies. Copies drift. Within months the sales figure in one file disagrees with the figure in another, and meetings start with a debate about which number is real rather than what to do about it. The organization loses confidence in its own data, and decisions get slower and more instinct-driven at precisely the moment the business is becoming too complex for instinct alone.
The fix is rarely to delete the spreadsheet. It is to identify what the file is actually doing and move only that part into a proper system, keeping the parts spreadsheets are genuinely good at. Shared, validated data with a history of who changed what belongs in an application. Ad hoc analysis and one-off modeling can stay exactly where they are, and are usually better for it.
A reasonable first step costs nothing: find the file the business could least afford to lose, and ask three questions. Who owns it? What happens if it is corrupted tomorrow? How would we know if a number in it were wrong? If the answers are uncomfortable, you have found the process most worth systemizing first.