`Spreadsheets are incredibly useful.
For a lot of businesses, they are also where entire systems quietly begin.
A simple Excel or Google Sheets file might start as a way to track customers, manage jobs, record stock, organise enquiries or calculate quotes.
Then the business grows.
More people start using it. More columns get added. Several versions appear. Formulas become harder to understand. Someone accidentally overwrites something important.
Eventually, the spreadsheet that originally made life easier starts creating work of its own.
At Nort Labs, we do not think businesses should replace spreadsheets simply because custom software sounds more advanced.
The question is whether the spreadsheet is still helping the business — or whether the business is now having to work around the spreadsheet.
That is usually the point where it is worth looking at alternatives.
There Is Nothing Wrong With Running a Business Process in a Spreadsheet
Spreadsheets solve a lot of problems remarkably well.
They are quick to create, familiar to most teams and flexible enough to handle everything from simple lists to reasonably complex calculations.
For a small process, that can be exactly what you need.
If one person maintains a spreadsheet, the information is straightforward and the process works reliably, replacing it with bespoke software may achieve very little.
Custom software should solve a problem.
It should not be built simply because a spreadsheet looks less impressive.
The problems normally begin when the process becomes more complicated than the tool managing it.
Sign One: You Have Several Versions of the Same Spreadsheet
One of the clearest warning signs is when nobody is completely sure which file is correct.
You might have:
- Customers-Final.xlsx
- Customers-Final-v2.xlsx
- Customers-Updated.xlsx
- a copy somebody downloaded last Tuesday
- another version being maintained by a different department
At that point, the problem is no longer simply organisation.
It becomes a question of which information the business can actually trust.
Cloud-based spreadsheets can reduce some of this by allowing several people to work on the same document, but they do not automatically solve every process problem.
If teams are still exporting, copying, duplicating or maintaining separate datasets, the underlying workflow may need attention.
Sign Two: People Are Entering the Same Information More Than Once
Imagine somebody receives a new customer enquiry.
They enter it into a spreadsheet.
Then they copy the details into another system.
Then somebody else adds the same customer to a project tracker.
Then finance re-enters part of the information somewhere else.
None of those individual jobs may take very long.
But repeated across hundreds or thousands of records, duplication becomes expensive.
It also creates more opportunities for information to become inconsistent.
If the same information constantly needs to be copied between spreadsheets and other systems, the problem may be the workflow rather than the individual tools.
This is where integration or purpose-built software can become useful.
Instead of asking staff to move information manually, systems can potentially pass the relevant data between each other automatically.
Sign Three: One Person Understands How Everything Works
Some business spreadsheets are masterpieces.
They contain formulas, lookups, formatting rules, linked worksheets and years of accumulated knowledge.
There is just one problem.
Only one person understands them.
If that person is unavailable, leaves the company or simply forgets why a particular formula was created three years ago, an important business process suddenly becomes difficult to maintain.
This is sometimes described as key-person dependency.
The spreadsheet itself may still work perfectly.
The risk is that the knowledge required to operate or repair it is concentrated in one person.
A business process becomes much healthier when important rules are documented, understandable and less dependent on somebody remembering how a particular cell works.
Sign Four: Mistakes Are Becoming Expensive
A typo in a personal budgeting spreadsheet is annoying.
A typo in a spreadsheet being used to manage customer orders, stock, pricing or project delivery can be much more serious.
Spreadsheets generally give users a great deal of freedom.
That flexibility is one of their strengths, but it can also become a weakness.
People may be able to:
- overwrite formulas
- delete rows
- enter information in the wrong format
- change values that should be controlled
- duplicate records
- leave important fields empty
If mistakes are rare and easy to correct, this may not matter.
If mistakes are affecting customers, causing financial problems or consuming significant staff time, stronger controls may become worthwhile.
Purpose-built systems can restrict what users are allowed to change and validate information before it is saved.
Sign Five: The Spreadsheet Has Become the Workflow
This is an important distinction.
A spreadsheet can support a business process.
But sometimes the business process starts being designed around what the spreadsheet can do.
Staff create workarounds because the file cannot handle a particular step.
Extra columns appear to represent different stages.
Colours start carrying specific meanings.
Comments become task management.
Someone has to remember to send an email whenever a row changes.
At this point, the spreadsheet may no longer simply contain information.
It has become an improvised software application.
That does not automatically mean it needs replacing, but it is usually worth asking whether a system designed around the actual workflow would make more sense.
Sign Six: You Cannot Easily See What Is Happening
A business might have all of the information it needs and still struggle to use it.
For example, management may want to know:
- how many jobs are currently active
- which customers are waiting for a response
- which projects are overdue
- what stock needs ordering
- where enquiries are being lost
- which team member is responsible for the next action
If answering a basic operational question means filtering several sheets, combining files or asking somebody to manually prepare a report, the information may not be structured around how the business now needs to use it.
A custom dashboard or application can present different information to different people without expecting everybody to navigate the underlying dataset themselves.
Sign Seven: Permissions Are Becoming Complicated
As more people become involved, access becomes another consideration.
Not everybody necessarily needs to see or edit everything.
A salesperson may need access to customer information but not financial data.
A customer may need to see the progress of their own project but obviously not anybody else’s.
A manager may need reporting access without being able to accidentally change operational records.
Spreadsheets can support some access controls, but complex permission requirements can quickly become awkward.
Purpose-built software can give users defined roles and control exactly what each type of user can see or change.
Do You Need Custom Software?
Not necessarily.
Recognising that a spreadsheet is struggling does not automatically mean the answer is a large bespoke software project.
There may be an existing product that already solves the problem.
A CRM, project management system, inventory platform or another specialist application might provide everything the business needs.
Nort has previously looked at the decision between subscription platforms and custom CRM software, and the same principle applies here.
Use an existing product when an existing product genuinely fits the process.
Custom software becomes more interesting when the workflow is genuinely specific to the business, existing products require significant compromises or several disconnected systems need to work together.
Do Not Rebuild Every Spreadsheet at Once
If a company has relied on spreadsheets for years, there may be dozens of them.
Trying to replace everything at once can create a much larger project than necessary.
A better starting point is often the process causing the most friction.
That might be:
- customer management
- quoting
- job tracking
- stock management
- internal approvals
- reporting
Understand how that process currently works.
Identify what is actually going wrong.
Then decide whether the answer is improving the spreadsheet, changing the workflow, adopting an existing platform or building custom software.
That order matters.
Starting with the technology before understanding the process is an easy way to build something the business does not really need.
So, When Does a Spreadsheet Stop Being Good Enough?
There is no particular number of rows, employees or formulas where a spreadsheet suddenly becomes unsuitable.
The real tipping point is operational.
A spreadsheet has probably stopped being good enough when managing the spreadsheet creates more problems than the spreadsheet is solving.
If staff are constantly duplicating information, correcting mistakes, maintaining several versions, relying on manual reminders or designing workarounds around the limitations of the file, it is worth reviewing the process.
Sometimes the answer will still be a better spreadsheet.
Sometimes an existing piece of software will solve it.
And sometimes the way the business works is specific enough that building something around that process makes sense.
The important thing is not to replace spreadsheets for the sake of replacing them.
It is to recognise when a simple tool has quietly become responsible for a job it was never really designed to do.
“`
