Hourly, Fixed, or Retainer: Choosing by the Shape of the Work
Most freelancers pick a pricing model the way they picked their first rate: whatever the last client asked for. Then they repeat it, because it worked once. The result is hourly pricing on work that has no clear hours, and fixed fees on work with no clear edges — and both produce the same complaint at the end of the month, which is that the money does not match the effort.
The model should follow the shape of the work, not the habit of the person selling it. There are four questions that identify the shape, and each answer narrows the choice.
The four questions
1. Can you see the end of the work? If you can describe the deliverable and when it is finished, fixed fee is available. If the work is more like a standing responsibility, it is not.
2. Does the client control how long it takes? Review cycles, approvals, access delays, people who answer in three weeks. If your income depends on their calendar, hourly pricing moves that risk to them — which is the honest place for it.
3. Do you want to keep the efficiency gains? On a fixed fee, working faster earns you more. On an hourly rate, working faster earns you less. Same work, opposite incentive.
4. Does the work repeat on a rhythm? Every month, every quarter, the same shape. If yes, a retainer is a pricing model and a scheduling model at once.
The three models, and what each one is really selling
Hourly sells time. It is the easiest to explain and the hardest to profit from, because every improvement you make reduces your own invoice. Its real virtue is that it removes disputes: nobody argues about hours that are logged and visible. Use it when scope is genuinely unknowable, when the client controls pace, or when the relationship is new enough that neither side wants to commit to a number.
Fixed fee sells an outcome. It is the best model for profit and the worst model for surprises: a fixed fee plus a creeping scope is how people end up working for half their rate. It only works with a written definition of done, a change process, and a buffer in the number. Use it when the deliverable is describable and the client can decide without endless rounds.
Retainer sells availability. It is the most stable and the most dangerous, because a retainer bought by a client who then does not use it becomes a monthly argument about value. It works when the work is genuinely ongoing, when the hours are bounded, and when both sides accept that unused capacity expires rather than accumulating. Use it when the rhythm question is yes and the relationship is already established.
Matching model to shape
| Shape of the work | Model | What to write down |
|---|---|---|
| Deliverable is clear, client decides fast | Fixed fee | Definition of done, revision limit, change rate |
| Scope unclear or client-driven pace | Hourly | Rounding rule, minimum block, review cadence |
| Recurring, bounded, relationship established | Retainer | Monthly cap, rollover rule, notice period |
| One-off, high uncertainty, new client | Hourly, capped | Estimate plus a ceiling you will not exceed without a new conversation |
The last row is the one worth remembering. An hourly quote with a ceiling — "estimated 30 hours, we will not exceed 40 without coming back to you" — prices uncertainty honestly and still gives the client a number they can budget.
The hybrid that actually works
Most experienced freelancers end up mixing models inside one engagement rather than choosing one for the whole relationship:
- Fixed fee for the defined part. The audit, the document, the build — described, priced, delivered.
- Hourly for the open part. The follow-up questions, the extra analysis, the meetings nobody scoped.
- Retainer for the standing part. The monthly reporting, the availability, the on-call.
Written as one proposal, this reads as clarity rather than complexity: here is what is fixed, here is what is metered, here is what recurs. Clients understand all three immediately, because that is how they buy almost everything else.
The warning signs you chose wrong
- Working evenings to finish a fixed-fee project. The fee was too low or the definition of done was too vague; either way, the model is now punishing you for someone else's ambiguity.
- A retainer that gets renegotiated every month. The cap is wrong, or the work is not actually recurring.
- Hourly work where you are the bottleneck and the client waits. You are selling time to someone who needs throughput — a fixed fee or a retainer fits better.
- Any model where you cannot state the number before the work starts. That is not a pricing model; it is a hope with an invoice attached.
Where the decision lives
Whatever you choose, the model should be visible in the same place as the hours: one line per engagement saying which model applies, what the cap or ceiling is, and what triggers a renegotiation. When the model and the hours live in different documents, you get the argument you were trying to avoid — at the end, when nobody remembers what was agreed.
Changing models mid-relationship is possible, but it needs the same treatment as a rate change: notice, a date, and one sentence of reason. Switching a client from hourly to retainer because you are tired of tracking is not a pricing decision; it is a wish.
Related notes
- The Three Numbers Behind Every Hourly Rate — the floor and ceiling any model has to clear.
- Define Done Before You Start, or Argue About It Later — the precondition for fixed-fee work.
- Scope Doesn't Creep. It Gets Invited. — what breaks a fixed fee first.