Why Should a Marketing Engagement End?

Here is a sentence you will not hear from a marketing vendor, so I will say it plainly and then spend a post defending it: a healthy marketing engagement should have a declared end date, announced by the vendor, at the start.

Not a renewal date. Not a review checkpoint. An end – a point at which the work is done, the assets are in your hands, and the default is that you continue without them. I run my own engagements this way, the strategy work capped in weeks, and clients sometimes think it is a gimmick until they have lived through the alternative. If you have ever paid a retainer for month fourteen without being able to say what month fourteen bought, you have lived through the alternative.

The Retainer Has a Structural Problem

As with the audit two weeks ago, the problem is incentives, not villains. An open-ended retainer pays the vendor for continued presence, not completed work. Sit with what that does to behavior over time, even to decent people.

Knowledge stays in the vendor’s heads, because documented knowledge is transferable and transferable means leavable. Reports fill with activity – posts published, hours logged, impressions served – because activity justifies presence even in months when nothing compounds. Systems get built inside the vendor’s accounts, on the vendor’s logins. And the strategy, if there ever was one, is never written down to a standard you could hand to someone else. None of this requires bad faith. It is what the payment structure quietly selects for, month after month, until the client is load-bearing furniture in the vendor’s revenue and the vendor is an unremovable organ in the client’s marketing.

The test from the first series applies here with full force: if the payments stopped tomorrow, what would the business keep? Under a presence-based retainer, the honest answer is usually: the invoices.

What a Declared End Changes

Now flip the structure. The vendor says on day one: this engagement runs a fixed number of weeks, here is what exists at the end, and the end is the plan. Watch what that single commitment forces.

Everything must transfer

If the engagement ends, the knowledge has to live somewhere other than the vendor’s heads by the time it does. The spec gets written. The systems get built in your accounts. The process gets documented well enough for whoever comes next. Transfer stops being a courtesy and becomes the deliverable.

Scope gets honest

An open timeline absorbs infinite scope, which is why open engagements drift. A capped one forces the only conversation that matters at the start: what, exactly, will be true when this is done? That question, asked seriously, is half the strategy work by itself – it is the spec showing up in contract form.

The relationship inverts

Here is the part I find owners feel before they can articulate it. Under a retainer, the vendor asks to stay – every renewal is the vendor selling continuation. Under a declared end, if more work happens, it is because the client asked. That inversion changes the entire texture of the relationship. Advice gets sharper, because the advisor is not protecting a renewal. A no costs nothing to say. And when the client does ask for the next phase, they are asking from evidence – they watched the last phase end on time with the assets in hand.

But Is Not Marketing Ongoing?

The obvious objection: marketing never ends, so how can an engagement? The answer is to keep two things separate that the industry deliberately blurs – the work and the working.

Building the machine is project work. The spec, the assembly, the systems, the library’s foundation – these have a done state, the way a kitchen renovation has a done state. Running the machine is ongoing – the publishing loop, the gauges, the adjustments – but ongoing does not mean outsourced forever. A well-built engine is designed to be run by the business that owns it, with help where help earns its keep. When I stay on for the running phase, it is quarter by quarter, each one ending with the same question: is this still the highest use of your money? Some quarters the honest answer is no, and saying so is the whole point. The rhythm of the machine belongs to you. Whether any vendor stays inside it should be a standing question, not a standing order.

The Exit Is the Proof

Step back and the pattern across this series snaps together. The honest diagnostic can say no. The real strategist hands you a spec that works without them. The honest engagement declares its own end. One principle underneath all three: the value must survive the vendor’s departure, or it was never value – it was dependence with deliverables attached.

Which gives you a wonderfully compact test for anyone who wants your marketing budget, me included. Ask them: how does this end? A confident, specific answer – here is the end state, here is what you own, here is the handoff – tells you they have built things that survived them before. Discomfort, deflection, or a speech about partnership for the long haul tells you the business model is the stay, not the work. The exit is the most honest feature you can buy, precisely because it is the one feature the seller cannot fake enthusiasm for.

This Week’s Homework

Pull up every ongoing marketing relationship you pay for – retainers, subscriptions with human services attached, the maintenance agreement you stopped reading invoices for. For each one, answer three questions in writing.

What did this relationship complete in the last ninety days – complete, not perform? If it ended next Friday, what would I keep, and what would leave with them? And was the last renewal my idea or theirs?

You are not looking for villains. You are looking for structure – which relationships are built to finish things and which are built to continue. Keep the list. It becomes the working material for a post coming in three weeks, on how to buy marketing without getting sold. Next Thursday, though, we open the box: what clarity work actually produces – the money map, the buyer’s path, the load numbers – and what the document in your hands should contain before anyone builds anything.