Replacing Excel: When a Small Business App Outperforms Any Spreadsheet

A trade business in the Ruhr region has been managing its orders in an Excel spreadsheet for ten years — now with five employees all accessing it at the same time. Every Monday there is a disagreement about which version is the "right" one. Sometimes one employee overwrites another's entries. Occasionally the file is corrupted. It sounds like a minor irritation, but in many businesses it is the trigger for a more fundamental question: when does a purpose-built application make more sense than yet another worksheet?

When Excel creates more operational problems than it solves

Excel is the right tool for many tasks: quick calculations, ad-hoc analyses, one-off models. It is not, however, a multi-user system. Microsoft has phased out the legacy "Shared Workbook" feature and no longer actively supports it, citing, in its own words, "many limitations." The only officially supported path for simultaneous editing is now co-authoring via OneDrive or SharePoint Online — businesses without a cloud Microsoft 365 subscription simply have no reliable multi-user option left.

Add to that error rates that tend to be underestimated in practice. Panko and the European Spreadsheet Risks Interest Group (EuSpRIG) found, in an analysis of 88 production spreadsheets, that 94 percent contained at least one error (study period 1995–2004; this remains the most comprehensive systematic study of its kind). These errors do not arise from carelessness: they are the structural consequence of an architecture without data separation, automatic validation, or versioning.

Five operational warning signs that deserve an honest answer:

1. Multiple employees edit the same file and regularly lose each other's changes.
2. Formulas return wrong results after a restructuring because references shifted.
3. The "current version" cannot be determined beyond doubt.
4. New entries are created by copying and pasting — typographical errors are structurally inevitable.
5. The file has grown to the point where nobody knows all the dependencies and any change feels risky.

What Germany's GoBD says about spreadsheets in bookkeeping

For businesses that keep commercial records — order confirmations, delivery notes, invoice data, time records — in Excel, a statutory dimension enters the picture. The GoBD (Grundsätze zur ordnungsmäßigen Führung und Aufbewahrung von Büchern, Aufzeichnungen und Unterlagen in elektronischer Form) stipulates in paragraph 58: "A booking or a record may not be altered in such a way that the original content can no longer be determined" (§ 146 para. 4 of the German Tax Code, AO). The Federal Ministry of Finance letter dated 14 July 2025 most recently reaffirmed this requirement.

An Excel file without an audit-log function does not satisfy this principle of immutability. Any cell can be overwritten after the fact without any timestamp or user attribution being created. During a tax audit, the German tax authorities may challenge electronic records that fail to meet GoBD requirements — with potential consequences for the authority to estimate taxable income under § 162 AO.

This does not mean that Excel is categorically prohibited. It means that GoBD-relevant business transactions require a system that logs changes and preserves original states.

Note: This article does not constitute legal or tax advice. Please consult a tax adviser or auditor for your specific situation.

What a small .NET business app actually looks like

A lean business app does not have to be an ERP system. It does one thing well: order capture, time tracking, inventory management, or quality documentation. A typical technology stack for new development in 2026:

• Backend: .NET 10 LTS (released 11 November 2025, official support until 14 November 2028), Minimal API or Blazor Server
• Database: SQL Server or PostgreSQL — both with built-in transaction logs and audit capabilities
• Front end: Blazor or a lightweight web interface, accessible in any browser without installation on each workstation
• Hosting: on-premises on your own server, or as an Azure App Service in the cloud

The app brings, structurally, what Excel lacks: role-based access rights (who can read, write, or delete), automatic input validation, a complete change log, and a privacy-compliant data model from day one. New employees type into defined fields instead of arbitrary cells.

For an overview of how .NET is used in SMB applications and why it has advantages over other platforms, see the article .NET for SMBs: Stability as a Competitive Advantage. Businesses with existing older .NET applications should also consider whether modernising the legacy system is more cost-effective than a greenfield project — more on that in Modernising a Legacy .NET Application: Three Honest Options.

Which processes are good candidates for replacement?

Good candidates are processes that are maintained daily by multiple people, touch statutory retention requirements (GoBD, GDPR), require a traceable history of changes, or have clear input rules (required fields, numeric formats, drop-down selections).

Typical candidates: order capture and management, maintenance and inspection logs, employee time records, complaint tracking, material procurement requests, customer master data.

Less suitable: one-off calculation models for management, complex pivot analyses with frequently changing dimensions, or ad-hoc analyses used by a single person. For those, Excel remains the right tool.

What does continuing with Excel cost — and what does replacing it cost?

The simplest approximation: two employees each spend two hours per week correcting Excel problems — duplicate data entry, error tracing, version conflicts. At an internal rate of 35 euros per hour, that amounts to roughly 7,280 euros per year in tied staff costs just to manage the workaround system. Projected over three years: 21,840 euros.

On top come harder-to-quantify risks: the additional effort during a tax audit that flags a GoBD deficiency, errors in quotes or invoices caused by broken cell references, or data loss from a corrupted file. To calculate what an unexpected IT outage costs your business, you can use the downtime cost calculator.

Against these costs stands the development investment. Market-typical benchmarks: from around 5,000 euros for a tightly scoped tool, 10,000 to 25,000 euros for a first full version (MVP). The factors that actually drive the price, and what a solid specification document achieves, are covered with detailed cost tables in the article Commissioning Custom Software: What Does a Project Cost for SMBs?.

With a savings and risk-avoidance potential of 7,000 to 10,000 euros per year, a small app pays for itself within two to three years on a conservative estimate — before accounting for the value of improved data integrity and audit readiness.

Frequently asked questions about replacing Excel

Can I simply use Microsoft Lists or a no-code platform instead? Microsoft Lists, Power Apps, and similar tools can make sense when the process is straightforward and Microsoft 365 is already licensed. The limits appear with complex business logic, external system integrations (e.g. with ERP or accounting software), or when you want a self-hosted solution with no dependency on a cloud platform.

Does the application have to be built on .NET? No — but .NET 10 LTS is a natural choice for new SMB applications in Germany: Microsoft ecosystem integration, guaranteed support until November 2028, and broad developer availability. The article .NET 8 and .NET 9 Reach End of Life — Plan the Move to .NET 10 LTS Now explains what the LTS designation means in day-to-day operations.

What happens to my existing Excel data? Data migration is feasible in nearly every project. Excel spreadsheets can be imported in a structured way, provided the data is consistent enough. In practice, the cleansing phase reveals inconsistencies that were previously hidden — a side effect that improves data quality over the long term.

How long does development of a small business app take? A tightly scoped tool can be built in eight to twelve weeks. A full SMB application with multi-user management, integrations, and reporting typically takes three to six months. The biggest time factor is almost always requirements analysis, not coding.

What about GDPR and data protection? A custom application can be designed for data protection compliance from the outset: data minimisation, clearly defined processing purposes, deletion policies, and role-based rights that correspond precisely to the purpose. This is a structural advantage over an Excel file that typically contains more data than any one use case requires.

Do you have an Excel solution that has grown beyond its useful limits and want to know whether a purpose-built application is the right next step? The .NET development page shows the type of projects I take on — and you can arrange a no-obligation initial consultation there.