Software Development Cost Breakdown 2026: Where the Money Goes

These shares come from the estimates we write and from the competing proposals clients bring to first calls. The totals above assume a blended rate of $45–80 an hour, which is what CEE and Latin American vendors charge in 2026, and they include every role a working product needs. If you need the totals explained in more depth (complexity tiers, product types, regional rates), start with our software development cost guide. This article is about the inside of the number.

Where a typical software budget goes

Founders often picture a budget as developers multiplied by months. Then the first detailed quote arrives with a designer, a QA engineer, a project manager, a DevOps line and a contingency, and it looks padded. It isn't. Every one of those roles exists because skipping it costs more somewhere else.

Here is how a healthy budget splits across six lines, and how the split moves as products get more complex.

Two things stand out. Engineering shrinks as a share while the absolute amount grows, because complexity creates coordination, testing and infrastructure work faster than it creates features. And the buffer grows, because complex products carry more unknowns into the build. When a quote for a regulated platform shows 65% engineering and 8% QA, the vendor is not more efficient. Something is missing.

The breakdown by phase, with dollar amounts

Percentages are easier to argue with when they turn into money. This table applies the mid-size split to a $175k build, which is roughly 3,000 hours with a CEE team at a $58 blended rate.

Discovery: the cheapest line with the biggest effect

Discovery is two to six weeks of a business analyst, a designer and a tech lead turning an idea into a list of buildable items with hours next to them. It feels like paying for documents. In practice it is where we remove the most money from projects: in most discovery phases we run, a quarter or more of the original feature list moves to a dated version-two list once the client sees what each item costs. It also catches the integration that has no sandbox before anyone signs a fixed price on it. Our business analysis team does this work, and our guide to software development cost estimation explains how the hours behind each item are built.

Design: cheap to change in Figma, expensive in code

Moving a button in a mockup takes minutes. Moving it after the backend, frontend and tests are built takes a day across three people. That is the whole argument for a design phase before engineering. The share drops to 5–6% for internal tools built on a UI kit and climbs to 12–15% for consumer products where the interface is the brand.

Engineering: where scope turns into hours

Inside the engineering line, backend and integrations usually take the larger part (roughly 50–60% of engineering on a product with a web app and a cross-platform mobile app), with frontend and mobile splitting the rest. Each integration is its own small project. A well-documented API such as Stripe takes days; a partner system without documentation can take weeks. If integrations make up a large part of your scope, our API integration cost guide breaks them down further.

QA, PM and DevOps: the lines buyers try to cut

These three are where quotes get "optimized" during negotiation, and where we most often trace the overruns in projects that reach us halfway through. We cover them in detail below, because cutting them is the single most expensive saving in software.

Calculate your own breakdown

Enter a budget, or the quote you already have, and describe the project. The calculator splits it into the six lines plus contingency, then converts the working budget into hours at the rate you pick. Use it to check whether a vendor's breakdown looks like a real team or like engineering with everything else trimmed off.

Try the same $180k with the US onshore rate and then the CEE rate. The split stays the same; the hours change from about 980 to about 2,700. That is the honest way to compare regions: the same budget buys a very different amount of work, and the question is whether the cheaper hours come with the overlap and seniority you need.

The breakdown by role

Phases describe when money is spent. Roles describe who it pays. On a mid-size product built over five to seven months, the team usually looks like this.

Rates differ by role, so the dollar split is not identical to the hour split. Senior engineers and DevOps cost more per hour than QA. Here are typical 2026 ranges we see in proposals.

These are vendor rates, which include everything the vendor pays for. Country-by-country detail is in our nearshore software development rates guide. One note on geography: Gilzor works from Poland and Cyprus, which for a US company is offshore, not nearshore. Warsaw is six hours ahead of New York, so East Coast teams get two to four shared hours with shifted schedules; West Coast teams get very little. Latin America gives more overlap at similar rates. That is a real trade-off and worth pricing in.

Built by Gilzor

Results we’ve shipped

70+products launched

98%delivered on time

85%clients come back

Aviation33%faster baggage weigh-inWeb and Mobile application for Airlines→Healthcare+30%lab test ordersMedical Lab Web and Native Mobile Applications→Retail · Startup700+stores aggregatedMobile application for Grocery shops→

Talk to the people who build it. Tell us about your project and get a free estimate of scope, timeline and cost.

See how we’d approach yours →

What is inside an hourly rate

A buyer looking at a $60 rate often does the math backwards: "the developer probably earns $30, so the vendor keeps half." Some of that half is margin. Most of it is cost that an in-house team has too, just spread across other budgets.

The in-house figure is built from public data. The US Bureau of Labor Statistics put the median annual wage of software developers at $135,980 in May 2025 (and $104,300 for QA analysts and testers). Its Employer Costs for Employee Compensation survey for June 2025 found that wages make up 70.2% of private-industry compensation costs and benefits the other 29.8%. Gross the salary up and divide by roughly 1,800 working hours, and a median US developer costs about $105 an hour before you pay a recruiter, buy a laptop or count the manager's time.

The vendor rate covers those extras, which is why comparing it to a bare salary misleads. Comparing it to a fully loaded hour is closer to fair. The full in-house versus outsourced comparison, with a different calculator, is in the cost of outsourcing software development, and the pricing models (T&M, fixed price, retainer) are compared in staff augmentation pricing models.

Where is your money most at risk?

Every project has one line that is most likely to overrun. Six questions point to yours, so you know which part of a vendor's breakdown to scrutinize first.

Cutting QA, PM or discovery: what it really costs

When a client asks us to bring an estimate down, the first suggestion is almost always one of the non-engineering lines. On paper it works: removing QA takes 15% off the quote instantly. Here is what happens next, in the projects that come to our tech troubleshooting team after someone tried it.

• No QA. Developers test their own happy path. Edge cases, older devices and regression go untested, so each release breaks something that worked last month. The bugs get found by users, and every production fix includes investigation, a hotfix release and re-testing. Inside our own projects we track how many tasks QA sends back to developers; it is 5%, and keeping it there is what keeps rework hours out of the engineering line.
• No PM. The vendor's developers wait on the client, the client waits on the vendor, and nobody owns the gap. A week of a four-person team waiting costs about as much as two months of a part-time PM. If you are running the team yourself, our notes on project management show what the role actually covers.
• No discovery. The scope gets written during the build, one change request at a time, at engineering rates rather than analyst rates.
• No DevOps. Releases are manual, environments drift, and the first outage happens without monitoring. Adding CI/CD and infrastructure as code later costs more than setting it up in week one.
• No contingency. The overrun still happens. It just arrives as an unbudgeted invoice instead of a planned line.

The statistics agree with what we see. The Standish Group's 2020 CHAOS report counted 31% of software projects as successful, 50% as challenged (late, over budget or short on features) and 19% as failed. Research by McKinsey with the University of Oxford on more than 5,400 large IT projects found they ran 45% over budget on average while delivering 56% less value than planned. The causes they name (unclear objectives, shifting requirements, weak execution) map directly onto the lines buyers cut.

Costs the build breakdown leaves out

A breakdown of the build ends at launch. Owning software keeps costing money every month, and these lines rarely appear in the first quote.

On a $175k build, maintenance alone is roughly $26k–35k a year. For most products we recommend a small retained capacity (a part-time developer and QA) over ad-hoc requests; our development support model is set up that way.

How to lower each line without breaking the product

The safe way to spend less is to reduce the amount of work, not the roles that keep the work correct. By line:

1. DiscoveryKeep it, but time-box it to two to four weeks for a focused first release. Its output should be a prioritized list with hours, so you can cut by cost, not by guesswork.
2. DesignStart from a mature UI kit and customize it, especially for internal tools and admin panels. Spend custom design hours on the screens customers see most.
3. EngineeringShrink the first release. Buy the commodity parts (auth, payments, email, search, CMS). Choose cross-platform mobile unless you need heavy device features. These moves often remove 25–40% of engineering hours.
4. QADon't cut the share. Automate the regression suite for the flows that make money, and test manually where judgment matters. Automation costs more in month one and less every month after.
5. Project managementOn smaller projects, a part-time delivery manager or a tech lead who owns the backlog is enough. What you cannot cut is someone accountable for decisions and dates.
6. DevOpsUse managed cloud services instead of self-run infrastructure, and set up CI/CD in the first sprint so every later release is cheap.
7. RatePick the region deliberately. CEE and Latin American teams cost 50–70% less per hour than US agencies; price in the time-zone trade-off and judge seniority, not just the number.

AI coding assistants help at the margins. Stack Overflow's 2025 Developer Survey found 84% of developers use or plan to use AI tools, and in our estimates they trim implementation hours on boilerplate and tests. They do not shrink discovery, integration, QA or PM, which is most of what this page is about.

FAQ

Where Gilzor fits

We build web and mobile products for startups and SMBs from Poland and Cyprus, with 70+ projects launched and 85% of clients coming back for more work. Every estimate we send is split by phase and role, with the hours and assumptions behind each line, so you can hold it next to any other quote and see where the differences are.

If you already have a breakdown from another vendor and something looks off (QA too thin, no PM, engineering suspiciously high), send it with your scope. A second look at the lines usually tells you whether the total is wrong or whether it describes a smaller product than the one you want.