Products have prices; services have pricing models, and the model matters as much as the number. The same expertise, sold by the hour, by the day or by the project, produces three different incomes, three different client relationships and three different allocations of risk — who pays when the work takes longer than expected, and who profits when it takes less. Choosing carelessly between them is how skilled people end up busy, appreciated and underpaid.
Time-based pricing — hourly or day rates — is transparent and flexible, and it caps your income at your hours while charging the client for your learning curve and your slow afternoons alike. Project fees invert the trade: the client buys certainty and a defined outcome, and you take the estimation risk in exchange for keeping the gains when your experience makes the work fast. Neither is more “professional”; they suit different work, different clients and different stages of a practice.
This article compares the models honestly, shows the conversion arithmetic that keeps a project fee anchored to a floor rate, and describes the hybrid structure most established service businesses quietly converge on — because it prices risk where risk belongs.
Time-based pricing: honest, capped, and quietly corrosive at the edges
The day rate's virtues are real. It is legible — clients budget in days. It flexes — exploratory work, support and consultancy genuinely cannot be scoped in advance, and time pricing lets them start without a fiction. And it is fair in one direction: work that grows is paid for as it grows, without renegotiation theatre. For work whose scope is truly unknowable, it remains the only honest structure.
Its costs accumulate at the edges. Income is hard-capped by available days, so the model pays you least in the years your expertise is greatest — experience makes you faster, and time pricing converts that speed directly into lower earnings per job. It also aligns your interest against the client's in a way both sides can feel: they watch the clock you are billing. And it exposes you to the utilisation trap: a practice sold by the day must keep selling days forever, including the ones spent selling them, which is why time-priced practices feel frantic even when they are profitable.
Project fees: selling the outcome, owning the estimate
A project fee prices the deliverable — the website, the audit, the campaign — at a figure agreed before work begins. The client buys budget certainty and a supplier motivated to be efficient. You buy the possibility that expertise compounds: the tenth time you build something, it takes half the days of the first, and under a fee the saving is yours rather than refunded to the client as a shorter bill. Value-based fees are the far end of this model: pricing against the worth of the outcome — the loss prevented, the revenue enabled — where the client's return dwarfs any day count.
The risk sits with you, and it is specifically estimation risk. A fee set from an optimistic scope is a discount awarded in advance. The defences are professional habits: define the deliverable and its boundaries in writing (what “done” includes, how many revision rounds, what counts as a change), price contingency for the unknowable parts, and charge changes as changes, visibly and without apology. A project fee with a written scope is a business instrument; without one it is a bet, and the client holds most of the cards because the scope will be interpreted by whoever wants more.
Converting safely: the floor underneath every fee
However a price is presented, it must survive translation into your floor rate. Estimate the days honestly — your calendar history, not your hopes — multiply by the day rate your freelance build produced, and the product is the fee's floor: quote below it and the project subsidises the client by the difference. Then adjust upward for everything the fee model adds: estimation risk (a margin for the unknowns), the value of the outcome where it is large and visible, and the terms — a fee paid in sixty days is worth less than the same fee in fourteen, and staged payments (deposit, milestone, completion) cut both your risk and the fee's necessary padding.
Watch the reverse conversion too, because clients will perform it: dividing your fee by their imagined day count and comparing it to a day rate they have heard. A fee that looks startling as a day-equivalent is defensible precisely when the scope, risk and outcome justify it — which is why the written scope matters commercially as well as operationally. You are not selling days in costume. You are selling a finished thing, a deadline and the transfer of the risk that it takes longer than anyone thinks. Price those, name those, and the day-equivalent conversation becomes a short one.
The hybrid most practices converge on
Look inside established service businesses and a pattern recurs: fixed fees for the work they have done often enough to estimate in their sleep, day rates for the exploratory and support work around it, and a retainer — a monthly fee for availability and a defined basket — for the ongoing relationships. Each model is placed where its risk belongs: the known with the seller who can control it, the unknown shared by the hour, the recurring smoothed into a subscription both sides can budget.
Adopting the pattern is mostly a matter of sorting your own catalogue. Anything you have delivered five times is a fee candidate, with its scope written from the last delivery's reality. Anything genuinely diagnostic stays on time. And everything carries the floor beneath it, quietly, so that the model is a choice about presentation and risk — never an accident that reprices your year while you were looking at the work instead of the numbers.
Key takeaways
- Time pricing is legible and flexible but caps income at your hours, and pays you less as experience makes you faster.
- Project fees sell certainty and keep efficiency gains with you — in exchange for estimation risk, managed by written scope and charged changes.
- Every fee must survive conversion: estimated days × floor day rate is the minimum; add for risk, value and payment terms.
- Staged payments (deposit, milestone, completion) reduce the risk a fee must be padded for.
- The working hybrid: fees for repeatable work, day rates for exploration, retainers for continuity — floor rate beneath all three.
Mistakes to avoid
- Quoting project fees from optimistic day estimates, then funding the overrun personally.
- Leaving scope verbal — a fee without written boundaries is a bet the client's interpretation settles.
- Staying purely on day rates for a decade and wondering why rising expertise never raised the income ceiling.
- Forgetting payment terms inside the fee: sixty-day money is not fourteen-day money and should not be priced as if it were.
Questions readers ask
When is hourly billing genuinely the right model?
For open-ended work neither side can scope — investigations, support, early-stage consulting — and for clients whose procurement requires it. The errors are using it everywhere by default, and failing to review whether repeatable work has quietly become fee-shaped.
How many revision rounds should a fee include?
State a number — two is a common professional standard — and define what a round means (a consolidated set of changes at an agreed checkpoint, not a drip of single edits). Beyond it, revisions are chargeable changes, which disciplines the feedback process for everyone's benefit.
Should I show the client my day-rate maths behind a fee?
Only where it helps. The fee's justification is the scope, the outcome and the risk carried — not your internal floor. Revealing the floor invites negotiation against your costs rather than the work's value, which is a conversation the fee model exists to retire.
Put it into numbers
Before your next quote, convert it both ways: fee into days at your floor rate, days into the fee they imply — and notice which model the work is really asking for.
Open the Freelance Rate Calculator