A custom web app pays off when several people work with the same data, fixed processes grow out of it, and mistakes or waiting times visibly cost money. For a list that only one person maintains, Excel remains the better choice. This guide shows how to spot the line and what matters when you move to a web app.
When does Excel reach its limits?
Excel is an excellent tool for calculations and quick analysis. Trouble starts when the spreadsheet turns into a process. Typical signs:
- Several versions: there is a
quotes_final_new_2.xlsxon three computers and nobody knows which one is right. - Double entry: the same data sits in Excel, in the mailbox and in the accounting system.
- Missing permissions: anyone who can open the file sees and changes everything, including prices or customer data.
- No status: who has taken over a job, what is missing, when is it done? That lives in heads and emails, not in a system.
- External parties: customers should upload documents or pick appointments, and you send files back and forth instead.
If two or three of these apply, you are already paying for the lack of software, just in working time.
What a web app does differently
A website informs, a web app gets work done. Users log in, see only their own data, create cases and approve them. It runs in the browser on a computer, phone or tablet, with nothing to install. Your team and your customers need a link and a login.
| Question | Excel list | Web app |
|---|---|---|
| Who sees which data? | Whoever has the file sees everything | Roles and permissions per user |
| Working at the same time | Conflicts, several versions | One state for everyone |
| Status of a case | In emails and heads | In the system, traceable |
| Involving customers | Files by email | Portal with login |
| Connection to other systems | Copy and paste | Interfaces to accounting, CRM, calendar |
| Entry cost | Practically zero | One-off development |
Which processes are worth it most
In our experience a web app pays off where a process recurs often and involves several people. These are rules of thumb from KSTAQ's practice, not a guarantee. One example, which we deliberately treat as a thought experiment: a trades business manages jobs in a spreadsheet, fitters report hours by messenger, and the office retypes everything. An app could bring the job, the time tracking and the feedback together in one place.
Well suited:
- Customer portals with documents, status and messages
- Online appointment booking and resource planning
- Forms and approvals instead of paper and email
- Dashboards that combine figures from several systems
- Internal tools for quotes, orders or stock lists
Less suited is anything that is a one-off calculation model or maintained by a single person. There Excel is faster and cheaper.
Off-the-shelf software or a custom web app?
Before commissioning custom software, look at ready-made products. If one covers 80 per cent of your process, it is usually the cheaper choice. A custom web app makes sense if
- your process is a competitive advantage that no standard product maps,
- you would have to join several standard products with workarounds,
- running licence fees per user over the years cost more than the development,
- you want to own the data and the source code yourself.
An honest test: describe the process in five sentences. If you keep having to say "except when", off-the-shelf software rarely fits.
What to watch for in security and data protection
Once customer or employee data lives in an app, clear requirements apply. Article 32 of the GDPR requires appropriate technical and organisational measures proportionate to the risk. These include, among other things, encryption, the ability to restore data quickly after an incident and a process for regularly testing the measures. If a service provider runs the app, Article 28 GDPR requires a data processing agreement.
Technically, the most important question is about access rights. The list of the most common web application security risks, the OWASP Top 10 in its 2025 edition, ranks "Broken Access Control" first: users can see or change data they should not. So ask every provider how roles and permissions are built and tested. This is general information and not legal advice. For data protection questions, turn to your data protection officer.
How does the switch work?
The safe way is to start small:
- Map the process: where is time lost today, who is involved, which data flows where?
- Pick the core flow: a single sequence that removes the biggest pain comes first.
- Test a prototype: before anything is programmed, two or three future users click through a draft. Changes are still cheap at this stage.
- Bring over the data: existing Excel data is cleaned and imported so nobody works twice.
- Train and extend: the team gets to know the app, more features follow step by step.
At KSTAQ, web apps and internal tools start at €3,999. We agree a fixed price after the process analysis, so you know what is delivered before development starts. Support after launch costs €49 a month. More on the page web apps and internal tools and in the packages. If you plan a product for other people's customers, the guide building a SaaS MVP shows the right path.
Conclusion
Excel stays right as long as one person works with one list. Once several people, permissions, status and customers come in, a fitting web app saves time and avoids errors. Check first whether off-the-shelf software is enough, and start with the process that costs the most time.
Thinking about replacing a spreadsheet with a web app? Describe your process briefly. You will get an honest assessment within one business day, even if the answer is "Excel is enough".