How Much Does It Cost to Build a Custom Web App?

Anyone who gives you a price for a web app before asking questions is guessing. The cost of custom software comes from a small number of factors, and once you understand them you can estimate your own project and judge the quotes you receive.

The formula behind every quote

Every estimate, however it is presented, comes down to this:

Cost = people × time × rate

A fixed-price quote is the same calculation with a risk margin added on top. So the useful questions are how many people the project needs, for how many weeks, and at what rate.

What drives the time

Number of distinct screens and flows

A screen that lists records is quick to build. A multi-step flow with validation, saved drafts and error recovery takes far longer. Count the flows in your product, and be honest about which ones are complex.

User roles and permissions

An app where every user sees the same thing is simple. Once you add admins, team members and guests who each see and do different things, every feature has to be built and tested for each role.

Integrations

Payments, email, calendars, CRMs, accounting tools and single sign-on each add work. A well-documented API such as Stripe is predictable. An older system with poor documentation can take several times longer than expected.

Data complexity

Reporting, search, imports and exports, and audit history are often described in one line of a brief and take weeks to build properly.

Quality requirements

Accessibility, automated tests, performance under load, and compliance requirements such as GDPR or SOC 2 all add effort. They are worth paying for in most products, and you should know that you are paying for them.

Rough sizes

As a guide to effort, for a team of two to three engineers:

Focused first version: one core flow, authentication, a simple admin view. Six to ten weeks.
Full product: several flows, roles, billing, a few integrations. Three to six months.
Complex platform: many roles, heavy reporting, compliance requirements. Six months or more, delivered in phases.

Multiply the weeks by the team's weekly rate to get a budget. Rates vary widely by region and seniority, which is why two quotes for the same project can differ by a factor of three.

How to read a quote

A quote you can trust has these properties:

It is broken down by feature. You can see what each part costs and remove what you do not need.
It states assumptions. For example, that designs are provided, or that an integration has a working sandbox.
It says what is excluded. Hosting, third-party licenses, content and post-launch support are common exclusions.
It explains how changes are handled. Scope always changes. The quote should say how a change is priced and approved.

Be careful with a single number and no breakdown. You cannot tell what it includes, and you will find out during the project.

How to reduce cost without hurting the product

Cut flows and keep quality. Shipping three flows that work well beats shipping eight that are fragile.
Use existing services. Authentication, payments, email and file storage are solved problems. Pay for a service and spend your budget on what makes your product different.
Delay the admin panel. In the first months, a database tool and a few scripts can replace most admin screens.
Launch on web first. A responsive web app reaches every device. Add native mobile apps once you know which features people use.
Decide quickly. Slow feedback is a hidden cost. A team that waits a week for an answer still costs a week.

Costs after launch

Budget for hosting, third-party services, monitoring and maintenance. Dependencies need updating, browsers change and users find bugs. A common planning figure is to set aside a portion of the build cost each year for maintenance, and the right amount depends on how actively the product keeps changing.

Getting a real number

The fastest route to an accurate estimate is a short written brief: who the users are, the three to five things they must be able to do, the systems you need to connect to, and your deadline. With that, a team can give you a breakdown you can act on.

If you would like one for your project, tell us about it and we will send a written estimate. You can also read more about how we approach custom web app development.