Skip to main content
Service

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 belong to you from the first line.

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

  1. 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.

  2. 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.

  3. 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.

  4. 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.

Common questions

Further reading

Let us talk about Web apps

A conversation where we listen first and then say honestly whether and how we can help.