Spreadsheet or custom app? How to know when Excel has reached its limit

Excel is excellent at analysis, calculations and ad hoc planning. A spreadsheet becomes a poor substitute for an operational system when several people must update the same process, follow rules and leave a reliable audit trail.

The answer is not to replace every workbook. It is to recognise when you are asking one to behave like an application.

Look for the symptoms

• Staff send files around and nobody knows which copy is current.
• Changes need approval, but the approval happens in a separate chat.
• A customer or driver needs to submit information from a phone.
• Important columns are overwritten without a record of who changed them.
• One person knows all the formulas, and their absence stops the process.
• You need different permissions for employees, managers and clients.

These are workflow problems, not spreadsheet problems.

Three options before commissioning software

• Improve the spreadsheet when one person owns the file, edits are limited and the work is mostly analysis. Reconsider when multiple users need different permissions or formal approvals.
• Configure an existing product when the process is common and standard workflows will work. Make sure you are not paying for complexity that your business will never use.
• Build a configurable app when the workflow is distinctive, repeats often and has a clear owner. Avoid starting development before the process and its exceptions are understood.

A custom app is justified when its value comes from controlling the process, not merely giving Excel a prettier screen.

Example: collections and deliveries

Imagine a business scheduling container collections.

The spreadsheet holds customer details, a collection date and a driver name. By the time the driver arrives, an address has changed. The office phones the driver, sends a photo of the corrected sheet and later reconciles the delivery confirmation manually.

A focused application could present the driver with today’s assigned stops, allow a one-tap status update, capture photos or signatures and keep dispatch informed. The office sees exceptions immediately instead of reconstructing them at day’s end.

That is an illustrative workflow, not a claim about a particular client project.

Why a reusable engine makes sense

Many businesses share a similar core workflow: request, assignment, execution, evidence and closure. A reusable engine can provide authentication, status history, notifications and reporting.

The client-specific part can then cover their forms, approval rules, terminology, integrations and reports. This is usually a better starting point than building every feature from scratch, provided the core stays maintainable.

What to define before building

Write down:

1. People and permissions: who may view, create, approve and close?
2. Statuses: what exactly moves an item from one stage to the next?
3. Required evidence: what proof is needed before completion?
4. Exceptions: what happens when something goes wrong?
5. Connections: must the app read or update an ERP, accounting or support system?
6. Measures: which delays, errors or manual hours are you trying to reduce?

Ask for a clickable prototype with sample data before committing to a full build. Test it with the actual people who will use it, especially those working on mobile devices.

Avoid rebuilding your accounting system by accident

An operational app should generally integrate with the system that owns financial records rather than quietly creating a second ledger. Define which system is the source of truth for customers, items, invoices and payments.

The same principle applies to privacy: collect only the data the workflow needs and restrict access by role.

Next step: if your spreadsheet is really a shared daily process, describe the workflow to us. We can help you decide whether to improve the workbook, configure an existing tool or design a small custom app.