Rates & salaries · · 3 min read

Salary versus day rate: the comparison most buyers get wrong

Why dividing an engineer's salary by working days understates the true cost by 30 to 50 percent, and the full calculation to run before comparing hiring against contracting.


A hiring manager sees a €95,000 salary and a €500 day rate and concludes the contractor costs roughly 30% more. The arithmetic behind that conclusion is wrong in three places, and correcting it usually reverses the answer for engagements under twelve months.

The calculation people run

Salary divided by working days. €95,000 over 220 days is €432 a day, against €500 for the contractor. The contractor looks 16% more expensive.

The calculation to run instead

Total annual cost of employment, divided by productive days actually delivered.

Cost side, on a €95,000 base in a Western European market:

Total loaded cost lands between €130,000 and €163,000.

Days side:

Productive delivery days land between 190 and 205, not 220.

At €145,000 loaded across 197 productive days, the effective cost is €736 a day. The contractor at €500 is 32% cheaper, not 16% more expensive.

Where the comparison flips back

This is not an argument that contracting always wins. It stops winning when:

The variable nobody prices

Time to productivity. Hiring a senior AI engineer in Western Europe takes 10 to 16 weeks from approved requisition to first commit, and that is before notice periods. An augmented engineer starts in one to three weeks.

If the work has a deadline, those 9 to 13 missing weeks are not a cost line, they are the whole decision. A team that ships a quarter earlier usually justifies the rate difference several times over, and the comparison never appears in the spreadsheet because it is not a cost, it is foregone revenue.

A cleaner way to frame the choice

Stop asking which is cheaper and ask which risk you would rather hold:

You hold this riskEmploymentContract or augmentation
Wrong hireHigh, slow to unwindLow, 30-day exit
Demand fallsYou keep payingYou stop
Demand risesSlow to addFast to add
Knowledge walks outModerateHigher, unless you manage it
Cost per productive dayHigher under 2 yearsLower under 2 years

The last row is the only one that appears in a budget, and it is the least important of the five.

What to do with this

Three practical steps:

  1. Rebuild your own number. Take one real engineer’s total cost last year and divide by the days they actually delivered. Most teams have never done this and are surprised by the result.
  2. Set the horizon before you compare. Under twelve months, augmentation wins on cost almost regardless of rate. Over three years, employment wins. Between the two it depends on utilisation.
  3. Price the delay. Put a number on shipping a quarter later. If you cannot, the comparison is incomplete.

Current European day rates by role, market and seniority sit on the daily rate benchmark. If you want the loaded comparison run against a specific team shape, the project cost calculator does it directly.