It is the first question we get and the hardest to answer with a number. Not because we are dodging it, but because “web application” covers things that differ by an order of magnitude: a form that saves orders and a multi-warehouse inventory system with role-based permissions are both web applications.
What can be explained precisely is what drives the price. With that you can evaluate any quote that lands on your desk, from us or anyone else.
The five factors that move the price
1. Number of modules
Each functional area is independent work: screen design, logic, database and testing. An application with inventory, sales and reporting costs roughly three times one with inventory alone. There is no economy of scale here; there is more surface area.
2. User types and permissions
An application where everyone sees the same thing is considerably simpler than one where the administrator sees everything, the salesperson sees only their own sales and the warehouse clerk sees only stock. Every permission rule has to be implemented and, more importantly, tested on every screen.
3. Integrations
Connecting to a payment gateway, an accounting system or an existing ERP can be quick or it can be half the project. It depends entirely on whether the other system has a documented API. If it does not, much of the work is discovering how it stores data.
4. Design
Using an existing component system is fast. A bespoke design, with brand identity and screens considered one by one, is separate work that adds up.
5. Expected volume
An application for ten internal users and one for ten thousand concurrent users are not built the same way. The second needs architecture, caching and infrastructure decisions the first does not justify. Be honest about the real expected figure: over-engineering costs as much as under-engineering.
Why to distrust a price given over the phone
If someone gives you a firm number without having looked at your processes, they are doing one of three things: pricing high to cover themselves, pricing low to close the sale and renegotiate later, or selling you a template they will try to bend around your business.
A serious quote comes after a conversation about what you do today, with which tools, and where time gets lost.
Questions to ask before signing
- What exactly does the price include? Design, development, deployment, testing, training — each of these can be in or out.
- Who owns the code? If they do not hand it over, you are tied to that vendor permanently.
- What happens if scope changes? There should be a clear mechanism for quoting extensions.
- What does it cost to maintain? Development is one payment; hosting, domain and maintenance are recurring.
- Can I see it working before the end? If the answer is no, the risk is entirely yours.
How to reduce cost without wrecking the project
The most effective route is not negotiating the hourly rate, but reducing the scope of the first version. Identify the process that eats most of your time today, build that, put it into production and grow from there.
It has two advantages over building everything at once: the upfront outlay is far smaller, and by the time you build the second module you will understand much better what you need, because you will have been using the first one.
Want an estimate for your specific case? Tell us what you need and we will come back with a detailed scope and quote. The initial consultation is free. You can also read how we work on web application development.