How much does it cost to build a web app?

As of October 2026, a web app costs about $12,000 to $90,000 for an internal tool and $35,000 to $210,000 for a SaaS MVP. Marketplaces start near $60,000. Each range is build hours priced from $50 an hour, an offshore agency rate, to $150 an hour, a US agency rate. Web app development cost then continues every month through hosting, services and maintenance.

The hours matter more than the rate. Two quotes at the same $150 rate can differ by as much as $60,000. One includes roles, billing and data migration, and the other leaves them for later. The tables below price each app type, phase and feature at both reference rates, so you can test any quote line by line.

On this page

• Web app development cost by type of app
• Website or web app: which one are you buying?
• Web app cost by industry
• Where the hours go in a web app build
• What a discovery phase costs and what it should deliver
• Which web app features add the most cost?
• How hourly rates and team location set the price
• Monthly running costs after launch
• Costs that web app quotes often leave out
• What a web app costs to maintain each year
• Security and compliance costs for US web apps
• Custom build, no-code or off-the-shelf SaaS?
• Worked example: a client portal for a 40-person firm
• How to lower web app development cost
• Fixed price or time and materials?
• How to get an accurate web app quote

Web app development cost by type of app

Timelines assume a team of two to four people. Larger teams shorten the calendar, but they do not cut the hours.

Most small and mid-sized businesses need one of the first three rows. A portal that replaces email attachments and spreadsheets pays for itself through staff hours. So does an internal tool that replaces three disconnected systems, long before either needs marketplace features.

AI features sit on top of these figures. A summary, search or drafting feature has its own hours and a monthly model bill. Both are priced in the guide to AI app development cost.

Website or web app: which one are you buying?

A website publishes pages that every visitor sees the same way. A web app does work for each signed-in user: it stores their data, runs their workflow and shows them their own records. The line matters for the budget. The smallest internal tool in the table above takes 240 hours, against 60 to 100 hours for a 12-page WordPress site on a custom-styled theme.

A booking form, a quote calculator or a members-only page does not make a site a web app. Those fit inside a WordPress or builder site for a fraction of the price, as the comparison of WordPress vs a custom website shows. Commission a web app when users need accounts, permissions, saved data and a process the site runs for them.

Take a staffing agency. A site with job listings and an application form is a website. A system where candidates track applications, clients approve timesheets and recruiters see placements by account is a web app, and it belongs in the price ranges above.

Web app cost by industry

Industry changes the price through data rules and integrations more than through screens. The ranges below map the most common first app in each industry to the build types above, at $50 to $150 an hour.

Health and finance apps sit higher inside each range because access rules, audit logs and vendor agreements add hours. The clinic row adds about 100 hours of compliance work to a standard portal, and the distribution row adds a two-way ERP sync.

Where the hours go in a web app build

Take a 1,000-hour SaaS MVP. The work splits into seven lines, and every quote should show each one.

Backend work is the largest line, and it is the one owners see least. Permissions, data rules and the admin screens that staff use every day sit there. A quote that is light on backend hours is usually light on what makes the app usable.

Testing is the line to defend. Cutting 120 hours of QA saves $6,000 to $18,000 and returns as bugs found by paying customers.

What a discovery phase costs and what it should deliver

Discovery is the paid step that turns an idea into a scope a team can price. For an app of 500 hours or more, it is the best-spent money in the project. It runs two to four weeks and 40 to 80 hours. That is $2,000 to $4,000 at $50 an hour, or $6,000 to $12,000 at $150.

A discovery phase should hand you documents you own and can take to any vendor:

• User types and the main workflows, written step by step.
• A data model: what the app stores and who may see each record.
• A clickable prototype of the key screens.
• A feature list split into launch and later, with hours against each item.
• A hosting and services plan with monthly cost estimates.
• A risk list: integrations with poor APIs, unclear rules, data that needs cleaning.

Never accept a fixed build price for a large app without this step. A vendor that skips it either pads the quote to cover unknowns or bills the unknowns later as change requests.

Which web app features add the most cost?

Each estimate below is the extra work one feature adds to an MVP, priced at the two reference rates.

Single sign-on and audit logs look like enterprise extras. They are the price of selling to many mid-sized companies, whose IT teams ask for both during procurement. Build them when a named customer requires them, not before.

How hourly rates and team location set the price

The $50 and $150 reference rates bracket most agency quotes a US buyer sees. Offshore teams sit near the low end and US agencies near the high end. For an in-house comparison, the Bureau of Labor Statistics puts median pay for software developers at $135,980 a year in May 2025. Two in-house developers cost about $272,000 a year in salary alone, before benefits, payroll taxes and recruiting.

That number frames the choice. The same $272,000 buys about 5,400 agency hours at $50 or 1,800 at $150. An in-house team makes sense once the app is the business and the roadmap runs for years. An agency makes sense for the first release, when you need a designer, developers, QA and a project manager for six months, not forever.

A team in India or Eastern Europe can bring the rate down while keeping senior people on the project. The trade is coordination: ask for daily overlap with your working hours, a named project manager and weekly demos of working software. A team that overlaps US Eastern mornings can answer the same day.

Monthly running costs after launch

A small web app runs on a stack of services, each with its own bill. List prices as of October 2026:

Fixed service costs for an early app can sit under $100 a month. Payment fees grow with revenue instead. Say a SaaS app bills 400 customers $50 a month. Card fees come to $580 plus $120 in per-payment charges, and Stripe Billing adds $140. Payments cost about $840 a month on $20,000 of revenue.

Usage-based pricing is the line to watch. Database size, data transfer, users above the included tier and any AI model calls all scale with growth. Ask your developer for a cost model at 10 times today's users before launch. Budget for a staging copy as well: it needs its own database project, and Supabase lists extra projects from $10 a month.

Costs that web app quotes often leave out

Build quotes price the screens and features. Several lines sit outside them and arrive as surprises:

• A staging copy of the app with its own database and services, for testing changes before customers see them.
• Error monitoring and uptime alerts, so problems reach a developer before they reach support.
• Transactional email for sign-ups, password resets and receipts, billed by volume.
• Terms of service, a privacy policy and a data processing agreement drafted by an attorney.
• Staff training and help articles for customers, written by someone who knows the workflow.
• Support time after launch, which lands on your team before any developer sees a ticket.
• Third-party API fees for maps, address checks, text messages or AI models, which scale with use.

None of these is large alone, but together they land in year one. Ask each vendor which of them the quote covers, and price the rest yourself.

What a web app costs to maintain each year

A live web app needs a developer every month. Frameworks and packages ship security fixes, browsers change, integrations update their APIs, and users report bugs. Budget 10 to 20 hours a month for a SaaS MVP in its first year.

At the reference rates, that is $6,000 to $12,000 a year at $50 an hour, or $18,000 to $36,000 at $150. On a 1,000-hour build, maintenance runs about 12 to 24 percent of the build price each year.

The patch work is not optional. In December 2025, the React team disclosed a vulnerability in React Server Components rated CVSS 10.0 that affected Next.js apps. Each affected app needed its own upgrade and redeploy. No hosting plan applies those fixes for you.

Upkeep across site types, and what to ask for in a maintenance plan, is broken down in website maintenance cost.

Security and compliance costs for US web apps

Security belongs in the build estimate, not in a later phase. The OWASP Top 10:2025 ranks Broken Access Control first, Security Misconfiguration second and Software Supply Chain Failures third. All three are build-time decisions: who can see which record, how servers are configured, and which packages the app depends on.

Plan 40 to 80 hours for a security review and fixes before launch. At the reference rates, that adds $2,000 to $12,000.

Privacy rules depend on who your users are. The California Privacy Protection Agency says the CCPA applies to a for-profit business that collects personal information and has gross annual revenue of $26.625 million or more. It also applies when a business buys, sells or shares data on 100,000 or more California residents or households. A third trigger is earning 50 percent of revenue from selling or sharing such data.

Apps that store patient health information for a covered entity fall under HIPAA and need business associate agreements with each vendor. Card payments through hosted Stripe fields keep card numbers off your servers, which shrinks PCI DSS scope. Accessibility applies to customer-facing apps too, covered in the guide to making a website ADA compliant. This is general information, not legal advice.

Custom build, no-code or off-the-shelf SaaS?

Custom code is the most expensive way to get software, so rule out the cheaper two first. Bubble's pricing runs from $59 a month for Starter to $549 for Team on annual billing, with usage capped by workload units. A no-code build suits an internal tool for under 50 users or an MVP whose workflow is still unproven.

The CRM decision shows the pattern well. Most teams should buy, and a few should build, as the comparison of a custom CRM vs HubSpot explains. AI coding tools now produce prototypes fast enough to test an idea before either commitment. Their limits are set out in the explainer on vibe coding.

Worked example: a client portal for a 40-person firm

Say a 40-person engineering firm in Colorado wants clients to log in, check project status, download drawings and invoices, and message their project manager. Invoices sync from the firm's accounting system.

Running costs add about $780 a year at the list prices above: one Vercel Pro seat, Supabase Pro and Clerk Pro on annual billing. Ten hours of monthly maintenance add $6,000 or $18,000. The first full year comes to about $47,300 at $50 an hour or $140,300 at $150.

Payback comes from staff time. If the portal saves each of 8 project managers 3 hours a week of email and file requests, that is about 1,250 hours a year. At an assumed $60 an hour of loaded staff cost, the firm recovers about $75,000 a year. That covers the $50-an-hour version inside the first year and the $150 version in a little over two.

The firm can trim the build to about 650 hours by launching without messaging. Messaging can follow in phase two, once clients show they use the portal.

How to lower web app development cost

1. Pay for a two to four week discovery phase before the build quote, so the estimate prices a real scope.
2. Launch with one user type and one core workflow, and date everything else into phase two.
3. Use managed services for sign-in, payments and file storage instead of building them.
4. Reuse a design system or component library rather than designing every screen from scratch.
5. Prepare migration data early, because cleaning it during the build costs developer hours.
6. Name one product owner who answers questions within a day.

Each of these cuts hours without cutting testing or security. The build calendar for each phase, and what delays it, is in the guide to how long it takes to build a website.

Fixed price or time and materials?

The pricing model moves risk between you and the vendor. A fixed price puts the risk of underestimating on the vendor, who covers it with a buffer in the price. Time and materials puts it on you, and rewards a team that works efficiently and reports clearly.

The strongest setup for most first builds combines two of these. Discovery and the first release go on a fixed price, and everything after launch moves to time and materials or a retainer. Hold a 15 percent contingency in your own budget either way, because scope found during testing still has to be paid for.

How to get an accurate web app quote

Send every vendor the same brief. It should list the user types, the main workflow as numbered steps, the systems the app must connect to, year-one user numbers and any compliance needs. Then ask each vendor for:

• Hours by phase and by feature, not one total.
• The team: names or roles, seniority and weekly hours on your project.
• A fixed price for discovery and a time-and-materials estimate for the build, or a fixed price with a written change process.
• A monthly running-cost estimate at launch and at 10 times the users.
• A written assignment of the code copyright and the repository in your own account.

Quotes that cannot split their total into phases are guesses. Compare the hours line by line against the tables above, and ask about any phase that is far below them.

Start by writing the main workflow as numbered steps and listing who uses it, then request quotes with hours by phase. The web development team at Techno Mantra builds web apps from client portals to SaaS products and adds AI features where they earn their cost. You own all code, designs and accounts at handover. Send your workflow through the contact page or to info@technomantraa.com, and every inquiry gets a reply within one business day.