Pricing Mode Converter: How to Price the Same Work 3 Ways

By Maya Ellison · Updated September 2026

The same forty hours of work can be quoted as an hourly rate, a day rate, or a fixed project fee — and the three numbers can look wildly different while meaning exactly the same thing. Clients ask for whichever format fits their risk tolerance, and freelancers who cannot convert fluidly either over-quote, under-quote, or lose the proposal to someone who sounded more confident. This guide converts one real price three ways ($80 an hour, a $440 day, a $3,840 project), gives you the six formulas as a table, walks the full worked example, dismantles the divide-by-8 habit, and shows how a 20% buffer turns a fixed fee from a gamble into a business. Run your own figures in the pricing mode converter as you read — every section maps to a field in it.

The three pricing modes — and when clients prefer each

Hourly pricing sells time. The client pays for the hours actually spent, the invoice matches the timesheet, and trust comes for free because nothing is hidden. Clients reach for hourly on small, exploratory, or poorly defined jobs — nobody can estimate the work yet, so the client refuses to commit to a total. The trade is that the client carries the risk of an open-ended total while you carry the risk of being slow: finish early and you earn less, take forever and you still earn the same. Hourly also punishes efficiency, which is exactly why experienced freelancers migrate off it once they have data.

Day-rate pricing sells a working day. The client books your Tuesday through Friday, scope is allowed to move inside those days, and you are paid for focused presence rather than justified minutes. Clients prefer day rates when the scope is genuinely uncertain but the calendar is certain — discovery phases, workshops, embedded sprints, advisory weeks. It sits between the other two: more budget predictability for the client than hourly (they know the day's price before the week starts) and less risk transfer for you than a fixed fee. The only field it needs is honest paid-hours math, covered in the freelance day rate pricing guide.

Project (fixed-fee) pricing sells an outcome. One number, approved before work starts, covering a defined deliverable — and the client loves it for one reason: budget certainty. Procurement can approve $3,840 in a way they cannot approve "somewhere between $3,000 and $5,000, honestly we don't know yet." Fixed fees are preferred for defined deliverables — a website, a report, a migration, an integration — where the scope can be written down. The risk transfers to you: overrun and you absorb it. In exchange, you get the upside of speed, which is where the interesting math starts.

The conversion formulas

Six directions, two assumptions (paid hours per day, default 5.5; scope buffer, default 20%), one tool. Formula: day rate = hourly × paid hours per day; project price = hourly × scope hours × (1 + buffer). The buffer applies only where a fixed fee is involved — it is the contingency you add when quoting, and the contingency you strip when auditing what you actually earned.

Two properties are worth checking yourself. First, conversions are exact round trips: the day rate converts to a project fee that converts back to the same day rate, because the buffer is added on one leg and removed on the other. Second, only the two directions involving a fixed fee touch the buffer — comparing hourly to day rates is pure paid-hours arithmetic, which is why the paid-hours assumption deserves your full attention.

Worked example: $80 an hour, three ways

Start where most freelancers start: a rate. You charge $80/hour. A client wants you on site four days a week — or five days; the conversation keeps saying "days" without saying hours. At the calculator's 5.5 paid hours per day, your day rate is $80 × 5.5 = $440. Quote $440, say the hours assumption out loud, and the conversion back to hourly is trivial for anyone who asks: $440 ÷ 5.5 = $80. No drift, no argument.

Now the same client wants a project instead: a defined deliverable you estimate at 40 hours. Your base is $80 × 40 = $3,200, and you add the 20% scope-creep buffer: $3,200 × 1.2 = $3,840. That is the quote. Notice what happens when the client instead hands you a number — "we have $4,000 budgeted" — and asks what hourly rate that implies. The naive answer is $4,000 ÷ 40 = $100/hr, and it is wrong: a 20% buffer means only 83.33% of the fee is buying delivery time. The honest conversion is $4,000 ÷ (40 × 1.2) = $4,000 ÷ 48 = $83.33 an hour — the calculator rounds the display to $83.33, and roughly $83 is the number to keep in your head. The $667 difference is not your rate; it is the contingency the fee carries.

One more leg closes the loop. Take the $3,840 fixed fee and convert it back to a day: strip the buffer ($3,840 ÷ 1.2 = $3,200), spread it over the project at 40 hours with 5.5 paid hours per day ($3,200 ÷ 40 × 5.5), and you land on $440 — exactly where you started. Three modes, one price, no leakage. If your conversions do not round-trip like this, an assumption is inconsistent somewhere, and the tool will show you which one.

The divide-by-8 trap

Every freelance forum contains the same shortcut: day rate ÷ 8 = hourly. It is wrong, and it is wrong in a direction that quietly costs money. An eight-hour day assumes you bill every hour you work — that admin, email, proposals, sales calls, invoicing, breaks, and training all happen outside working hours, and that holidays, sick days, and time off are paid by someone else. They are not. In practice, freelancers deliver about five to six paid hours a day; most freelancers bill only about half to sixty percent of working hours once non-billable time is counted.

Run the numbers. A $440 day ÷ 8 suggests $55 an hour — a full 31% below the $80 you actually earn, which is how freelancers talk themselves into "I must be charging too much" and discount mid-conversation. The reverse error is just as bad: $80/hr × 8 = a $640 "day rate" no client will pay when the comparable quote is $440. The fix is one field: set paid hours per day to 5–6 for focused work (development, design, writing), higher only for on-site days that are genuinely wall-to-wall billable. The day rate converter makes the same point for the two-way case; the pricing mode converter applies it across all six directions.

The buffer and the waterfall: protecting the quote from scope creep

Scope creep is not an event, it is a flow — small requests arriving continuously after the brief: one more revision round, the "tiny" copy change, the stakeholder who joins late with opinions. The 20% buffer is the catchment built under that flow, and it behaves like a waterfall: overruns drain the buffer layer by layer, and only when it is exhausted does money start falling past your target rate.

The arithmetic makes the protection concrete. On the $3,840 project, the buffer is $640 — and at your $80/hr rate, $640 ÷ 80 = eight extra hours. The quote silently converts "40 hours" into "up to 48 hours at full rate": finish in 44 and you still clear $80/hr; finish in exactly 48 and you still earned exactly $80/hr ($3,840 ÷ 48); step to 50 and you are at $76.80 — below target. That is the waterfall line. It reframes the buffer not as padding on the price but as paid tolerance in hours, which is how to set it: if your experience says a project like this typically wanders 10%, quote 15%; if the client is still describing what they want, quote 30% or move the unknowns to an hourly rate. A written scope with a change-order clause is what keeps the waterfall from running dry — the clause is where overflow gets redirected when a request falls outside it. The buffer is priced risk; the change clause is refused risk. You need both.

Which mode maximizes your income

Effective hourly rate = fee ÷ hours actually spent. Hold that equation still and the three modes differ in one way only: who captures the gain when you get faster.

Under hourly, the client does — you don't. Speed gains return to the client as a smaller invoice. Under a fixed fee, you do: the $3,840 project delivered in 30 hours is $128/hr; the same project in 25 hours is $153.60. Every template, snippet, checklist, and automation you build raises your effective rate without touching the invoice — this is the single strongest economic argument for project pricing, and it compounds yearly. Under day rates the gain is partial: being booked for four days pays four days regardless of pace, so efficiency shows up as spare capacity for other work rather than a higher invoice.

The pattern that follows is a sequencing strategy, not a rule. Early in a service, when your estimate data is thin, bill hourly or by day: you are gathering the delivery statistics that make fixed fees survivable, and the client's willingness to pay time-based is highest when nobody can predict the work. Once you have completed several similar jobs and know they take 35–45 hours, quote the fixed fee with the buffer — you now hold the estimating edge, and every speed gain is yours to keep. Clients still get what they came for: budget certainty on the number, day-rate flexibility in the middle, hourly granularity at the edges. Bid the mode that answers the client's risk question and the pricing stops being a gamble; full conversion math lives in the pricing mode converter.

Run your own numbers

Open the pricing mode converter, pick a direction, and enter your real rate — then test the round trip: hourly → project, project → hourly, and compare with what you last quoted. Set paid hours per day to what you actually deliver (5–6 for most focused work) and leave the buffer at 20% unless your scope documentation says otherwise. Next, check the rate underneath it: the freelance hourly rate guide builds a defensible floor from income goal, expenses, and tax, and the hourly rate calculator runs it. A pricing mode is only as strong as the number being converted. This guide and its calculator are for education only — not financial, tax, or legal advice; for large or unusual engagements, a quick review with your accountant is money well spent.