How much does it cost to build a web app in 2026? Published prices, hourly rates and a worked estimate

The short answer

A first version of a web app costs from about USD 8,000 for one focused workflow built by a small studio to USD 50,000 or more for an MVP with accounts, payments, an admin panel and integrations. Those are the published figures we read in October 2026: studios on Dribbble list fixed-scope app builds at USD 8,000 (Musemind) and USD 9,900 (Geex Arts), and Upwork's planning range for a custom web application is USD 10,000 to 50,000.

Larger products cost far more. Clutch puts the average software project reviewed on its platform at USD 132,480, with most between USD 10,000 and 49,999 and a usual timeline of about 13 months. Every one of those numbers is hours times a rate, so this guide shows the rates, the components that add hours, a worked estimate with the arithmetic, and what the app costs to run each month.

If your project is a marketing site rather than an app, our guide to what a website costs in the US is the better starting point, and our website cost calculator prices a custom site or platform from published prices in four markets.

Published web app prices (read in October 2026)

Upwork's, Clutch's and the BLS's pages refused our automated read, so those figures come from the Internet Archive's captures from July to mid-October 2026. Altar.io lists more examples on the same page, up to EUR 350,000 for a five-month AI product; the range is the point.

Two cautions. The fixed prices at the top buy a narrow scope: four screens, or one product area. And Clutch's averages are pulled up by large projects; it publishes no median, so read the "most projects" band as the more useful number.

Hourly rates: what an hour of development costs

The BLS figure is a floor for US work, not a price: it's what an employer pays in wages, before benefits, tools, management and profit. An agency rate of USD 150 an hour is more than twice that wage, which covers those costs plus the people who aren't billing at any given moment.

What drives the cost: the components

The page count of an app tells you little. The components do. These are the ones that add the most hours to a first version, and what each one adds to the monthly bill:

Two of those rows can shrink a lot with the right architecture. Payments: when Stripe Checkout or Elements collect the card in an iframe served from Stripe's domain, card data never touches your servers, and Stripe says businesses below its top volume tier can validate PCI DSS compliance with the short SAQ A questionnaire (Stripe). Accounts: a hosted provider replaces weeks of security-sensitive work with configuration. Buying both is usually cheaper than building them, even after the monthly fees.

For security, ask what standard the team tests against. The OWASP Application Security Verification Standard exists for exactly that: a basis for testing an app's security controls and a list of requirements for secure development (OWASP).

A worked estimate, with the arithmetic

This is an illustration of how an estimate is built, not a quote from Dardo. The hours are assumptions for a simple B2B client portal: customers sign in, submit and track requests, pay a subscription, and your team manages it all from an admin panel.

Now multiply by three example rates taken from the table above:

• At USD 35 an hour, the top of Upwork's full-stack range: 440 × 35 = USD 15,400.
• At USD 75 an hour, inside Clutch's US band for software firms: 440 × 75 = USD 33,000.
• At USD 150 an hour, the bottom of Clique Studios' range: 440 × 150 = USD 66,000.

A careful estimate adds a contingency for what the discovery phase uncovers. With 20%, those totals become USD 18,480, USD 39,600 and USD 79,200. The same app, the same hours, and a fourfold spread from the rate alone. When you compare quotes, ask for the hours behind each line: a quote that's cheap because it assumes 200 hours isn't comparable with one that assumes 440.

What the app costs to run each month

The build is a one-time cost; the stack is a monthly one. Two example stacks for the portal above at small scale, from the vendors' pricing pages read in October 2026:

Payments sit on top as a percentage: on a USD 50 monthly subscription, Stripe's 2.9% plus 30 cents is USD 1.75 per charge. Enterprise customers who ask for single sign-on add USD 125 a month per connection on WorkOS, or USD 75 for each connection after the first on Clerk Pro.

The point isn't the exact total; it's that running costs for a young app are usually tens of dollars a month, not thousands, as long as you rent the hard parts. Costs grow with users, emails, events and storage, so read each vendor's unit price, not just the entry plan. Our comparison of Astro and Next.js explains how the framework choice affects where the app can run.

How to cut scope for the first version

The fastest way to lower the estimate is to remove hours, not to find a cheaper rate:

1. One user type first. Two roles means two sets of screens, permissions and tests. Start with the customer, and run the internal side from the admin panel or even a spreadsheet.
2. One workflow, done well. The core action your buyers pay for. Everything else waits for evidence that people use the first one.
3. Rent auth, payments and email. A hosted provider costs a few dollars to tens of dollars a month and saves weeks of work you'd have to secure yourself.
4. Use a hosted checkout. It's quicker to build and keeps you on the lightest PCI DSS questionnaire.
5. Defer real-time and multi-tenancy unless the product doesn't make sense without them. Refreshing a page is fine for a first version; separate customer workspaces can come with your second customer.
6. Design the admin panel last and plainest. Your team can live with a table and a search box.
7. Write down what's out. A list of exclusions in the proposal is what stops a fixed price from turning into a change-request bill.

If AI assistants are part of how your customers will use the product, our guide to MCP servers for SaaS explains when that belongs in the first version and when it can wait.

How Dardo quotes a web app

We don't publish a price for app development: we quote each web app per scope, after a short discovery of the workflow, the roles and the integrations, with design, development, third-party services and recurring costs on separate lines. Our inquiry form's optional budget ranges run from under USD 5,000 to over USD 60,000, and there's no minimum budget; our pricing page explains how quotes work.

When the product needs its flows and screens worked out before anyone writes code, that's product design, and a portal like the one in the worked estimate is what our client portal development page describes. We're a team of three in Bogotá on UTC−5 all year. If your product needs a large team from day one, a bigger agency will fit better.

Next step

Write down the one workflow your first version must do, list the components it needs from the table above, and ask every provider for the hours behind each line. If you'd like Dardo's estimate, send that list from our web app development page.