Retainer vs project pricing: what each one actually sells

Aug 22
4 min read

Updated: Aug 27

Introduction

The advice given to service businesses is usually one-directional: move to retainers, because recurring revenue is more valuable.

That is true for the supplier's valuation and not always true for the client, the margin, or the quality of the work. The two models sell genuinely different things, and choosing by fashion rather than by fit produces resentment on both sides.

1. Retainer vs project pricing is a question about whether the work recurs

The distinction is not commercial preference. It is whether the underlying need is continuous or finite.

Monitoring, maintenance, ongoing advice, regular production and anything requiring availability genuinely recurs. Building something, fixing something, or producing a defined outcome does not.

A retainer over finite work creates an obligation to invent activity in the later months. A project over continuous work means renegotiating constantly. Most difficulties with either model start with this mismatch.

2. A project sells a defined outcome and an ending

Projects suit work with a clear scope: a build, an implementation, a strategy, a system installed and a team trained.

The client knows what they will have and when. You know what you committed to and can price it against measured effort. Both parties can judge success.

The ending is a feature rather than a weakness. Some of the most valuable engagements are explicitly designed to hand over something the client then operates themselves, and pricing that as a project is honest.

3. A retainer sells availability and continuity

What a client actually buys is priority, continuity of knowledge, and not having to negotiate each time.

Which means a retainer needs to specify what they get: how many hours or deliverables, what response time, and what happens beyond the cap.

Retainers described as "ongoing support" fail predictably. The client's expectation expands, the supplier's margin contracts, and neither can point to what was agreed.

4. Understand how each fails

Both models have a characteristic failure worth anticipating.

Projects: scope creep, underestimated effort, and the revenue cliff when the project ends with nothing behind it. Fixed by countable deliverables, change control and a pipeline.

Retainers: the invented-work problem in quiet months, unbounded usage by the heaviest clients, and a client who cannot see what they are paying for and cancels. Fixed by caps, reporting, and honesty about whether the need still recurs.

5. Price a project on measured effort, and a retainer on your heaviest user

Different pricing logic for each.

For a project, take realistic hours including coordination and revisions, apply your required margin per hour, and add a contingency for the parts that always take longer. Fixed prices are safe when hours are measured and dangerous when they are estimated.

For a retainer, cost it against your most demanding plausible client rather than the average. Retainers attract heavy users, because they benefit most.

6. Do not convert a project into instalments and call it a retainer

The practice worth naming, because it is common and it damages relationships.

Dividing a finite piece of work into twelve monthly payments creates an expectation of twelve months of activity. Months seven onward are filled with reports and small tasks, and the client eventually notices they are paying for administration.

If the work has a natural end, sell it with a natural end. Payment can still be staged; the engagement should not pretend to be continuous.

7. Consider the sequence rather than the choice

For many service businesses the answer is both, in order.

A project to build the thing, followed — if there is a genuine recurring need — by a smaller retainer to maintain it. That is defensible on both sides, because the retainer covers real ongoing work rather than filling space.

It also produces better projects, since you will live with the result, and better retainers, since you know the system intimately.

8. Judge each on margin, not on revenue shape

The commercial test that cuts through the debate.

Calculate margin per hour for your projects and for your retainers, including all the unbilled coordination. Many service businesses find their retainers are worse business than their projects and have never checked, because recurring revenue is assumed superior.

Review it quarterly per client. A retainer that has been unprofitable for two consecutive quarters needs a conversation about scope or price, not another quarter of quiet subsidy.

Conclusion

Choose by whether the underlying need recurs: projects sell a defined outcome with an ending, retainers sell availability and continuity within a stated cap.

Price projects from measured effort with contingency and retainers against your heaviest plausible user, never disguise a finite project as monthly instalments, consider a build followed by a genuine maintenance retainer, and compare the two on margin per hour rather than assuming recurring revenue is better.