Cost
What You Actually Pay For in a Dev Agency Invoice
8 Jun 2026 · 7 min read · The Contrast
When you pay a dev agency $150 an hour, only about $50 to $60 of that reaches the person writing your code. The rest covers sales, account management, office overhead, unbilled bench time and margin. None of that is a scandal, it is simply how the agency model works, but most invoices hide the split behind a single blended rate. Here is what you are actually paying for, and how to pay for code instead.
The rate is not the developer's wage
Founders often assume a high hourly rate means a highly paid expert is on their project. Sometimes that is true. But the rate is a business number, not a wage. It has to cover everyone at the agency who is not writing your code, plus profit. The developer's salary is just one input.
That is why an agency can bill $150 an hour while the engineer earns a fraction of it. The gap is not pocketed by the developer, it is spread across the whole organisation that surrounds them. The same dynamic plays out across borders too, which we cover in software developer rates by country.
Where the money actually goes
Here is a rough breakdown of where a typical $150/hour agency rate ends up. The exact split varies, but the shape is consistent across the industry.
| Where it goes | Rough share | Reaches your product? |
|---|---|---|
| Engineering (the actual build) | 30–40% | Yes |
| Sales and marketing | 15–20% | No |
| Account and project management | 15–20% | Indirectly |
| Office, admin, tools | 10–15% | No |
| Bench time (unbilled staff) | 5–10% | No |
| Margin (profit) | 10–20% | No |
So of $150, somewhere between $45 and $60 buys engineering. The rest keeps the agency running. These are indicative 2026 figures, not quotes, but they explain why the same scope can cost so wildly different amounts depending on who you hire. We compare those models directly in agency vs in-house vs offshore cost.
The line items worth questioning
A high overhead share is not automatically bad. A good account manager can save you time, and a stable agency needs some bench. The problem is when these costs grow without adding value to your product. Watch for:
- Layers of account managers. If three people relay messages between you and the developer, you pay for all three and the message still degrades.
- Discovery that never ends. Long paid discovery phases can be real work or can be a way to bill before building.
- Blended rates. A single rate for "the team" hides whether a senior or a junior did the work.
- Change requests. Anything outside a rigid scope becomes a paid change, and the scope is written to make that common.
These are close cousins of the traps we cover in the hidden costs of cheap offshore development. In both cases, the fix is visibility.
Why blended rates hide the truth
The single most important thing an invoice can do is show you what you bought. A blended rate does the opposite. It bundles senior and junior time, engineering and management, into one number you cannot take apart. You see the total, not the value.
Transparency flips that. When you can see the rate, the hours and who worked them, you can judge whether you are paying for code or for the building that surrounds it. That is the difference between an invoice you trust and one you simply pay.
How to pay for code, not overhead
You reduce overhead by removing the layers that create it, not by squeezing the engineers. Practical ways to make more of every dollar reach the build:
- Talk to the engineers directly. Cut the relay chain and the cost of running it.
- Demand a visible rate. If you cannot see the hourly rate, you cannot judge the value.
- Bill for hours worked. Weekly billing for real hours beats fixed milestones padded for risk.
- Own your code. Ownership means you are never locked into one provider's pricing.
- Pick senior people. Seniors solve problems in fewer hours, so a higher per-hour rate can still mean a lower total.
What our invoice looks like
We built our pricing to be the opposite of a blended black box. A senior engineer with us starts at about $20 an hour, billed weekly for the hours actually worked. There is no sales team to fund, no account-management relay, no padded discovery. You talk to the engineers building your product, and you own the code from day one.
That means almost all of what you pay reaches the build, which is how the same product can cost a fraction of a US or UK agency total for comparable work. We do not hide the number behind a "request a quote" wall. The rate is on our transparent pricing page, you can estimate your own project with the cost calculator, and a real person will give you a precise figure in a 15-minute callback. Since 2015 and across 320,000+ project hours, we have run on the belief that an invoice should show you exactly what you bought.
FAQ
Quick answers.
What does a dev agency invoice actually pay for?
Only a portion of the rate pays for engineering. The rest covers sales and marketing, account management, office and admin overhead, bench time and margin. At a $150/hour rate, roughly $50–60 reaches the person writing your code.
Why is the agency hourly rate so much higher than a developer's salary?
Because the rate has to cover everyone who is not coding: salespeople, account managers, administrators and unbilled bench time, plus the agency's profit margin. The developer's salary is only one input into that number.
Are agency overheads a scam?
No, they are how the model works. The issue is visibility. When the rate is a single blended number, you cannot see how much is engineering and how much is overhead, which makes it hard to judge value.
How can I pay for code instead of overhead?
Work with a team that shows its rate, bills for hours actually worked, and puts you in direct contact with the engineers. Removing the account-management layers means more of every dollar reaches the build.
