The decision to sunset the retainer book came down to three forks. Drop the retainers quietly, no announcements. Price them out at the next cycle and let the market choose. Or publish a firm date on the public availability page and build everything around it. I picked the third. Every retainer conversation since has been easier. Here is the mechanic and what it cost me to get wrong on the first pass.
The fork behind the retainer sunset mechanic
At the time of the decision, the retainer book was running at $8K to $15K per month per client, on six-to-twelve-month commitments. The clients were real. The relationships were real. The work was valuable. And the model had a hard ceiling: hourly-rate math, documented in the hourly-billing retrospective, capped annual revenue somewhere around $180K to $300K before overhead. No amount of retainer discipline moved that number.
The productized ladder had started shipping. A $129 entry tier had closed its first cohort. A $497 tier was in draft. The question was not whether to sunset retainers. It was how to do it without burning relationships or leaving money on the table during the transition.
Three options showed up on the spreadsheet.
Option A: The silent drop
The mechanic is simple. When each retainer comes up for renewal, do not renew it. No announcement, no deadline. The book winds down naturally across six to twelve months as renewals lapse.
What the silent drop gives you: no awkward conversations. No clients feeling pushed out. No public commitment to defend. Internally, it is the lowest-friction option for the first 30 days.
What it costs: the clients have no participation in the transition. The first client who gets a "I am not renewing" message is surprised. They were expecting continuity. They have to scramble to find a replacement operator. The second client hears about it from the first. By the third, the book is leaking trust faster than revenue.
There is also no marketing signal from a silent drop. The productized tiers do not get a "this is why we are moving here" story. The website cannot reference a transition that does not exist publicly. Every productized-tier conversion has to stand on its own without the legacy business contextualizing it.
Option B: The price hike
The mechanic is almost as simple. At the next renewal cycle, raise the rate 50% to 100%. Let clients decide whether the new rate is worth it. Some stay at the higher rate, some leave. The book lifts on the ones who stay.
What the price hike gives you: revenue stability in the short term. Keeps some clients on retainer at better margins. Does not require a hard decision about the future of the model.
What it costs: the ceiling problem remains. A doubled hourly-equivalent rate still caps revenue at a number a single operator cannot exceed. Worse, the price hike creates a reputation for rate-pressuring. Clients who stay tell other operators. Clients who leave describe you as "the one who raised rates on us." Neither story is useful when you are trying to build a productized brand that sells to a different audience.
The price hike also does not transition anyone. The clients who stay on retainer are still on retainer. The retainer model is still the business. You have postponed the decision rather than made it.
Option C: The published sunset
The mechanic takes more thought. Publish a firm sunset date on the public-facing availability page. Give every existing client at least six months of notice. Price the remaining window as a clear runway: "retainers available through date X, at rate Y, with these scope constraints." Pair the announcement with the productized tiers that will replace the retainer model for most use cases.
What the published sunset gives you: transparency. Every client knows the timeline. Every prospect knows you are not taking new retainers past date X. Every productized-tier buyer sees the sunset as context for why the tiers exist. The calendar becomes a forcing function for shipping the products that will replace the retainer work.
What it costs: it is a hard public commitment. If the products are not ready by the date, you have embarrassed yourself in front of your entire client base and public audience. It also requires you to defend the decision when clients push back in the first 30 days.
What I chose and why
I picked Option C. The sunset date went on the public /availability page with six months of runway. Every retainer conversation since that announcement has started from a different frame.
Before the sunset, the conversation at renewal was "renew for another six months or don't." Most clients renewed without thinking hard about alternatives. Renewal was the default.
After the sunset, the conversation is "what is the off-ramp." The clients who could fit into the productized tiers moved to $129/$497/$1997 offers. The clients whose work genuinely required an ongoing relationship booked the remaining retainer-bridge slots early, filling the calendar. The clients who fit neither got a named referral to another operator whose model still made sense for them.
“The date on the availability page converts every retainer conversation into what is the off-ramp, not renew or don't.
”
The productized tiers benefited from the framing. Buyers who landed on /products could see the sunset context explaining why the tiers existed. The tiers were not a random productization play. They were the replacement for a real service the operator had delivered for years. That context showed up in the conversion rate.
The availability page's /availability slot count itself became a marketing signal. Remaining slots visible, filling down, with a hard date behind them. The scarcity was real, not manufactured. The calendar backed it up. Clients who had been on retainer for years could see their seat count decreasing and made decisions inside the window.
What I would revisit
Three things I would change if I ran the same decision again today.
Announce the sunset 12 months out, not 8. Eight months was enough runway for most clients but tight for the ones on 12-month commitments that straddled the date. A 12-month window would have made the "one final renewal at the legacy rate" pattern cleaner. It also would have given me more time to ship the mid-tier products before the calendar pressure hit.
Communicate at months 3 and 6 of the bridge window, not just at start and end. I announced the sunset, told every client, and then went mostly quiet on the topic for six months while I shipped product. A handful of clients forgot the date was real and planned Q4 work assuming continuity. The fix is scheduled check-ins at 90-day intervals, each one confirming the timeline and updating clients on what was being built to replace the retainer model. The client-offboarding protocol has the mechanics of those transition conversations.
Publish the ladder tiers before announcing the sunset, not alongside. I published both at once. Some clients saw the sunset and assumed the ladder was a half-finished backup plan rather than a real replacement. Shipping the ladder first, even in a draft form, would have let the sunset announcement land as "here is the path, and here is the date the old path ends" rather than "here is the date the old path ends, and here is the rough sketch of the new path."
A named "legacy rate" for one final renewal cycle would also have reduced the cliff. Clients on a $10K/month retainer looking at a $1997 productized tier see a 5x price drop, which is a signal problem even if the deliverable is different. A single-cycle legacy rate gives them a structured exit rather than a price jump-scare.
Frequently asked questions
Will clients react badly to a public sunset date?
A few will. Most will not. The clients I worried most about handled the announcement well because they valued the heads-up. The ones who reacted badly were ones who were going to react badly to any transition signal, including a silent drop. The public date at least gave them something concrete to react to rather than leaving them guessing.
What if I do not have products ready by the sunset date?
Then you have a serious problem and you need to either extend the date (publicly, with an explanation) or scope the products down so something ships. Missing the date silently is worse than either option. The sunset commitment is trust architecture. Broken commitments on public dates cost more reputation than the retainer revenue was ever worth.
Can I still take on new retainer work during the bridge?
Only if the work ends before the sunset date, and only if the scope fits inside what you can actually deliver while shipping product. I took two new retainer bridge engagements in the final six months and regretted one of them because it ate focus that belonged to product work. The default answer to "can you take on one more retainer" during the bridge should be no unless the engagement genuinely fits.
What if a client wants to extend past the sunset date?
Offer a structured alternative: a productized engagement, a one-time scoped project, a named referral to an operator who still does retainer work. Do not extend the retainer. Extending once publicly teaches clients (and your future self) that the date was negotiable, and it reopens the same conversation at the extended date. Hold the line.
How do I price the final bridge window?
Two options work. Hold the existing rate and make scarcity the mechanic (fewer slots, first-come-first-served). Or modestly raise the rate (10-20%) to reflect the tighter runway and constrained availability. Either signals that the window is closing. I held the rate and relied on scarcity, which felt right for the relationship-heavy book, but rate-bumps would have been defensible.
Sources and specifics
- The sunset date is published on the public /availability page and every retainer conversation since has been anchored to that date.
- Three forks considered (silent drop, price hike, published sunset) were real options on the spreadsheet; Option C was chosen and has held since announcement.
- The productized ladder that replaces most retainer work across $129 / $497 / $1997 tiers is documented in the three-tier productized pricing hub and visible at /products.
- The revenue ceiling math that triggered the decision is in the retrospective on leaving hourly billing behind.
- The direct cost comparison between retainer and productized engagements is documented in the retainer-vs-productized cost comparison.