Email marketing retainer vs project: how to buy the work you need

A project ships a thing, a retainer keeps it working

A project has an end. Somebody scopes the build, quotes it, ships it and hands it over, and the morning after handover it's yours to run. A retainer buys a share of a team every month, and what it produces isn't a thing but a rate of change.

That's the whole distinction, and almost every argument in month four comes from buying one and expecting the other. A brand that wanted assets ends up paying for judgement it never uses. A brand that wanted judgement ends up with a stack nobody maintains.

The case for the one-off build

A one-off build is the right purchase far more often than agencies admit. If the account is close to empty and somebody in house is genuinely going to run it afterwards, a project gets you a stack you own for a number you agree once.

• The flows don't exist yet, so the first build is most of the value
• There's a real person in house who will send the campaigns afterwards
• The brand is seasonal enough that most of a year on retainer would sit idle
• You want to see whether the agency is any good before buying the year
• The budget is approved once, not monthly

The risk is the one everybody knows and nobody prices. A flow stack decays: products change, the offer changes, the delivery promise changes, and a build handed over in March is quietly wrong by autumn if nobody opens it.

So buy the handover with the build. A walkthrough of the flow logic, the naming convention and the reason behind every delay beats two extra emails in a sequence. It's the only part that lets somebody else keep it true.

The case for a retainer instead

A retainer is worth it when the value sits in the decisions and not in the assets. Once the stack exists, the money's in what gets tested, what gets rewritten because the data moved, and what gets sent this month that nobody planned last month.

That didn't come out of a build. It came out of a year of them, in an order nobody could have written down in advance, and the Rebel Aromas case study sets out the sequence.

Write it down before either one starts

The difference between a good engagement and a bad one is almost always scope. Both models fit on a page, and anybody who won't put theirs on a page has told you something useful for free.

Whichever you buy, the platform account, the list, the templates and the flows belong in your billing, with the agency as a user you can remove. That part isn't a negotiation, and the buyer's guide carries the rest of the questions worth asking before you sign.

The retainer that quietly became four sends a month

The commonest failure here isn't a bad build. It's a retainer that started as a rebuild and settled into a monthly campaign service, at the same fee, without anybody deciding that it should.

It happens because the backlog gets cleared and nothing replaces the ambition. The test takes one question: ask what was rewritten last month because the data said so, and see whether you get a list or a pause.

The fix is rarely a new agency. Put a standing item on the monthly call for what gets retired, and give whoever runs the account permission to switch off something that isn't working. A retainer with nothing left to delete has stopped looking.

Three questions that settle it

1. Who presses send in month four, and are they hired, real and available?
2. Is the value in the build itself, or in what gets decided every month after it?
3. If this isn't working, how do I leave, and what do I keep when I do?

A real person, the build and a clean exit: buy the project and keep the difference. Nobody in house, an account big enough that the monthly decisions outweigh the assets, and the retainer is the cheaper mistake.

We work on thirty day rolling terms, because a year signed before anything is proven protects our forecast, not your outcome. Ask whoever you're speaking to what happens on the day you give notice, and whether the build stays in your account. If that answer needs a lawyer, buy the project.