Replacing a Spreadsheet with a Web App: When It's Worth It

A spreadsheet is worth replacing when it can no longer carry the work safely, not when it gets long. The usual signs are people overwriting each other, everyone seeing everything, the same copy-and-paste routine every week, and small typos that turn into wrong invoices or missed appointments.

If one or two people maintain the sheet and mistakes are caught quickly, keep it. If several of those signs apply, try an off-the-shelf tool first: industry software, a CRM or a no-code database. A custom web app makes sense when your process is specific enough that standard software only handles it with workarounds, and when you can describe a first version in a page or two.

When the spreadsheet is still the right tool

Spreadsheets are flexible, almost everyone can use them, and most teams already pay for Microsoft 365 or Google Workspace. For lists one person maintains, for analysis and for processes that are still changing every month, they are hard to beat.

Size is rarely the real limit. According to Microsoft, an Excel worksheet holds up to 1,048,576 rows and 16,384 columns. Treat that as a technical ceiling, not as a rule for when to switch. Other problems appear long before you get there.

Before you look at software, look at the sheet. Are the columns consistent? Do you use drop-down lists instead of free text? Is it clear who owns which columns? A cleaned-up sheet with protected ranges and one named owner often buys another year or two.

Signs your spreadsheet has hit its limits

Run through this list for the sheet that matters most. One tick on its own is not a reason to switch. Three or more mean it is time to compare options properly.

• Several people edit at the same time and entries get overwritten or lost.
• Copies like "clients_final_v3_NEW.xlsx" are circulating and nobody is sure which one is current.
• Not everyone should see everything (prices, client details, internal notes), but the file only knows "access" or "no access".
• Clients, freelancers or partners need to enter data or check a status without getting the whole file.
• The same manual steps repeat: copying values, writing emails from rows, colour-coding statuses by hand.
• Personal data about customers sits in files that are emailed around or shared widely.
• One wrong cell has real consequences: a wrong price, a double booking, a missed deadline.
• Only one person understands the formulas, and the process stops when they are away.
• You cannot tell who changed what and when, but you need to.

Spreadsheet, off-the-shelf tool or custom app: a comparison

Between "keep the sheet" and "build software" there is a wide middle ground. It includes industry software for trades, practices or agencies, general project and CRM tools, and no-code databases where you assemble forms and views yourself. For many small businesses, that middle ground is the right answer.

If your team works in both German and English, add one question to every trial: does the tool work in both languages for the people who will use it daily?

What a custom web app changes

A web app is software that runs in the browser, with a login, data stored in a database and screens built around your process. Compared with a spreadsheet, three things change.

Structure instead of freedom. Fields have fixed types and required values. A date is a date, and a status comes from a fixed list. That prevents many errors, but you can no longer add a column on a whim.

Access per person and role. The office sees all jobs, a freelancer sees only theirs, a client sees only their own status. Once clients get access, you are effectively building a small customer portal; Customer Portal: What the First Version Should Include covers that case. Access control has to be built and tested carefully: "Broken Access Control" is number one in the OWASP Top 10 2025, the best-known list of common web application security risks.

Workflows instead of chores. Repeated steps can be triggered automatically: a confirmation email when a job is created, a reminder before a deadline, an export for your accountant (Steuerberater).

An app will not fix unclear responsibilities, inconsistent data or a process that changes every week. Sort those out before development starts.

Start small: replace one workflow, not the whole sheet

The most common planning mistake is trying to rebuild every column and every clever formula of the old sheet. Pick the workflow that causes the most trouble and move only that into a first version. How to prioritise features and keep version one small is covered in Web App MVP: Which Features Belong in Version One?.

To get your workflow down on paper in a form a developer can quote on, use the template in Web App Brief Template: Describe Your App Without Writing Code.

Data protection: customer data in spreadsheets is not a special case

The GDPR (in German: DSGVO) applies to customer data in a spreadsheet just as it does to a database. Three points matter when you switch:

• Data minimisation (Art. 5(1)(c) GDPR): keep only what the purpose requires. Moving to a new system is a good moment to delete old columns with birthdays, private notes or long-finished contacts.
• Integrity and confidentiality (Art. 5(1)(f) GDPR): data must be protected appropriately, including against unauthorised access. A file forwarded by email is a weak setup for that.
• Processors (Art. 28 GDPR): cloud spreadsheet providers, no-code platforms and hosting companies process the data on your behalf. That requires a contract under Art. 28(3), usually offered by the vendor as a data processing agreement (DPA, in German "AVV").

What does switching cost?

Without a defined scope, any number would be a guess. The cost of a custom app depends mainly on the number of screens and roles, integrations with other systems and how much data has to be migrated. The cost drivers are explained in How Much Does a Custom Web App Cost in Germany?.

For reference, Ichii builds small, clearly defined web apps from €1,999 net (plus VAT), one-time. The final price depends on the agreed features and is fixed in a quote before work starts. Hosting, third-party services and technical maintenance (from €29 a month) are separate. Replacing an ERP system, multi-tenant platforms with their own billing, or deep integrations with several existing systems are outside that scope.

Your next step

Run the checklist above for your most important spreadsheet. Fewer than three ticks: tidy it up and keep it. More: trial two off-the-shelf tools with real, anonymised data. If both need workarounds and you can pin down one workflow, write it up briefly and send us an enquiry about a web app. A cleaned-up copy of the sheet with sample data is the most useful thing to attach.