Every founder has seen the pitch: senior developers at a rate that seems too good to be true. Sometimes it works out. More often, the number on the invoice turns out to be the smallest part of what you actually pay. After years of inheriting projects started by the lowest bidder, we've come to a simple conclusion: the hourly rate is the most visible cost of a developer and the least informative one.
The costs that never appear on an invoice
Rework. Weak code doesn't fail loudly on day one — it fails quietly six months later, when the feature built on top of it collapses. In our experience taking over troubled codebases, the rework triggered by early shortcuts routinely costs more than the original build. You pay for the feature twice: once to write it badly, once to write it properly, plus the untangling in between.
Delays. A developer who costs half as much but takes three times as long is not a bargain — and the calendar cost compounds. Every slipped sprint delays revenue, burns runway, and keeps your product team blocked. The most expensive thing about a slow engineer is rarely their invoice; it's what the rest of the company couldn't do while waiting.
Your own attention. Struggling engineers consume disproportionate management time — more detailed specs, more review cycles, more meetings to clarify what should have been obvious. That time comes out of your senior people's output, which is usually the scarcest resource in the building.
The agency games that make it worse
Opaque margins. Here is the uncomfortable arithmetic of much of the industry: an agency bills you a "competitive" rate while paying the engineer a fraction of it. The gap can be enormous — and it creates a perverse incentive to staff the cheapest engineer the client won't notice. When you can't see the split, you can't see the incentive. That's why we publish ours: a low flat margin on top of what the engineer actually earns, visible in every contract. Strong engineers also gravitate to arrangements where they keep more of the rate, which quietly raises the quality of the pool — more on that on our Why Dillo page.
Seniority misrepresentation. The oldest trick in outsourcing: the "senior" on the invoice is a mid-level engineer with an inflated CV, or worse — the impressive architect you interviewed disappears after the kickoff call and the actual work lands on someone you've never met. If a vendor won't let you interview the specific engineers who will write your code, that is not a red flag; it's the whole flag.
A useful mental model: total cost = rate × time × rework factor + management overhead + opportunity cost of delay. The rate is the only term the "cheap" pitch talks about — and it's often the smallest one.
Why senior engineers are usually the cheaper option
A genuinely senior engineer costs more per hour and less per outcome. They ask the question that removes a week of work. They build the boring, reliable version instead of the clever, fragile one. They flag the requirement that doesn't make sense before it becomes code. In our experience, one strong senior frequently outships two juniors while producing a codebase the next person can actually maintain — which is why our staff augmentation bench is senior-only by policy, not by accident.
You don't save money by paying less per hour. You save money by paying for fewer hours, less rework, and zero surprises.
What to demand instead of a lower rate
- Margin transparency. Ask exactly what the engineer is paid and what the provider keeps. A fair partner answers in one sentence.
- Interviews with the actual engineers — the people who will commit code, not a sales-engineer stand-in.
- Verifiable seniority. A real technical interview by your team beats any CV or vendor rating.
- An easy exit. Short notice periods and clean IP terms keep the incentive to perform alive every month.
If you want a fuller vetting script, we wrote one: 7 Questions to Ask Before Hiring a Remote Development Team.
Key takeaways
- The hourly rate is the most visible cost and the least informative; rework, delays, and management overhead dominate total cost.
- Opaque agency margins create an incentive to staff the cheapest engineer you won't notice — demand to see the split.
- Seniority misrepresentation is common; always interview the specific engineers who will do the work.
- Senior engineers usually cost less per outcome, even at a higher rate.
- Optimize for transparency and an easy exit, not for the lowest number on the pitch deck.
Curious what a transparent quote looks like? Ask us for one — engineer pay and our flat margin, side by side.