How much a developer hour really costs

We’ll break down both numbers separately — the mistake usually hides in both at once.

Salary isn’t cost

An engineer on a $60,000 salary costs your studio well over $60,000. On top of salary come employer taxes and mandatory contributions, benefits, hardware and software licences, and a share of office and operating overhead. And then there’s paid time you’ll never bill a client — holidays, vacation, sick days, stand-ups, training, internal work — which makes every billable hour more expensive.

Miss any of these pieces and every margin number down the line comes out inflated. Hourly cost isn’t an accounting formality — it’s the anchor number for the whole studio’s economics: project margin, the minimum rate and the floor of any fixed-price quote all start here.

What goes into the fully-loaded hourly cost

The fully-loaded annual cost is everything hiring this person costs your studio over a year:

• Salary (gross)
• Employer taxes and mandatory contributions
• Benefits, hardware, software licences
• Share of office and operating overhead
• Not a separate line: paid holidays, vacation and sick days are already in the salary — they come in at the next step, when you divide by billable hours

How much this adds on top of salary depends on your country and studio; a common rule of thumb is 30–50%. An example at 40%:

And this number is different for every role. With the same taxes, overhead and utilization, a senior on a $90,000 salary works out to roughly $81 an hour; a junior at $35,000, to about $35. That’s why a single “studio average rate” is dangerous: it hides who actually earns the margin and who works at break-even.

Divide by billable hours, not calendar hours

This is where most owners slip. A work year has about 2,080 hours, but you won’t bill the client for all of them. Subtract holidays and vacation, sick days, stand-ups, onboarding, internal work and admin — and the genuinely billable hours land closer to 1,500. That’s what you divide the full cost by.

Divide by the calendar 2,080 out of habit and you get about $40 — understating your cost by more than a quarter. The same mistake in reverse: dividing the bare $60,000 salary by 2,080 gives a “comfortable” $29 that has nothing to do with reality.

The share of billable hours in your total time is called utilization, and it moves your hourly cost directly: the lower the utilization, the more expensive each billable hour becomes — at the same salary. So the denominator can’t be a guess; utilization should be measured from actual hours. More in the breakdown of billable vs non-billable hours.

What this number changes in fixed-price quotes

Once you know your hourly cost, a fixed-price quote becomes arithmetic: estimated hours × fully-loaded cost = your floor in money. Everything above is margin; everything below is a loss you agreed to in advance, before the project even started.

Example. You bill this engineer to the client at $90 an hour. Margin on their time is about (90 − 56) / 90 ≈ 38%, and that’s before any project overruns. Cut the rate to $65 “to win the deal” and you’re left with ~14%, where any overrun pushes the project into the red. And $50 — which looked generous on the salary calculator — is actually below cost: at that rate you’re paying the client for the privilege of working.

Tie hourly cost to live project margin and you stop discovering deals like these after the fact — in the quarterly report, when nothing can be changed.

Overtime quietly raises project cost

Overtime on a salaried engineer looks free — the salary is fixed, after all. It’s an illusion. On a fixed-price project every overtime hour is an hour the quote never priced: the work got done, the time was spent, and none of it made it into the estimate. If you pay for overtime, it adds cost directly; if you don’t, it eats capacity that could have been billed elsewhere — and a team that regularly stays late burns out. Your hourly cost can still read $56 while the project costs more than you quoted. Counting overtime is the difference between the real margin and a flattering one.

A practical consequence: revisit your hourly cost at least once a quarter. Salaries rise, the team mix changes, utilization dips — and the old number is already lying, and with it every estimate that leans on it.

Five mistakes that make hourly cost lie

The number usually breaks in the same few places. A quick checklist to test yourself:

• Dividing by calendar hours. 2,080 instead of ~1,500 understates cost by more than a quarter.
• Forgetting overhead. Rent, software, hardware and admin staff are part of every billable hour too.
• Treating overtime as free. It doesn’t show on a salaried payslip, but it eats billable capacity.
• Confusing the client rate with cost. $90 on the invoice and $56 in cost are two different numbers; margin lives between them.
• Using one “studio average”. A junior and a senior cost differently; averaging hides the loss-making roles.

See your hourly cost and margin in real time

You can work all this out in a spreadsheet once a quarter. The trouble is that by the time you do, the loss-making deal is already closed and delivered. AltOrbit turns the salaries, hourly rates and approved overtime you enter into project cost and recalculates margin as the team logs hours — no screenshots, no click counters. Employer taxes and overhead aren’t added automatically, so keep them in the rates you quote. Margin and P&L are part of Pro and of the 30-day trial; how it works is in features.

The product is in early access — join the early access below.