Retainer Vs Project Pricing: The Honest Trade-off

Project pricing pays for output. Retainers pay for outcomes. Which one you should use depends on whether the work has an end, and most agencies get this wrong in the same direction.

Where project pricing is right

The work has a defined scope and a finish. A website, a brand identity, a photography shoot, a document.

You can specify what is being delivered, both sides know when it is done, and the client can evaluate it against what was agreed.

For this kind of work, project pricing is honest and a retainer is not. Charging monthly for a thing that finishes creates an incentive to stretch it.

Where retainers are right

The work has no natural end and the value comes from continuity. Content, advertising, search, anything that compounds.

These are not projects that happen to repeat. The output in month six is only possible because of what was learned in months one to five, and pricing it as a series of discrete projects destroys the mechanic that makes it work.

Our own model is a retainer for exactly that reason. The guarantee we run, a million views in six months or you do not pay until we do, only makes sense over a period long enough for the engine to compound.

The failure in project pricing

Scope creep, and the relationship damage that comes with it.

Every project generates requests that were not in the original scope. Most are small individually and enormous in aggregate, and the agency either absorbs them and loses money or raises them and looks difficult.

The fix is not better estimating. It is writing down what is included, what is not, and what happens when something is not, before the work starts. Then raising it the first time it happens rather than the fifth.

A change is not a confrontation if you agreed the process for it in advance.

The failure in retainers

Drift. The scope was clear in month one, and by month eight nobody can say precisely what the retainer covers.

The client feels they are paying for less than they were. The agency feels they are doing more than they agreed. Both are usually right, because the work expanded without the agreement changing.

The fix is a defined output, reviewed quarterly. Not a list of hours. A list of what gets produced and what gets reported, revisited often enough that it never drifts far.

Hourly is worse than both

Hourly billing punishes the agency for getting faster and gives the client a number that has nothing to do with value.

It also produces the worst conversation in the business, which is a client evaluating a timesheet rather than an outcome.

The only place it belongs is genuinely unpredictable work where neither side can scope it, and even then it should have a cap.

The hybrid that usually fits

An upfront project component for the build, then a retainer for the ongoing work.

The build is scoped and priced as a project because it finishes. The engine that runs afterwards is a retainer because it does not. Each is priced for what it actually is.

This is the structure most service relationships eventually arrive at, and starting there saves a year of renegotiation.

The rule

If you can write down what "done" looks like, it is a project.

If the value depends on it continuing, it is a retainer.

If you cannot tell, the scope is not clear enough to price either way, and that is the thing to fix first.