The number that confuses every buyer
A salaried senior developer in the US earns roughly $90–140k a year, call it $45–70/hour on paper. A freelance senior developer quotes $75–150/hour. The buyer's instinct: "the freelancer is double the price." The reality: the freelancer is not keeping double, the rate is buying an entire business, and once you see the line items, the two numbers converge fast.
What a rate actually contains
- Non-billable time, the biggest line. A freelancer bills maybe 20–25 hours a week in a good month. Sales, proposals, admin, accounting, learning, and the unavoidable gaps between projects consume the rest. The $100/hr becomes roughly $50/hr of actual paid time before any other cost.
- The business overhead a salary hides. Software and tools (hundreds monthly), hardware, insurance (health, liability), professional development, retirement (no employer contribution), taxes both sides of what an employer would pay, and the accounting to stay legal across borders.
- Risk absorption. No paid sick leave, no paid vacation, no severance, the freelancer prices the dry months into the busy ones, or goes out of business quietly.
What this means for hiring decisions
Stop comparing a freelancer's rate to an employee's salary, compare the freelancer to what an employee actually costs (salary + taxes + benefits + equipment + the management overhead, typically 1.25–1.5× salary), and then compare what you get: a specialist engaged for exactly the hours needed, no desk, no long-term commitment, and incentive alignment (freelancers eat their own overruns; salaried time simply... passes). The full rate context by region and seniority lives on the pricing page and the region pages; the hourly engagement page covers when hourly is the right model at all. And the resentment test, honestly: if a rate feels high, ask what a year of that rate buys compared to a year of employment, for scoped projects, the freelance number usually wins on math alone, before quality enters.