When a spreadsheet quietly becomes a system

Spreadsheets are excellent tools. That is the problem.

They are so good at the first version of a job that they end up doing the tenth version too. A tab gets added. A lookup gets added. Somebody writes a macro. Two years later the weekly plan, the prices, the customer codes and the dispatch order all live in one workbook, and the business would genuinely struggle if it was lost on a Friday afternoon.

Four signs it has crossed the line

One person is the manual. If a specific employee has to be available for the week to run properly, that is not a tool any more. That is a dependency.

It has stopped being trusted. People check the numbers again somewhere else before they act on them. That double checking is a cost and it never appears on a report.

Changes have become frightening. When nobody wants to touch the formulas because something might silently break, the spreadsheet is now in charge of you.

Its output is somebody's job. If a person spends part of every week turning the workbook into invoices, labels, orders or a report, that time is the real price of keeping it.

What we do not do

We do not walk in and recommend a new system. The first job is understanding what the spreadsheet is actually holding, because a good workbook usually encodes real operational knowledge that nobody has written down anywhere else. That knowledge is the valuable part. The file is not.

Sometimes the right answer is smaller than a build. Occasionally the existing software can do the job once it is configured properly. Sometimes the process itself is the thing to simplify.

What replacing it usually involves

The pattern that works is a first release that covers one real part of the week, in use quickly, rather than a long build that arrives complete and wrong. The rules the spreadsheet holds get made explicit. The steps that only existed because of the tool get dropped. The output the business actually needs comes out of the system rather than out of a person.

A worked example

Keystone started this way. An Irish farmhouse cheese producer was running weekly order planning on a large Excel workbook with macros, with dispatch and traceability information sitting around it. The process itself was sound. What was missing was somewhere for it to live. We followed the operation first, then built around it.

If a spreadsheet in your business has become something you cannot afford to lose, that is usually the moment to act, and it is worth an hour of conversation before anybody talks about software.