A spreadsheet can begin as a useful tool for estimating, planning or reporting. Over time, it may become the place where people approve work, calculate customer prices, allocate stock, track jobs or decide what happens next.
At that point, the decision is not simply whether to replace Excel. It is whether a specific operational workflow should stay in a spreadsheet, move into an ERP, or be handled through a focused managed custom web application.
For UK SMEs, the right answer depends on the process boundary, the controls required and how closely that process must connect to finance, stock, purchasing, customer records or other shared data.
ERP vs spreadsheet: start with the workflow, not the software
A business can sensibly use all three approaches at once:
- Spreadsheets for modelling, forecasting, one-off analysis and flexible calculations.
- ERP for connected business transactions and shared records across functions.
- Managed custom apps for a defined operational workflow that needs stronger control than a workbook, but does not require a broad suite.
The useful question is: what happens if this process is wrong, delayed or unclear?
A workbook used for occasional scenario planning has a different risk profile from one that determines quoted prices, records inspection results or tracks work that must be completed on time.
Practical rule: Judge a spreadsheet by the operational consequences of an incorrect entry, missed approval or unclear version, not by its number of tabs or users.
What each option is designed to do
Spreadsheet
Excel remains a strong choice for work that is analytical, exploratory or temporary. It is familiar, adaptable and quick to change when a capable owner understands the model.
A spreadsheet becomes less suitable when it acts as the live record of an operational process and users need to know:
- which record is current
- who can change it
- whether an approval has happened
- why an exception was allowed
- which rules were applied
- what another department should do next
Protected cells, instructions and file naming can reduce risk, but they depend heavily on people using the right version and following the right sequence.
ERP
An ERP is intended to manage connected records and repeatable transactions across business functions. It is often the stronger option when a workflow must reliably connect sales, purchasing, inventory, finance, customer information or reporting.
An ERP may fit when a completed action in one area must automatically affect another. For example, an approved order may need to reserve stock, create purchasing activity, update customer records and feed financial reporting.
The trade-off is breadth. An ERP implementation needs clear ownership, data preparation, process decisions, testing and adoption work. It can be the right strategic choice, but it should not be selected merely because one operational workbook has become difficult to manage.
Managed custom web app
A managed custom web app is a purpose-built application for one defined business workflow. It can provide structured forms, role-based access, validation, approval steps, activity history and reporting without attempting to replace every business system.
This approach can suit a workflow that is operationally important and distinctive, such as:
- quoting with business-specific pricing and approval rules
- job tracking across teams and locations
- production planning with exceptions and changing priorities
- inspections, maintenance or compliance records
- project tracking and operational handoffs
- recurring management reporting that depends on controlled inputs
The aim is not to reproduce every feature of an ERP. It is to make one important process easier to run consistently, while keeping appropriate finance, inventory or customer systems in place.
Comparison: spreadsheet, ERP or managed custom app
| Decision criterion | Spreadsheet | ERP | Managed custom web app |
|---|---|---|---|
| Best use | Analysis, modelling, temporary work and contained processes | Connected transactions across multiple functions | One defined operational workflow with specific rules |
| Workflow control | Relies on ownership, review and user discipline | Structured records, permissions and transaction controls | Guided forms, validation, approvals and role-specific actions |
| Shared data | Often depends on imports, exports or manual reconciliation | Strong where departments need common master data | Can support selected handoffs and integrations where needed |
| Change handling | Quick to alter, but changes can be difficult to govern | Changes may require configuration and testing | Changes can be scoped around the workflow and managed over time |
| Operational fit | Useful where mistakes are recoverable and the file is not the system of record | Useful where the process is inseparable from broader business transactions | Useful where the process is critical but narrower than an enterprise suite |
| Common risk | Version conflict, copied logic, duplicate entry and key-person dependency | Overly broad scope, difficult adoption or forcing local work into a standard process | Unclear boundaries or trying to preserve every historic spreadsheet workaround |
When a spreadsheet is still the right answer
Keeping Excel can be sensible when the work is primarily analytical rather than transactional.
Examples include:
- forecasting and scenario modelling
- management analysis based on trusted source data
- temporary data preparation
- early-stage process exploration
- a controlled calculation owned by one person and reviewed before use
The presence of multiple users does not automatically mean that Excel is unsuitable. Equally, one user or a small workbook does not automatically make it safe.
The key distinction is whether the workbook is helping someone think, or whether it is directing a live operational process that others must rely on.
When ERP is the stronger fit
ERP is usually worth considering when the workflow is part of a wider chain of shared transactions.
For example, ERP may be the stronger option if a process needs to:
- use the same customer, supplier or product data across departments
- update stock, purchasing and finance records together
- support consistent transaction history across several business functions
- enforce shared controls across sales, operations and finance
- avoid separate teams re-entering or reconciling the same information
A job workflow may need ERP if job activity must drive purchasing, stock movements, timesheets, invoicing and financial reporting in a connected process.
The case is less compelling when the problem is narrow, such as a specialised approval route or operational screen that standard ERP workflows do not reflect well.
When a managed custom app is the better middle ground
A focused managed app can be a good fit where a workflow is too important for informal spreadsheet governance but too specific to justify a broad ERP change.
Consider this approach when the process has:
- a clear start and end point
- several roles with different actions or permissions
- approval or validation rules that should not depend on memory
- repeatable exceptions that are currently handled through messages or side files
- a need for one authoritative operational record
- a small number of defined handoffs to existing systems
For a closer look at this approach, read Managed Custom Web App vs Packaged Software for One Excel Workflow.
Three examples of the decision in practice
1. Sales quoting and margin approval
A quoting spreadsheet may work while one person manages the process and pricing is straightforward. Risk grows when supplier costs change, several people prepare quotes, customer-specific terms apply or margin approval happens outside the workbook.
A managed custom app may fit when the business needs structured quote inputs, controlled pricing rules, approval states and a consistent output document.
An ERP may be the stronger choice when quotes must immediately drive stock commitments, customer credit, fulfilment, invoicing and financial reporting.
Excel can remain useful for modelling scenarios, provided it is not the live approval and transaction record.
2. Job tracking and operational coordination
A spreadsheet job tracker can provide a useful planning view. It becomes fragile when people maintain separate copies, update statuses inconsistently or cannot see who owns the next action.
ERP is often appropriate if job progress must connect directly to stock, procurement, timesheets, invoicing and finance.
A managed custom app can suit a workflow where operational coordination is the primary challenge, such as assigning work, recording status, escalating exceptions and handing approved information into an existing finance system.
3. Recurring management reporting
Monthly reporting often exposes a different problem. The spreadsheet may not be the original source of transactions, but it becomes the place where someone cleans data, reconciles definitions and assembles reports manually.
Excel remains valuable for analysis once the data is trusted. A managed app may help where recurring reporting relies on controlled inputs, consistent definitions and visible ownership. ERP may be needed where reporting issues reveal broader gaps in shared master data and connected transaction records.
Avoid the parallel-system trap
The problem is not that staff continue to use Excel after an ERP or app is introduced. Excel can still be useful for local analysis and planning.
The risk appears when two systems claim to represent the same operational event.
For example:
- the ERP shows one order status while a workbook shows another
- a manager approves a value in an email but the live record is not updated
- operations work from a tracker while finance relies on a separate version
- staff re-enter the same information because neither system has a clear role
For every important record, decide which system is authoritative. Then define what information moves elsewhere, who owns that handoff and how exceptions are handled.
A focused app should complement an ERP where appropriate, not create a competing record for the same transaction.
A practical decision checklist
Before choosing an approach, document one workflow from start to finish.
Define the boundary
Name the event that starts the process, the people involved, the decisions they make and the output the business relies on.
For a quotation process, this could include input costs, pricing rules, approval conditions, document generation and the handoff to order processing. For a job workflow, it could include job creation, assignment, progress updates, exceptions, completion and invoicing handoff.
A clear boundary helps prevent a focused improvement becoming an accidental company-wide systems programme.
Identify the controls that matter
List the points where staff currently rely on memory, messages or informal checking:
- approval before a quote is issued
- use of an approved cost or rate
- restricted access to sensitive records
- a record of who changed a status and when
- escalation of unusual cases
- use of the latest approved information in a document or report
If these controls are important, they should be built into the operating process through permissions, validation, guided steps, approval states and activity history.
Map data and handoffs
Ask what the workflow must exchange with finance, stock, purchasing, customer records and reporting.
- Shared transactions and master data point more strongly towards ERP.
- A limited number of defined handoffs may suit a managed app alongside existing systems.
- No meaningful integration need may support retaining a redesigned spreadsheet, if the workflow remains low risk.
The objective is not to buy broad functionality for a narrow data-transfer problem. It is also not to isolate a process that genuinely depends on wider business records.
Make hidden effort visible
Compare the operational effort involved in each option, including:
- preparing, checking and reconciling spreadsheets
- resolving duplicate entry and unclear versions
- data cleaning and migration work
- testing and training
- support, access changes and future process amendments
- the consequences of late or incorrect operational information
This is a better basis for a decision than comparing software categories in isolation.
Choosing the smallest safe change
Use the smallest change that gives the workflow the control it needs:
- Keep or redesign Excel when the process is analytical, contained and recoverable.
- Use ERP when the workflow relies on connected business transactions and shared data across functions.
- Use a managed custom app when the process is operationally critical, role-specific and too narrow or distinctive for a standard ERP module.
You do not need to replace every spreadsheet. The priority is the workbook that has become an unofficial operational system, where unclear ownership, version conflict or manual workarounds now affect customers, cash flow, delivery or compliance.
If you are considering a focused replacement, see how Spreadsheet Upgrade works.
Start with a Free Fit Check
A Free Fit Check is an early conversation about the workflow, not an assumption that every spreadsheet should become an app.
It can help you clarify the process boundary, identify the main control and handoff issues, and consider whether the sensible direction is to retain Excel, assess ERP fit or explore a managed custom application for a defined workflow.