---
title: "Getting a web application built: cost, examples and process in 2026 | Codavo"
canonical_url: "https://codavo.nl/en/blog/build-a-web-application"
last_updated: "2026-07-26T00:00:00.000Z"
meta:
  description: "Getting a web application built? See realistic costs, examples, timelines, scope and a practical process for a secure custom web app."
  "og:description": "Getting a web application built? See realistic costs, examples, timelines, scope and a practical process for a secure custom web app."
  "og:title": "Getting a web application built: cost, examples and process in 2026"
---

Codavo homepage

Advice·March 20, 2026· [ Sjoerd Ligtvoet](https://codavo.nl/en/about)

# Getting a web application built: cost, examples and process in 2026

Getting a web application built? See realistic costs, examples, timelines, scope and a practical process for a secure custom web app.

Getting a **web application built** costs from €5,000 excluding VAT at Codavo and usually takes 4 to 8 weeks for a focused first version. A typical custom application with user roles, an admin area and integrations usually lands between €10,000 and €15,000. The right starting point is not a list of every desired feature. It is one complete workflow that measurably removes time, errors or frustration for a user.

Examples include a client portal, internal dashboard, planning system, booking tool or SaaS product. They have one thing in common: users sign in, work with current data and take actions. If you only need a public page where people read information, a [**custom website**](https://codavo.nl/en/websites) is probably the more suitable and affordable option.

## What is a web application?

A web application is software that runs in a browser. Users generally do not need to install anything: they open the application on desktop, tablet or phone and see only the functions and data relevant to their role.

|  | **Website** | **Web application** |
| --- | --- | --- |
| Main purpose | Inform and persuade | Run or automate a process |
| Users | Visitors | Often signed-in clients or employees |
| Data | Primarily published content | Current data from a database |
| Interaction | Read, submit a form | Read, add, edit, approve and pay |
| Examples | Company site, landing page, blog | Portal, dashboard, planner, SaaS product |

A website and a web application can work together. The website attracts new customers; the application helps existing customers or employees get work done.

## Six web application examples

The figures below are realistic ranges for a useful first version, not fixed packages. Data migration, exceptions and external systems can expand the scope.

| **Example** | **What the user does** | **First-version indication** |
| --- | --- | --- |
| Client portal | View status, download documents and send messages | €5,000–€10,000 |
| Internal dashboard | Manage workload, KPIs and exceptions | €5,000–€12,000 |
| Planning tool | Schedule people, equipment or appointments | €8,000–€15,000 |
| Workflow app | Route, approve and follow up requests | €8,000–€15,000 |
| Booking or payment platform | Show availability, reserve and pay | €10,000–€20,000 |
| SaaS MVP | Serve multiple clients with subscriptions and separate workspaces | €10,000–€20,000+ |

In the [**Van Maaren investment portal**](https://codavo.nl/en/portfolio/van-maaren), investors see their own portfolio overview. [**Opairly**](https://codavo.nl/en/portfolio/opairly) is a SaaS product in which au pair families coordinate their household and agreements. The products look different, but they use the same building blocks: roles, data, actions, notifications and administration.

## When is custom software the right choice?

A custom web application is most valuable when an important process is unique or existing software demonstrably creates extra work. Think of employees copying information between Excel, email and a CRM, customers repeatedly asking for the same status, or exceptions that do not fit a standard product.

Custom development often makes sense when:

- several people need to work with the same current data;
- manual handovers cost hours every week;
- customers or partners need secure self-service;
- different systems need to cooperate through APIs;
- you are building a digital product with its own business model;
- errors, waiting time or missing visibility directly cost revenue.

Custom is not automatically better. If an existing SaaS product covers 90% and the remaining workarounds are cheap, configuring it is often smarter. You should not automate an unstable process too early either: software mainly makes an unclear workflow unclear at greater speed.

If you are unsure, read the [**five signs you need a web application**](https://codavo.nl/en/blog/do-you-need-a-webapp).

## What determines the scope?

The price is not determined by the number of screens alone. One overview with complicated permissions and data flows can require more work than ten simple pages. These elements determine scope:

1. **Users and roles.** Who may view, change, approve or export which data?
2. **Core workflow.** What event starts the process and when is it successfully complete?
3. **Data model.** How do customers, orders, cases or appointments relate?
4. **Admin area.** What should an administrator change without a developer?
5. **Integrations.** Consider accounting, CRM, payments, email or industry software.
6. **Migration.** Do existing spreadsheets, documents or customer records need to move?
7. **Notifications and reporting.** Who receives an email, task or warning and when?
8. **Non-functional requirements.** Security, privacy, logging, speed and availability.

A strong scope describes user scenarios rather than isolated features. “An employee can assess a request and the customer automatically receives the outcome” is clearer and easier to test than “we need a dashboard and email”.

## How much does a web application cost?

| **Level** | **Typical scope** | **Investment** | **Timeline** |
| --- | --- | --- | --- |
| Small first version | One role, one core workflow, limited administration | €5,000–€10,000 | 4–6 weeks |
| Typical custom app | Several roles, administration and 1–3 integrations | €10,000–€15,000 | 6–10 weeks |
| Complex platform | Multi-tenant, payments, migration or many integrations | €15,000+ | 10+ weeks |

The greatest cost drivers are often not visual design but exception rules, permissions, poor source data and integrations without a reliable API. A proposal should therefore state exactly what is included, which assumptions apply and how extra work is approved.

After launch, simple hosting often costs €0 to €20 per month. If you want active maintenance, monitoring and small improvements, Codavo offers [**Maintenance or Growth**](https://codavo.nl/en#pricing); active maintenance starts at €175 per month. Hosting keeps the application available. Maintenance keeps the software healthy and current.

## The development process in four phases

### 1. Define the problem and first version

We map the users, current tools, bottlenecks and desired outcome. We then select the smallest complete workflow that produces value by itself. You receive a proposal with scope, timeline, investment and explicit assumptions.

### 2. Design the product and technical foundation

The main screens, user roles and data flows are designed. We also decide how authentication, backups, logging and integrations work. That prevents security or operations from being bolted on at the end.

### 3. Build and test iteratively

You see a working version regularly and test it with recognisable scenarios. Feedback is about real behaviour instead of static mock-ups. Automated tests protect critical parts; acceptance tests confirm that the agreed workflow works in practice.

### 4. Migrate, launch and improve

Existing data is cleaned and imported in a controlled way. After a short parallel period, the team moves to the new source of truth. Actual usage then determines which improvement creates the most value.

The [**way I work**](https://codavo.nl/en/how-i-work) page describes this process in more detail.

## Security, privacy and ownership

A production application needs more than a login. It needs role-based access, secure sessions, encrypted transport, backups, logging, input validation and a recovery path when an integration fails. The [**OWASP Application Security Verification Standard**](https://owasp.org/www-project-application-security-verification-standard/) provides a public set of requirements for designing and verifying web application security.

Ask a supplier specifically:

- where data is stored and who has access;
- how roles and permissions are tested;
- what happens when a payment or API integration fails;
- how backups are made and restored;
- whether you own the code, accounts, domains and data;
- what documentation is needed to transfer the system later.

With Codavo, the client retains ownership of code and data. I use modern, widely supported technology such as Nuxt, Cloudflare and Supabase, but product decisions start with the process—not a favourite tool. Read more in my [**technology stack**](https://codavo.nl/en/blog/tech-stack).

## How do you choose a web application developer?

A strong technical partner can build, but can also remove features and explain decisions. Look for these signals:

- the proposal names user scenarios and acceptance criteria;
- risks and assumptions are visible rather than hidden;
- you speak directly with someone who can make technical decisions;
- comparable live projects are available;
- source code, accounts and data remain transferable;
- there is a concrete operations plan for after launch;
- the partner will recommend standard software when custom development is not worthwhile.

Comparing an independent developer with an agency? See [**Codavo versus a web agency**](https://codavo.nl/en/compare/agencies).

## From idea to a focused first version

Write down three things before an initial call: who the primary user is, which task currently costs the most time or money, and how you will know the new workflow is better. That is usually enough to determine whether you need a website, integration, standard product or custom web application.

Want to get a **web application built**? Explore [**custom web applications**](https://codavo.nl/en/web-applications) or [**book a free call**](https://codavo.nl/en/contact). You will get an honest first assessment of scope, risks, investment and a sensible first version.

## Frequently asked questions

[**Get a SaaS MVP built: cost, scope and timeline in 2026**](https://codavo.nl/en/blog/build-a-saas-mvp) [**Custom website or WordPress: the honest comparison**](https://codavo.nl/en/blog/custom-vs-wordpress)