The Spreadsheet Ceiling: What Wigan Manufacturers Get Wrong About Replacing Excel

There is a specific conversation we have with Wigan businesses more than any other. It usually happens in a portacabin office on an industrial estate off Martland Park or Robin Park, and it starts like this:

"We've got a spreadsheet that runs the whole operation. Only Dave really understands it. Dave's retiring in eighteen months."

The spreadsheet is never really the problem. The problem is that a business has quietly become dependent on a system nobody designed, nobody documented, and one person maintains in their head. That is a genuine operational risk, and it is extremely common across the borough's warehousing, distribution and manufacturing base.

But the answer is not automatically "replace it with custom software". Sometimes it is. Often it is not, or not yet. Here is how we tell the difference, and what it actually costs when the answer is yes.

First: spreadsheets are not the enemy

There is a certain kind of software salesperson who treats Excel as a disease to be eradicated. Ignore them.

Spreadsheets are the most successful business software ever written. They are flexible, immediate, and every person you hire already knows how to use them. A business running on a well-organised spreadsheet is not a business doing something wrong. It is usually a business that solved a real problem quickly and cheaply, which is exactly what you want.

The question is never "should we still be using spreadsheets". It is "has this particular spreadsheet stopped paying for itself".

The five signs you've hit the ceiling

In our experience these are the signals that actually matter. Not one of them on its own, but three or more together means the spreadsheet is now costing more than it saves.

1. Two people cannot use it at once

This is the clearest one. If your team has a rule like "don't open the stock sheet while Sarah's doing the Monday count", you are paying for that rule in lost time every single week. Shared network drives and even cloud-hosted Excel handle concurrent editing badly the moment formulas and lookups are involved.

2. Somebody re-types data that already exists

Orders arriving by email and being typed into a sheet. The sheet being re-typed into the accounts package. Delivery notes typed a third time. Every re-keying is a chance to introduce an error, and every error surfaces weeks later as a stock discrepancy or a wrong invoice.

We find most Wigan operations of 10 to 50 people have between two and four of these re-keying steps running daily. That is usually the single biggest recoverable cost in the whole business, and it is often the cheapest thing to fix.

3. The version history is a folder full of final_v3_USE_THIS.xlsx

If you cannot answer "what did this look like last Tuesday, and who changed it", you have no audit trail. That is an annoyance right up until the day it becomes a compliance problem, a customer dispute, or an insurance claim.

4. One person is the system

The Dave problem. If a single person's departure or illness would stop the operation, the risk is no longer theoretical. This is the reason most of our Wigan enquiries actually arrive, and it usually surfaces about a year before it becomes urgent — which, fortunately, is roughly the right amount of lead time.

5. You've stopped asking questions because the answer is too hard to get

This one is subtle and it is the most expensive. When getting a number out of the spreadsheet takes 40 minutes, people stop asking for numbers. Decisions start getting made on instinct, not because instinct is preferred but because the data is impractical to retrieve. A business that has stopped measuring things it used to measure has usually hit the ceiling without noticing.

What Wigan businesses get wrong about the fix

Mistake 1: Trying to replace the whole spreadsheet

The spreadsheet has been growing for eleven years. It has forty tabs. Thirty-two of them are dead, six are lightly used, and two are the business.

The instinct is to specify a system that does everything the spreadsheet currently does. This is how you turn a £12,000 project into a £60,000 project that takes nine months and gets abandoned. Replicating dead functionality is pure cost with no return.

Find the two tabs that matter. Build those properly. Leave the rest in Excel for now — and in most cases, forever. Nobody will miss them.

Mistake 2: Assuming it has to be all-or-nothing

You do not have to choose between "spreadsheet" and "full ERP system". The most cost-effective work we do in Wigan sits between the two: a small system that owns the one workflow that genuinely needs structure — stock movements, job costing, quotes — while everything else carries on as it is.

Newtown Gates is a good example of the shape. Rather than replacing how the business ran, we built an automated estimating and quotation system for the specific job of valuing work accurately and keeping control of materials and labour pricing. One workflow, done properly. Everything else stayed where it was.

Mistake 3: Buying software that fits somebody else's process

Off-the-shelf products are excellent when your process is standard. Payroll is standard. Accounts are standard. Use Xero, use Sage, do not build those.

But the reason a business ends up with an elaborate custom spreadsheet in the first place is almost always that its process is not standard — some quirk of how it quotes, schedules, or tracks that does not match what any product assumes. Buying a product then means changing how the business works to fit the software, which for a profitable operation is often a genuinely bad trade.

The honest test: if your spreadsheet is complicated because your business is genuinely unusual, custom is probably right. If it is complicated because it grew organically and nobody ever tidied it, a product might do fine.

Mistake 4: Not counting the cost of doing nothing

"We can't justify £15,000 for software" is a reasonable sentence. But it is only half a calculation.

Two people spending an hour a day each on re-keying and reconciliation, at a fully-loaded cost of around £20 an hour, is roughly £10,000 a year, every year, forever. Against that, a system that removes most of it pays for itself inside eighteen months and then keeps paying. That is before counting the errors it prevents or the Dave risk it removes.

Run the number honestly in both directions. Sometimes it still says don't do it — and that is a legitimate answer.

When we tell Wigan businesses not to build anything

We turn down or defer this work fairly often. The usual reasons:

• The process is about to change anyway. Building software around a workflow you are mid-way through rethinking wastes the build.
• The spreadsheet is fine and the real problem is training. Two people who both know how it works removes most of the Dave risk for the cost of an afternoon.
• The volume does not justify it. Automating something that happens four times a month rarely repays a build.
• An off-the-shelf product genuinely fits. If Unleashed or Katana does what you need, use it. We will say so.

A supplier who never talks you out of anything is not being straight with you.

What it actually costs in Wigan

Rough, honest bands, based on what we quote locally:

| Scope | Typical cost | Timeline | |---|---|---| | Automating one repetitive workflow (email-to-job, supplier ordering, document generation) | £1,500 – £4,000 | 1–2 weeks | | One workflow replaced properly (stock, quoting, job costing) with a proper interface and audit trail | £8,000 – £15,000 | 6–10 weeks | | Multi-workflow internal system replacing most of the spreadsheet estate | £25,000 – £60,000 | 3–6 months, phased |

Being based in Shevington rather than Manchester or Liverpool matters here mainly because in-person time is cheap for us. A discovery visit to Hindley, Leigh or Standish costs us a 20-minute drive instead of a chargeable half-day, so we can afford to scope properly before quoting rather than guessing from a phone call.

Where to start

If three or more of the five signs above sound familiar, the first step is not a specification document. It is an afternoon watching how the work actually happens.

Almost every time, the thing that turns out to be worth building is not the thing the business initially asked for. The stock system they wanted is less valuable than the automated supplier ordering nobody mentioned because they had stopped noticing it was manual.

Start by writing down every point in the week where somebody types information that already exists somewhere else. That list is your project, in priority order, and you can produce it without talking to a software company at all.

---

Zim Digital are software developers in Wigan, building bespoke software for businesses across the borough — warehousing, distribution, manufacturing, healthcare and professional services. If you want an honest read on whether your spreadsheet has hit the ceiling, get in touch — the first conversation is free and we will tell you if the answer is to do nothing.