Hourly, fixed or value: what each one actually trades
The pricing model determines who carries the risk of the work taking longer, and everything else follows from that.
Discussions about pricing models tend to become ideological — hourly billing punishes efficiency, value pricing is what serious firms do. Underneath the arguments there is a single mechanical question: who pays if the work takes longer than expected.
The three positions
- Hourly or time and materials: the client carries the overrun risk. Simple, transparent, and it caps your upside — being fast reduces your revenue.
- Fixed price: you carry the risk. Higher margin when the work goes well, and a loss-making project when it does not.
- Value-based: price set against the outcome to the client rather than the effort. Highest upside, requires being able to name and defend the value, and only workable where the outcome is attributable.
High uncertainty and hourly. Low uncertainty and fixed. Value pricing only where the outcome is measurable and clearly yours. For a simple reference on annual full-time work hours, this overview can help when sense-checking capacity assumptions.
Hourly's real problem is not the incentive
The usual objection is that hourly billing rewards slowness. In practice, few suppliers deliberately pad, and clients who suspect it leave.
The real problem is different: hourly makes every invoice a discussion about how long something took, which is a conversation about your competence rather than about the outcome. Weekly or milestone-based invoicing with a stated estimate is the same commercial model with far less friction.
Fixed price needs an airtight scope
A fixed price without a written, specific scope is an unlimited commitment. This is the single most common way small studios lose money, and it is entirely preventable. For a broader framework, PMI's overview of project management summarises the standard concepts behind planning and delivery.
If you quote fixed, the scope document has to say what is excluded, how many rounds are included, what the client is responsible for supplying and by when, and what happens when any of that changes. Without those four, the fixed price is fixed only for the client.
Value pricing has a narrow application
It works where the outcome is measurable, attributable to your work, and large relative to the fee — a conversion improvement, a process that saves quantifiable hours, a launch with a revenue number attached.
It does not work for most production work, where the deliverable is an input to something else and the value is genuinely unknowable. Attempting it there produces a negotiation about a number neither party can justify, which usually settles at whatever a day rate would have been.
Retainers are a different thing again
A retainer buys availability and predictability for both sides. Its characteristic failure is that the scope is vague, so the client's expectation expands to fill it while the fee stays fixed.
Retainers need the same discipline as fixed price: a stated hours allocation or a defined list of what is included, a rule about what happens to unused hours, and a review point. A retainer with none of these becomes an unlimited support contract within about six months.
Whichever you choose, track the hours
Time recording is often thought of as a billing mechanism, which makes it look unnecessary under fixed or value pricing. That is backwards: under those models you are carrying the risk, so knowing the real cost matters more, not less.
A fixed-price studio that does not record hours has no idea which of its projects are profitable, and will keep selling the loss-making ones because they are easy to win.