Most agencies and consultancies spend enormous energy on onboarding — the welcome, the kickoff, the first-30-days checklist — and almost none on the exit. So every offboarded client leaves behind a folder nobody dares delete, two domains you still technically administer, and a "quick question" email that arrives monthly for a year. The exit quietly costs you support hours, access risk, and the referral the relationship should have produced.
The full client offboarding checklist is the fix. Here's the shape of it.
1. The three exits — and why the exit type sets the checklist
Before anything else, write one sentence in the client's file: which exit is this?
- The completion exit — the project shipped, the goal hit. Offboarding here is a celebration with paperwork: final invoice, handover pack, and the referral ask at its most natural moment.
- The pause exit — budget freeze, hiring change. The relationship is sleeping, not dead: agree pause terms in writing (duration, holding rate, restart trigger), skip the hard access cut-off, keep the keep-warm cadence running. Half of paused clients restart within a year — if you didn't make the exit feel final.
- The ended exit — fired, outgrown, or drifted. The full checklist: everything gets a date, every access gets cut, and the goodbye is scripted so it can't be skipped.
The most expensive offboarding mistake is running the full cut-off on a pause, or a soft goodbye on an end.
2. Money before feelings: the final invoice
The final invoice goes out within 48 hours of the exit conversation — not "when we wrap up the last bits." Every day between the goodbye and the invoice converts billed work into a favor, and favors don't survive a client's finance department.
- The invoice names itself: "Final invoice — engagement complete 30 Sep." FINAL gets prioritized and closes the account in their AP system.
- Hold-backs get resolved, not discovered. A $90 pass-through found in November on a September exit reads as sloppiness, not arithmetic.
- Payment terms stay the same terms. A final invoice is not an apology invoice. Bending terms at the exit teaches clients the terms were negotiable all along.
3. The handover pack: one folder, four things
The pack is what turns "we can't leave, they'll be lost without us" into "here is everything, in one folder, yours" — and it's what ends zombie support.
- The files — every deliverable, final versions only, named by the promised convention.
- The credentials — domains, hosting, ad accounts, analytics, transferred to ownership the client controls, via a password manager share. Never in the pack itself.
- The one-page map — what everything is, where it lives, who hosts it, when it renews. Dumping 300 files in a folder is abandonment; the same 300 files with a one-page index is a professional exit — and the page that gets forwarded when someone asks "who built this?"
- The maintenance reality — one honest paragraph: what breaks without attention, and how often.
Send it once, marked final. The pack itself sets the boundary you'd otherwise have to enforce in conversation.
4. Access cut-off: last in, first out
The cut-off date is said in the exit conversation, on the record: "our access ends 14 days from Friday." Revocation order: payment and billing access first (nobody spends the client's money after the last invoice), then publishing and admin rights, then write access, then read-only last. Every removal gets a one-line log entry — account, role removed, date.
That log is also your security-review evidence: the annual "do you offboard access?" question becomes an afternoon instead of an archaeology dig.
5. The exit conversation that isn't a goodbye
The end of an engagement is the highest-goodwill, lowest-stakes moment in the whole relationship — no live work to judge, no invoice anxiety, no proposal pressure. It is the best referral window you will ever get, and most teams spend it mumbling "let's keep in touch."
The ask rides the handover send: thanks tied to a real outcome, one named person, an easy exit. The testimonial ask is one sentence with an out: "two lines I could quote would genuinely help — no worries if not." Two lines is a two-minute job; a blank page is a never.
And leave the door open in one specific sentence, not a vague one: "If the replatform lands next quarter, the fastest version of this is a two-week refresher" is a door. "Let's definitely work together again" is noise.
6. The keep-warm file
An ended client is a prospect who already trusts you and hasn't been marketed to in months. One row per offboarded client: exit date, exit type, the one thing they'd need next ("the replatform lands in spring"), last-touch date, next scheduled touch. Two touches a year, both worth opening: the "this reminded me of you" note and the anniversary check-in. When the thing you predicted happens, that's not cold outreach — that's the follow-up you promised.
What it looked like in practice
A nine-client consultancy ran offboarding the old way: invoice whenever the owner got to it, files in "FINAL_final_v2", access cut whenever someone noticed. About eleven hours a month of out-of-scope "quick question" support from former clients, and one referral in three years.
One year after the checklist: exit support under 2 hours a month, four introductions from four exits, one ended client back as a $14k project when the predicted replatform landed, and a zero-dangling-access audit passed first time. Nothing about the delivery changed — only the exit became a designed event.
The full checklist — the worked example, the five weekly numbers (final-invoice-within-48h, handover completeness, dangling access age, exit referral rate, 12-month return rate), and the pause-heartbeat mechanic — is on the site:
Client Offboarding Checklist for Small Teams (The Exit That Feeds the Pipeline)
Pair it with the retainer renewal checklist (the offboard is the third renewal path — decide it in week one, not the last week), the referral request sequence (the ask, engineered), and the win-back sequence (the ladder for the ones that left badly). If you want the kit versions, the Ops Starter Kit ($14) and the Ops Mega Bundle ($29) are on Gumroad.
HIVE80lab publishes one practical ops-note per day for small teams — free, no signup, no fluff.
Top comments (0)