Short answer: In 2026, a custom web application costs $15,000–$50,000 for an MVP, $50,000–$120,000 for a full-featured product, and $120,000–$300,000+ for a complex platform (marketplaces, fintech, multi-tenant SaaS). Where you build matters as much as what you build: the same app costs 2–4× more with a US agency than with a senior team in Vietnam. Here's the full breakdown so you can budget with real numbers.

Web app development cost in 2026 at a glance

ComplexityExamplesVietnam / offshore (USD)US / Western Europe (USD)Timeline
SimpleLanding site + forms, internal tool, dashboard$8,000 – $25,000$30,000 – $80,0004–8 weeks
Medium (MVP)SaaS MVP, booking system, customer portal$25,000 – $60,000$80,000 – $200,0002–4 months
ComplexMarketplace, fintech app, multi-tenant SaaS$60,000 – $150,000$200,000 – $500,0004–8 months
EnterpriseRegulated-sector platform, high-scale system$120,000 – $300,000+$400,000 – $1M+6–12+ months

Where the money actually goes

A typical web app budget splits roughly like this:

  • Backend & APIs (30–40%): business logic, database design, authentication, integrations. This is where complexity hides — payments, permissions, and third-party systems cost far more than screens.
  • Frontend (25–35%): the interface users see. Costs scale with the number of distinct screens and interactive complexity, not with how "pretty" it looks.
  • UI/UX design (10–15%): flows, wireframes, and visual design. Skimping here is false economy — design rework after code is written costs 3–5× more.
  • QA & testing (10–15%): manual and automated testing. Every dollar cut from QA returns as post-launch bug-fixing at a higher rate.
  • DevOps & infrastructure (5–10%): CI/CD, hosting setup, monitoring, security hardening.
  • Project management (10%): the coordination that keeps the other 90% from going sideways.

The cost drivers nobody tells you about

1. Integrations

Every external system — payment gateway, CRM, accounting software, government API — adds $3,000–$15,000 depending on documentation quality and edge cases. An app with five integrations can spend a third of its budget on them.

2. User roles and permissions

"Admins can see everything, managers can see their team, users see their own data" sounds simple and is not. Role-based access touches every feature. Each additional role type adds 5–10% to backend cost.

3. Real-time features

Live chat, notifications, collaborative editing, and live dashboards require different architecture (websockets, event systems) than standard request/response apps. Budget 15–25% extra if real-time is core to the product.

4. Scale assumptions

An app for 500 internal users and an app for 500,000 consumers are different builds. Premature scaling wastes money; ignoring scale creates rewrites. We covered the failure patterns in what actually breaks when your product scales.

5. The "second 90%"

Password reset, email templates, error states, admin tools, data export, audit logs — features no one lists in the brief but every real product needs. Good estimates include them; cheap estimates surface them as change requests.

MVP strategy: how to spend less and learn more

  1. Cut scope, not quality. A polished app that does three things beats a buggy app that does ten. Launch with the one workflow users would pay for.
  2. Use boring, proven technology. Standard stacks (React/Next.js, Node or Python backends, PostgreSQL) are cheaper to build, staff, and maintain than exotic choices.
  3. Buy, don't build, the commodity parts. Auth (Supabase/Auth0), payments (Stripe), email (Resend), file storage — using managed services saves weeks of engineering.
  4. Fixed-price the MVP, then move to a dedicated team. Fixed price de-risks the first build; a small ongoing team iterates after launch when scope is genuinely unpredictable.

Web app vs mobile app: which first?

If your users work at desks or your product is B2B, start web — it's 30–40% cheaper than building native iOS + Android, ships to all platforms instantly, and modern responsive web apps handle most mobile use cases. Go mobile-first only when your product depends on camera, GPS, offline use, or push-driven daily habits. Many of our clients launch web first, validate, then add mobile — like Azuki's fashion-tech app once the model was proven.

How to compare proposals (and spot the lowball)

  • Demand a feature-level breakdown, not one big number. Vague estimates hide either padding or missing scope.
  • Check what's included: design, QA, project management, DevOps, warranty period, documentation. The cheapest quote usually excludes half of these.
  • Ask about the team composition — how many seniors vs juniors will actually write your code?
  • Verify reviews on Clutch or GoodFirms and ask to speak to one past client.
  • Confirm you own the source code and IP from day one, with repository access in your accounts.

For a broader view of rates by role and engagement model, see our custom software cost guide for Vietnam. When you're ready to scope your project, our software systems team will give you a feature-level estimate — or just tell us what you're building.

Frequently Asked Questions

How much does it cost to build a web app in 2026?

Most business web apps cost $25,000–$120,000 with an offshore senior team, or $80,000–$400,000 with a US/European agency. Simple internal tools start around $8,000; complex platforms like marketplaces or fintech products exceed $150,000.

How much does a SaaS MVP cost?

A production-ready SaaS MVP — authentication, billing, core workflow, admin panel — typically costs $25,000–$60,000 with a Vietnamese team and takes 2–4 months. The same scope in the US commonly runs $100,000–$250,000.

What is the monthly cost to maintain a web app?

Plan for 15–20% of the build cost annually. That covers hosting ($100–$2,000+/month depending on scale), security updates, dependency upgrades, monitoring, and small improvements. A $60,000 app therefore needs roughly $750–$1,000/month in ongoing investment.

Why do web app quotes vary so much between agencies?

Three reasons: geography (US rates are 2–4× Asian rates), what's included (design, QA, PM, warranty — or just raw coding), and how honestly the estimate covers the unglamorous features every product needs. Compare feature-level breakdowns, never headline numbers.

Can I build a web app for under $10,000?

Yes, if scope is genuinely small: an internal tool, a dashboard over an existing database, or a single-workflow app using managed services for auth and payments. At this budget, ruthless scope discipline matters more than the hourly rate.