All resources
Money
8 min read

Freelance Rates in 2026: How Much Should You Actually Charge?

A concrete method for setting your rate — based on your costs and target income, not on what a stranger on Reddit charges.


"What should I charge?" gets answered badly almost everywhere, because the honest answer — *it depends* — is useless. So here is a method instead of a number.

Start from the money you need, not the market

Most freelancers pick a rate by looking at what others charge and shading slightly under. That is how a whole market drifts downward.

Work backwards from your actual costs instead.

Step 1: Your target income

Pick the annual figure you need. Not aspirational — the number that covers your life. Say $70,000.

Step 2: Add the costs an employer used to absorb

As a freelancer you now pay for things a salary hid:

  • Self-employment / employer-side taxes
  • Health insurance
  • Retirement contributions
  • Equipment and software
  • Accountant
  • Sick days and holidays — nobody pays you for these

Rule of thumb: add 30%. $70,000 becomes $91,000.

Step 3: Count real billable hours

This is where most calculations break. A year has about 2,000 working hours. You will not bill 2,000.

Realistically, subtract:

  • 5 weeks off (holiday + sick + slow periods)
  • ~30% of remaining time on unbillable work: sales, invoices, admin, learning

That leaves roughly 1,200 billable hours a year. Optimistic, even.

Step 4: Divide

$91,000 ÷ 1,200 = about $76/hour.

That is your floor — the rate at which freelancing matches a $70,000 salary. Not your ambitious rate. Your break-even.

The number surprises people, and it should: a $70k salary is roughly a $76/hour freelance rate. Anyone billing $35/hour and calling it a good living is quietly funding their clients.

Then adjust for reality

Your floor is arithmetic. Your actual rate accounts for:

Specialisation. Generalists compete with everyone. "React developer" competes globally on price. "Accessibility remediation for healthcare apps" competes with almost nobody.

Proof. Concrete outcomes justify higher rates than years of experience. "Cut checkout abandonment 18%" beats "10 years experience".

Client type. A funded startup and a local restaurant have different budgets for the same work. Neither is wrong; know which one you are talking to.

Urgency. Rush work costs more. This is normal and clients expect it.

Hourly vs fixed vs value

Hourly is safest when scope is unclear. It also caps your income at hours × rate and quietly punishes you for getting faster.

Fixed price is better once you can estimate reliably. Get faster, earn more per hour. Requires a written scope, or you will bleed.

Value-based — pricing against the outcome's worth, not your time — pays best and demands the most confidence. If your work will generate $200,000 in revenue, $20,000 is a bargain and hours are irrelevant.

Most freelancers should start hourly, move to fixed within a year, and reach for value-based on projects with a measurable business outcome.

Raising your rate

The cleanest method:

  1. Set your new rate for all new clients, starting now.
  2. Leave existing clients alone until a natural boundary — a new project, a contract renewal.
  3. At that boundary, tell them plainly: *"My rate for new projects is $X from [date]."*
  4. Do not justify, apologise, or over-explain. One sentence.

Some clients will leave. Usually the ones consuming the most time for the least money. That is the mechanism working, not failing.

If nobody ever pushes back on your rate, it is too low. A healthy rate loses you some deals.

Remember what the platform takes

Your rate is not your income. On a 20% platform, $76/hour is $61. To take home the equivalent of $76 you would need to charge $95.

Platform cutCharge to net $76
0%$76
10%$84
20%$95

This is why fee structure is a pricing decision, not an admin detail. On Freelancezero there is no commission — your rate is your income.

Keep 100% of what you earn

Freelancezero charges 0% commission — no fees to apply, no cut of your invoice.

Create a free account

Keep reading