DEV Community

Karactif Tech
Karactif Tech

Posted on Edited on

Hourly or Fixed Price? Choosing the Billing Model That Fits the Client

Hourly or Fixed Price? Choosing the Billing Model That Fits the Client

Two freelancers quote the same project. One says $95 an hour, the other $9,000 fixed. The client hears "roughly $9,500, but who knows" from the first and "$9,000, fixed" from the second. That difference in perceived certainty is worth money, and it is why fixed price often wins work even when it is the riskier choice for the person quoting it.

The model decides who absorbs the surprise when the work takes longer than expected. The invoice format and the conversation follow from it.

The difference is who carries the estimation risk

Under hourly billing, the client carries scope risk: if the work expands, the bill expands. You carry utilisation risk: quiet weeks are your problem, not theirs.

Under fixed price, you carry scope risk: if it takes three times as long, you absorb it. The client buys certainty, and you are paid for your ability to estimate.

Neither is fairer. They are two ways of pricing uncertainty, and the right one depends on how well either of you can see the work.

When hourly is honest, when fixed price wins

Hourly is the better fit when:

  • The scope is not knowable yet. Discovery, audits, debugging, "we think the API is broken" — you cannot responsibly quote a fixed number for work you have not diagnosed.
  • The client changes direction often. Weekly priority shifts mean fixed price either carries a large contingency or becomes a series of painful renegotiations.
  • It is ongoing support. Small, unpredictable requests suit a rate, a minimum block and a monthly invoice.
  • You have no usable history. The first time you build something, you do not know your real hours.

Fixed price is the better fit when:

  • The deliverable is definable. You can describe "done" in a paragraph and both of you agree.
  • You have done this before, repeatedly. Estimates based on real data, not optimism.
  • The client needs budget certainty. A fixed number is often the only thing that gets approved, especially against a purchase order.
  • You control the variables. Few dependencies, a responsive client, no third-party blockers.

The hybrid most freelancers end up using

Fixed by phase, hourly for changes. Quote a fixed price per phase with clear deliverables, and bill additional requests hourly. It separates "the job" from "the additions", where scope arguments begin.

Retainer with an hour bank. A fixed monthly fee buys a block of hours, with excess billed hourly and a stated rollover rule.

Fixed price with a not-to-exceed cap. Quote a range and bill actual hours up to an approved ceiling. It combines transparency with a hard stop, provided the client understands that reaching it means renegotiating scope.

What hourly billing demands of you

  • Contemporaneous tracking. Hours reconstructed on Friday lose arguments you should win.
  • Task-level descriptions. "Design work, 6 hrs" invites scrutiny; "checkout wireframes, 3 screens, revision round 2 — 4.5 hrs" does not.
  • A stated rounding policy. Six or fifteen-minute increments, and whether you round up, so a twelve-minute call is not a dispute.
  • A minimum block. One hour is common for ad hoc requests; the context switch costs more than the work.
  • A cadence. Weekly or fortnightly, not monthly: a monthly hourly invoice is a surprise, and surprises get disputed.
  • A running total and a warning. "This is heading past the estimate" protects the relationship.

What fixed-price billing demands of you

  • Deliverables, not activities. "A 12-page brand guide in Figma" beats "brand work".
  • Revision rounds, counted. "Two rounds included; further rounds at $X" ends the endless-tweak problem.
  • Assumptions and dependencies. What the client supplies, what you are not doing, and that the price assumes one decision-maker replying within five working days.
  • A buffer. Price in 15% to 25% for what you cannot foresee. That is not padding; it is the premium for absorbing risk.
  • A change process. Written change orders with cost and schedule impact, before the work happens.

The failure mode: fixed price plus vague scope plus a client who "just wants one small thing" equals unpaid overtime.

How the invoice itself changes

The model should be visible in the document: the client reconciles against what they expected.

Hourly invoices need the period covered, a task description per line, hours, rate, amount, and total hours. Group by week or phase so the invoice reads as a record of the work.

Front-end development, week of 3 Nov — checkout refactor, 14.5 hrs @ $95.00 — $1,377.50
Front-end development, week of 10 Nov — payment integration, 11.0 hrs @ $95.00 — $1,045.00
Total hours: 25.5 · Total: $2,422.50

Fixed-price invoices need the deliverable or milestone, the flat amount, and a reference to the phase. Hours are irrelevant and should not appear. If a client asks for a breakdown, give it as a percentage of project rather than as time, because time invites a conversation about whether the work was worth it.

Brand identity package — milestone 2, logo system and guidelines — $3,600.00

Do not mix the two in one block. If an invoice carries both, use separate subtotals, because the approver may code them differently.

Saved line items make either model faster to invoice. Invoice Maker is a free iPhone and Android app from Caractiv Tech with reusable line items, saved clients, PDF sharing, paid, unpaid and partial tracking, 34 currencies, and 40+ Premium templates with branding. Manual invoicing works offline; AI drafting, which turns a typed or dictated description into an editable draft you review and confirm, needs a connection. Free to download, with an optional subscription.

Switching models without renegotiating history

The usual path is hourly first, fixed later: a few projects teach you your real hours, then you can quote fixed prices with confidence. The reverse happens too — a fixed-price client whose scope keeps moving is better served by hourly.

Three rules make the switch clean: apply it to new work or the next phase, never to work already delivered; say why, in plain business terms; and put it in writing before the next invoice, with the new rate or fixed price and the effective date.

A two-minute decision test

  1. Can you describe the deliverable in a paragraph the client would recognise? (Yes → fixed is viable.)
  2. Have you done this exact work at least three times? (No → hourly, or fixed with a large buffer.)
  3. Does the client need a fixed number to get budget approval? (Yes → fixed, even at a premium.)
  4. Will the client change direction mid-project? (Yes → hourly, or fixed by phase with hourly changes.)
  5. Can you absorb a 30% overrun without resenting the client? (No → do not offer fixed price.)

If the answers conflict, the hybrid is usually right: fix the parts you can define, charge hourly for the parts you cannot.

The point

The billing model is a risk-allocation decision, not a personality trait. Choose it per client, write the scope either way, and show the model on the invoice. Most billing disputes are about a client who expected one model and received an invoice built for another.


Get Invoice Maker

Disclosure: I work on Invoice Maker, the app linked above. This article is general business information, not legal, tax or accounting advice. Contract terms, consumer-protection rules and invoicing requirements vary by jurisdiction, so confirm the specifics for where you operate.


Appendix: distribution assets (not part of the article body)

Social summaries

X: Hourly vs fixed isn't about fairness — it's about who carries the estimation risk. Hourly: the client absorbs scope creep, you absorb quiet weeks. Fixed: you absorb the overrun. Pick per client, and make the invoice show which model you're on.

LinkedIn: A fixed quote of $9,000 often beats $95/hour for the same work, because the client is buying certainty, not hours. The model you choose decides who absorbs the surprise when the work takes longer than expected. Notes on when hourly is honest, when fixed price is genuinely better for both sides, the hybrid most freelancers settle into (fixed by phase, hourly for changes), and why an hourly invoice needs task-level lines while a fixed one should never show hours at all.

Reddit (r/freelance — answer-first, no link): Fixed price got much less scary once I only quoted it for work I'd done at least three times, with a 20% buffer and two revision rounds written into the scope. Hourly got less contentious when I started sending fortnightly invoices with a running total — the monthly invoice was always a shock, even when the number was correct.

Image suggestion

Concept: A split-frame graphic: left side an hourly invoice with task, hours and rate lines; right side a fixed-price invoice with a single milestone line; a balance scale in the middle labelled "who carries the overrun".

Alt text: Side-by-side hourly and fixed-price invoice layouts with a balance scale between them.

Notes: 1200×800 header, 1080×1080 LinkedIn crop. Use fictional rates and amounts, and keep the invoice text large enough to read at thumbnail size.

Top comments (0)