Price is how you assign risk

Hourly billing says risk shared minute by minute: scope can move and the meter reflects it. Fixed price says risk shifts to the seller unless change orders exist: scope must be stable or the seller eats overruns.

Neither is morally better. They fit different projects and different client relationships.

Choose hourly when

Scope is exploratory. Research spikes, audits, "figure out why performance collapsed" work.

The client changes mind often. Product discovery with a founder who pivots weekly.

You are new to the domain. Unknown unknowns dominate; pretending otherwise is a fixed-price trap.

Trust is still forming. Hourly plus frequent demos lets both sides adjust without renegotiating the whole deal.

Hourly pairs well with transparent time notes and outcome summaries so the client sees value, not just hours (billable versus working hours).

Choose fixed price when

Deliverables are crisp. "Migrate these twelve pages to the new CMS with approved designs."

Inputs are client-controlled and dated. Content, assets, and approvals arrive on schedule or the timeline slips by contract.

You have done this before. Similar projects give you a distribution of hours, not a fantasy single number.

The client wants budget certainty. Finance teams often prefer a cap even if the cap is higher than optimistic hourly.

Fixed price demands buffer in money and explicit change-order rules (how much buffer).

Hybrid models that work

Fixed discovery, hourly build. Paid workshop produces a spec both sides sign; implementation hourly or fixed per milestone.

Hourly with a cap. "Up to forty hours at X; stop and re-estimate if we hit eighty percent of cap."

Fixed per milestone, hourly for support. Launch package fixed; post-launch retainer hourly with a monthly bucket.

Hybrids fail when the boundary between phases is vague. Write the deliverable that ends phase one.

Pricing follows how stable the scope is

Red flags for fixed price

  • "We will know it when we see it" design
  • Third-party APIs nobody has integrated
  • Stakeholders who have not agreed on one owner
  • "Quick project" with no written acceptance criteria

Any of those without a paid discovery phase should stay hourly or very small fixed slices.

Red flags for hourly-only

  • Client asks for detailed estimates every week but refuses to pay planning time
  • Scope never shrinks but budget must
  • You absorb meeting sprawl without billing because it feels petty

Hourly is not permission to skip estimates. It is permission to re-estimate when reality diverges.

Outcomes still beat arguing about hours

Clients buy results. Hours are one way to price them. When you can name an outcome clearly, price the outcome and keep hours internal in your rate model (calculate a freelance hourly rate).

The freelance hourly rate guide helps you back into a rate whether the client sees hours or not.

Conversation script

Ask four questions before proposing a model:

  1. What does done look like in one paragraph?
  2. What inputs do you owe me, and by when?
  3. Who can approve scope changes in one reply?
  4. Is exploration part of success or failure?

Exploration-heavy answers point hourly or fixed discovery. Crisp answers with stable inputs point fixed milestones.

Switch models without shame

Projects that grow past the original shape need a new agreement, not silent resentment. "This outgrew fixed scope; here is a change order or we move to hourly for phase two" is normal business.

Pick the model that matches scope stability and write the assumptions down. Price follows risk; risk follows clarity.

Document the handoff between models

Projects often start hourly for discovery and shift fixed for delivery. Write the trigger: "Fixed quote follows signed spec v1."

Without a trigger, clients hear fixed numbers early and you hear hourly flexibility late. Misaligned expectations are where disputes start.

Trust and record-keeping

Hourly needs honest time records you would show if questioned. Fixed needs honest scope records you would show if questioned.

Both need the same integrity; only the unit of account changes. Pick the model that matches how messy the work will be, then keep records that match the model.