App Development Cost Per Hour Calculator: Rates & Budget
App development cost per hour by region, freelancer and agency, how a rate turns into a budget, and worked examples at three scopes.
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 CalculatorQuick answer: app development cost per hour
App development costs $88–$218 an hour with a US freelancer (median $135) and $145–$385 with a US agency (median $232); the same hour is $29–$95 (median $52) for an Eastern European freelancer and $16–$62 (median $31) in South Asia. Those are the custom development rows of the engine's rate table, which is the closest row to app work. Source: Project Cost Estimator engine, calibrated against 600+ project quotes and public rate benchmarks across 6 markets.
An hourly rate on its own tells you almost nothing about what an app will cost. The budget is rate times hours, and the hours are set by scope, by how parallel the team is, and by how many times the spec changes. This page gives the rates by region, explains what an hour includes from a freelancer and from an agency, and then multiplies through at three scopes so you can see the arithmetic. The calculator above does the same thing from the scope side: pick a scope and a team, and it returns the band the hours fall into.
Mobile Web App / PWA Cost Calculator
Live estimateWeb app or PWA version of your app
Where's your developer?
Budget
$16,100
Realistic
$23,000
Premium
$32,200
Powered by the same 9-engine calculator behind every estimate on this site — full version →
Hourly rates by region: custom development row
The engine's rate table is organised by platform and region. App work is not a platform row of its own; the custom row (bespoke code rather than a template or a CMS) is the one that matches how app developers price, and it is the row used throughout this page. Low to high, with the median in brackets.
| Region | Freelancer per hour (median) | Agency per hour (median) |
|---|---|---|
| United States | $88–$218 ($135) | $145–$385 ($232) |
| United Kingdom | $72–$190 ($120) | $130–$319 ($202) |
| Australia | $72–$190 ($120) | $130–$334 ($202) |
| Western Europe | $65–$168 ($105) | $116–$283 ($185) |
| Eastern Europe | $29–$95 ($52) | $65–$168 ($105) |
| South Asia | $16–$62 ($31) | $36–$109 ($63) |
Three things to read off the table before using it. The agency median is roughly the freelancer median plus the cost of the people a freelancer does not bring. The spread within a region is wider than the gap between neighbouring regions; a senior US freelancer and a junior US agency hour can cost the same. And the UK and Australia rows are the same except at the top of the agency range.
If a developer quotes a rate outside their region's band, ask why. Above the band usually means a specialism (payments, hardware, security). Below it usually means a junior, a marketplace profile that will subcontract, or a rate that goes up after the first invoice.
What an hour includes
A freelancer's hour is one person's hour. It includes the code, and whatever else that person is willing to do at the same rate: often some design, some testing, and the conversation with you. It does not include a second opinion, cover for sick days, or anyone whose job is to keep the project on schedule.
An agency's hour is a blended hour. The rate you see is an average across the people on the project: a developer, a designer, a tester, and a project manager whose time is billed whether or not you talk to them. Some agencies show the blend; most show one number. Ask for the breakdown and the seniority of each person. A blended rate with a senior developer and a junior tester prices differently from the reverse, and both can be quoted as the same median.
What neither hour includes:
- 1. Developer programme fees for the app stores and any paid third-party service.
- Hosting and running cost after launch, which the engine prices separately per scope.
- Your own time, which is largest on the freelancer side and smallest with an agency that has a project manager.
- Rework caused by a changed spec. That is billed as more hours at the same rate, and it is where most hourly projects overrun.
A day rate is an hourly rate in disguise. Divide by the hours in the contractor's working day, and ask whether that is seven, seven and a half or eight.
How hours turn into a budget
The formula is simple: hours multiplied by rate. The hard part is the hours. Three ways to get them.
- 1. From the engine's weeks. The engine gives a timeline per scope in elapsed weeks for one focused build. Multiply the weeks by the hours per week the developer will actually give you, which for a freelancer with other clients is rarely a full week. The result is a rough hour count to sanity-check a quote against.
- From the developer's estimate. Ask for hours per feature, not a total. A total hides the assumptions; a per-feature list shows where the uncertainty is and lets you cut scope line by line.
- From the band backwards. Take the engine's project band for your scope, divide by the regional median rate, and you have the hour range the engine expects. A quote with far fewer hours than that is cutting something.
Then add a buffer. Hourly projects overrun on hours, not on rate. A spec that changes twice costs more than a spec that is wrong once and fixed before the build. The buffer is for the changes you will make, not for the developer's mistakes; those are theirs.
And decide what happens when the hours run out. A cap with a written process for extending it is the difference between an hourly contract and an open cheque.
Worked examples at three scopes
Three hour counts, chosen to sit inside the engine's own timelines: 160 hours is about a month of one developer's focused time and matches the smallest version (up to 5 screens, no accounts); 700 hours is a medium app with accounts and payments; 1,500 hours is a complex app with roles, many APIs and an AI chatbot. Each is multiplied by the median rate from the table above. The figures are arithmetic, not quotes.
| Hours | US freelancer ($135) | US agency ($232) | UK freelancer ($120) | Eastern Europe freelancer ($52) | South Asia freelancer ($31) |
|---|---|---|---|---|---|
| 160 (smallest version) | $21,600 | $37,120 | $19,200 | $8,320 | $4,960 |
| 700 (medium) | $94,500 | $162,400 | $84,000 | $36,400 | $21,700 |
| 1,500 (complex) | $202,500 | $348,000 | $180,000 | $78,000 | $46,500 |
Read across a row and the regional gap is obvious. Read down a column and the thing to notice is that the complex row is more than nine times the smallest-version row at every rate. Scope multiplies; rate only scales.
The agency column is not a like-for-like multiplication. An agency finishes the same scope in fewer elapsed weeks because its people work in parallel, so 700 agency hours are spread across a team over about 16 weeks, while 700 freelancer hours are one person over about 23. The money is higher; the calendar is shorter.
Cross-check against the engine bands
The worked examples only mean something if they land inside the ranges the calculator produces from the scope side. They do. Engine bands for the mobile niche, freelancer, with the worked figure from the table above in the last column.
| Scope | Market | Engine freelancer band | Worked figure |
|---|---|---|---|
| Smallest version | United States | $16,100–$32,200 | $21,600 |
| Medium | United States | $74,250–$148,450 | $94,500 |
| Complex | United States | $165,050–$330,100 | $202,500 |
| Smallest version | Eastern Europe | $6,250–$12,550 | $8,320 |
| Medium | Eastern Europe | $28,650–$57,350 | $36,400 |
| Complex | Eastern Europe | $63,650–$127,350 | $78,000 |
| Smallest version | South Asia | $3,800–$7,550 | $4,960 |
| Medium | South Asia | $17,100–$34,250 | $21,700 |
| Complex | South Asia | $38,000–$75,950 | $46,500 |
The US agency figures land the same way: $37,120 inside the smallest-version agency band of $27,600–$55,250, $162,400 inside the medium band of $127,450–$254,950, and $348,000 inside the complex band of $283,600–$567,200.
This is the test to run on any hourly quote. Multiply the quoted hours by the quoted rate and put the result against the engine band for the scope and region. Inside the band, the quote is plausible. Below it, something is missing. Above it, ask what the extra hours are for, and whether they are hours you asked for.
When to pay by the hour and when to pay a fixed price
Pay by the hour when the scope will change and you know it: an early product, a research build, anything where the second week's decisions depend on the first week's results. Hourly billing with a cap and a weekly report keeps you in control of the spend and lets you redirect the hours.
Pay a fixed price when the scope is written down and will stay written down: a defined app with a screen map, a feature list and a chosen payment provider. The fixed price moves the overrun risk to the developer, and the developer prices that risk into the quote, which is why a fixed price for a defined scope sits a little above the hourly arithmetic for the same work.
The worst of both is a fixed price for an undefined scope. It produces change orders, and change orders are billed by the hour at a rate you did not negotiate.
Whichever you choose, the engine band is the reference. The mobile app cost page produces it for the mobile niche; the web app development cost page produces it for browser-based products; and the MVP cost calculator prices a first version by scope. The full table of rates by platform and region is the rate database, and how the bands are built is on the methodology page. Country pages with local context on how quotes are written: US, UK, Australia and India.
How to use the calculator with an hourly quote
1. Pick the scope that matches the quote's feature list and the team type that matches who will do the work.
- 2. Switch the market to where the developer sits, not where you sit. The rate follows the developer.
- Multiply the quoted hours by the quoted rate, and put the result against the band the calculator returns.
- If the result is below the band, go through the list in the section above: store submission, QA, hosting setup, handover. One of them is missing.
- If it is above, ask for the hours per feature and cut from the list rather than negotiating the rate. A lower rate from the same person is the same hours with less goodwill.
The calculator prices the mobile niche by default on this page. Use the market switch inside it to compare the same scope across regions before you decide where the team should sit.
Sources
1. Hourly rate table by region and platform, custom development row used for app work: https://projectcostestimator.com/rate-database (source: Clutch Apr 2026, Talmatic Global Snapshot, Arc.dev, Upwork medians, TechReviewer, calibrated to real 2026 agency and freelancer benchmarks)
- 2. Project Cost Estimator engine, calibrated against 600+ project quotes and public rate benchmarks across 6 markets. Method: https://projectcostestimator.com/methodology
- Mobile app calculator, the scope-side bands used in the cross-check: https://projectcostestimator.com/mobile-app-cost
Hourly rates used (custom development, per hour, US dollars): United States freelancer $88–$218 (median $135), agency $145–$385 (median $232); United Kingdom freelancer $72–$190 (median $120), agency $130–$319 (median $202); Australia freelancer $72–$190 (median $120), agency $130–$334 (median $202); Western Europe freelancer $65–$168 (median $105), agency $116–$283 (median $185); Eastern Europe freelancer $29–$95 (median $52), agency $65–$168 (median $105); South Asia freelancer $16–$62 (median $31), agency $36–$109 (median $63).
Worked examples (hours times median rate): 160 hours at $135 is $21,600, at $232 is $37,120, at $120 is $19,200, at $52 is $8,320, at $31 is $4,960; 700 hours at $135 is $94,500, at $232 is $162,400, at $120 is $84,000, at $52 is $36,400, at $31 is $21,700; 1,500 hours at $135 is $202,500, at $232 is $348,000, at $120 is $180,000, at $52 is $78,000, at $31 is $46,500.
Engine mobile bands used in the cross-check: US freelancer smallest version $16,100–$32,200, medium $74,250–$148,450, complex $165,050–$330,100; US agency smallest version $27,600–$55,250, medium $127,450–$254,950, complex $283,600–$567,200; Eastern Europe freelancer smallest version $6,250–$12,550, medium $28,650–$57,350, complex $63,650–$127,350; South Asia freelancer smallest version $3,800–$7,550, medium $17,100–$34,250, complex $38,000–$75,950.
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 EstimateFree · No signup · Results in 2 minutes