Why Your Business Keeps Rebuilding the Same Spreadsheet (And What to Do About It)

Published on 21 May 2026 by New Media Aid — bespoke SME app development since the year 2000

Spreadsheets Business Process Automation Workforce Planning Workflow Management Operational Software Bespoke Software Development SME Systems Resource Scheduling Digital Transformation Web Applications


Most business-critical spreadsheets don't start out that way.

They are usually created by someone trying to solve a practical problem. Perhaps it's a job schedule, a vehicle planner, an inspection register, a stock tracker or a reporting workbook. The spreadsheet works well enough, so it grows. New columns are added. New tabs appear. Extra formulas get bolted on.

Eventually, what began as a quick fix becomes one of the most important systems in the organisation.

We've seen this pattern repeatedly across industries including construction, scaffolding, facilities management, manufacturing, logistics and professional services.

The problem isn't that spreadsheets are bad. The problem is that they often end up doing jobs they were never designed to do.

How the spreadsheet starts

The original spreadsheet is usually sensible.

Perhaps somebody needed a simple way to schedule staff, track jobs or monitor costs. Creating a spreadsheet was faster than buying software and required no approval process or technical expertise.

Initially the benefits are obvious:

  • Fast to create
  • Easy to modify
  • Low cost
  • Familiar to everyone
  • No specialist software required

For small teams and straightforward processes, spreadsheets can be extremely effective.

The trouble begins when the business grows but the spreadsheet remains the same.

The spreadsheet becomes a system

At some point, the spreadsheet stops being a document and starts becoming software.

You begin seeing things like:

  • Multiple worksheets linked together
  • Complex formulas nobody fully understands
  • Macros and automation scripts
  • Manual imports and exports
  • Conditional formatting used as workflow rules
  • Several staff updating the same workbook
  • Different versions emailed around the business

In effect, the spreadsheet becomes a custom application — except without the safeguards, controls and maintainability normally associated with software development.

The hidden costs of spreadsheet dependency

Many organisations underestimate the true cost of relying on complex spreadsheets.

Duplicate data entry

Information often needs to be copied between spreadsheets, accounting systems, CRM systems and operational records. The same data may be entered multiple times by different members of staff.

Reporting delays

Generating management reports frequently involves manually combining information from multiple sources. Reporting becomes slower as the business grows.

Human error

Incorrect formulas, accidental overwrites and version confusion can introduce errors that are difficult to identify.

Knowledge concentration

Often a single employee becomes the person who understands how the spreadsheet works. If they leave, take holiday or change role, the business suddenly discovers how dependent it has become.

Limited visibility

Management frequently lacks a real-time view of operations because data is spread across multiple files and locations.

Why businesses keep rebuilding the same spreadsheet

One interesting pattern is that businesses rarely create a spreadsheet once.

Instead, they repeatedly rebuild it.

Typically this happens because:

  • The original workbook becomes too large
  • New operational requirements emerge
  • Processes change over time
  • Performance becomes poor
  • Users lose confidence in the data
  • Different departments need different views of information

Eventually somebody creates a "new version" to fix the problems. Then another version appears a year later. Then another.

The underlying process never improves because the organisation continues treating a software problem as a spreadsheet problem.

A real example: workforce planning

One recent example involved a scaffolding contractor using spreadsheets to manage daily workforce planning.

Operations managers needed to allocate scaffolders, vehicles and site work every day while tracking workload, team composition and operational requirements.

As the business expanded, the spreadsheets became increasingly difficult to maintain and update.

We ultimately replaced the spreadsheet process with a bespoke drag-and-drop planning system that allows managers to:

  • Assign scaffolders to teams visually
  • Allocate vehicles and resources
  • Schedule installation, strike and repair work
  • Generate daily work packs automatically
  • Track labour allocation centrally
  • Support payroll and operational reporting

Rather than creating another spreadsheet, the business now has a planning system designed specifically around its operational workflow.

Read the full workforce planning case study.

Why off-the-shelf software doesn't always solve the problem

Businesses often assume the next step after spreadsheets is buying generic software.

Sometimes that's absolutely the right decision. However, organisations with specialised processes frequently discover that off-the-shelf systems only solve part of the problem.

Common issues include:

  • Processes that don't match how the business operates
  • Missing industry-specific functionality
  • Additional spreadsheets still required for exceptions
  • Poor integration with existing systems
  • Complex workarounds and manual processes

In many cases the spreadsheet survives because the software cannot accommodate every operational requirement.

We discuss this challenge in more detail in our guide to why off-the-shelf SaaS breaks down for niche workflows.

When a bespoke web application becomes worthwhile

Not every spreadsheet should become a bespoke application.

However, if a spreadsheet is:

  • Business critical
  • Used by multiple staff members
  • Maintained daily
  • Generating reporting headaches
  • Driving operational decisions
  • Being repeatedly rebuilt or extended

Then it may be worth considering a dedicated system.

A bespoke web application can centralise data, automate repetitive tasks, improve reporting and provide a much better user experience while supporting the way the business already works.

You may also find our guide on replacing spreadsheets with a web application helpful.

The goal isn't to eliminate spreadsheets

It's worth emphasising that spreadsheets still have an important role.

They remain excellent tools for analysis, modelling, ad-hoc reporting and one-off calculations.

The objective isn't to remove spreadsheets entirely. The objective is to stop using them as mission-critical operational systems when more suitable alternatives exist.

The right spreadsheet in the right place can be extremely valuable. Problems arise when spreadsheets become the foundation of core business processes.

Final thoughts

If your organisation finds itself rebuilding the same spreadsheet every few years, that's often a sign that the underlying process has outgrown the tool being used to manage it.

The solution may not be another spreadsheet. It may be a system designed specifically around the workflow you're trying to support.

At New Media Aid, we help SMEs replace spreadsheet-heavy processes with bespoke software that improves visibility, reduces administration and supports long-term growth.

If you'd like to discuss replacing spreadsheets, automating workflows or developing a bespoke operational platform, get in touch.

Previous blog

How We Replaced Spreadsheet-Based Workforce Planning for a Scaffolding Contractor

Many construction and scaffolding businesses still rely on spreadsheets to plan vehicles, labour and site work. While spreadsheets can work when a business is small, they often become increasingly difficult to manage as teams grow and operational complexity increases.