How Much Does It Cost to Build a Web App in 2026?

A custom web app in 2026 typically costs $5,000 to $40,000 for a focused MVP built by a freelancer or small studio, $25,000 to $80,000 for an MVP from a mid-size agency, and $80,000 to $250,000 or more for a full product with many user roles and integrations. Expect to pay another 15 to 20 percent of the build cost each year to keep the app maintained, and a monthly bill for hosting and services. The biggest single factor is not the technology but how many separate workflows you ask for in version one.

Those ranges are wide because "web app" covers everything from a booking form with a login to a multi-tenant SaaS platform. The rest of this guide explains what moves the number, so you can read a quote and know whether it is fair.

Typical cost ranges by type of web app

These are market ranges pulled from published 2026 agency and freelancer data (Clutch, Arc.dev and agency price guides), not a price list. Treat them as a starting point for a conversation.

Clutch's review data has put the average web app project in the tens of thousands of dollars with timelines of most of a year, but many real projects land under $10,000 because they are small and well scoped.

What actually drives the cost

A quote is roughly hours times rate. Hours come from the features. Here is where the hours go.

1. Number of workflows and user roles

A "workflow" is one complete job a user does: book an appointment, submit an application, approve a request, check out. Each one needs screens, database tables, validation, emails and error states. One workflow for one type of user is cheap. Three workflows across customers, staff and admins is several times the work, because every role needs its own permissions and views.

2. Integrations

Every outside system adds work: Stripe for payments, Plaid for bank data, QuickBooks for accounting, a shipping API, a CRM like GoHighLevel. Agency guides commonly price each third-party integration at $2,000 to $5,000, more if the other system's API is poorly documented. Integrations also fail in ways your own code does not, so they need retries, logging and testing.

3. Authentication and permissions

Basic email and password login with a provider like Supabase Auth or Clerk is a small line item. Social login, magic links, team accounts, invitations and role-based permissions add up. Enterprise single sign-on (SAML) can cost more than the rest of a small MVP.

4. Design

Using a well-built component library with your brand colors is fast. A fully custom design system, designed in Figma screen by screen before any code is written, can add $5,000 to $25,000. For an MVP, the first option is usually the right call.

5. Who builds it and where

Published 2026 hourly rates look roughly like this:

• Freelance developers: about $50 to $150 per hour
• Eastern European agencies: about $48 to $86 per hour
• Western European agencies: about $78 to $173 per hour
• US agencies: about $101 to $225 per hour

A higher rate does not always mean a higher total. An experienced developer who has built the same kind of app before can finish in half the hours.

6. Data, security and compliance

Handling payments, health data or financial data means more care: row-level security in the database, audit logs, encryption, and sometimes formal compliance work. Importing data from an old system also takes time that many quotes leave out.

The costs most quotes leave out

The build is only part of what you will spend. Ask about each of these before you sign.

Hosting and services. A typical modern stack for a small app, such as Next.js on Vercel with a Supabase database, starts cheap. As of October 2026, Vercel Pro is $20 per month per seat (the free Hobby plan is for non-commercial use only) and Supabase Pro starts at $25 per month (free Supabase projects pause after a week of inactivity, which is not acceptable for a live business app). Add email sending, a domain, error monitoring and any paid APIs, and a small app often runs in the range of $50 to $300 per month at launch, depending on traffic and which services it uses. Payment fees. Stripe charges a percentage of every transaction. That is not a development cost, but it belongs in your budget. Maintenance. Frameworks release updates, libraries get security patches, APIs you depend on change. Budget 15 to 20 percent of the build cost per year, or a monthly retainer, for fixes and small changes. Testing and QA. Some quotes include testing time; some assume you will do it. Find out which. Contingency. Add 15 to 25 percent. Every project discovers something during the build.

How to keep the cost down without cutting corners

1. Write down one core workflow. Describe the single thing a user must be able to do for the app to be worth using. Build that first. Everything else goes on a "version two" list.
2. Use proven building blocks. Hosted auth, a managed database and Stripe Checkout save weeks compared with custom versions. A good developer will suggest these.
3. Start with a prototype if you are unsure. AI builders like Lovable and Bolt can produce a clickable prototype in days. They are good for testing an idea with real users. Our Bolt.new review covers where they work and where they fall short.
4. Make sure you own the code. Ask for the code in your own GitHub account from day one, and the hosting and database in accounts you control. If you start in an AI builder, you can export the code from Lovable and hand it to a developer later.
5. Pay in milestones. Tie payments to working features you can click through, not to calendar dates.

Fixed price or hourly?

Fixed price works when the scope is clear and written down: screens, user roles, integrations and what "done" means. You know the cost up front, but any change becomes a change request. Hourly or weekly billing works when you expect the scope to move, which is common for early-stage products. You keep flexibility, but you need regular demos and a weekly budget cap to stay in control.

A common middle ground is a fixed-price discovery phase (a few days to two weeks) that produces a detailed scope, followed by a fixed price for the build.

What about apps already built with Lovable, Bolt or Replit?

Many founders now arrive with an app that mostly works, built with an AI tool. Fixing and finishing one is often far cheaper than starting over, but not always. The cost depends on:

• Whether the database and security rules are set up correctly (missing or loose row-level security is a frequent problem in AI-generated Supabase apps)
• How tangled the generated code is
• Which features are half-built versus missing
• Whether it needs to move to its own hosting

A short code review before any quote will tell you whether to repair or rebuild. If the app runs on Supabase, our guide to connecting Next.js with Supabase shows what a clean setup looks like.

Red flags in a web app quote

• A single number with no breakdown by feature or phase
• No mention of who owns the code, hosting accounts and domain
• No testing, deployment or post-launch support in the scope
• A price far below every other quote, with no explanation
• No written definition of what is included in version one

A good quote reads like a plan: what will be built, in what order, what is out of scope, and what happens after launch.

Get a real number for your app

At Amex Technology we build and fix web apps for small businesses and founders, mostly on Next.js, Supabase and Vercel. That includes ground-up builds like a fintech funding marketplace with bank-data integration, takeovers of existing platforms that needed checkout and integration fixes, and deployment work on apps a client already had. You can see the work on our portfolio and what we offer on our services page. If you already have an app, run it through our free app checker first, then contact us with your feature list for a scoped estimate.