Web apps that solve a process, not a wish list
Customer portals, booking systems and internal tools: front end, back end, database and user management from one source, cut to fit one workflow.
Most requests for a custom web app are solved faster and more cheaply with off-the-shelf software. We say so before writing a quote, not afterwards. A ready-made tool that fits eighty per cent almost always beats a bespoke build that fits perfectly and costs many times more.
Three things turn that sum around. Your workflow is the reason customers buy from you and will not be forced into somebody else's form. You are holding several systems together with spreadsheets and copy-and-paste, losing hours every week. Or the per-seat licence cost is growing faster than your team.
A web app rarely gets expensive because of the technology; it gets expensive because of scope. So we first decide what the first version deliberately will not contain, and ship a lean, usable build rather than spending months on concepts. Source code, data and access sit with you: the repository on your account, and on final payment you receive all usage rights and the complete source code.
Who this suits
A fit if
- Your workflow is your edge and fits no off-the-shelf product
- You currently hold several systems together with spreadsheets and copy-and-paste
- Per-seat licence costs are growing faster than your team
- You can name someone who settles domain questions within a few days
Not a fit if
- There is a ready-made tool for your case that fits eighty per cent
- The plan is an idea with not one concrete workflow behind it yet
- You need a conventional online shop with a basket and payment processing
- A fixed price before any analysis is a condition for you
What is included
- Analysis of the workflow the application replaces, including the exceptions currently handled by shouting across the room
- Front end, back end and data model designed together rather than assembled from parts
- User management with roles and permissions, sign-in, password recovery and audit logging
- Interfaces to the systems that stay: accounting, calendar, payment provider, CRM
- Deployment, monitoring and security updates after launch, with source code and data in your hands
How we work
- 01
Scoping
We walk through the workflow the application is to take over and separate the core from everything that can come later. The result is a list of what the first version deliberately leaves out.
- 02
First version
We build the core, with real data and real user roles. Not a prototype to look at, but a build your team can work with on Monday.
- 03
Live pilot
A small group uses the application alongside the existing route. What surfaces there is worth more than any requirements list, because it comes from daily work rather than assumption.
- 04
Extension and operation
Extensions follow usage, not a wish list. Alongside that run updates, backups and monitoring, so the application does not quietly rot once nobody is watching.
What it costs
There is no credible fixed price before the analysis, and any figure quoted would either be costed to the bare minimum or drawn so wide it says nothing. For orientation: providers and experienced freelancers in Germany currently work at roughly 100 to 160 euros net per hour, and for a first usable version of a B2B application German providers quote market corridors starting around 15,000 euros net. Those are researched market ranges, not a commitment. A tightly scoped internal tool sits well below that, and that is exactly where we prefer to start; you get your figure after scoping, with the reasoning attached.
See pricingCommon questions
Why do you not quote a fixed price?
Because the price depends entirely on scope, and before the analysis nobody knows the scope, you included. A fixed price without analysis is either a teaser that gets recovered through change requests, or a risk premium you pay for. We scope first, then cost, and you get a figure with reasoning instead of a guess.
How long does a first usable version take?
That depends on scope, not on technology. An internal tool with one clear workflow and few roles is a matter of weeks; a portal with payment processing, several user groups and connections to existing systems is more a matter of months. It can only be stated reliably after scoping, and then we do state it.
Who holds the rights to the source code and the data?
You do. The repository runs on your account, the data sits in a database you can access, and the hosting and service accounts are in your name. You receive the full usage rights in the source code on final payment. Providers who hand over only a login and keep the code make a later move expensive or impossible. Check for that before you sign, with us as with anyone else.
What does running it cost after launch?
Considerably less than development, but not nothing. There are hosting and database costs, plus effort for library updates, security patches and small adjustments. We cost that in before the start, because an application without maintenance ages faster than most people expect. Your website's care contract covers your website, not the operation of a bespoke application.
What happens if the studio drops out?
A fair question for a studio this size, and the answer is preparation rather than reassurance. We build on widely used standard technologies, not on a house framework only we understand. The code sits with you, documented and with setup instructions, and any developer with an ordinary toolkit can take over. That handover readiness is part of the work, not an extra.
Further reading
- WordPress or Custom Build? Run the Five-Year NumbersWordPress powers a large share of the web, and for good reasons. What it actually costs to run, where it wins outright, and when a custom build makes sense.
- Off-the-Shelf vs. Custom Web App: The Honest AnswerWhy off-the-shelf software is usually the right call, the three signals that actually justify a custom web app, and when a custom build is not worth it.
- Custom Web App Development: Cost, Drivers and the MVP PathWhat a custom web app costs, the four factors that actually drive the price, why we do not quote a flat rate, and how a lean MVP makes for a smarter start.
- Web App Development: The Process From Discovery to OperationThe five phases of a web app project, realistic timelines, your own role in the process, and how to spot a provider who actually understood your problem.
- Headless CMS 2026: What Actually Makes Sense for SMEsWhen a headless CMS is worth the extra effort, when a classic system is enough, and why storing content as code is a third option worth considering.
- Web Design for Online Shops 2026: Platform or Custom Build?When an established shop platform is the better choice, when a custom build pays off, and which levers improve any shop regardless of platform.
Let us talk about Web apps
A conversation where we listen first and then say honestly whether and how we can help.
Message us on WhatsApp