Replacing Excel: When a Custom Web App Pays Off

Replacing Excel pays off as soon as several people maintain the same data and you also need permissions, traceability, interfaces or automation. In that case, a custom web app with a database is the more stable solution. For single workstations, calculations and analyses, Excel often remains the better choice – the point is not to abolish the tool, but to stop misusing it as a database and workflow system.

This article shows how to recognize the right moment, which alternatives exist, what a web app does better and how the switch can succeed without disrupting day-to-day operations.

Seven signs that your spreadsheets are hitting their limits

1. There are several versions of the same file – “customer_list_final_new_2”.
2. Colleagues wait because someone else currently has the file open.
3. Formulas break when someone accidentally moves a row.
4. Nobody knows exactly who changed which value and when.
5. Everyone sees everything – including data not meant for everyone.
6. Information is retyped from the spreadsheet into other systems.
7. Only one person really understands the file.

If several of these apply, the spreadsheet costs more time than it saves – and carries risks for data quality and data protection. The last point is especially critical: if that one person is absent, in the worst case an entire process comes to a halt. The technical limits of Excel, such as a little over one million rows per worksheet, rarely play the main role in SMEs. Usually it is organization and collaboration that no longer scale.

Excel in the team, standard tool, low-code or custom web app?

Not every spreadsheet needs custom development. The following overview helps with classification:

Option	Fits when …	Limits
Excel with cloud collaboration	few people, simple structure, no fine-grained access rights needed	no form logic, hardly any record-level permissions, formula errors remain possible
Standard software	the process is industry-standard, such as time tracking or simple contact management	your process has to adapt to the software; license costs per user
Low-code platform	simple forms and lists, manageable permissions, internal use	limits with complex roles, interfaces and performance; vendor dependence
Custom web app	specific process, several roles, interfaces, the solution should grow with the company	higher initial investment; needs operation and maintenance

A detailed comparison is in our article Custom or standard software?. As a rule of thumb: the more roles, special cases and interfaces your process has, the sooner a custom solution pays off.

What a web app with a database does better

Problem in Excel	Solution in the web app
Version chaos and locked files	one shared data source: everyone works simultaneously in the browser on the same, current data – in the office, on the road or on a tablet in the workshop
Everyone sees everything	roles and permissions: sales sees its customers, accounting sees payments, management sees everything
Typos and incomplete entries	required fields, selection lists and plausibility checks prevent faulty records from the start
Unclear who changed what	change history: who, when, what – this creates clarity and helps with follow-up questions
Retyping into other systems	interfaces and automation: status changes trigger tasks, emails or documents, deadlines are monitored
Compiling reports by hand	dashboards show key figures in real time instead of someone merging data every month

Technically, a clean database sits behind this: columns and tabs become tables with relationships and rules. That prevents the same information from being maintained differently in three places.

Typical candidates for the switch

• job and deployment planning with several participants
• stock and material lists with goods in and out
• project and budget overviews that are reported regularly
• inspection and maintenance logs with deadlines
• customer and contact lists maintained by several teams

A typical scenario: a skilled-trades business plans jobs, appointments and material requirements in a spreadsheet that has grown over the years. Three people maintain it, each in their own way. In the web app, the office team captures jobs through a form, dispatch plans appointments in a calendar view and technicians see their assignments on their smartphones. Material is reserved automatically, and management sees utilization at a glance. The old file is only needed as an archive.

Data protection and traceability: spreadsheets as an underesti­mated risk

Excel files containing customer data are sent by email, copied to USB sticks and stored in private cloud folders. Who sees which data is hard to control, and deletion obligations are difficult to implement. Even sheet protection in Excel is not real access protection, but a hurdle against accidental changes.

A web app with a permissions concept, logging and central data storage, by contrast, makes data protection controllable: access can be restricted, changes traced and data deleted selectively. This also applies to records that may be relevant for tax purposes – there, the GoBD (German principles for proper bookkeeping, see our glossary entry) require traceability and immutability, among other things, which is hard to demonstrate with freely editable spreadsheets. Whether this affects your data is something your tax advisor can clarify. This article does not replace legal advice.

How the switch succeeds in six steps

1. Inventory: Which spreadsheets exist, who uses them for what, which formulas, macros and dependencies are inside?
2. Requirements: Goals, roles, special cases and priorities are documented – as a lean requirements specification if needed.
3. Data model: Columns and tabs become clean tables, relationships and rules – the foundation for a stable database.
4. Prototype: A first version with the most important screens is tested with the future users.
5. Data migration: Existing data is cleaned up, duplicates are merged and everything is imported; a sample checks the result against the original spreadsheet.
6. Rollout: short training, a clear cut-over date, the old file is set to read-only, and a dedicated contact person is available for a transition period.

One success factor is often underestimated: the people who work with the spreadsheet today should be involved from the start. They know the special cases that are not in any formula – and become advocates of the new solution when their experience is taken into account.

Typical mistakes during the switch

• Rebuilding the spreadsheet one-to-one: The switch is a chance to simplify processes rather than carry over every legacy burden.
• Wanting everything at once: Better a small, usable first version and then extensions in stages.
• Overlooking hidden logic: Formulas, macros and color coding often contain rules that nobody has documented.
• Underestimating data cleansing: Inconsistent spellings and duplicates take time, but are the basis for reliable reporting.
• Not assigning responsibility: Someone in-house has to own the business side of the app and consolidate change requests.

“And what if our process changes?”

We hear this concern often – after all, Excel’s flexibility was a reason for its success. A web app can be adapted too: with a clean architecture, new fields, statuses or reports are added quickly. The difference is that changes are made deliberately and documented, instead of everyone inserting their own column. And where ad-hoc analyses are needed, export helps: Excel remains the tool for analyzing, the app the system for maintaining.

What does the switch cost?

That depends on the scope. These factors determine the effort:

Factor	Affects the effort through …
Screens and functions	number of forms, lists, calendar and report views
Roles and permissions	who may view, change and approve what?
Interfaces	connection to ERP, accounting, email or calendar
Data migration	volume and quality of the legacy data
Automation and reports	rules for statuses, deadlines, notifications and dashboards
Operation and maintenance	hosting, updates, support and further development

Lean web tools with only a few screens can fall under the Starter package from €2,500. We implement portals with roles, interfaces and automation in the Professional package from €8,000. After the free initial consultation, you receive a transparent quote – preferably at a fixed price if the scope is clearly defined.

How Nano Concepts can help

Excel is an excellent tool – but not enterprise software. When spreadsheets become a bottleneck, a web app with a database brings order, security and speed. We help you recognize the right moment, support the Excel replacement from inventory to rollout and develop a custom solution that fits your process exactly. In the free initial consultation, we look at your most important spreadsheets together.