A lot of businesses end up living in spreadsheets because nothing else ever quite fitted properly.
One system handles quoting. Another handles production. Someone exports data into Excel because reporting is awkward. Then another spreadsheet appears to bridge the gap between two systems that do not really talk to each other.
A few years later, half the operational knowledge in the business sits in spreadsheets nobody really wants to touch.
Most of the time this is not caused by poor businesses or poor staff. It usually happens because the business evolved faster than the systems around it. Processes change, reporting requirements change, departments build their own workarounds, and eventually the spreadsheet becomes the safest place to manage things because everyone understands it.
The spreadsheet is usually a symptom
Spreadsheets are rarely the original problem.
They normally appear because something practical needs to happen and the current setup does not make it easy.
Sales need a better view of live quotes. Operations need to know what is due out this week. Finance need a cleaner breakdown of revenue by customer or job type.
The main system may already contain some of that information, but not in a way that answers the question quickly. So someone exports a CSV, adds a few columns, builds a pivot table, and sends it round.
That is usually fine at first. It solves an immediate problem. It gives people visibility. It lets work carry on.
The issue starts when the workaround becomes part of the process.
Workflows drift over time
Systems tend to be chosen for a particular moment in the business. At the time, they make sense.
A CRM is brought in to manage enquiries. A finance system handles invoicing. A production platform replaces the old job sheet process. Monday.com helps teams track work more clearly. SharePoint becomes the place for shared documents, forms, and lists.
Individually, each system may be doing a reasonable job.
The problem is that the business does not stand still.
New services are added. Teams change. Reporting expectations increase. Customers ask for different information. A department starts using extra fields that nobody else sees. Another team builds a SharePoint list because they need a simple approval process.
None of these decisions are necessarily wrong.
Most businesses are carrying far more operational complexity than their software stack was ever originally designed for.
Over time, the systems begin to drift apart. The CRM thinks one thing is the source of truth. Finance thinks another. Operations have their own tracker. The spreadsheet becomes the thing that reconciles them all.
Why businesses trust spreadsheets
Businesses trust spreadsheets because they are familiar, flexible, and immediate.
You can open one, change it, filter it, copy it, colour-code it, and make it answer a question without raising a ticket or waiting for a supplier.
If a production manager needs to know which jobs are blocked, a spreadsheet can be adjusted in minutes. If finance need a one-off report for a board meeting, Excel is often quicker than waiting for a system change.
There is also a human side to this.
People like tools they understand. They trust what they can see. A spreadsheet does not hide logic behind a permission structure or a fixed report builder.
They are not always the weakest tool in the chain. Sometimes they are the only tool flexible enough to match the reality of the work.
The patterns are usually the same
We see the same patterns constantly:
- duplicated reporting
- manual updates between systems
- disconnected workflows
- people re-keying the same information
- "master spreadsheets" everyone is scared to break
- reporting that only works if one person is in the office
A customer record exists in the CRM, the finance system, and a spreadsheet. The job status is updated in Monday.com, then copied into SharePoint, then summarised manually for a weekly meeting.
Nobody set out to create a fragile process.
It just became normal.
Reporting becomes a bottleneck
Reports are often where the cracks become visible.
The business already has the information it needs, but it exists in too many places. Some of it is structured. Some of it is buried in notes. Some of it lives in exported files.
Someone asks for a view of current workload, overdue actions, margin by job, or forecast capacity. The answer should be straightforward, but it means pulling data from several places and joining it manually.
The result may be useful, but it is also delayed.
By the time the report is finished, some of the information has already changed. The business starts making decisions from a mixture of live data, stale exports, and individual knowledge.
This is where spreadsheets quietly move from being useful to being risky. Not because the spreadsheet itself is wrong, but because the process around it depends too much on manual effort.
The hidden risk is knowledge living with individuals
One of the biggest risks is not the spreadsheet. It is the knowledge around the spreadsheet.
The formulas, exceptions, naming conventions, colour codes, and manual checks often live with one or two people. They know which tab matters, which export to use, and which figures need adjusting before they are shared.
That knowledge is valuable, but it is also vulnerable.
If that person is on holiday, the report waits. If they leave, the business has to reverse-engineer the process. If someone else touches the wrong cell, confidence in the numbers disappears.
This is not a staff problem. It is a systems problem.
Good people often hold businesses together by understanding the gaps between systems.
The risk is that the business becomes dependent on that invisible effort.
Replacing everything usually fails
When the spreadsheet problem becomes obvious, the first instinct is often to look for one system to replace everything.
That is understandable, but it rarely works cleanly.
Most businesses are more specific than they look from the outside. They have particular approval steps, customer commitments, stock rules, job types, and reporting habits.
The danger is that the business spends a lot of time and money implementing a system that looks comprehensive, only to recreate the same workarounds around the edges.
The spreadsheet comes back, just in a different place.
That does not mean systems should never be replaced. Sometimes they should. But replacing everything is not automatically the mature option. Often the real issue is not that every system is wrong. It is that the tools are not joined around the way the business actually operates.
Connecting the work properly
The businesses that usually make progress are the ones that stop building more process around the gaps and start fixing how information moves through the business.
That might mean pulling key data out of the tools people already use and presenting it in one reliable view. It might mean replacing a fragile spreadsheet with an internal platform that handles approvals and status changes. It might mean connecting Monday.com, SharePoint, finance data, and a line-of-business system.
Often, the best answer is not dramatic.
It is making sure the quote becomes the job without being copied manually. Making sure the job status is visible without someone exporting a file. Making sure the report reads from the right source instead of relying on last week's spreadsheet.
Small connections can remove a lot of friction.
The aim is not to remove every spreadsheet
Spreadsheets still have a place.
They are useful for modelling, exploration, one-off analysis, and quick commercial thinking. A well-used spreadsheet is not a sign of failure.
The problem is when a spreadsheet becomes the operational system by accident.
When it controls live work, holds business-critical logic, or becomes the only place where people can see what is really happening, it is probably carrying more weight than it should.
The better approach is usually to look at where the spreadsheet sits in the workflow and ask why it is needed.
Is it joining data from disconnected systems? Is it compensating for poor reporting? Is it tracking a process that no existing system supports properly? Is it the only place where people trust the numbers?
Those answers normally point to the real work.
Not more process. Not a bigger spreadsheet. Not a rushed replacement project.
Just clearer operational systems, better connections between them, and reporting that reflects how the business actually runs.
That is usually where the value is.