Fixed Price, Value, or Retainer
Hourly stopped measuring what it used to. The alternatives are usually presented as a maturity ladder, with hourly at the bottom and value-based at the top.
That framing is wrong. They are different instruments that price different things and allocate risk differently, and the right one depends on what you can actually estimate. For the operational side of recording work and turning it into client-facing evidence, see productivity versus efficiency.
What each one actually prices
Hourly prices your time. The client carries the risk that it takes longer than expected.
Fixed price prices an outcome. You carry that risk.
Day rate prices your attention in coarse units. Risk is shared, roughly — small overruns are yours, large ones become a conversation.
Retainer prices availability. Both sides trade variance for predictability. Xero provides a broader accounting and billing reference for independent work See Xero.
Value-based prices the client's benefit. In principle you carry delivery risk and share in the upside; in practice it usually means a higher fixed price with a better story.
The question is never which is most sophisticated. It is which risk you are able to carry, and whether you can estimate well enough to carry it.
Fixed price
Works when the scope is genuinely definable, you have data on similar work, and the client will not change direction constantly.
Fails when you cannot estimate. If your ranges are still wide because you have not recorded enough actuals, fixed price converts an estimating problem into a financial one.
What changed: it got both more attractive and more dangerous. More attractive because you keep the upside when generation goes well — which is now sometimes substantial. More dangerous because verification-heavy work has wider variance than it used to, and a badly-classified project can consume the margin from three good ones.
The discipline: price from your own recorded ratios, never from how the last similar job felt. And put a change-control clause in writing, because scope changes are now cheap to propose and not cheap to absorb.
Day rate
The most underrated option for small studios, and the easiest transition from hourly.
Works when the client wants flexibility but you want protection from your own efficiency. Coarser units mean a two-hour saving does not reduce your income, while the arrangement stays simple enough that nobody needs a contract negotiation.
Fails when the work is genuinely intermittent — an hour here and there — where charging full days is either unfair or unsellable.
The advantage that matters: it prices attention rather than typing, which is much closer to what a client is actually buying now. The judgement about which approach to take does not get faster with better tools, and a day rate charges for it honestly.
Retainer
Works when the relationship is ongoing, the client values availability, and neither side wants to negotiate each piece of work.
Fails when the scope is undefined and the client's expectations grow to fill the amount. The failure is slow and it ends badly, so a retainer needs a stated scope of what it covers.
The specific advantage now: it removes the productivity conversation entirely. Nobody on a retainer asks whether AI made this month cheaper, because they are not buying units of anything. That question is otherwise inevitable.
For a small studio with two or three steady clients, retainers plus fixed-price projects for everyone else is a stable arrangement.
Value-based
Fashionable, and worth being blunt about.
Works when the client can quantify the benefit, will agree the number beforehand, and the connection between your work and that benefit is direct. Which describes very few small-business projects.
Fails when the value is real but unattributable. If a site brings in enquiries, was that the design, the copy, the client's own reputation, or the season?
The honest version for most studios is not value-based pricing. It is fixed price informed by value — you charge more for work that matters more to the client, without pretending to a formula. That is defensible and does not require a negotiation about their business model.
How to choose, in practice
Can you estimate this within about 30%? If no, hourly or day rate. Do not carry risk you cannot size. (Terms about generated code belong in the same conversation.)
Is the scope definable? If yes, fixed price is available.
Is it ongoing? Retainer.
Is it genuinely open-ended? Hourly, and say so plainly.
Do you have recorded data on similar work? If no, this project is where you start collecting it — and the fifteen-second version is enough.
The mistake to avoid
Switching model and raising price at the same time. Two arguments where there could be one, and the client will attribute the whole change to the price.
Move to the new structure at a comparable number first. Adjust the number later, once the structure is normal.
The short version
- These are different instruments, not a maturity ladder — each prices a different thing and allocates risk differently
- The real question is which risk you can carry, which depends on whether you can estimate
- Fixed price got more attractive and more dangerous: bigger upside, wider variance on verification-heavy work
- Day rate is the underrated middle — it prices attention rather than typing
- Retainer removes the productivity conversation entirely, which is worth more than it sounds
- Do not change structure and price in the same conversation