How to set freelance rates that actually pay the bills
Most freelancers undercharge because they price against a salary number that doesn't include any of the costs an employer used to absorb. Here is the math that fixes it.
Almost every undercharging freelancer I've met made the same mistake: they took the salary they wanted, divided by 2,080 working hours a year, and called that their hourly rate. That number is wrong by a factor of roughly two. Here is why, and how to fix it before your next proposal.
The hidden cost of being your own employer
When you were employed, your company quietly paid for health insurance, retirement contributions, paid leave, sick days, software licenses, hardware, training, the payroll-tax employer share, an accountant, and the empty hours between projects. As a freelancer, every one of those line items moves onto your invoice — or you absorb the loss. Industry surveys consistently put the true cost of an employed worker at 1.25 to 1.4 times their base salary. You need to bill enough to cover the same multiplier on yourself.
The billable-hours problem
A year has 2,080 working hours on paper. In practice, very few freelancers bill more than 1,200 of them. The rest disappears into proposals, admin, marketing, learning, sick days, and the gaps between contracts. Divide your target income by 1,200, not 2,080, and the realistic rate suddenly looks very different.
A working formula
- Take the salary you want to earn.
- Add 30% for benefits and employer-side taxes.
- Add your annual business overhead (tools, accountant, insurance, coworking).
- Add a 15–20% buffer for retirement and a cash cushion.
- Divide by 1,200 billable hours.
A freelancer wanting the equivalent of an $80,000 salary, with $6,000 of annual overhead and a 15% buffer, lands at roughly ($80,000 × 1.3 + $6,000) × 1.15 ÷ 1,200 ≈ $105/hour. Most people quoting "around $50" are systematically losing money.
Hourly vs. day vs. project
Hourly billing rewards inefficiency and caps your upside. Day rates are friendlier for both sides — clients budget in days, and you avoid arguments about a 15-minute call. Project-based pricing works when the scope is genuinely fixed and you have enough past data to estimate accurately. Value-based pricing (a percentage of the outcome) is the highest-leverage model, but only viable once you can credibly tie your work to revenue or savings the client recognises.
How to raise rates without losing clients
Raise the rate for new clients first, not existing ones. Once two or three new contracts come in at the higher number, give existing clients 60 days' notice and bump them with a brief note framed around continued investment in tooling and reliability. Most stay. The ones who don't were the ones quietly eroding your margin anyway.
What to put on the invoice
However you price, the invoice itself should be clear: rate, units, scope description, and any expenses listed separately. Bundling everything into a single "Services rendered — $4,000" line invites questions and slows payment. AetherInvoice's default template keeps the line-item structure even for project-priced work, with a single rate row and zero quantity, so the total reads cleanly.
The mindset shift
Your rate is not what you're "worth" — it's the price at which your business stays solvent. Pricing low to be "fair" only guarantees you'll quit freelancing in two years. Price for the business you want to still be running in five.