Managed Custom Web App vs Packaged Software for One Excel Workflow
When one Excel workbook supports a business-critical process, the choice is not simply whether to replace Excel. It is whether a packaged product can support that defined workflow well enough, or whether a fully managed custom web application is a better fit.
This is not an ERP selection guide, and it is not a general argument against spreadsheets. Excel remains useful for modelling, forecasting, analysis and exploratory work. The comparison becomes relevant when one workbook is being used to run an operational process such as job tracking, quotation approvals, production planning, inspections, stock control or recurring reporting.
The right option depends less on the size of the workbook or team and more on how closely the process needs to fit the system.
| Decision area | Managed custom web app | Packaged software |
|---|---|---|
| Process fit | Designed around the defined workflow | Uses a pre-existing workflow model |
| Setup approach | The application is shaped around agreed requirements | The business configures the product and adapts where needed |
| Handling exceptions | Can accommodate process-specific rules where appropriate | Usually works best when exceptions can be simplified or handled within product options |
| Ongoing change | Changes can be considered around the workflow as it evolves | Changes are limited by available configuration and the supplier's product direction |
| Operational control | Screens, roles and workflow stages can reflect the process | Controls follow the product's structure and available settings |
| Best fit | A distinctive, business-critical workflow | A common, stable workflow already well served by standard software |
Start with the workflow, not the software category
A shared spreadsheet can combine several jobs in one file: data capture, calculations, handoffs, approvals and reporting. Before comparing solutions, separate those jobs.
Ask what the workbook is actually doing:
- Recording operational information
- Applying rules or calculations
- Routing work between people
- Requiring approvals or sign-off
- Producing reports or customer-facing outputs
- Maintaining a record of changes or decisions
A packaged product may be suitable when those activities follow a familiar pattern. For example, a straightforward timesheet, basic task list or standard stock process may fit an established product without creating significant workarounds.
A managed custom web app becomes more relevant where the workflow has its own terminology, sequence of decisions, commercial rules, approval routes or exceptions. In that situation, the question is whether adapting the business to a packaged product would create a more awkward process than designing an application around the process itself.
The main decision criteria
1. Process fit versus process adaptation
Packaged software is built to serve a category of problem. That can be a strength when the business process is conventional and the product already covers the required stages, fields and reports.
However, a product may be less suitable if the Excel workflow contains legitimate differences that the business cannot reasonably remove. These might include:
- Different approval routes by value, customer, site or project type
- Rules that depend on combinations of inputs
- Distinct handoffs between office, commercial, finance and operational teams
- Industry-specific terminology or documents
- A process that must present different information to different roles
Custom development is not automatically the answer to every variation. Some variations are habits that can be simplified. But where the differences are central to how the workflow operates, a managed custom application can offer a closer fit without relying on parallel spreadsheets, informal notes or repeated manual workarounds.
2. Configuration limits and workarounds
A packaged product should be assessed against the real workflow, not only a polished demonstration.
Ask suppliers and internal stakeholders to test the less tidy parts of the process:
- What happens when a request is incomplete?
- Can an item be returned for correction without losing context?
- Can the right person see and act on the right information at the right stage?
- Can exceptions be handled clearly rather than outside the system?
- Can required reports be produced without exporting data into another spreadsheet?
If the answer repeatedly involves manual exports, side spreadsheets, generic fields used for unrelated purposes or steps that users must remember outside the product, that may indicate a poor process fit.
A managed custom web app may be appropriate when those gaps are material to the workflow. A packaged product may still be the better choice when the gaps are minor and the team can adopt a simpler, standardised process.
3. Migration and data clean-up
Neither route makes the existing workbook ready for use automatically. A replacement project usually requires decisions about which data should move, which historic records should be retained and which spreadsheet rules still reflect the current process.
For a packaged product, migration often means mapping spreadsheet columns to the product's fields and deciding how to represent information the product does not model directly.
For a custom application, migration involves defining the application's data structure and deciding which existing rules belong in the new workflow.
In either case, useful questions include:
- Which data is current and trustworthy enough to carry forward?
- Which columns are genuinely needed for daily operation?
- Which calculations are still required?
- Which free-text notes represent important business knowledge?
- Which historical records need to remain accessible?
This work is not a reason to avoid replacement. It is an opportunity to distinguish the useful operational record from old spreadsheet clutter.
For a broader explanation of moving spreadsheet logic and data into an application, see Can you turn an Excel spreadsheet into a web app?.
4. Implementation risk
The implementation risk differs between the two approaches.
With packaged software, the main risk is discovering late that the product does not support a critical part of the process, or that the business has to maintain workarounds to make it fit.
With a custom application, the main risk is defining the workflow unclearly or attempting to reproduce every historical spreadsheet feature without deciding what should change.
A practical way to reduce risk is to focus on one defined workflow and identify:
- The people who enter or update information
- The decisions and approvals that move work forward
- The outputs the business relies on
- The exceptions that must be handled
- The information each role should be able to view or change
This article focuses on that comparison for one workflow. If you need a wider guide to deciding whether a spreadsheet should become an application at all, read When should a business replace Excel with a web app?.
5. Support and change handling
A business-critical workflow will change. New reporting needs, policy changes, revised approval responsibilities and operational exceptions are normal parts of running a business.
With packaged software, the available response is usually configuration, an add-on, a revised internal process or a request that depends on the supplier's product direction.
With a managed custom web app, the application can be considered in relation to the specific workflow as it changes. This can suit businesses that need a continuing operational partner rather than a fixed product feature set.
The key question is not whether the system will ever change. It is whether the likely changes are standard enough for a product's configuration options, or specific enough that the workflow needs an application designed around it.
6. Operational control
Operational control is about whether the system helps the business run its process clearly. It includes questions such as:
- Who can create, amend, approve or view a record?
- Which information is visible at each stage?
- How is work assigned and handed over?
- How are exceptions identified and resolved?
- How can managers understand the current status of work?
A packaged product may provide suitable controls where its model aligns with the process. A custom app may provide a stronger fit where roles, decisions and workflow stages need to reflect the business's own operating model.
Source-code ownership can be a contractual consideration in some circumstances, but it should not be the starting point for this decision. For most businesses, the more immediate question is whether the workflow is supported and can be changed responsibly as operational needs develop.
When packaged software is likely to fit
Packaged software is worth prioritising when the workflow is common, stable and can be handled without important compromises.
It may be the stronger option when:
- The process closely resembles a recognised software category
- The required fields, stages and reports are conventional
- Users can work within the product's standard workflow
- Exceptions are limited or can be simplified sensibly
- The business does not need a distinctive process experience
- Product configuration can meet the practical requirements
For example, a simple internal request tracker with standard statuses and basic reporting may be well served by a packaged product. Choosing custom development simply because the existing spreadsheet is inconvenient would not necessarily be justified.
When a managed custom web app is likely to fit
A managed custom web app is more likely to suit a workflow where the process itself creates business value or needs careful control.
That may include a workflow with:
- Several teams handing work between one another
- Approval routes that depend on the record's details
- Complex or process-specific business rules
- Different screens or actions for different roles
- A need to bring data entry, decisions and reporting into one workflow
- Repeated workarounds caused by forcing the process into a generic tool
Consider a quotation workflow. A packaged quotation product may suit a business with standard rates, simple approvals and a conventional sales process. A managed custom application may be more appropriate where quotations depend on detailed operational inputs, conditional pricing rules, multiple internal decisions and a process that must connect closely with delivery or production planning.
The distinction is not that one route is inherently better. It is whether the product's assumptions are a workable match for the defined process.
A practical comparison exercise
Before deciding, write down the workflow in plain language. Avoid starting with features. Start with what happens from the first input to the final outcome.
Use this comparison table with the people who operate the process.
| Question | If the answer is mostly yes | Likely direction |
|---|---|---|
| Can we adopt a standard process without losing important control or clarity? | The product model is likely to fit | Packaged software |
| Can the product handle our key exceptions without separate spreadsheets or manual tracking? | Configuration may be sufficient | Packaged software |
| Is our workflow defined by business-specific rules, approvals or handoffs? | The process needs closer fit | Managed custom web app |
| Would different roles need different actions, views or decision points? | A purpose-built workflow may be helpful | Managed custom web app |
| Are we trying to preserve spreadsheet behaviour that no longer serves the process? | Simplification may be needed first | Review both options |
| Is the workbook mainly used for analysis rather than running an operational process? | Excel may remain the right tool | Keep the workbook or improve it |
The aim is not to force a custom build. It is to make a defensible choice for the workflow that matters.
Choosing without broadening the project
Keep the first decision narrow. Select one business-critical workflow, define its users and outcomes, and compare the two approaches against that reality.
Avoid turning the project into a broad systems replacement exercise unless that is genuinely required. A focused application can be appropriate for one operational process without becoming an attempt to replace every spreadsheet or select a company-wide platform.
If you are considering a managed custom application, learn more about the approach on how it works.
Start with a Free Fit Check
If one Excel workflow is difficult to manage and you are weighing packaged software against a managed custom application, start with the process rather than a feature list.