Marketing Retainer Versus Project Work

Updated September 2026 · Written and maintained by the Progression Agency strategy team

A project buys a defined outcome with a finish line; a retainer buys capacity and continuity. Most engagements that go wrong structurally did so by buying one for work that needed the other. This page covers which work fits which model, the incentive each creates, what a retainer must specify to be worth buying, what a project must specify to avoid the usual arguments, why hybrids are common, and the four questions that settle it.

The models buy different things, not the same thing differently

A project buys a defined outcome with a finish line. A retainer buys capacity and continuity. Confusing the two is why engagements go wrong in ways that look like a performance problem but are actually a structural one.

The clearest test is whether the work has an end. A website, a rebrand, a campaign for a launch: these finish. Search visibility, paid media management, content and community: these do not, and buying them as a project produces something that decays the moment it is delivered.

The corollary matters too. Buying ongoing capacity for work that has a finish line means paying for months in which there is nothing meaningful to do, which is the most common way retainers quietly stop earning their fee.

Each model pulls the agency in a predictable direction

Neither structure is neutral, and knowing which distortion you have bought is more useful than trying to find one without any.

A retainer rewards retention. That is good where continuity genuinely produces better work and poor where it encourages an agency to keep an engagement alive past its usefulness. Deliverable counts written into a retainer amplify this: twelve posts is a countable obligation, whereas deciding that six better ones would work harder is not.

A project rewards completion. That is good where the finish line is real and poor where it encourages delivering to specification rather than to outcome, and moving on before anyone knows whether it worked. Projects also create an incentive to scope tightly and charge for variations, which is legitimate but produces friction.

Retainers drift toward activity

Without periodic renegotiation, a retainer becomes a list of recurring tasks that nobody has questioned for a year.

Projects drift toward handover

The agency’s interest ends at acceptance, which is precisely when the client’s begins. A short post-launch period addresses this cheaply.

Deliverable counts are a blunt instrument

They give both sides certainty and reward volume over judgment. Build a review point where the count itself can change.

Variations are not bad faith

A project priced against a scope will charge for work outside it. The fix is a scope that anticipates the obvious variations, not resentment when they are billed.

What a retainer should specify to be worth buying

The weakness of retainers is vagueness. A retainer that names a fee and a broad remit gives neither side anything to point at when expectations diverge.

A usable retainer states what is included and excluded, roughly how much senior time is involved and from whom, the reporting cadence and what reports will contain, response expectations in both directions, and how unused capacity is treated. It should also state what happens when priorities change mid-month, which is the normal case rather than the exception.

The most valuable clause is the least common: a scheduled review at which the scope itself can change. Without it, a retainer set in month one is still being delivered in month twenty against a situation that no longer exists.

What a project should specify to avoid the usual arguments

Project disputes concentrate on three things, and all three are addressable in the scope document.

Revisions: how many rounds are included, what constitutes a round, and what happens beyond it. Inputs: who supplies content, imagery, access and approvals, and what happens to the timeline when they are late — client delay is the most common cause of project overrun and the least often addressed. Acceptance: what condition constitutes completion, because without it a project can remain open indefinitely.

Adding a short post-delivery period is the single most useful improvement to a typical project. Two to four weeks in which small fixes are included costs little and prevents the pattern where everything works at handover and nobody is responsible a fortnight later.

The hybrid is common and usually sensible

Most mature arrangements are neither purely one nor the other, and describing the hybrid explicitly avoids the failure modes of both.

The usual shape is a smaller retainer covering genuinely continuous work — managing paid accounts, maintaining and improving content, reporting — with discrete projects sitting alongside it for things that finish, such as a site build, a campaign or a production.

This structure has a practical advantage beyond incentives: it makes the value of each visible. A single large retainer absorbing everything makes it impossible to tell what the ongoing work is worth, because it is bundled with things that were one-offs.

Separate the recurring from the one-off

Bundling a build into a retainer hides what the ongoing work costs, and makes it impossible to judge whether it is worth continuing.

Price the ongoing part on its own

If you cannot state what the monthly work is worth separately, you cannot decide whether to keep buying it.

Let projects come and go

The retainer should be stable while projects vary. A retainer that swells and shrinks with project work is really a series of projects with a subscription attached.

Review the split annually

Work migrates. Things that were projects become continuous, and continuous work sometimes finishes.

When a retainer is the wrong purchase

Several situations are reliably poor fits for ongoing fees, and recognizing them saves considerable money.

When the work genuinely finishes. When you have no capacity to supply inputs or approvals, since an agency retained without access produces little regardless of skill. When the budget is small enough that the retainer buys only a few hours a month, which is usually too little to accomplish anything and too much to be worth the coordination. And when you do not yet know what you need — buying strategy as a project first is cheaper than paying an agency to work it out on a retainer.

The small-retainer case deserves particular attention. A fee that buys three or four hours monthly is frequently worse than either doing nothing or saving for a defined project, because the coordination overhead consumes most of what was bought.

When a project is the wrong purchase

The mirror image is equally common and more expensive, because the cost appears later.

Buying a website as a project and nothing afterwards produces a site that is accurate on launch day and steadily less so thereafter. Buying an SEO project produces recommendations that were correct for a search landscape that has since moved. Buying a content project produces a batch of articles with nobody maintaining or promoting them.

The pattern in each case is the same: the deliverable was real, and its value depended on continuation that was never purchased. If you buy a project for work that is genuinely ongoing, plan how it will be maintained before it is delivered rather than after.

Moving between models without renegotiating everything

Engagements change shape, and the model should be allowed to change with them rather than persisting because it is what was signed.

The usual progression runs project first — a strategy or a build — then a retainer once the ongoing requirement is understood. The reverse also happens legitimately: a retainer reduced to a smaller maintenance fee with projects layered on, once the heavy lifting is done.

Both transitions are easier if the original agreement anticipated them. A clause allowing scope and fee to be revisited at defined points converts what would otherwise be an awkward renegotiation into a scheduled conversation.

Watch for the model outgrowing the work

A retainer sized for a launch period is usually too large a year later, and the honest agency raises it before you do.

Watch for the work outgrowing the model

Repeated variations on a project mean the requirement became continuous. That is a signal to change structure, not to argue about scope.

Change the model rather than the agency

A structural mismatch reads exactly like a performance problem, and replacing the agency reproduces it with someone new.

Questions that settle which model you need

Four questions resolve most cases without any comparison of pricing.

Does the work have a finish line, or does it stop working when it stops? Do you have the internal capacity to supply inputs continuously, or only in bursts? Is the budget large enough that a monthly fee buys meaningful time rather than a few hours? And do you know what you need, or are you paying someone to work that out?

A finish line, burst capacity, a modest budget, or an unclear requirement each point toward a project. Continuous value, steady internal capacity, sufficient budget and a clear requirement point toward a retainer. Mixed answers point toward the hybrid, which is where most arrangements end up.

Reference videos

Commercial and measurement fundamentals relevant to the models described above.

Frequently asked questions