How much does it cost to build a web application?

A website shows; a web application works. On a website, visitors read pages and perhaps fill in a form. In a web application, people log in and get something done with their own data: book a slot, approve a quote, follow an order, plan a crew. It runs in the browser on any device, with nothing to install, which is also what sets it apart from an app in the App Store or Google Play.

The line is not always sharp. A webshop already has a catalogue, a checkout and orders behind it, and a business website can take bookings through a form. The real difference is who it is for: a website serves anonymous visitors, a web application serves known users with accounts, roles and data that belongs to them.

Most businesses that search for a web application need the middle of the second group: a tool their customers or staff log in to, built around a process that off-the-shelf software handles badly. If you mainly need to be found and to present your business, a website does that for less, and our pricing page lists the packages.

A web application can also behave like an app on a phone: added to the home screen, working full screen and sending notifications. When it must be in the stores, or needs Bluetooth or background location, our guide to what an app costs covers that route.

These are the web applications small and medium-sized businesses have built most often. The ranges show where each one typically lands with us, depending on how far the first version goes.

Look at what the dearer rows have in common: more kinds of users, more systems to talk to, and more rules about who may see what. That is where the money goes, as the next chapter shows.

Two web applications with the same number of screens can differ in price several times over. A screen is quick to draw. What takes time is everything that happens when someone clicks: who may do it, what it changes in the data, which other system needs to know, and what happens when something goes wrong.

Six things move that total more than anything else:

• Users and roles: one kind of user is the cheapest. Every extra role, such as customer, employee, manager or partner, brings its own screens and its own rules about what it may see.
• Integrations: a link to a system with a well-documented API, such as Mollie, Stripe, Moneybird or Exact Online, is routine work. A system without documentation or a test environment can cost more than the rest of the application.
• Existing data: importing years of records from spreadsheets or an old system takes cleaning and checking, and someone has to decide what happens to the messy rows.
• Reports and exports: a list with filters is quick. Reports that combine data in new ways, PDFs in your house style or exports for your accountant each add work.
• Privacy and security: personal data brings duties under the GDPR, and some clients ask for two-factor login, an audit log or data kept in the EU. Each is reasonable; none is free.
• Design depth: a clean design built on proven components costs less than a fully custom interface with its own animations. For a tool staff use all day, clarity matters more than flourish.

These are our indicative ranges for a first version, excluding VAT. Your quote is a fixed price for an agreed scope, so the range turns into one number before any work starts.

For comparison, this is what three other agencies publish. Their ranges start higher than ours in every tier, and definitions differ: what one calls a simple tool, another counts as a portal.

Why are ours lower? We are a small team that designs and builds without hand-offs, on the same modern stack for every project, so the parts every web application needs, such as login, roles, email and hosting, are not reinvented each time. The Haarlem agency MG Software advises a closer look at any quote under €10,000. That is fair advice for every quote, ours included: check that it covers the admin panel, testing, the security check and launch, and ask what happens after.

A web application pays no store fees and faces no yearly operating system deadlines, as a mobile app does. It still runs on a server, holds your customers' data and depends on libraries that receive security updates, so it needs looking after.

Budget for these from the start. A web application nobody maintains keeps working for a while, until a browser update, an expired certificate or a changed API at your payment provider breaks something at the worst moment. Our managed hosting covers hosting, updates and monitoring, and our guide to website maintenance costs breaks the same items down for websites.

Before you have anything built, check whether it already exists. For accounting, email, a general CRM or a standard booking calendar, off-the-shelf software is cheaper, better tested and improved every month by someone else. Build when your process is what sets you apart, when existing tools force your team into workarounds, or when per-user fees grow with every colleague you hire.

With 20 users, the example portal is the cheaper choice from its second year and saves about €13,000 over five years. With 5 users, the subscription stays cheaper all along, because its monthly fee is lower than what your own application costs just to run. Your numbers will differ, but the shape rarely does: the more people use a tool, the sooner your own pays for itself.

No-code platforms and AI app builders sit in between. They are good for a prototype or a small internal tool, and a working prototype makes any quote more accurate. They stop where a web application becomes a business system, because security, data ownership and maintenance remain your job. Our guide to app costs looks at where AI app builders help and where they stop.

A business web application of about eight weeks runs roughly like this. You see working software early and often, so nothing comes as a surprise at the end.

The better you can describe your process, the narrower the quote. You do not need a technical specification. You need to know who uses the application and what they must get done with it.

1. 1

   Describe the people

   Who logs in: customers, staff, partners? How many, on which devices, and how do they do the job today?

2. 2

   Write it as tasks

   One sentence per task: "As a planner, I want to move a job to another day, so the crew sees it at once." Fifteen to forty of these describe most first versions.

3. 3

   Collect what exists

   The spreadsheets, forms and emails the process runs on today. They show the real data and the exceptions.

4. 4

   List your systems

   Accounting, CRM, webshop, calendar: everything the application must talk to, with a contact at each supplier.

5. 5

   Mark the must-haves

   What the first version cannot launch without. Everything else goes on the list for version two.

6. 6

   Name the deadline and the budget

   A season, a contract or a launch date. A budget range lets a studio propose what fits instead of guessing.

With that in hand, ask each studio for a fixed price for the same scope, and compare what is included: design, admin panel, integrations, testing, a security check, launch and support afterwards. Web & app development shows how we work. To get a fixed price and a date for yours, describe your web application; we reply within one working day.