Replacing Excel With a Web App: When It's Time (And When It Isn't)
Excel is the right tool until one of five symptoms shows up: version chaos across multiple editors, formula chains nobody dares touch, customer PII travelling by email, manual retyping into other systems, or a single person who understands the file. The fix is usually a small web app with roles, validation, and an audit trail — €15,000–€50,000 depending on how many workflows it covers. Don't rebuild the spreadsheet 1:1: map the process first, then run both in parallel for a month.
Almost every company we work with has THE spreadsheet — the one that quietly runs orders, pricing, or planning. We're not here to mock it: Excel earned that job by being flexible, familiar, and effectively free.
When should you replace Excel with a web app?
When these symptoms appear. One is a warning; two or more mean the spreadsheet has become infrastructure — and infrastructure deserves better tooling.
| Symptom | What it actually costs you |
|---|---|
| Several people edit it ("FINAL_v7_new.xlsx") | Version chaos, silently overwritten work |
| VLOOKUP and macro chains nobody dares touch | Every change is a gamble; errors surface weeks later |
| It holds customer PII and travels by email | Real GDPR exposure — no access control, no deletion concept |
| Data gets retyped into other systems | Hours of manual work plus transfer errors |
| Only one person understands it | Bus factor of one on a core process |
When Excel should stay
Just as important. If one person uses the file, the structure changes every week, and nothing downstream depends on it — keep Excel. Ad-hoc analysis, one-off calculations, and early-stage experiments don't deserve custom software. Replacing a living, exploratory spreadsheet with a rigid app makes things worse, not better.
What the replacement actually looks like
Not SAP, and not a sprawl of no-code tools either. Typically a focused web app: user accounts with roles, forms with validation so bad data can't get in, an audit trail that answers "who changed what, when", and integrations with the systems people were retyping into. In our projects that lands at €15,000–€50,000 depending on the number of workflows — our web app cost breakdown covers what drives the range.
The trap: rebuilding Excel 1:1
The most expensive mistake is treating the spreadsheet as the spec. Spreadsheets accumulate workarounds — helper columns, copy-paste steps, that one tab everyone ignores — which only exist because Excel lacks roles and validation. Map the actual process first, then drop every step that was a workaround. The app should end up simpler than the sheet it replaces.
Migration without drama
Import the existing sheet as the starting dataset, then run app and spreadsheet in parallel for a month. Discrepancies surface the edge cases nobody documented, and the team switches when the app has proven itself — not because a deadline says so.
We build exactly these focused replacements as part of our process automation work — usually starting with the one spreadsheet everyone is afraid of.
Olio on LinkedIn
