Use hourly billing when uncertainty is the product
Hourly billing is useful for troubleshooting, consulting, ongoing design support, legacy code, research and work that depends on decisions not yet made. It allows the plan to evolve without forcing either side to pretend the final scope is known.
The tradeoff is budget uncertainty for the client. Reduce that concern with a weekly cap, time reports, clear check-in points and an estimate expressed as a range rather than a promise.
Use a fixed quote when acceptance can be described
Fixed pricing works when the deliverable, deadline, inputs, approval process and definition of done are specific. A landing page with approved copy and two revision rounds is easier to price than an open-ended request to improve a brand.
The fixed price should cover delivery effort plus coordination and uncertainty. It should not be only hours multiplied by a wage. Include meetings, research, testing, handoff and the cost of reserving schedule capacity.
- Define the deliverables and exclusions
- Name the client inputs and their due dates
- Limit revision rounds and define a revision
- State what triggers a change order
- Tie payments to deposit and milestones
Watch for efficiency punishment
Hourly billing can punish expertise when an experienced freelancer solves a problem in four hours that once required twelve. A fixed price lets the client buy the result while the freelancer keeps the benefit of a reliable process.
That does not mean every fast task deserves a large fixed fee. The price still needs a rational connection to the outcome, alternatives, risk and client budget. Explain the deliverable and business impact instead of defending the number with hours alone.
Use a hybrid when neither extreme fits
Many projects are clearer after discovery. Price the discovery phase hourly or as a small fixed workshop, then use its findings to quote implementation. Another option is a fixed base scope with an hourly rate for documented additions.
A hybrid model prevents a vague first conversation from becoming a fixed-price promise while still giving the client a predictable implementation budget.
Make the decision before writing the proposal
Ask what information is missing, who can request changes, how approval works and what failure would cost. If several answers are unknown, the risk belongs in the commercial model rather than in a hopeful estimate.
Whichever model you choose, record assumptions in plain language. Pricing disputes usually begin with different expectations about scope, not with the arithmetic itself.