← Journal

Seven signs your company has outgrown what Excel can carry

7 min readLaurent Roy

Excel is a remarkable tool. It lets one person model in an afternoon what a developer would take three weeks to ship. Most companies owe it years of functioning, and deservedly so.

The problem is never Excel. It is the moment a file stops being one person's tool and becomes a team's infrastructure. That shift does not announce itself: there is no warning message, no limit reached, no invoice going up. You notice afterwards, while tracing where an error came from.

Here are seven signs. None is serious on its own. It is the accumulation that counts — and if you tick three, the limit is well behind you.

1. Nobody knows which version is authoritative

The file is called budget_2026_v3_FINAL.xlsx and there is another one called budget_2026_v3_FINAL_real.xlsx. Someone made a copy "so as not to break the original". Someone else corrected a row in the copy.

This is not a discipline problem. It is a mechanical consequence of the format: a file duplicates by nature, and nothing in the tool designates the reference copy. Discipline can delay the disorder; it cannot prevent it.

2. Your teams retype from one tool into another

Someone exports from accounting, pastes into a tab, reformats, then copies the result into a third file. Every week, the same gestures.

That time is easy to cost and nobody costs it. Take one person spending half a day a week on it: that is a month of work a year, spent entirely moving numbers that already exist somewhere else.

3. The file leaves the company

It goes out by email to a supplier, a customer, a contractor. From that point you no longer know who has it, what they do with it, or which version they are using to answer you.

A spreadsheet cannot tell one recipient from another. It sends everything, to everyone, permanently. If your file contains margins, negotiated terms or a third party's data, the problem is no longer organisational.

4. Answering "where are we?" means rebuilding a file

The question comes up in a meeting. The answer exists, but getting it takes two hours: consolidate three tabs, find the last export, check the totals add up.

Data that takes two hours of work to read is not available. It is archived.

5. The file does not know who you are

A field agent, a regional manager and a chief executive open the same file and see exactly the same thing. Either you are sharing too much, or you are sharing nothing and everyone works from their own stale extract.

This is probably the most structural limit, because there is no way around it. A spreadsheet has no notion of identity. Permissions do not exist in the format.

6. Only one person really knows how it works

There are formulas nested six levels deep, named ranges nobody documented, a macro written four years ago. It works. One person knows why.

That person takes a holiday. One day, they change jobs. The file keeps running right up until it needs to be changed — and at that point nobody knows where to touch it.

7. You have already decided on a wrong number

A cell was overwritten. A formula pointed at a deleted row and returned #REF!, but in a tab nobody opens. The total was three per cent out.

You did not know at the time. You found out afterwards, because a figure did not add up somewhere else. This is the most serious sign on the list: it means the system no longer protects you from its own errors.

What the seven signs have in common

Not one of them comes from carelessness. They are all side effects of the format: a spreadsheet is a file, and a file duplicates, travels, tells nobody apart and warns of nothing.

Moving to operational software is not buying Excel again at a higher price. It is changing three properties:

  • one set of data, in one place, with a history of who changed it;
  • permissions, so each person sees what concerns them and nothing else;
  • checks, so an implausible entry is refused rather than recorded in silence.

Where to start

Not with a large project. Take the process that hurts most — the one everybody names when you ask the question — and look at what it would cost to get that one, alone, out of the spreadsheet.

That is exactly what we do in a two-hour audit: map the real flows, spot what can be automated, and put a number on the time being lost. You keep the document, whether or not we work together.

The two-hour audit

We map your flows, and you keep the document.

Remote or on site. No commitment, and no automated follow-up.

Read next

Hire a developer or use a studio: the sum nobody does

People compare a salary with a day rate and conclude far too quickly. Here are the lines that sum leaves out — and the cases where hiring is still right.