Almost every argument about pricing structure is really an argument about one thing: who pays when the work takes longer than anyone thought. Fixed price puts that on the freelancer. Hourly puts it on you. Everything else follows from that single fact.
What fixed price actually buys you
Certainty about the number, and nothing else. You know the cost before you commit, which matters when the money is approved by someone who will not approve it twice.
The cost of that certainty is a risk premium built into the quote, and a structural tension around scope. Once the price is fixed, every change becomes a negotiation, because the freelancer is no longer paid for additional work. This is not bad faith; it is arithmetic. Projects where the requirements keep evolving are the worst possible fit for fixed pricing, and they are also the projects where clients most want it.
- Well suited to: a defined website, a logo, a set of articles, a migration with a known inventory
- Poorly suited to: "improve our product", ongoing development, anything exploratory
- Requires: a specification detailed enough that both parties agree what is included
What hourly actually buys you
Flexibility, and the ability to change direction without renegotiating. If you genuinely do not know where the work will end up — because you are learning as you go, or because the first discovery will change the plan — hourly is the honest structure.
The cost is that you carry the overrun risk, and you need some way to know that the hours are real. On a marketplace with time tracking that is largely solved. Off one, it depends on trust and on you seeing progress frequently enough to notice if it stalls.
- Well suited to: debugging, maintenance, retainers, discovery, evolving products
- Poorly suited to: one-off deliverables with a clear finish line
- Requires: a cap, an agreed check-in cadence, and visible progress between them
Worth noting: Always set a cap on hourly work — a number that cannot be exceeded without your explicit approval. It converts most of the risk back to something you control, at no cost to either side.
The structure most projects should actually use
Milestone-based fixed pricing solves more real problems than either pure form. The project is split into stages, each with its own deliverable, price, and acceptance criteria. You pay on completion of each.
- Discovery or design, paid separately and delivered as a document or prototype
- A first working slice, small enough to see real output early
- The bulk of the build, split into two or three stages
- Launch, handover, and an agreed support window
The benefit is that each milestone is a decision point. If the first stage goes badly you have lost one stage, not a project. If it goes well you have evidence rather than optimism before committing the rest. This is also how the discovery-first pattern works: pay for a small paid analysis, use its output as the specification for a fixed quote on the real work, and both sides now price against something real.
Retainers
For ongoing work — maintenance, monthly content, continuous development — a retainer buys availability rather than a deliverable. It is the right structure when your need is recurring and unpredictable in shape but predictable in volume.
Two things make retainers work: a written statement of what is included and what is not, and a policy on unused hours. Unlimited rollover turns a retainer into a debt the freelancer owes you; no rollover at all encourages busywork in slow months. A one-month carry-over is the common compromise.
Deposits and payment timing
A deposit before work starts is standard and reasonable — typically 25–50%. A freelancer who asks for the full amount up front on a first engagement is asking you to carry all the risk; a client who insists on paying everything only at the end is asking the freelancer to. Neither is normal practice, and both are worth pushing back on.
The mechanism that protects both sides is escrow: the money is committed and held, so the freelancer knows it exists and you know it is not released until the milestone is accepted. Where a platform offers it, use it.
A decision rule
- Can you write down exactly what "finished" means? Fixed price, in milestones.
- Will the requirements change as you learn? Hourly, with a cap.
- Is the work continuous and recurring? Retainer, with an inclusions list.
- Do you not yet know which of these applies? Buy a small paid discovery first and decide afterwards.