Freelance Pricing Calculator: Hourly, Project and Value

One price, three ways: convert hourly rates, day rates, and project fees into each other using realistic paid hours and a scope-creep buffer — not a guess.

Figures checked against 2026 IRS limits · Reviewed September 2026

Why dividing a day rate by 8 is wrong

A day rate does not buy the client eight billable hours. In a normal working day a freelancer delivers roughly five to six paid hours: the rest goes to email, admin, invoicing, proposals, sales conversations, and breaks — and days off, holidays, and sick days still have to be funded from the hours that do get billed. The calculator's paid-hours default of 5.5 sits exactly in that range, the same assumption behind the day rate converter. The arithmetic difference is large. Dividing a $440 day by the 8-hour habit suggests $55 an hour; converting it at 5.5 paid hours returns $80 — the rate you started from. Run in the other direction, an $80/hr rate does not justify a $640 day either: clients compare your $440 to a competitor's $440, not to day-rate folklore. State the assumption when you quote — "day rate $440, based on 5.5 hours of focused delivery" — and your effective hourly rate stays honest in both directions.

The scope-creep buffer: why 20% is the default

Fixed-fee work carries a risk hourly work does not: your hours are an estimate, and estimates are wrong. Revision rounds nobody counted, a late stakeholder with new opinions, edge cases the brief never mentioned, and the "small" requests that arrive after kickoff — on a 40-hour project they routinely add five or ten hours. The buffer field prices that risk into the quote instead of donating it. At the 20% default, an $80/hr × 40-hour job becomes $3,840 rather than $3,200; if the work runs to 45 hours you still clear your target. The buffer also works in reverse as a reality check: a $4,000 fixed fee over 40 hours with a 20% buffer implies $83.33/hr of real delivery pay, not the $100/hr the raw division suggests — $667 of that fee is buffering risk, not buying your time. Use 10% when the scope is locked in writing with a change-order clause, 20% as the everyday default, and 30% when the client is still describing what they want — or keep the unknowns on an hourly rate.

Which pricing mode clients prefer

Clients pick pricing modes to manage their own risk, and mirroring that choice gets proposals accepted more often than being cheapest. Fixed project pricing is preferred when the client wants budget certainty: one number approved before work starts, with overrun risk transferred to you — it works once deliverables can be defined. Day rates suit uncertain scope on a known calendar: the client books your week while requirements are still moving, and you are paid for focused presence without justifying every hour. Hourly billing is the default for small or exploratory jobs nobody can estimate yet — the invoice tracks the timesheet, so trust is automatic, and it is the safest mode when scope is genuinely undefined. A practical pattern many freelancers follow: quote project pricing for defined work, day rates for discovery and sprints, and hourly for fixes, support, and anything the brief cannot pin down yet.

Project pricing rewards speed

Hourly billing caps your income at the clock: 40 hours at $80 is $3,200, but finish the same work in 30 and you bill only $2,400 — being faster earns you less, and being slow costs you nothing (the client pays every hour you log). Fixed-fee work reverses that. The $3,840 project delivered in 30 hours is an effective $128/hr; the same project dragged to 50 hours falls to $76.80/hr — below the hourly rate you started from. This is why project pricing rewards skill: every template, snippet, checklist, and automation you build raises your effective rate without changing the invoice, and the client benefits too, getting the outcome sooner at a price that never moved. The discipline that makes it work is the written scope plus the buffer above; without them, speed only protects you from underpaying yourself.

What your rate must cover: the cost breakdown

Every hourly figure the converter produces has to fund four costs before it becomes income. The table uses illustrative example shares to show the structure — your own shares come from the hourly rate calculator and the tax set-aside calculator.

Illustrative example of what a freelance rate must cover (structure only — replace shares with your own)
CostWhat it isHow to allow for it
Business overheadSoftware, insurance, hardware, training, home officeIllustrative example: add 10–20% on top of your salary target before dividing by billable hours
Self-employment taxSocial Security and Medicare on freelance profitSite standard: 15.3% on 92.35% of net profit — set aside per the tax calculator
Non-billable timeAdmin, sales, invoicing, breaks, time off funded by billed hoursIllustrative example: price at 5.5 paid hours per day (this page's default), not 8
Reserves and scope riskBookkeeping gaps, late payment, revision overrunsIllustrative example: 20% scope buffer — $80 × 40 hours = $3,200 quotes at $3,840

Every figure above is hand-checked: the worked example was recomputed independently of the calculator code, and tax figures track 2026 IRS limits. How we check every page.

Related tools

Start with the hourly rate calculator to build the rate everything else multiplies. Use the day rate converter for the pure hours-in-a-day question, and the break-even calculator to see the monthly revenue this pricing has to produce. The full walkthrough — formulas, worked examples, and which mode to lead with — is in the pricing mode converter guide. Role benchmarks: what writers charge, what developers charge, what designers charge. Estimates for education only — not financial advice.

Frequently Asked Questions

How many hours are in a freelance day rate?

Treat a working day as five to six paid hours, not eight. Admin, sales, invoicing, breaks, and unpaid time off all come out of the day, and the calculator's 5.5-hour default sits in the middle of the realistic range. At that default, $80 an hour converts to a $440 day — not the $640 the 8-hour assumption implies. Set the paid-hours field to what you actually deliver: deep-focus work is usually 5-6 hours, while on-site days packed with meetings can reach 7-8.

What buffer should I add to a project quote?

Twenty percent is a practical default and what the calculator uses. It covers scope creep — the extra revision rounds and late requests — plus error in your own hour estimate, and on a 40-hour job it turns $3,200 into $3,840. Drop to 10% when the scope is locked in writing with a change-order clause; go to 30% when the client is still describing what they want, or price those unknowns hourly instead.

When do clients prefer hourly, day rate, or project pricing?

Clients reach for fixed project pricing when they want budget certainty for a defined deliverable, day rates when the scope is uncertain but the calendar is booked, and hourly billing for small or exploratory jobs that nobody can estimate yet. Mirroring the client's risk concern — rather than defaulting to your own habit — is what makes a proposal easier to accept.

Does project pricing really pay more per hour?

It can, because it rewards speed. On hourly billing the invoice follows the clock — 30 hours at $80 earns $2,400, 40 earns $3,200, so finishing faster shrinks your invoice; a $3,840 fixed fee finished in 30 hours is $128 an hour. The catch: run past the buffer — 50 hours on that same fee — and you drop to $76.80, below your hourly rate. Fixed fees only pay more when the scope is written down and the buffer stays intact.

How much should I charge as a freelancer?

Charge what your costs, utilization, and benchmarks require: build the hourly floor from income, expenses, and tax, convert it at 5.5 paid hours per day — $80 an hour is a $440 day — and add a 20% scope buffer to fixed quotes, so $3,200 becomes $3,840. Compare hourly, day, and project modes in the converter above before you quote.