If you are quoting a project and torn between hourly and fixed price, skip the philosophy debate: the right model is a function of two things, how precisely the scope can be defined, and how long the engagement will run. Fixed price for short, well-defined work, priced with a serious buffer; hourly or retainer for long, evolving work; hybrids for everything between. The wrong choice isn't immoral, it is just consistently unprofitable in a predictable direction.
What practitioners actually do
Developer Jovan Cicmil polled his audience, 144 freelancers, and got a 60/40 split: 87 preferred fixed price, 57 hourly. A small, informal sample, but his accompanying analysis matches what freelance communities repeat from experience: fixed works for small, well-defined projects and builds client trust early; hourly is "financially more safe" on engagements past roughly six months, where estimation honestly isn't possible. He names fixed pricing's failure modes precisely, difficult estimation, imperfect project definition, changing requirements, and offers the mitigation we'd underline twice: price fixed work at at least double your calculated hours.
The doubling isn't greed; it is pricing the risk you just accepted. Under fixed price, estimation error, scope drift and revision rounds are all your costs. A quote at bare calculated hours is an insurance policy sold at zero premium, which is how freelancers end up earning below minimum wage on projects they "won."
The decision matrix
| Scope definable in writing | Scope genuinely fuzzy | |
|---|---|---|
| Short (< ~6 weeks) | Fixed price, at 2x calculated hours, with a written scope and a revision limit | Paid discovery first (small fixed fee) to define it, then quote |
| Long / ongoing | Milestones: a chain of fixed-price slices, each invoiced on delivery | Hourly with a weekly cap, or a monthly retainer |
Three structural notes that resolve most real cases:
- Paid discovery is the escape hatch. When a client can't articulate the scope, the first deliverable is the scope, a short fixed-fee engagement producing the document you can then quote from. Clients who refuse to pay for definition are previewing how they'll treat everything else.
- Caps make hourly sellable. The client fear about hourly is the open meter; "hourly, capped at N hours a week, you can stop any week" removes it while keeping your downside protection. Uncapped hourly's real risk is the trust erosion of a surprise invoice.
- Retainers are the senior model. A flat monthly fee for defined availability converts unpredictable project income into the closest thing freelancing has to MRR, usually after a fixed or hourly engagement has proven the fit.
Whatever the model, anchor on the outcome
Hourly-vs-fixed decides how risk is split; it doesn't decide what the work is worth. A quote justified only by hours invites hourly-rate arithmetic in the client's head; the same number presented against the outcome ("the checkout flow that stops losing you weekend sales") is judged against value. This is the same repricing logic as our article on underpricing, applied per-project. And the billing model is only half the money conversation, the other half is terms: deposits, milestones and short nets, covered in Getting Paid on Time, apply to either model, and matter more.
Limitations
The poll cited is small and informal (opened July 23, 2026), treat it as practitioner signal, not statistics. Agency subcontracting, government work, and platforms with enforced billing models constrain your choice; and cross-border invoicing layers its own costs on top, which we covered in the international payments comparison.
The bottom line
Definable and short: fixed, at twice calculated hours. Fuzzy: sell paid discovery before anything. Long: milestones, capped hourly, or a retainer. Model choice manages risk; only pricing against outcomes manages worth, do both deliberately and the billing-model argument disappears.
Discussion
Sign in with Google or just a name. No email link, no password to remember.