All articles
5 min read

How much does web app development cost?

The price for my Web Application package is €8,200. The services your project needs and any additional costs depend on your workflows, data, and interfaces.

How much does web app development cost?

On my website, the Web Application package is listed at €8,200. It includes an application with user login, custom workflows, a database as needed, and cloud deployment. For more extensive projects, there is the Enterprise package at €12,500.

These prices give you an initial idea of what I offer. We’ll agree on the exact scope before getting started. An application for managing internal requests and a platform for multiple companies can both run in a browser. But the effort involved in developing them can still differ considerably.

So if you want to set a budget, you’ll need to describe what your application actually needs to do. A list of terms such as customer portal, dashboard, and integration isn’t enough on its own.

What your development budget pays for

Development includes clarifying requirements, designing the user experience, and implementing the technical solution. Data needs to be stored, inputs validated, and access permissions put in place. Before launch, the agreed workflows are tested and the application is deployed.

Let’s take a customer inquiry portal as an example. A customer fills out a form and uploads a document. Your team can see the inquiry, process it, and send back the result.

For this process to work, several questions need to be answered. Which fields are required? Which files can be uploaded? Who can see the inquiry? Can the customer change their details later? And what happens if an upload is interrupted?

The answers affect both the user interface and the processing behind the scenes. This is what determines the work that a proposal needs to cover.

Which requirements affect the price

Workflows and exceptions

A request with a status of open or completed is straightforward. If several people need to approve it, deadlines apply, and the request goes back to the applicant if it is rejected, the effort increases.

Each of these rules needs to be described, implemented, and tested. Then there are exceptions: a responsible person is unavailable, information is missing, or an approval that has already been granted is withdrawn.

Describe these scenarios as early as possible. They are part of the workflow and can account for a significant part of the development work.

Users and access permissions

Logging in does not answer the question of who can access what. Perhaps a customer should only be able to see their own orders. An employee handles the orders for their team. A manager needs an overview of several departments.

If multiple companies use the same platform, their data must also remain separate. These rules need to apply to every relevant access point, including downloads and data exports.

The effort also depends on the number and types of roles. A thousand customers with the same permissions may be easier to support than a handful of users with many different permissions.

Connections to other systems

If the application needs to send data to your CRM, retrieve invoices from another system, or synchronize appointments, it needs the right integrations.

What matters here is what the existing software can do. Is there a documented interface? Is the required data available through it? Can the connection be tested in advance?

You also need to account for errors. If another system is temporarily unavailable, you need to decide whether the transfer should be retried and how your team will be notified. A connection that your workflow depends on needs these rules.

Existing data

If you already use spreadsheets or an older application, you’ll often want to transfer its data. To do this, the data needs to be checked and mapped to the new structure.

Duplicate customers, inconsistent spellings, and missing required information can make the transfer more complex. An export alone won’t solve these problems. Ideally, sample data should be available during planning so the work involved can be estimated.

A comparable proposal needs a defined scope

Two proposals titled Customer Portal can include very different services. One may account for design, data migration, and deployment. The other may cover only the technical implementation of predefined screens.

To compare them, you should establish:

  • Which processes can be completed from start to finish using the finished application?
  • Which roles and access permissions are included?
  • Which systems will be connected, and which data will be transferred?
  • Are design, data migration, testing, and deployment included?
  • What support will you receive after launch?
  • How will additional requirements be agreed on during the project?

The last point in particular deserves a clear agreement. A correction to an agreed feature and an additional workflow affect the scope in different ways. The proposal should explain how these will be handled.

Costs after launch

Once the application is deployed, people start using it. Your budget should therefore also account for ongoing expenses.

Depending on how it is built, there may be costs for hosting, databases, file storage, and backups. External services can involve additional fees, for example for sending messages or processing payments. Some charge based on usage, while others have fixed pricing.

Maintenance and further development also need an agreed framework. Technical components are updated, bugs are fixed, and new requirements are implemented. The scope depends on how the application is used and what level of support you need.

An internal application for occasional requests has different availability and support requirements from a customer portal that receives orders every day. These differences should be factored into the cost plan before development begins.

How to prepare for a cost estimate

You don’t need a finished technical specification for an initial estimate. Describe a typical process from start to finish. Add who is involved, which software you already use, and what data you have.

It’s also helpful to share your budget range and preferred launch date. Then we can assess what scope is feasible within it and which requirements need further investigation.

If your budget is limited, I’d start by fully supporting one frequently used process—for example, recording and handling a customer inquiry. An additional report can come later. This lets you keep the initial scope limited while putting the application to use in your day-to-day work.

Tell me about your project and the workflows you’d like to simplify. Before development begins, we’ll clarify the scope, open questions, and a suitable budget range.