Florin Florea··15 min read·Last reviewed:

Web Application Development Cost Estimation: Process, Methods and a Worked Estimate

Web application development cost estimation in seven steps: scope, feature list, hours per feature, rate, contingency, timeline, running costs. Four estimation methods and a worked estimate: 710 hours, $110,400 with a US freelancer, $189,600 with a US agency.

FF

Florin Florea

10+ years web dev · Scoping web projects since 2011

Some links in this guide are affiliate links — if you buy through one, I earn a commission at no extra cost to you. I only link to tools I'd use myself.

Want your specific number? Try our free calculator — it takes 2 minutes.

Open the Free Cost Calculator

Quick answer: how to estimate web application development cost

To estimate a web application, write down the scope, turn it into a feature list, put hours on each feature, multiply the hours by an hourly rate, add contingency, convert the hours into a timeline and add the monthly running costs. Worked through for a medium web app, that gives 710 hours, $110,400 with a US freelancer and $189,600 with a US agency.

The seven steps, with the output of each for the example used in this guide. Every number in the right-hand column is produced by this site's calculator, the same one embedded below.

StepWhat you produceExample: medium web app, US freelancer
1. ScopeOne page: users, what they do, what is out15–50 screens, branded layouts, roles and SSO login, a few integrations, analytics dashboards
2. Feature listEvery screen group, feature and integration as a line4 lines: core app, roles and SSO, integrations, analytics
3. Hours per featureHours next to each line579 + 70 + 45 + 40, less 24 for shared infrastructure = 710 hours
4. RateHourly rate of the team you would hire$135/h, the US freelancer median for custom work
5. ContingencyA reserve for what the list missed15% of $95,850 = $14,378, plus one revision round at $150
6. TimelineCalendar weeksAbout 24.5 weeks
7. Running costsMonthly bill after launch$225.50 a month for hosting and tools
Estimate$110,400, range $77,300–$154,550


This guide is about the estimation process. For prices by type of app, feature and country, the web app development cost guide has the full tables, built on the same calculator, so the figures agree.

Use the estimator below to run the same steps on your own scope: pick the size of the app, the market and freelancer or agency.

Web App Website Cost Calculator

Live estimate

What are you building?

Where's your developer?

Budget

$16,100

Realistic

$23,000

Premium

$32,200

~5.5 weeksCustom Development (React/Next.js/Node) recommended

Email me this estimate — your reference number when the quotes come in

No spam, ever. Unsubscribe anytime.

Powered by the same 9-engine calculator behind every estimate on this site — full version →

The app cost estimation process, step by step

Step 1. Write the scope on one page. Who uses the application, the three to five things each kind of user must be able to do, what data it holds, what it connects to, and what is explicitly not in the first version. An estimate is only as good as this page. If two people read it and imagine different products, stop and fix the page before you put a number on it.

Step 2. Turn the scope into a feature list. One line per thing a developer has to build: screen groups, user accounts, roles, search, payments, each third-party integration by name, reports, admin tools, notifications. "A few integrations" is not a line; "Stripe, HubSpot, SendGrid" is three.

Step 3. Put hours on each line. This is where the four methods in the next section differ. The calculator uses fixed hours per feature, and on a custom-coded app it counts feature hours past the first 75 at 70%, because features share infrastructure. For the example they are:

LineHours
Web app core: screens, data model, API, design579
Roles, permissions and SSO login70
A few third-party integrations45
Analytics dashboards40
Shared infrastructure: the 80 feature hours past 75 count at 70%−24
Total710


Step 4. Multiply by the rate. Use the rate of the kind of team you will actually hire, in the country they work in. In our rate table a US freelancer doing custom work has a median of $135 an hour and a US agency $232. 710 hours is $95,850 at the first and $164,720 at the second.

Step 5. Add contingency. The feature list never contains everything. The calculator adds 15% for a project of this size and complexity, and the cost of the agreed revision rounds.

Step 6. Convert hours to weeks. Hours are not calendar time: a freelancer does not bill 40 hours a week to one project, and an agency runs people in parallel. The calculator gives about 24.5 weeks for a freelancer and about 16 for an agency on this scope.

Step 7. Add what it costs to run. Hosting, email, licences, CDN, backups and security tooling are a monthly bill that starts at launch, and developer time for fixes and updates is a yearly one. Both belong in the estimate you take to whoever approves the budget.

How agencies run the same process. Agencies describe it in stages. Railwaymen describes a brief estimate in a couple of hours that can move 25–30% up or down, then a one-to-two-week discovery phase, then a detailed estimate it calls "up to 95% accurate" (Railwaymen). Cleveroad describes a rough estimate with optimistic, neutral and pessimistic figures, then a detailed estimate from wireframes and specifications (Cleveroad). Digiteum uses a 2–4 hour scoping workshop or a 2–4 week discovery phase (Digiteum). The accuracy figures are those companies' own claims. The pattern is the same everywhere: a fast rough number first, a detailed one after the scope has been worked through.

Estimation methods: analogous, parametric, bottom-up, three-point

Four methods are in common use. They are not rivals: they are used in this order as more becomes known about the project.

MethodHow it worksWhat you needUse it for
AnalogousTake the cost of a similar finished project and adjustA comparable project or a table of typical costsThe first conversation: is this a $20,000 or a $200,000 idea?
ParametricCount units (features, screens, integrations) and multiply each by a standard number of hours, then by a rateA feature list and a table of hours per featureSetting a budget and comparing quotes
Bottom-upBreak every feature into tasks of a few hours each, estimate each task, add them upA written specification and the people who will build itThe number that goes in a contract
Three-pointGive each uncertain item an optimistic, most likely and pessimistic value and take a weighted averageAny of the above, plus honesty about what is uncertainSizing the contingency


Analogous estimation, plainly. You say "this is a customer portal" and look up what customer portals cost. It takes minutes and it is only as good as the comparison. The calculator's figures by type of web app, United States:

Type of web appBuild hoursFreelancerAgency
Internal tool or admin dashboard404$44,000–$88,000 (median $62,850)$75,550–$151,150 (median $107,950)
Booking or scheduling app490$53,350–$106,700 (median $76,200)$91,650–$183,250 (median $130,900)
Customer portal515$56,050–$112,150 (median $80,100)$96,300–$192,550 (median $137,550)
SaaS product, growth stage861$93,650–$187,300 (median $133,800)$160,900–$321,800 (median $229,850)
Two-sided marketplace, custom850$92,450–$184,950 (median $132,100)$158,850–$317,750 (median $226,950)


The usual mistake is comparing with the wrong thing: a well-known product as it is today, after years of work, and not its first version.

Parametric estimation, plainly. Features times hours times rate. This is what the calculator does. Its hours for common features when they are written on a custom stack, with the cost at the US medians:

FeatureHoursUS freelancer, $135/hUS agency, $232/h
User accounts: sign-up, login, password reset30$4,050$6,960
Roles, permissions, SSO or social login70$9,450$16,240
Advanced search with filters and autocomplete50$6,750$11,600
A few third-party APIs45$6,075$10,440
Many third-party APIs120$16,200$27,840
Multiple payment methods40$5,400$9,280
Invoicing40$5,400$9,280
Booking or scheduling60$8,100$13,920
Analytics dashboards40$5,400$9,280
CRM two-way sync45$6,075$10,440
ERP integration70$9,450$16,240
AI chatbot on your own data60$8,100$13,920
Multi-vendor marketplace functions200$27,000$46,400


These are build hours times the rate, before contingency; in a full estimate, feature hours past the first 75 count at 70%. The full list is on the feature cost breakdown page.

Bottom-up estimation, plainly. Take one line from the feature list, for example "roles, permissions and SSO login", and write out the tasks: data model for roles, permission checks on each endpoint, admin screen for assigning roles, SSO provider setup, login and logout flows, account linking, error states, tests. Each task gets its own hours from the person who will do it, with the assumption behind it written next to it. The value is less in the total than in the questions it forces: "which SSO providers?", "can a user have two roles?". Asked before the contract they are free; asked in week six they are change requests. A bottom-up total that lands far from the parametric figure for the same feature means the feature is not what you thought it was.

Three-point estimation, plainly. For anything uncertain you write three numbers, optimistic (O), most likely (M) and pessimistic (P), and use (O + 4 × M + P) ÷ 6. Applied to the whole example using the calculator's own range: O = $77,300, M = $110,400, P = $154,550, so (77,300 + 441,600 + 154,550) ÷ 6 = about $112,250. The weighted figure sits above the most likely one because the range is wider on the upside, which is how software projects behave. In a real estimate you apply this per feature, in hours, with your team's own three numbers for the risky lines: data import, integrations with poor documentation, anything real-time.

A worked estimate with the calculator's hours and rates

The same medium web app, estimated for a US freelancer and a US agency. Scope: 15–50 screens with branded layouts, roles and permissions with SSO or social login, a few third-party integrations, event and funnel analytics with dashboards.

LineHoursFreelancer at $135/hAgency at $232/h
Web app core: screens, data model, API, design579$78,165$134,328
Roles, permissions and SSO login70$9,450$16,240
A few third-party integrations45$6,075$10,440
Analytics dashboards40$5,400$9,280
Shared infrastructure: the 80 feature hours past 75 count at 70%−24−$3,240−$5,568
Build subtotal710$95,850$164,720
Contingency, 15%$14,378$24,708
One revision round$150$150
Sum$110,378$189,578
Estimate, rounded$110,400$189,600
Range the calculator shows (−30% to +40%)$77,300–$154,550$132,700–$265,450
Timelineabout 24.5 weeksabout 16 weeks


Calculator figures, 17 Nov 2026. The engine is calibrated on 600+ project quotes and public rate benchmarks across 6 markets.

A smaller and a larger version of the same estimate

ScopeHoursFreelancerAgency
Simple: up to 5 screens, template UI, one data model, no accounts, no integrations154$16,100–$32,200 (median $23,000), about 5.5 weeks$27,600–$55,250 (median $39,450), about 4 weeks
Medium: the example above710$77,300–$154,550 (median $110,400), about 24.5 weeks$132,700–$265,450 (median $189,600), about 16 weeks
Complex: 50+ screens designed from scratch, many integrations, AI chatbot, advanced analytics1,421$154,550–$309,050 (median $220,750), about 50.5 weeks$265,500–$530,950 (median $379,250), about 33.5 weeks


Where the money goes by stage. The calculator does not split the total by stage. Andersen publishes typical shares for a web application: discovery 5–10%, design 15–20%, core development 45–55%, QA and security validation 15–20%, deployment 5–8% (Andersen). Applied to the $110,400 freelancer median, discovery is $5,500–$11,050 and core development $49,700–$60,700. The shares are Andersen's; the dollar figures are those shares times our median.

The rate: the biggest single input

The hours for a given scope do not change with who builds it. The rate does. The table shows the hourly rate bands in our rate table for custom web application work, and the same 710-hour estimate in each market.

MarketFreelancer rate, low – median – highAgency rate, low – median – highEstimate, freelancerEstimate, agency
United States$88 – $135 – $218$145 – $232 – $385$110,400$189,600
United Kingdom$72 – $120 – $190$130 – $202 – $319$98,150$165,100
Australia$72 – $120 – $190$130 – $202 – $334$98,150$165,100
Western Europe$65 – $105 – $168$116 – $185 – $283$85,900$151,200
Eastern Europe$29 – $52 – $95$65 – $105 – $168$42,600$85,900
South and Southeast Asia$16 – $31 – $62$36 – $63 – $109$25,450$51,600


Rates: this site's rate table, whose stated sources are Clutch (April 2026), the Talmatic Global Snapshot, Arc.dev, Upwork medians and TechReviewer. Estimates: calculator medians, 17 Nov 2026. The rate database has the rates for other platforms.

Three things to get right when you plug in a rate:

  • - Use a blended rate for a team. An agency quote of 710 hours hides designers, developers, testers and a project manager at different rates. Ask for the blended rate or the split.
  • Compare like with like. A $52 freelancer and a $232 agency are not the same service at different prices. The agency price includes project management, testing and someone to call when a developer leaves.
  • Do not estimate with the lowest rate you have seen. The low end of each band exists, and so does the high end. The median is the honest planning number.

Contingency, deadline and revisions

Contingency. The calculator adds 15% to the build subtotal for this scope: $14,378 on the freelancer estimate and $24,708 on the agency one. It is a line in the estimate, visible to whoever approves the budget, and it is spent only when something the feature list missed turns up. A quote with no contingency line has not removed the risk; it has moved it to change requests.

Deadline. Compressing the schedule costs money because work has to run in parallel. The same medium web app with a US freelancer at four deadline settings:

DeadlineEstimateTimeline
Relaxed$104,950about 29.5 weeks
Normal$110,400about 24.5 weeks
Tight$132,400about 23 weeks
Rush$182,100about 22.5 weeks


A rush deadline adds $71,700 to this estimate and saves about two weeks in the calculator's model. If the date is fixed, cut scope before you pay for speed.

Revision rounds. Agreed rounds of changes after delivery are priced into the estimate. On this scope a second round adds $4,850; a third round or unlimited rounds add time in the calculator's model but no further cost.

Revision roundsEstimateTimeline
1$110,400about 24.5 weeks
2$115,250about 25 weeks
3$115,250about 26 weeks
Unlimited$115,250about 27.5 weeks


Calculator figures, medium web app, US freelancer, 17 Nov 2026.

What published guides add. Cleveroad advises budgeting 10–25% of development cost for bug fixing after release and says that skipping the discovery phase "can increase the total project cost by 20–30%" (Cleveroad). Those are that company's figures, not ours.

Running costs: the part of the estimate after launch

An estimate that stops at launch understates what the application costs. The calculator's monthly figure for the medium web app is $225.50:

LinePer month
Hosting$100
Transactional and business email$36
Licences and paid libraries$35
CDN$20
Backups$15
Security tooling$10
SSL$8
Domain$1.50
Total$225.50


The complex tier comes to $385.50 a month and the simple one to $175.50, because hosting in the calculator follows the size of the app. These are allowances for typical tools at this size, not a bill from a specific vendor, and they grow with traffic and data.

Developer time for fixes, dependency and security updates and small changes is separate, and the calculator does not price it. Published guides put it at 15–25% of the build cost a year (Andersen) or 15–20% (MindK). Applied to our medians, 15–25% is $16,550–$27,600 a year on the $110,400 freelancer build and $28,450–$47,400 on the $189,600 agency build.

So the first-year figure to approve for the freelancer example is the $110,400 build, about $2,700 of hosting and tools, and $16,550–$27,600 of maintenance if you take the published shares.

What makes web app estimates wrong

Most wrong estimates are wrong in the same few ways. The dollar figures show what each one is worth in the calculator, starting from the simple tier ($23,000 with a US freelancer).

What changedAdds to the estimate
User accounts were assumed, not listed$5,700
"Accounts" turned out to mean roles, permissions and SSO$11,950
A few third-party APIs were left off the list$8,050
"A few" integrations became many$17,500
The app grew from up to 5 screens to 15–50$55,400
The design changed from a template to custom$10,550
An AI chatbot on your own data was added$10,350
The deadline became a rush$14,850
An agency was hired where a freelancer was budgeted$16,450


Calculator figures: each row changes one input on the simple tier, US freelancer, 17 Nov 2026.

The causes behind those rows:

  • - The feature list only has features. Setup, deployment, error states, empty states, responsive layouts and testing are work. The calculator carries them in the core hours; a hand-made list often has no line for them.
  • Integrations are counted, not named. Every external system has its own authentication, limits and failure modes. Name each one.
  • Existing data is ignored. Importing and cleaning real data is work that appears on no screen, and it is the first thing a three-point estimate should be applied to.
  • The estimate is for the first version, the expectations are for the third. Write down what is out of scope as carefully as what is in.
  • Hours are confused with weeks. 710 hours is not 18 weeks of one person.
  • One number is given where a range is honest. The calculator shows −30% to +40% around its median for a reason.
  • Scope changes after the estimate and the estimate is not redone. Every change gets re-estimated in writing with the same method. The scope creep cost guide covers what happens otherwise.

How to validate a quote against your estimate

Once you have your own estimate, a quote can be checked in a few minutes.

  1. 1. Convert the quote to hours and a rate. Divide the price by the stated rate, or ask for both. A quote that will not show hours cannot be checked.
  2. Compare the hours with the feature list. Line by line against the table of hours above or the feature cost breakdown. A line at half the calculator's hours is either a narrower feature or an optimistic guess; ask which.
  3. Look for what is missing. Testing, deployment, project management, contingency, revision rounds, data migration, handover. If a line is absent, ask whether it is included in another line or not included at all.
  4. Check the rate against the market. Compare it with the band for the vendor's country and type in the rates table.
  5. Check the timeline against the hours. 710 hours in eight weeks means several people in parallel or a number that will not hold.
  6. Compare quotes on the same scope. If three quotes for one document imply 200, 400 and 900 hours, the document is the problem. Fix the scope and ask again.
  7. Ask what happens when scope changes. The hourly rate for changes and how they are approved should be in the contract.

The quote analyzer is this site's paid tool for this step: you enter the project basics, paste in one to five quotes, and it returns a score and a red-flag report for each. The website quote checklist lists what a complete quote contains. For the wider process of collecting and comparing quotes see the project cost estimate guide.

Related estimators on the same engine: the MVP cost calculator, the SaaS cost estimator and the marketplace cost estimator.

Where these figures come from

Calculator figures. Every hour count, estimate, range, timeline and monthly cost in this article was produced by this site's pricing engine on 17 Nov 2026, with the presets of the web app calculator embedded above. Feature hours are fixed per feature (on a custom build, feature hours past the first 75 count at 70%), the rate is the median for the market and provider type, the range is the median −30% to +40%, and the engine is calibrated on 600+ project quotes and public rate benchmarks across 6 markets. The methodology page describes it, and the web app development cost guide shows the same figures computed live.

Published figures from other companies. Stage shares and maintenance shares (Andersen, MindK), process descriptions and accuracy claims (Railwaymen, Cleveroad, Digiteum) and price ranges (Cleveroad, SaM Solutions, QArea, MindK, Andersen, Digiteum) are quoted from the linked pages as those companies' own statements.

What we removed. Earlier versions of this article gave accuracy percentages for each method, a "winning bid" that matched the estimate, hand-typed hours for a worked example, discovery-phase prices and claims about projects we had rescued. None had a source, and they are gone. The formula for three-point estimation is the standard weighted average; the numbers put through it here are the calculator's.

Ready to build? Three ways to do it

The right path depends on budget, not preference. These bands come from our own published cost data.

Do it yourself

$0–$500

WordPress on cheap hosting like SiteGround — enough for a simple site you maintain yourself.

Hire a freelancer

$500–$5,000

Custom design and setup without agency overhead — the sweet spot for most small-business sites.

Browse Fiverrdevelopers →

Custom project

$5,000+

Scope it properly before you talk to anyone — our calculator prices your exact feature list so quotes can't inflate.

Price my project →

Magento & Shopify Plus

Scopebit

The agency behind this calculator builds, upgrades and migrates Magento and Shopify Plus stores for companies across Europe and North America.

Book a call with Scopebit →

Disclosure: some links above are partner links — we may earn a commission at no extra cost to you. Recommendations come from our cost data, not from who pays us.

Get your personalized estimate

Our 9-engine calculator analyzes 30+ features, platform-specific rates, and your geographic market.

Start Free Estimate

Free · No signup · Results in 2 minutes

Frequently Asked Questions

How do you do web application development cost estimation?+
In seven steps: write the scope, turn it into a feature list, put hours on each feature, multiply by the hourly rate of the team you would hire, add contingency, convert hours into a timeline and add monthly running costs. For a medium web app this site's calculator gets 710 build hours, $95,850 at the US freelancer median of $135 an hour, plus 15% contingency and one revision round, which is $110,400. The same scope at a US agency is $189,600.
What is the cost estimation process for web apps?+
A rough number first, a detailed one later. Start with an analogous estimate from similar apps, move to a parametric estimate (features times hours times rate) once you have a feature list, and get a bottom-up estimate from the team before signing. Agencies describe the same sequence: Railwaymen, for example, describes a brief estimate, a one-to-two-week discovery phase and then a detailed estimate.
What is the app cost estimation process an agency follows?+
Typically a discovery call, a scoping workshop or discovery phase, a breakdown of the product into user stories or features, hours estimated per item by the developers, a roadmap, and a cost table. Digiteum describes a 2–4 hour scoping workshop or a 2–4 week discovery phase; Railwaymen estimates each element in man-days per role. Ask to see the hours per feature, because that is the part you can check.
Is there a web app cost estimator I can use?+
Yes, the estimator embedded in this article. Choose the size of the app, the market and freelancer or agency, and it returns the estimate, the range, the timeline and the monthly running cost. With its presets a US freelancer build is $16,100–$32,200 for a simple app, $77,300–$154,550 for a medium one and $154,550–$309,050 for a complex one.
What is app estimation?+
App estimation is working out the effort, cost and time of building an application before it is built. The effort is measured in hours per feature, the cost is hours times an hourly rate plus contingency, and the time is the hours spread over the people available. Its output is a range, not a single number: the calculator here shows the median with −30% to +40% around it.
How many hours does a web app take to build?+
In this site's calculator: 154 build hours for a simple app with up to 5 screens and no accounts, 710 hours for a medium app with roles, a few integrations and analytics, and 1,421 hours for a complex app with 50+ custom screens, many integrations and an AI chatbot. Published hour counts for a medium app run from 1,276 in Digiteum's sample estimate to about 3,000 (QArea, MindK), which describes larger products.
Which estimation method is the most accurate?+
Bottom-up, because every task is estimated by the person who will do it against a written specification. It is also the slowest and needs the specification to exist. Analogous and parametric estimates are faster and are the right tools for deciding a budget; three-point estimation is not a rival method but a way to size the contingency in any of them.
How much contingency should a web app estimate include?+
This site's calculator adds 15% of the build subtotal for a medium web app: $14,378 on a $95,850 freelancer build. To size it for your own project, apply three-point estimation to the risky lines, which are usually data import, integrations and anything real-time, and reserve the difference between the weighted and the most likely figures.
Why do web app quotes differ so much for the same project?+
Three reasons: the rate (the median for custom work is $135 an hour for a US freelancer, $232 for a US agency and $52 for an Eastern European freelancer in our rate table), the hours each vendor assumes for the same words in the scope, and what is left out, such as testing, contingency or project management. Convert every quote to hours and a rate before comparing, and compare them on the same scope; the quote analyzer on this site scores quotes side by side.

Related Articles

web application development cost estimationcost estimation for web appsapp cost estimation processweb app cost estimatorapp estimationhow to estimate web app costweb app estimation methodssoftware cost estimationweb app hours estimatethree-point estimation