Two ways a retainer can end
The first is the default. A retainer winds down — budget shifts, priorities change, the project completes — and the agency produces a final report. Traffic numbers. Ranking movements. Ad spend summary. A slide deck with month-over-month comparisons. The relationship ends and the client has a record of what was done.
The second is what we aim for. The retainer winds down and the client can run the work themselves. They have the documentation. They have the systems. They know what to watch, what to adjust, and when to call someone for help. The relationship ends and the client has operational capacity they did not have before.
These are not the same thing. The first produces a summary. The second produces a transfer.
What actually gets handed over
When a retainer ends at Nuko, the deliverable is not a report. It is a working handover package — the specific things the client needs to continue operating at the level we built to, without us in the room.
Documentation of the current state. Every active channel, every running campaign, every configuration that was changed during the engagement — documented at a level of specificity that a new person could pick up without asking us.
This documentation does not get written at the end. It is written throughout, updated when decisions change, and reviewed before handover. A final report that tries to reconstruct months of decisions in 48 hours is not documentation. It is archaeology.
The measurement framework the client actually owns. We do not hand over a dashboard full of metrics that require our login to read. We build reporting inside tools the client controls — Google Search Console, Google Analytics, whatever ad platform they use natively — and we walk through what each number means, what to do if it moves in the wrong direction, and what is normal variance versus a signal that something is broken.
This sounds basic. It is consistently the thing clients say they did not get from previous agencies.
The AI ecosystem, if one was built. Where AI workflows were part of the engagement — prompt libraries, context files, automation logic — those get documented and transferred the same way as everything else. The client owns them. They do not live in our tools or our accounts.
A named person who can run it. Documentation without a trained operator is a filing cabinet. Before the retainer ends, there is a specific person on the client side who has worked through the systems with us, understands the decisions behind them, and knows what they do not know — meaning they know what type of problem warrants calling someone for help versus what they can resolve themselves.
What we do not measure
A few things get left off the handover review deliberately.
Vanity metrics without a revenue connection. Follower counts, impression volume, engagement rates in isolation — these are fine data points but they are not the answer to any question a founder actually needs answered. If we cannot draw a line between a metric and revenue, bookings, or cost reduction, we do not build reporting infrastructure around it.
"Engagement" as a catch-all. This term has been stretched to cover so many things that it now means almost nothing. When we use it, we are specific: link clicks from a specific campaign to a specific page, form completions from organic traffic, call bookings from a newsletter. The measurement earns its place by being actionable.
Activity as a proxy for outcome. Hours worked. Number of blog posts published. Ads created. These measure effort, not effect. A retainer that produced 40 blog posts and no measurable organic growth is not a success because the volume was high. We track what moved.
The retainer that ends on purpose
There is a version of an ongoing client relationship that is designed from the start to end. The scope is defined. The build-out has a finish line. The goal is to transfer something functional, not to maintain an indefinite dependency.
This is not the only model. Some relationships should stay long because the work is genuinely ongoing — a clinic that needs continuous SEO expansion into new service lines and cities, consistent ad management across multiple platforms, and monthly reporting that feeds into the next month's decisions. That relationship has no natural finish line because the market does not stay still. The bottleneck changes. The channel mix shifts. The work is real and recurring.
But the retainer that exists mainly because nobody built an exit plan is a different thing. We try to be honest about which one we are in, and to build the exit plan for the ones that have one.
What this looks like in practice
A retainer that ends well looks like this: the client's internal team lead can open the Google Ads account, read the campaign structure, understand the logic behind the bidding decisions, and make a minor adjustment without calling us. They know what a healthy cost-per-booking looks like and what would make them concerned. They have the brief templates for the content that feeds organic traffic. They know which metrics to watch weekly and which to review monthly.
They also know what they would call us for. Not because they are dependent, but because some problems — a platform policy appeal that requires knowing the nuances of ad platform compliance, a strategic pivot that changes the channel mix, a new market entry that requires a diagnostic from scratch — are genuinely non-trivial. The handover creates capacity. It does not pretend to cover everything.
The measure of a good retainer is not how much was done during it. It is how well the client runs after it.