Quick answer: Web app development cost is estimated hours multiplied by an hourly rate. The hours come from your screens, user roles, business rules and integrations. The rate comes from who builds it and where. To get a realistic figure, list your must-have features, ask developers for hours per feature, then add hosting and maintenance. A small first version keeps the cost under control.

Search for web app prices and you will find numbers that are miles apart. One page says a few thousand dollars. Another says six figures. Both can be true, which does not help you plan a budget.
I am a WordPress and Shopify developer, and custom web apps are a newer part of my work. So I will not pretend to have a secret price list. What I can give you is the method developers actually use to price a project, so you can judge any quote you receive.
By the end you will be able to estimate your own project and see where the money goes.
Table of Contents
Why web app prices vary so much
A web app is not one product. A booking form with a login and a full marketplace are both called web apps. The work behind them is completely different.
Almost every quote is built the same way: estimated hours multiplied by an hourly rate. Hours depend on your feature list. The rate depends on who builds it and where they live. Change either one and the total moves a lot.
So instead of asking for one magic number, look at the things that create hours.
The 7 things that decide web app development cost
| Driver | Cheaper when | More expensive when |
|---|---|---|
| Number of screens | A handful of simple screens | Dozens of screens with many states |
| User roles | One type of user | Admin, staff, customers and partners with different permissions |
| Data and logic | Simple forms and lists | Calculations, approvals, schedules, reports |
| Integrations | None, or one payment gateway | Several third-party systems that must stay in sync |
| Design | A clean UI kit | Fully custom design with animation |
| Real-time features | Not needed | Live chat, live tracking, notifications |
| Security and compliance | Standard login and backups | Sensitive data, audits, industry rules |
Integrations surprise people most. Connecting a payment gateway, a courier, an accounting tool or an old internal system often takes longer than building the screens. Each one has its own rules, limits and failure cases.
Three project sizes, in plain terms
I find it more honest to talk about size than to throw out a price.
- Small. One clear job, one or two user roles and a few screens. For example an internal tool that replaces a spreadsheet. Usually a matter of weeks.
- Medium. Several connected features, payments, an admin panel, email notifications and reports. For example a booking system or a restaurant online ordering system. Usually a few months.
- Large. Many roles, heavy logic, several integrations and a need to scale. Marketplaces and SaaS products sit here. This is long-term work for a team, not a single developer.
Most small business ideas start as small or medium. If your first version looks large, the scope is probably too big for a first version.
How to estimate your own project
You can get a rough figure before you talk to anyone. It takes about an hour.
- List every screen. Login, dashboard, each form, each list, each settings page. Write them all down.
- List every rule. Who can see what, what happens after each action, which emails are sent.
- List every integration. Payments, SMS, email, maps, accounting, anything outside your app.
- Mark each item must-have or later. Be strict. The first version only needs the must-have items.
- Ask two or three developers for hours per item. Not a total. Hours per line make quotes easy to compare.
- Multiply by the rate and add a buffer. Testing, fixes and small changes always take time, so leave room for them.
Here is the arithmetic with made-up numbers, only to show how it works. If your must-have list comes to 200 hours and the rate is $25 an hour, the build is $5,000. At $100 an hour the same list is $20,000. Same app, same hours, different rate. This is why two honest quotes for the same project can be far apart.
Costs after launch that people forget
The build is not the whole bill. Plan for these as well.
- Hosting. A server or cloud plan, paid monthly.
- Third-party services. Email sending, SMS, maps and payment gateway fees.
- Maintenance. Security updates, backups and dependency upgrades.
- Bug fixes and small changes. Real users always find things nobody planned for.
- New features. A useful app keeps growing. Budget for a second phase.
Ask every developer what the monthly running cost will be. If they cannot answer, they have not thought about your project past launch day.
How to lower the cost without hurting quality
- Build the smallest useful version first. Launch, learn from real users, then add features.
- Use what already exists. Login, payments and email do not need to be invented again. Good libraries and services save many hours.
- Consider a progressive web app. One codebase runs in the browser and can be installed on phones, so you may not need separate mobile apps at the start. MDN has a clear introduction to progressive web apps.
- Start from a platform when it fits. If your idea is mostly content, products or bookings, WordPress with a custom plugin can do it for far less than a fully custom app.
- Buy before you build. For common jobs like invoicing, ready-made software is often enough. I compared both paths in invoice software for small business.
- Write things down. Unclear requirements are the most expensive part of any project. Every change in the middle of the build costs more than the same decision made at the start.
Fixed price or hourly?
Both models work. They suit different situations.
| Model | Good when | Watch out for |
|---|---|---|
| Fixed price | The scope is clear and written down | Changes need a new quote |
| Hourly | The idea is still changing | The total is open, so ask for weekly reports |
| Fixed price per phase | Larger projects | Each phase needs its own clear scope |
For a first version I prefer a fixed price per phase. You know the cost of each step, and you can stop or change direction between phases. It is the same approach I use for websites, which I explain in my WordPress development cost guide.
What I can honestly offer
My main work is WordPress, WooCommerce and Shopify. I also build custom tools on top of them: order systems, billing features, dashboards and AI agent integrations. For standalone apps in React I take on small, clearly scoped projects.
If your idea needs a large team, I will tell you so. If it can be done on a platform you already use, I will tell you that too, because it will save you money.
Frequently asked questions
How much does it cost to build a web app?
There is no single price. The cost is the hours needed for your features multiplied by the developer rate, plus hosting and maintenance. A written feature list is the only way to get a real quote.
What is the biggest factor in web app development cost?
Scope. The number of screens, user roles, rules and integrations decides the hours. Cutting the first version down to must-have features lowers the price more than anything else.
Is a web app cheaper than a mobile app?
Often, yes. One web app works on every device through the browser, while native apps usually need separate builds for iOS and Android.
Can WordPress be used instead of a custom web app?
Sometimes. If the idea is mainly content, products, bookings or forms, WordPress with a custom plugin can cover it at a lower cost. Heavy real-time or complex logic is better as a custom app.
Have an idea and want a straight answer on scope? Send me your feature list and I will tell you what it would take, or whether a simpler option fits. You can see what I build on my development services page.


