P4 · Finding and closing clients
Hourly, Project, or Retainer: Choosing a Pricing Model
Choose hourly, project, retainer, or hybrid pricing by scope uncertainty, client budget needs, revision risk, service cadence, and the margin you actually realize after delivery.
Hourly pricing places volume risk mostly on the client and estimation risk mostly on neither side, but it can punish efficiency and makes the client sensitive to every recorded hour. Project pricing transfers more estimation and scope risk to the solo operator. It works best when deliverables, revision limits, dependencies, and acceptance criteria are concrete enough to price uncertainty.
Scope volatility is what usually decides the pricing model
Scope volatility is the deciding variable for many services. Exploratory strategy, incident response, and open-ended stakeholder work are harder to fix-price than a defined audit or a repeatable monthly deliverable.
Price a 35–50 hour project three different ways
Model comparison: a branding project is expected to require 35 to 50 hours. At an internal $140 target rate, the labor value spans $4,900 to $7,000 before risk. A $6,800 fixed price with two revision rounds may be defensible; 'unlimited revisions for $5,000' is a different risk profile entirely.
Keep an internal cost model even when the client never sees hours
Use an internal cost model even when the client never sees hours. A fixed $6,000 project that quietly consumes 80 hours plus five sales calls may be worse than an apparently lower $120 hourly engagement.
A retainer needs a service promise, not a monthly mystery
A retainer can stabilize cash flow, but 'retainer' should describe a specific access or service promise. Decide whether unused capacity expires, rolls over, or purchases priority rather than promising unlimited work.
Put response, meeting, scope, and exit boundaries around retainers
Retainers need boundaries around response times, included meetings, out-of-scope requests, and termination notice. Without those limits, recurring revenue can become recurring overwork.
Match the commercial model to the uncertainty
Hourly pricing is easiest when the scope is uncertain and the client is comfortable paying for effort, but it exposes the buyer to budget variability and can make efficiency feel like a penalty to the seller. Project pricing does the opposite: the client gets price certainty while the freelancer accepts estimation and scope risk. A retainer should not be a vague monthly fee for 'availability.' Define what the client is reserving—hours, response time, recurring deliverables, a number of requests, strategic access, or priority scheduling—and what happens to unused capacity.
Hybrid structures often fit real work better than ideological pricing rules. A consultant can price discovery at a fixed fee, the defined implementation as a project, and unknown change requests at an hourly or day rate. Retainers can include a defined monthly package plus a separate change-order rate. Whatever model you choose, maintain an internal time and cost record so realized margin is visible. If a $7,000 fixed project consumes 70 hours when the plan assumed 40, the lesson is not automatically 'hourly is better'; it may be that the scope, assumptions, revision boundary, or client responsibilities were written too loosely.
Choose the pricing model based on where uncertainty lives. Hourly pricing can be sensible when the client is still discovering the problem, scope changes frequently, or the freelancer cannot estimate effort responsibly. A project fee fits better when the deliverable and acceptance criteria are observable and historical effort is predictable. A retainer should buy a clearly defined ongoing promise—such as a capacity reservation, set deliverable cadence, support window, or recurring service—not simply ‘access to me.’ Write down what happens to unused capacity, emergency work, out-of-scope requests, pauses, holidays, and termination. A retainer that promises unlimited work for a flat fee is often an uncapped project in disguise.
Use the same internal economics behind all three. Estimate hours for delivery, project management, revisions, meetings, and admin; multiply by the internal floor rate; add external costs and risk; then compare that cost model with the proposed client price. For a $4,800 project expected to take 32 total hours, the initial realized rate is $150/hour. If revisions expand the work to 48 hours, it falls to $100/hour. That signal can mean the scope was weak, the process needs improvement, or the next price should rise. For retainers, track used capacity and response burden each month. For hourly work, track whether the billing unit penalizes efficiency or creates budget anxiety. Pricing model and price level are separate decisions: a badly scoped $10,000 project can be worse than a well-managed $150/hour engagement.
For hybrid work, split the uncertain and predictable pieces. A discovery or audit phase can be hourly or a small fixed fee, followed by a scoped project once the unknowns are reduced. Ongoing support can then become a retainer with a stated response window or capacity cap. That sequence can be safer than forcing a single price model onto the entire relationship. When converting an existing hourly client to project pricing, use past time records to identify the average, the bad-case tail, and which requests caused overruns. Quote from the whole distribution, not the fastest month. If a retainer repeatedly consumes more capacity than planned, either narrow the included promise, raise the fee at renewal, or return volatile work to hourly/change-order pricing.
Pricing-model risk matrix
| Hourly | Best when scope or investigation time is genuinely uncertain and the client can tolerate a variable total. Define what time is billable, how often it is reported, any estimate range, and what happens before the estimate is exceeded. |
|---|---|
| Fixed project | Best when deliverables, acceptance, dependencies, and revision limits are observable. The freelancer absorbs estimation risk, so price from expected effort plus uncertainty rather than multiplying a best-case hour count. |
| Retainer | Best for recurring access or recurring outputs. State the included capacity or deliverables, response expectations, minimum term, renewal/cancellation rule, and whether unused capacity expires, rolls, or has no hour-based meaning. |
| Hybrid/change order | Use a fixed discovery phase, fixed core scope, and hourly/day-rate or separately quoted changes when different parts of the work carry different uncertainty. Review realized margin after delivery so the next model is based on evidence. |
Pick a pricing model before you quote
- Define deliverables before choosing a pricing model.
- Set revision and meeting limits on fixed work.
- Write rollover rules for retainers.
- Use change orders for new scope.
- Compare estimated and realized margin after delivery.
Pricing-model references worth comparing
Pricing-model questions clients rarely ask for you
When is hourly pricing the safer choice?
Hourly pricing can be useful when scope is uncertain, work is exploratory, or the client is likely to change direction frequently. It makes time visible but can create budget anxiety, so pair it with estimates, caps, or approval thresholds where appropriate.
What makes a fixed project price dangerous?
A fixed price becomes risky when deliverables, revision limits, client dependencies, and acceptance are vague. The price can be perfectly reasonable at the quoted scope and still become unprofitable after unpriced meetings, iterations, or added deliverables. Track actual project time to see the realized margin.
What should a retainer promise?
A retainer should define what access or output the monthly fee buys—capacity, specific deliverables, response time, strategic access, or another measurable service promise. Also state rollover, overage, pause, and termination rules so unused capacity does not become an unlimited future obligation.
Can I mix pricing models in one engagement?
Yes. A hybrid can keep a defined core project fixed while uncertain extras bill hourly, or combine a monthly base retainer with project fees for larger work. Use the contract to show which work falls into which bucket and how approval happens before extra charges accrue.