Most retainer relationships end in a slow leak. The last invoice gets paid, nobody ever schedules a final session, and three months later the operator notices they are still in the client's Slack but have not been asked a single question in weeks. Both sides drift into a polite distance. The referral that would have come out of that client never arrives, because nobody ever closed the door cleanly enough for the former client to think about who else might need this kind of help.
This is the playbook I run to end a retainer over a 90-day taper, hand off the work in a form the client can actually use, ask for the referral while the relationship is still warm, and stay in light contact afterward on a cadence that converts a former client into a recurring referrer. By the end you will have a calendar, a documentation pattern that fits on two pages, the script for the referral ask, and the post-engagement check-in cadence I use to keep the relationship alive.
Why most retainer endings stop the referral flywheel
The two failure modes are easy to spot once you have run a few exits. The first is the ghost-out: the operator stops sending status updates, lets the next renewal date slide past, and eventually goes quiet. The client never gets a clear ending or a closing memo, and they never think about the operator again because there was no moment when "Michael" became "former Michael who I should remember when my friend asks me who built their checkout."
The second is the forced march. The operator decides on a Wednesday that they want to be out by the end of the month, sends a notice email, runs a rushed handoff in two weeks, and disappears. The handoff comes out incomplete. Three months later the client is still finding things in the systems they did not know existed. Relationship survives, warmth does not, and the client tells the next person who asks about fractional help that "the last operator was great but be ready to do a lot of work yourself when they leave."
A planned taper creates room to document, transfer responsibility, and check that the new owner can run the work. Ninety days is one scheduling example. The agreement and the client's operational needs determine the notice and transition window.
I shipped this taper for the first time in late 2025 when one of my engagements wound down and I wanted to close it cleanly instead of letting it leak away. The cost tradeoffs that sit behind a clean exit are in the retainer-vs-productized cost breakdown. My first taper was rough; by the third I had the structure that follows.
Prerequisites
Before you start the 90-day taper, four things should already be true.
The retainer agreement has a review point. Without a six-month review baked into the contract, the ending conversation feels like you are proposing a breakup, because there is no neutral structural reason to be talking about the future. The published mechanic for putting a review point into the contract from day one sits in the decision log on the retainer review-point mechanic. If the current retainer has none, schedule one now and frame it as a structured conversation about the next six months.
The credential map is current: every account, secret, shared service, and permission the engagement touches has an owner. Use the final two week sequence below for the access review and rotation record.
You have somewhere to point the client. Either a productized alternative you sell yourself, or another operator you trust to refer to. Without it, the ending conversation has no answer to "what should we do instead," and the client will ask.
You have an honest accounting of what the client actually pays for. Most retainer scope drifts. By month nine the client thinks they are paying for X, you are actually delivering Y, and there are three things in Y the client did not know they were getting. The taper conversation goes better when you can describe what was nominally in scope, what was actually happening, and what needs to transition cleanly.
Step 1: the day -90 conversation
The conversation that opens the taper is the hardest part. Get this one right and everything that follows is mechanical.
Frame it as a structured talk about the next 90 days, not as an announcement of the ending. Use the review-point language directly: "Your review point is coming up in 90 days. I want to use this call to talk about what happens after that." That phrasing puts both sides into a planning posture instead of a defensive one.
The conversation has to settle four things before it ends:
- End date.
- Scope through that end date, including what new work you will and will not take on during the taper.
- Transition path, which is your concrete answer to where the client should go next.
- Referral posture, meaning whether you would welcome introductions to people in their network.
The opening message should name the agreed end date, explain the scope through that date, and give the client a concrete transition path. Retainers remain a durable offer in the practice; closing one engagement does not imply a fixed sunset for every retainer.
A few things to keep out of this conversation. Skip "always available" language after the end date. Skip the discounted future work meant to soften the news, because the discount trains the client to expect the relationship to keep paying off without changing shape. Don't keep credentials active "just in case." Promises like these are the ones you will quietly regret keeping or breaking, and they do more damage than the careful end did.
Step 2: the documentation handoff (day -90 to day -45)
The first half of the taper is documentation. Most operators ship a closing memo at the end and call it done, which is too late and too thin. Ship the documentation in the first 45 days while you are still in the work, then spend the second 45 days teaching the client team how to use it.
The closing artifact has four sections:
- Systems map covering every system in the engagement, who owns it now, who should own it after, and where the credentials live.
- Runbook covering recurring tasks, who runs them, and how often.
- Decision log of the three to seven decisions you made during the engagement that the client team needs to remember, with the reasoning.
- Vendor list covering every third-party tool, what it costs, when it renews, and the contact for support.
The two-page rule is the discipline. Each section should fit on two pages or fewer. Anything longer is a runbook in its own document, linked from the closing memo. The memo itself stays scannable enough that the client can print the whole thing and read it on a flight.
Most handoff documentation fails because it is written for the operator's record, not for the client team's use. Test it by handing the draft to someone on the client team who was not in the original work and asking them to perform a task using only what is written. The first three times you do this you will find gaps you did not know existed.
Step 3: the explicit referral ask (day -30)
This is the step most operators skip, and it is the one that determines whether you get any referrals at all. The polite version of the ask is the version that fails. "Let me know if you ever come across someone who could use my help" is a closing line, not an ask. It puts the entire burden of action on the client, who is not going to spontaneously remember you in a conversation about something else two months from now.
The version that works is specific, scripted, and timed at day -30. The relationship is still active, trust is still high, and the client has not yet started feeling the absence of your work.
“"Let me know if you ever come across someone who could use my help" is a closing line, not an ask. It puts the entire burden of action on the client, who is not going to spontaneously remember you in a conversation about something else two months from now.
”
The script has three questions. "Who do you talk to who has problem X?" Replace X with the specific shape of the work you do (for me it has been "broken Shopify analytics" or "fractional CTO without the title"). The client thinks for a moment and names two or three people. Most of the time those names are real. "Would you be willing to introduce me to one or two of them?" Almost everyone says yes if the first question landed, because they have already mentally identified the people. "Can I send you a one-pager you can forward, or would a warm intro by email be better?" That gives the client an easy out from writing the intro themselves and puts you in control of the message.
The one-pager is the asset that makes the referral easy to forward. Keep it short: who you are, what you build, the kind of company that benefits, and a link to your availability page. The client forwards the one-pager, the new contact reads it on their own time, and the conversation starts already qualified.
Time the ask at day -30 because the work is still fresh enough for the client to describe clearly and the relationship is still active enough that asking is not awkward. By day +30 the awkwardness creeps in. By day +90 the moment has passed.
Step 4: the post-engagement check-in cadence
The cadence is what turns a former client into a recurring referrer. Most operators end the relationship and never reach out again, then wonder why former clients do not refer. The cadence is also the safest possible kind of follow-up because each touch is short, low-pressure, and useful to the client whether or not they ever refer anyone.
I run four touches: day +30, day +90, day +180, and day +365.
Day +30 is the "anything broken" check-in. Five sentences over email. "Quick check-in, you are 30 days in. Anything in the documentation that turned out to be wrong, anything that broke that you did not expect? Reply with the worst one and I will look at it for free." This message is not about referrals. It closes any open loop the handoff left dangling. The free fifteen minutes is a real offer; the cost is small and the relationship value is large.
Day +90 is the "second opinion" check-in. "You are 90 days past the handoff. If you are facing a decision in the next quarter where a second opinion would help, I am happy to spend 30 minutes on it, just thinking out loud together." Most clients do not take you up on this, and a few do. The few who do tend to be the ones most likely to refer later, because the second-opinion call demonstrates you are still useful without trying to sell anything.
Day +180 is the "what is working" check-in. Slightly longer. "Six months out. What is the engagement we ran together still doing for you, what stopped working, what would you change about the handoff if we did it again?" This is research as much as relationship. The answers go into your next handoff, and the act of asking signals you take the long view.
Day +365 is the "year in review" check-in. A short email summarizing what is publicly visible from your work that year (writing, products, case studies), an invitation to share their own year, and a soft reopen of the referral ask if it feels right. By this point the former client has watched you build and ship without their direct involvement, and the year-in-review email is the moment they think "I should mention Michael to so-and-so" and actually do it.
Each touch deposits a small amount of warmth. Over a year of former clients running through the cadence, the referrals start to compound. My second taper produced two referrals in the first six months and three more in the second, none of them in the first 30 days after the engagement ended. All of them landed after at least one of the cadence touches.
Common mistakes that kill the referral flywheel
The ghost-out is the most common failure. An operator runs the taper, ships the closing memo, and then disappears. The flywheel never starts because the cadence never runs.
Discount-during-exit is the next failure. An operator senses the client's hesitation and offers a reduced rate to extend the relationship. That discount telegraphs that the operator does not actually want the ending to happen, which makes the ending feel forced. It also trains the client to expect discounts in future work, which damages the productized pricing the operator is moving toward.
The forever-Slack failure happens when the operator never leaves the client's Slack workspace and answers occasional questions for free over months. That is the relationship version of forgetting to log out. It signals the engagement never really ended, which means the client never enters the mental category of "former client who could refer me."
The worst version of all four is the closing line "let me know if you ever need anything." That sentence sounds polite and does no work. It transfers the burden of future contact to the client, who is busy and was not waiting for permission to call you. A structured cadence and an explicit referral ask replace it cleanly.
What to try next after the 90-day taper
After the first taper, do three things.
Track the referrals back to source. When a new lead comes in, ask how they heard about you and write the answer down. Match it back to the cadence touches. The signal you are looking for is which interval produces the referrals. For me it has been the day +180 and day +365 touches more than the early ones. Knowing this lets you weight your cadence energy correctly.
Reuse the playbook for the next exit. Each one improves the playbook. Keep the closing memo template, the one-pager, and the cadence email scripts in a folder you can copy from. The second taper is half the work of the first.
Reallocate the released capacity deliberately. It can support a new retainer, a productized diagnostic, or time reserved for improving the practice. Keep the choice inside the capacity the remaining clients need.
The last two weeks of the taper
The longer taper handles the transition. Use the last two weeks to test whether the handoff actually works. Run a working session with the client's next owner driving the systems while you watch. Use a real recurring task, resolve the open questions, and update the runbook where the operator needed help.
A useful agenda covers the systems still in flight, the recurring tasks the new owner will run, unresolved items, and the response when a familiar failure happens. Finish by checking that the documentation names the person who owns each next action. Record corrections during the session rather than trusting a follow up from memory.
One week before the final day, reconcile access with the client. The list includes API keys, webhook secrets, shared account passwords, platform staff access, repository membership, deployment teams, and guest messaging access. Specify the replacement owner and what stops working if a credential is revoked. Let the client rotate or revoke its access, then remove the copies you no longer need. A dated unresolved access note is useful evidence when a client has not finished its side.
The final closing memo has six parts:
- Work completed, with links to the systems and deliverables
- Current state of each system and its operating documentation
- Outstanding items with a named owner and next action
- Known gaps the next operator needs to see
- Recommendations for the next 30, 90, and 365 days
- The contact path for a future scoped engagement
Keep the memo short enough for a new hire to use, with detailed runbooks linked separately.
Agree any later check ins while the relationship is active. The earlier exit notes used 30, 90, and 365 days; the longer taper adds an optional six month review. Those are scheduling examples. Match them to the client's needs and define when a new request becomes new paid work. The separate client offboarding protocol remains the general checklist for engagements beyond retainers.
Sources and specifics
- The 90-day taper window is from running my own retainer exits starting Q4 2025 across multiple clients in the services-pricing-business cluster.
- The four-touch post-engagement cadence (+30, +90, +180, +365) is calibrated from referral pattern observation across the first year of taper exits.
- The day -30 referral ask script is the one I use verbatim, edited only for client-specific context.
- The two-page closing memo discipline is a constraint, not a guideline; longer closing memos correlate with handoffs the client team never reads.
- The structural mechanic behind closing a single engagement cleanly is documented in the published retainer review-point mechanic, which sits in the same pricing hub as this piece.