Pricing models compared

Hourly, project, retainer, and value-based — what each one actually prices, and who bears the risk

4 min read

The variable that actually distinguishes these four models

Every pricing-advice article lists "hourly vs. project vs. retainer vs. value-based" as four options on a menu. The variable that actually separates them is who bears the risk of the work taking longer or delivering less than expected — and that variable is a direct consequence of the credence-goods problem in the mechanism: because the client can't verify quality or effort directly, every pricing model is implicitly a decision about who absorbs that uncertainty.

ModelWhat's actually pricedWho bears execution-time riskStructural incentive it creates
HourlyYour time, directlyThe client — more hours, more cost, regardless of outcomeRewards duration, not resolution — see below
Project / fixed-feeA defined deliverableYou — if it takes longer than scoped, your effective rate dropsRewards accurate scoping and efficient execution, punishes scope creep you didn't price in
RetainerOngoing access/capacity, not a specific outputShared — client pays regardless of workload that month, you're exposed if demand on your time spikes uncompensatedRewards a durable relationship over any single deliverable
Value-basedThe value the engagement creates for the clientYou, doubly — you bear execution risk and you bear the risk that "value" is disputed or hard to measureRewards outcomes, and — done well — aligns your incentive with the client's own

The problem with hourly billing, mechanically, not vibes

Hourly billing looks neutral but isn't. Because the client cannot directly verify how much time a task should take (the same credence-goods verification gap again), hourly billing structurally rewards duration over resolution: every hour billed is revenue, so there is no built-in incentive to finish faster, and a genuinely more efficient consultant literally earns less for delivering the same result in less time. This is not a claim about consultants' character — it's the predictable output of the incentive structure itself, and it's been studied most rigorously in the adjacent profession of law, where the same billing model dominates. William Ross's The Honest Hour — built on judicial opinions, bar-association ethics rulings, and surveys of hundreds of practicing attorneys — documents that this incentive misalignment produces real, widespread (if usually unintentional) inflation of billed time, even among attorneys who consider themselves ethical. [Established] — Ross, The Honest Hour: The Ethics of Time-Based Billing By Attorneys (Carolina Academic Press).

That said, hourly billing is not indefensible, and this course won't pretend the debate is one-sided. Jonathan H. Choi's 2018 law-review analysis argues hourly billing persists specifically because it gives the client a monitoring mechanism the alternatives lack — a client reviewing an itemized hourly invoice can at least see what was worked on, where a flat project fee gives the client no comparable visibility into effort. [Established, as a real academic argument — not proof the monitoring benefit outweighs the incentive cost in any specific engagement] — Choi, "In Defense of the Billable Hour: A Monitoring Theory of Law Firm Fees," South Carolina Law Review 70:297 (2018). The honest synthesis: hourly billing trades a real incentive problem for a real monitoring benefit, and which one dominates depends on how easily the client could otherwise verify your work — which is precisely the credence-goods variable this whole course is built on. The less verifiable your work is by nature (strategy advice, versus something with an observable, countable output), the worse hourly billing's incentive problem gets relative to its monitoring benefit.

Why project and retainer pricing are the practical middle ground

Project pricing forces you to do the scoping work up front — which is itself valuable to the client, since a well-scoped fixed-fee proposal is a costly, hard-to-fake signal of competence in exactly the sense the mechanism describes. Its failure mode is scope creep: work the client keeps adding without acknowledging it's now outside what was priced, which silently converts your fixed-fee margin into de facto unpaid hourly work. The standard defense — a written scope document with an explicit change-order process — isn't a formality; it's the mechanism that keeps project pricing from quietly reverting to the worst version of hourly billing (all the client's requests, none of the negotiated rate).

Retainers solve a different problem: they convert an intermittent need (recall condition 1 from the mechanism) into a predictable relationship for both sides, which is why they dominate the fractional-executive and ongoing-advisory shapes described in What independent consulting actually is. Their risk, structurally, is the opposite of hourly billing's: a retainer client who under-uses you is still paying, which is good for you and can quietly resentment-build for them if the relationship isn't managed — the practical fix most experienced independent consultants use is a defined scope-of-access (response time, meeting cadence, deliverable count) rather than an unlimited-hours promise, which is really a hidden hourly model wearing a retainer's clothing.

Value-based pricing is covered on its own in Why value-based pricing commands a premium — it deserves separate treatment because the mechanism behind why it commands a premium, and why most consultants underuse it, is specific enough to need its own argument rather than a row in this table.

Consultancy · progress saved in this browser · sign in to sync across devices

Up next

Why value-based pricing commands a premium

The actual mechanism, why most consultants underprice, and a stat this research checked and threw out

4 min