How much does a web app cost? 2026 ranges from MVP to full product
An MVP web app costs US$30,000 to 120,000 from a small studio and US$10,000 to 40,000 from a freelancer. What drives the price and what it costs to run.
By Sohail Hussain29 October 20267 min read
As of October 2026, a first version of a web app, an MVP with accounts, one core workflow, payments and a basic admin area, costs US$30,000 to 120,000 from a small studio, US$10,000 to 40,000 from a freelancer or a two-person team, and US$100,000 to 400,000 from a larger agency. A clickable prototype to test the idea runs US$3,000 to 15,000. A full product with multiple user roles, integrations, reporting and billing is US$80,000 to 300,000 at a studio and often past a million at an agency.
Those ranges are wider than for websites because apps vary more. Two products with the same number of screens can differ five-fold in cost depending on roles, data, integrations and how much can go wrong. This guide sets out what is in each tier, what moves the price, what it costs to run, and when building is the wrong move.
What does each stage of a web app cost?
| Stage | What it includes | Freelancer or small team | Small studio | Larger agency |
|---|---|---|---|---|
| Clickable prototype | Designed screens in Figma, linked, no code | US$1,500 to 5,000 | US$3,000 to 15,000 | US$15,000 to 50,000 |
| Internal tool | One or two roles, forms and tables, no public sign-up | US$5,000 to 20,000 | US$10,000 to 60,000 | US$50,000 to 150,000 |
| MVP | Sign-up and login, one core workflow, payments, basic admin, hosting and monitoring | US$10,000 to 40,000 | US$30,000 to 120,000 | US$100,000 to 400,000 |
| Full product, version one | Multiple roles, team accounts, integrations, reporting, billing, onboarding | US$40,000 to 120,000 | US$80,000 to 300,000 | US$250,000 to 1,000,000+ |
The freelancer column is the hardest to use well. A strong solo developer can build an MVP for US$20,000 that would cost a studio US$60,000. The same project with a weak one costs US$20,000 and then US$60,000 again to rebuild. Ask to see a product they built that is still running, and talk to the owner.
Our web app and SaaS development work sits in the studio column: product scoping, interface design, a TypeScript stack with Next.js, Node.js and PostgreSQL, accounts and billing, admin tools, and hosting and monitoring set up before launch. Most MVPs we scope land in the lower half of that range because scoping is where the money is saved.
For how these numbers compare with websites, stores and mobile apps, the main guide to how much a website costs has the full table.
What drives the cost of a web app?
Six things explain most of the spread. In rough order of impact:
Number of user roles. Every role is a set of permissions, screens and edge cases. A product with customers only is one product. Customers, their team members, your staff and a super-admin is four, and the permission matrix between them is where bugs live. Each role after the first adds 15 to 30 percent.
Core workflow complexity. "Upload a document and get a summary" is one workflow. "Create a project, invite collaborators, assign tasks with deadlines, track status, comment, get notified, export a report" is six workflows that look like one feature on a slide.
Integrations. Stripe for billing, a CRM, an accounting system, an email provider, a WhatsApp API, a government e-invoicing portal. Each is two days to two weeks, and the ones with poor documentation take longer. Budget US$2,000 to 10,000 per integration at studio rates, as of October 2026.
Data. Importing existing data from spreadsheets or an old system, cleaning it, and handling the cases that do not fit the new structure. Clients consistently underestimate this. A migration from three years of spreadsheets can be a fifth of an MVP budget.
Design. A product that uses a component library like shadcn/ui with sensible defaults costs much less to design than one with a bespoke visual system. For an MVP, bespoke design is rarely the right spend.
Reliability requirements. An internal tool used by five people can go down for an hour. A product that customers pay for needs error tracking, backups, a staging environment, automated tests on the money paths, and someone on call. That is real cost and the first thing cheap quotes omit.
How do hourly rates turn into these prices?
Most web app quotes are hours multiplied by a rate, even when presented as a fixed price. As of October 2026, typical rates are:
| Supplier | Hourly rate | Notes |
|---|---|---|
| Freelancer, India or Eastern Europe | US$15 to 60 | Wide quality range |
| Freelancer, US, UK or Western Europe | US$60 to 150 | |
| Small studio, India | US$25 to 60 | Including design and project management |
| Small studio, US or UK | US$80 to 180 | |
| Larger agency | US$120 to 300 | Blended rate across roles |
An MVP is usually 600 to 1,500 hours across design, development, testing and management. Multiply by the rate and you get the table above. This is also why the same scope is US$35,000 from an Indian studio and US$140,000 from a London one: the hours are similar; the rate is not. For whether to buy on a fixed price or by the hour, read fixed price versus hourly, and for comparing a studio against hiring your own developers, see freelancer versus agency versus in-house.
What does it cost to run a web app after launch?
The build is the start. As of October 2026, a small SaaS product typically spends:
- Hosting: US$20 to 300 a month on Vercel, Railway, Render or a cloud provider for the app and database at low to moderate traffic; see Vercel's pricing for the common starting point. Databases, file storage and background jobs add to this as usage grows.
- Third-party services: US$50 to 500 a month for authentication, transactional email, error tracking, analytics and uptime monitoring. Most have free tiers that run out around your first few hundred users.
- Payment fees: Stripe takes a percentage plus a fixed fee per transaction; the current rates are on Stripe's pricing page. Build this into your prices.
- Maintenance and small improvements: 15 to 25 percent of the build cost per year is the usual planning figure. A product that does not change is a product that is dying, so most owners spend more.
- AI features, if any: token costs that scale with use. The AI API cost calculator turns requests per month and tokens per request into a monthly bill.
The guide to what to log and monitor from day one covers the minimum set of services and why they are worth paying for.
When should you not build a web app?
A studio that only says yes is a studio to avoid. Cases where building is the wrong spend:
- The problem is solved by an existing product. If Airtable, Notion, a CRM or a SaaS tool does 80 percent of what you need for US$50 a month, the remaining 20 percent is rarely worth US$60,000. The guide to custom software versus off-the-shelf has a decision list.
- You have not spoken to ten potential customers. A prototype and ten conversations cost US$5,000 and a month. An MVP nobody wants costs ten times that.
- The core workflow is unclear. If you cannot describe the first screen a paying user sees and what they do on it, you are not ready to build. Scope first; how to scope an MVP in one week walks through it.
- You want every feature in version one. The cost table is for a product with one core job. Version one with everything costs version-three money and launches a year late.
The honest case for building is a workflow that no existing tool handles well, customers who have said they would pay, and a first version small enough to launch in three to four months.
How do you get a quote you can trust?
Write the brief before you ask for prices: who the users are, the one thing they must be able to do, which systems it must connect to, what data exists today, and the budget range. The website brief guide applies with small changes, and the guide to what is an MVP helps you draw the line around version one.
Ask every supplier for a scope document, not just a number: screens, roles, integrations and what is excluded. Two quotes with the same scope document are comparable; two numbers are not. For a rough figure before you start, the app development cost calculator takes platforms, features, backend and design level and shows a range with its assumptions. It is built around mobile apps, but the feature and backend inputs map directly to a web app.
Was this guide useful?