The Ignis team reviewing work in the studio

Scope Creep In A Marketing Retainer

A retainer that quietly grows without a conversation ends with missed work on one side and resentment on the other. One page of rules stops it.

A marketing retainer rarely fails on the big things. It fails on the small extra asks that pile up over six months, until the team is doing a third more work than was scoped and the client still feels short-changed.

Nobody acts in bad faith. A marketing director asks for one more landing page, a quick event flyer, a round of edits on a board deck. Each request is small and reasonable, and saying yes is easier than having the talk.

Why it hurts both sides

The scoped work starts to slip. The daily content goes out later, the monthly report gets thinner, and the extras crowd out the work that was meant to move revenue.

Then the client notices the slip and not the extras, because the extras were favours and nobody wrote them down. The partnership now feels worse to both people at the same time, which is the fastest way to end one.

Write the scope as outputs, not hours

A scope that says 40 hours of marketing a month invites every request, because every request fits inside the hours until suddenly it does not.

A scope that names outputs is easier to hold. Daily posts across the agreed platforms, a set number of videos, the website and its landing pages, the SEO and GEO article engine, Google and Meta campaigns with a stated number of creative refreshes, and a monthly report against revenue. When a request arrives, the question is simple: is this on the list?

Our own tiers are matched to scope for exactly this reason, and the price is set on the application call once the scope is clear.

The one page

Three rules cover almost every case. They fit on one page that both sides agree to at the start.

  1. 1.Anything on the scope list ships to the agreed standard and cadence, with no negotiation.
  2. 2.Anything off the list gets a written note within one business day saying what it is, what it would take, and what scoped work it would push back.
  3. 3.Anything that recurs for two months running is a scope change, and the scope gets rewritten rather than absorbed.

The second rule does most of the work. It turns a favour into a choice, and a client who can see the trade usually makes a good call.

Swaps are fine

A retainer should flex. A product launch might need a burst of video while the blog slows for a month, and that is a good use of the same team.

The rule is that a swap gets named out loud. "We are moving two articles of effort onto the launch video this month" is a swap. Quietly doing both is creep, and so is quietly dropping the articles.

When the scope itself is wrong

Sometimes creep is a signal that the original scope missed something real. If the client keeps asking for landing pages, the business probably needs a landing page programme, and the honest move is to say so and scope it properly.

Treat a pattern of requests as information about the business rather than as a nuisance.

One owner on each side

One person on each side owns the scope. On our side that is the account lead, and on the client side it is usually the marketing director or general manager.

Requests from anyone else in the business go through that person. It stops a sales manager and an owner from asking for two different things on the same afternoon and both being told yes.

Review it every quarter

Every quarter, sit down with the scope, the delivery log and the results. Look at what shipped, what got added, what moved the numbers, and what should be in or out for the next three months.

A scope that gets reviewed on a calendar never needs a hard conversation, because that conversation already happens four times a year. It is also why we take a maximum of four new businesses a month: a team that is not stretched has room to hold the scope it agreed to.

The payoff is a retainer that stays the right size as the business grows, with every hour going into the work that was agreed to move revenue.

Written by David Eid. Published .