Agencies are designed to stay. Freelancers are designed to vanish. A practice is designed to end on a date the company can name. That is not a slogan. It is the test of whether anything was installed.
If the week collapses when the principal steps out, you purchased a person. Useful, sometimes. Not a practice. A practice leaves behind a calendar, a kill list, templates that legal already trusts, a reporting page a VP can read, and a meeting that runs without a guest star.
Knowledge transfer is usually a folder. Folders are where programmes go to die. The transfer that matters is operational: the next owner has already run the weekly, already shipped a week, already killed a send, already explained a number to finance. Then the seat can close. Not before.
This is why embedded work has a clock. Twelve months, reviewed quarterly. Not because the calendar is magic. Because without a clock, handover becomes a myth you tell in month eleven. With a clock, month three is already teaching. Month nine is already unassisted. Month twelve is a review, not a rescue.
Diagnostic missions have the same standard in a shorter body. Four to eight weeks should still leave an architecture, a 90-day plan, and a stack that is instrumented — not a PDF of observations. The end date is not permission to be abstract. It is a constraint, like any other.
Channel retainers fail this test when they become a permanent extra headcount with nicer stationery. If email cannot be held by the PMM after a year, the retainer taught nothing. It performed the channel. Performance is not installation.
What you hand back, in practice: the send plan or the editorial calendar; the claims and voice rules; the authentication and suppression logic; the stop rules; the names of the legal path; the numbers page; the weekly agenda. Written so a competent operator can run them. Not written as a novel.
What you do not hand back: a personality. A taste that cannot be explained. A relationship with a vendor that only one person can work. Those are how seats become traps. Fluency in Salesforce Marketing Cloud or Braze or Klaviyo is transferable if it was documented as configuration, not as folklore.
Companies fear handover because they have been trained by firms that leave a mess and a proposal for phase two. The fear is rational. The answer is to watch independence as a metric from the first month. Who ran the weekly. Who shipped without the principal in the room. Duplicate that until it is boring.
Confidentiality continues after the seat. Anonymized cases on a site are not a leak. Named clients would be. The operating system you leave is the company’s. The practice does not keep a shadow copy of the calendar as leverage. That is agency behaviour.
The last thirty days are a dress rehearsal. The principal is present and mostly quiet. The team runs. Exceptions come to the weekly, not to a private thread. If the exceptions are the whole week, you are not done. Extend only if independence is the reason — not if comfort is.
Boards like continuity. Continuity of a vendor is not continuity of a programme. Continuity of a programme is a team that can run the week. If you want a permanent bench, hire one. Do not rent a principal and then refuse the ending.
MBX is a solo practice. There is no rotating junior to quietly become the continuity plan. That is a feature. You always know who is in the work. You also know the work is meant to outlast her. Write when you want that ending designed from the start — the mission, the team, the constraint, and the date you intend to be unassisted.
The compliment is not that they asked her to stay. The compliment is that they did not need to.
There is a vanity version of independence: a playbook nobody opens. Count the weeks the team ran without a private thread to the principal. Count the sends that shipped on the legal path that was named. Count the meetings that killed work. Those are the numbers. A PDF is not a number.
When a mission ends, the practice does not keep a retainer-shaped shadow. If the company later wants another diagnostic, that is a new brief. Continuity of relationship is allowed. Continuity of dependence is not. The distinction is the entire ethics of a solo seat.
Write the ending into the first conversation. The 90-day outcome should include who runs the weekly in month four. If nobody can name that person, you are hiring a permanent guest. MBX is the wrong shape for that. Hire a head of channel, or admit you want a bench. Do not dress a dependency as a practice.
Camille Edith Baudouin, MBX Consulting