When the Spreadsheet Stops Being the Answer: Five Signals

Before any talk of systems, one thing has to be said plainly: the file your company runs on today is the reason you got this far. When the company was small, a single sheet was faster than any system, cheaper than any subscription, and closer to how you actually think than any off-the-shelf screen. That was the right choice, and anyone who tells you otherwise has not built a company.

But tools have limits, and the spreadsheet is an excellent tool being used in many companies years past its own. The difficulty is that passing the limit does not happen on a known date and sets off no alarm; it leaks in slowly until the new situation becomes the normal one. So we open this series with the signals rather than the solutions: five specific ones, and if you recognise three of them in your company, you are no longer managing a file — you are managing an exposure.

Why the problem never arrives all at once

A sheet absorbs a great deal before it breaks. You add a column when you need a new piece of data, a tab when a new activity starts, a copy when a colleague needs to work on it at the same time. Every one of those steps is reasonable on its own, and the sum of them two years later is something nobody decided and nobody fully understands.

And because the failure is gradual, the team adapts to it instead of reporting it. People learn which copy is the right one, who to ask before editing, and which number not to rely on at month end. That unwritten knowledge is the cover that hides the problem — and it is itself the most dangerous signal, as you will see.

The five signals

Five signals say the file has passed its limit. They are not equally serious, but any three of them together is enough:

• Copies multiply under near-identical names. Final, then final-revised, then final-2-approved, then a copy named after whoever emailed it. One file has become a family of files, and every decision now rests on a guess: is this the latest version, or did someone edit a different one in parallel?
• One person knows how to update it. It holds formulas they wrote two years ago, links to other files on their machine, and hidden columns that exist for a reason only they know. They are hiding nothing, but the knowledge lives in their head rather than in a place anyone can consult. This is precisely the single point of failure in its organisational form rather than its technical one.
• The number changes depending on who you ask. Ask sales for the month's revenue and you get one figure; ask finance and you get another. Both are honest and both have a file that supports them. The gap is not about integrity — it is that each function pulls from a different source and calculates on a different rule, and there is no single reference that settles it.
• Nobody knows who changed what and when. You discover a cell has changed, or a row was deleted, or a price on the list is no longer what it was. There is no log saying who did it, when, or why, so the attempt ends either in blame without evidence or in quietly restoring the number by hand. The more dangerous possibility is that the change is never noticed at all.
• Work stops when the file owner travels. Leave, travel or illness, and invoices or reports or the order list are delayed because the file is on their machine or the method is in their head. When the continuity of a process depends on one person being present, you are looking at an organisational issue, not a personal one.

Notice that none of the five is an individual mistake. Nobody erred by making a copy so they could work, or by writing a clever formula that saved time, or by keeping the file on their own machine. The problem is that the tool has no layer that protects against these outcomes, because it was never designed to.

What these signals actually cost

The cost here never appears as its own line in the income statement, so it looks free. It is paid in three places:

• A decision made on an old number. Not necessarily a wrong number — a number that was true two weeks ago. You approve a purchase quantity, extend a quote or decline an order based on a position that has since changed and that nobody told you about, because telling you requires a person to notice and send an updated copy.
• Hours spent collecting rather than deciding. Before every monthly meeting somebody opens several files, copies from them, unifies the formats and fixes what does not reconcile. That is real, exhausting work, and it produces no value of its own, because all it achieves is arriving at the number that should already have been ready.
• Internal disagreement with nothing to settle it. The worst kind of disagreement is the one facts cannot end. When each side has a file that supports its account, the discussion shifts from a question of numbers to a question of trust between people — and that is far more expensive than whatever the variance was.

What actually changes when you move to a system

Not the looks, and not the screens. The substantive difference comes down to three simple things: one version everyone writes into instead of parallel copies, a log that says who changed what and when, and permissions so each person sees and edits only their part. None of the three can be bolted onto a file however tidily you organise it, because they are not a missing feature — they are a different nature of tool.

That does not mean every company needs a system today. A sheet used by one person for one purpose, with no shared decision resting on it, is a perfectly sound tool and there is no reason to replace it. The questions that mark the dividing line are covered in when you actually need a system and when you don't, and the practical rule is that the need begins when more than one person relies on the same number to make different decisions.

The Origami view

We are a technology company that builds systems for Saudi businesses, and we start any project of this kind by understanding the existing files rather than presenting a replacement for them. The reason is that the file a company runs on carries the real logic of the business, including every exception that was never written into any document, and ignoring it means building a system that resembles what ought to happen rather than what does.

The order we recommend: understand the current file and name its owner, then move what deserves moving after cleaning it, then run both in parallel for a declared period before closing the old one. That order is what the rest of this series follows, and it is how we approach our services, because a migration forced on a team all at once usually ends in a quiet return to the old file.

A five-minute exercise you can run today

You need neither a tool nor a consultant to locate yourself. Open the last file you made a decision on, and ask four questions:

• Who updated it last, and when? If you have to ask a person to find out, the file does not carry its own history.
• Where is the original? If the answer is in more than one place, or on someone's machine, you do not have a single source.
• Who can edit it right now? If everyone holding the link or a copy can change any cell in it, there are no permissions.
• If it were deleted today, how long to rebuild it? If the answer is days, or I don't know, then a company asset is being treated as a draft.

Do not try to fix anything after this exercise. Write your answers down and keep them, because the next part builds directly on them.

In the parts ahead

The signals are named; what remains is sequence. The next part starts by inventorying your files to answer one question: which of the dozens of sheets you hold is actually your system of record? Then we move to cleaning data before it travels, then to a migration order that keeps you trading, then to permissions and who sees what, then to the reports you used to build by hand every month — and we close the series with the first thirty days after the move and what usually breaks in them.

Sources

• Zakat, Tax and Customs Authority — e-invoicing requirements and the retention of tax documents.
• Saudi Data and Artificial Intelligence Authority (SDAIA) — the Personal Data Protection Law and the authority responsible for applying it.
• Ministry of Human Resources and Social Development — requirements for maintaining employee records and data.
• Ministry of Commerce — provisions covering commercial books and records for establishments.
• Saudi Vision 2030 — the national direction on raising operational efficiency and digital transformation in the private sector.