INSIGHTS / SPREADSHEETS & BUSINESS SYSTEMS

When should a business replace Excel with custom software?

Excel is often exactly the right tool. The decision to replace it should come from the process becoming difficult to control, not from a desire to make the technology look more impressive.

Excel is not the problem. The process around it might be.

Spreadsheets are excellent tools. They are quick to start, flexible, familiar and particularly useful when a person needs to calculate, analyse, model or organise information. A well-built workbook can serve a business for years.

The difficulty starts when a spreadsheet stops being a document and quietly becomes the operating system for a business process. One file starts carrying customer information, job status, approvals, deadlines, calculations, reporting and handovers. More people need access. Copies appear. Rules live in someone’s head. The spreadsheet still works, but the process around it becomes fragile.

Where spreadsheets work well

Ad hoc analysis and financial modelling.
Small, controlled datasets maintained by one or two people.
Temporary tracking while a process is still being understood.
Calculations where the flexibility of cells and formulas is genuinely useful.
Simple imports, exports and lists that do not require complex permissions or workflow stages.

Replacing Excel merely because a custom system sounds more sophisticated is usually a poor reason to build software.

Warning signs that the spreadsheet has become an operational system

“Which version is the latest?”

If the answer depends on a filename, an email attachment or asking a colleague, version control is already part of the process. Multiple copies make it difficult to know which information is authoritative and which changes have been missed.

The same data is captured more than once

A request may start in an email, get copied into Excel, then be typed into another system and finally re-entered into a report. Every additional capture introduces delay and another opportunity for mistakes.

Approvals happen outside the file

When a row says “Approved” but the actual approval happened in WhatsApp, an email chain or a verbal conversation, the spreadsheet does not contain the full operational record. Someone must reconstruct what happened later.

Reporting requires a ritual

If weekly or monthly reporting means copying tabs, fixing formulas, merging workbooks and asking several people for updates, the reporting problem is often a symptom of fragmented source data.

Access is all-or-nothing

Sharing a workbook can give people visibility they do not need, while restricting sections becomes awkward. A purpose-built application can separate roles: a requester may create and view their own requests, an approver may approve, and management may see consolidated reporting.

There is no useful audit trail

Businesses eventually need to answer simple questions: who changed this, when was it approved, what was the previous value and why did it move to the next stage? A spreadsheet can sometimes capture parts of this, but once the audit trail itself needs policing, the tool is working against the process.

Integrations are becoming manual bridges

People become the integration layer. They download one file, clean columns, rename fields and upload it elsewhere. That may be perfectly reasonable at low volume. At higher frequency it becomes repetitive work that software can often handle more consistently.

What purpose-built software changes

Custom software does not magically fix a poor process. Its value is that it can make agreed rules explicit. A request can have defined fields. Status can move through defined stages. Permissions can depend on role. Notifications can happen automatically. Reports can read from the same underlying data instead of from copied versions.

Processes that often benefit

Quote, order or job tracking involving several people.
Requests that require review and approval before action.
Customer or supplier onboarding with required information and documents.
Recurring document generation from structured data.
Production workflows with handovers, statuses and deadlines.
Internal service requests where management needs visibility and reporting.

When not to replace Excel

Keep the spreadsheet when it is doing what spreadsheets do well. If one capable person owns the file, the information is manageable, collaboration is light and the cost of an occasional manual step is low, custom software may create more overhead than value.

It can also be sensible to improve the workbook first. Better validation, protected cells, clearer ownership or a shared storage convention may solve the real problem without building anything new.

A practical decision checklist

Question	If the answer is often “yes”
Do several people update the same operational information?	Centralised data may help.
Are approvals or status changes happening in messages or email?	A defined workflow may help.
Is information repeatedly captured or copied?	Automation or integration may help.
Do users need different levels of access?	Role-based permissions may help.
Is an audit trail important?	A database-backed application is usually easier to govern.
Are reports slow to prepare because source data is fragmented?	One operational data source may help.
Would losing one employee’s knowledge make the process difficult to run?	The process itself needs to become more explicit.

The useful question is not “Can this spreadsheet become software?” Almost any spreadsheet can. The better question is whether the process has enough repeated work, risk, coordination or visibility problems to justify a more structured tool.

A PRACTICAL NEXT STEP

Start with the process, not the software.

If a business process has become difficult to manage through spreadsheets, messages, email or disconnected systems, UNKNOT can help examine the workflow and determine whether purpose-built software makes sense. Sometimes the right answer is a smaller process change or an existing product.

Talk through the workflow