The choice between billing hourly and quoting a fixed project price looks like an administrative detail. It isn't. It's a decision about who absorbs the risk when the work runs long — you or the client — and getting it backward is how consultants either leave money on the table or quietly lose it on every overrun.
Hourly and fixed-fee aren't good and bad options. They're two ways of pricing the same work that shift the risk in opposite directions. Once you can see which way the risk flows in each, picking the right one for a given engagement stops being a gut call and becomes a framework. Here's the framework, with the dollar math that makes the trade-off concrete.
Both models rest on the same number
Before comparing them, understand that hourly and fixed-fee aren't really different prices — they're different wrappers around one number: your effective hourly rate. A fixed project fee is just your hourly estimate wearing a different coat. If you don't know your rate cold, you can't price either model, because the fixed fee is built by estimating hours and multiplying by that same rate.
So set the number first. Working backward from your target income, overhead, and realistic billable hours is what the consulting rate calculator does — it gives you the per-hour figure that anchors both a straightforward hourly quote and every fixed-fee estimate you'll ever build on top of it. For the worked comparison below, we'll assume that number is $185 an hour.
The same engagement, priced both ways
Take a concrete engagement: a market-entry assessment you estimate at about 60 hours of work.
Priced hourly, it's simple: 60 hours × $185 = $11,100 — if it takes 60 hours. But hourly means the client pays for every hour the work actually consumes. If the scope wobbles and it runs to 75 hours, the client pays $13,875. You carry no risk; the meter just runs.
Priced as a fixed project, the naive move is to quote that same $11,100. That's a mistake, and here's why: the moment you fix the price, the overrun risk transfers from the client to you. If it runs to 75 hours, you eat the extra $2,775. So a fixed fee should never be priced at your midpoint estimate — it has to be priced against a pessimistic one.
If your honest range for this engagement is 55 to 80 hours, you price the fixed fee against roughly the 70th-percentile outcome — call it 72 hours — to protect your margin: 72 × $185 = $13,320, which you'd present as a clean $13,500. That's about 22% above the naive point estimate, and that gap is the risk premium.
Why the fixed price is higher, not lower
This is the part most consultants get exactly backward. They assume a fixed fee should be a discount — "I'm guaranteeing the price, so I should charge less." The opposite is true. A fixed fee is insurance, and the client is buying it from you.
When you quote $13,500 fixed against a $11,100 midpoint estimate, you're selling the client certainty: they know the number no matter what happens. You're absorbing the variance. Insurance costs more than the expected loss — that's how insurance works — so the fixed price sits above the midpoint, not below it. A consultant who fixed-prices at the midpoint is handing the client free insurance and eating every overrun personally.
The corollary is the good news: when scope is genuinely well-defined and stable, the range narrows, the risk premium shrinks, and the fixed fee approaches the hourly estimate. That's the sweet spot — you fix a price close to your estimate, then any efficiency gain is yours to keep. Finish the well-defined job in 50 hours instead of 60 and your effective rate jumps from $185 to $222, with the client just as happy because they got the outcome at the agreed price.
The decision matrix
Two questions decide it: is the scope well-defined, and does the client want budget certainty? Cross them and the recommendation falls out.
|
Client wants a fixed budget & certainty |
Client is comfortable paying for time |
| Scope is well-defined & stable |
Fixed project. Low risk premium, you keep any efficiency upside. The best-case model. |
Either — lean fixed. Fixed still rewards your speed; hourly is fine if the client insists. |
| Scope is fuzzy or likely to evolve |
Fixed with a real risk premium + a change-order clause — or a capped hourly ("not to exceed $X"). Never fix a fuzzy scope at the midpoint. |
Hourly. The client is generating the uncertainty, so the client should absorb it. |
Layer one more lens on top: client type. Procurement-driven and enterprise clients often require a single fixed number to get a PO approved — meet them there, with the risk premium built in. Founders and early-stage clients often prefer hourly flexibility because their own direction is still moving. And a client who keeps coming back for more isn't really a project client at all — that's a retainer conversation, which is a different structure worth pricing on its own terms.
The middle ground: not-to-exceed
There's a third structure that splits the risk down the middle, and it's underused: the not-to-exceed, or capped hourly. You bill your actual hours, but you guarantee the total won't pass an agreed ceiling. The client gets the budget protection of a fixed fee; you get paid for real hours when the work comes in light.
Run it against the same engagement. You bill hourly at $185 with a cap of $13,500. If the work lands at 62 hours, the client pays actuals — $11,470 — and you've charged fairly for exactly what it took. If it blows out to 80 hours, the client pays the $13,500 cap and you absorb the last 4.6 hours. The client's worst case is capped; your best case is uncapped only downward.
The trade is honest: you give up the full efficiency upside of a fixed fee (you can't pocket the savings when it runs short — the client does), in exchange for lower risk of an ugly overrun conversation. It's the right call when trust is still forming and the client needs a ceiling but you're not yet confident enough in the scope to price a true fixed fee. Think of it as a fixed fee with the efficiency upside handed to the client as a goodwill gesture — often a smart one early in a relationship.
The script to position a project
When you've decided fixed-fee is right, don't present it as "instead of hourly" apologetically — present it as the structure that serves the client. Lead with certainty and outcome, name the number plainly, and pre-empt scope creep with the change-order line.
Subject: Proposal — [engagement], fixed scope
Hi [Name],
I'd suggest we structure this as a fixed-fee project rather than hourly. It means you know the full investment up front — $13,500 — with no surprises if the work runs long, and it keeps us both focused on the outcome rather than the clock.
I've scoped it to [specific deliverables]. Anything that comes up beyond that, we'd handle as a separate change order — so the number you approve is the number you pay.
I can have this underway by [date]. Want me to send the agreement?
Best,
[You]
The change-order sentence is doing quiet, essential work: it fixes the price and protects you from the scope creep that makes fixed-fee dangerous. Certainty for the client, a boundary for you.
When to break your own rule
The default lean for defined work is fixed-fee — it rewards efficiency, reads as more professional, and usually produces a higher effective rate. But there are clear cases to reach for hourly instead:
- Discovery and open-ended advisory. If the whole point is to figure out what the work even is, you can't fix a price for it. Bill hourly, or fix a small price for the discovery phase alone.
- A brand-new relationship with no trust yet. Hourly is lower-commitment for both sides. Neither of you is betting a big fixed number on an untested fit.
- A client who keeps changing direction. If direction churns weekly, fixed-fee means you eat the rework. Hourly makes the cost of their indecision visible — which often fixes the indecision.
And the most useful hybrid: when scope is fuzzy but the client wants a fixed number, sell a paid discovery phase first (hourly or a small fixed fee), use it to define the scope precisely, then fixed-price the delivery against a now-narrow range. You get the clean fixed engagement the client wants without gambling on an undefined one.
Whichever model you pick, run the final number back through the rate calculator against your realistic hours — a fixed fee that pencils out below your effective hourly rate isn't a fixed fee, it's a discount you didn't mean to give. Price the risk on purpose, and let the model do the work.