The monthly retainer is the default shape most fractional operators default to because it's easy to sell. It is also the shape most likely to quietly decay into a weak engagement the buyer eventually cancels without a referral. Here's why the retainer is a trap, what productized offers do better, and the specific escape plan I'm running in my own practice.
This article sits inside the running-a-fractional-practice cluster and takes the contrarian view on retainers as a default shape.
The retainer's structural problem
A monthly retainer has no deliverable. The operator shows up on cadence, does work, invoices at month-end. The buyer gets an amount of time-and-attention that varies with how busy the operator is, how much the buyer wants, and how productive the conversations are.
Because there's no deliverable, there's no completion. The engagement just runs until somebody cancels. The natural termination condition is one side getting uncomfortable, not a specific thing shipping. That changes everything downstream about how the engagement feels and performs.
The retainer's first failure mode is scope elasticity. A month without many client asks is a month where the operator delivered less. A month with many asks is a month where the operator is overworked. Both months cost the buyer the same, so the buyer unconsciously optimizes toward more asks. The operator unconsciously optimizes toward fewer. The two trajectories are misaligned.
The retainer's second failure mode is attention drift. In month one, the engagement is fresh. The buyer brings real questions. The operator brings real focus. By month six, the engagement has usually decayed into status meetings and "how's everyone doing" chatter. Nobody canceled because nobody wanted to. The engagement is no longer productive but still billing.
The retainer's third failure mode is the quiet cancellation. When the buyer does cancel, it's usually not because they got what they wanted (they never knew what "done" looked like). It's because budgets got tight, or a new CFO reviewed vendors, or the buyer found another use for the monthly spend. The cancellation is about the buyer's context, not about the engagement's value. No referral emerges because nothing shipped worth referring.
Why productized is structurally stronger
A productized offer has a named deliverable, a fixed price, and a defined completion point. The buyer knows exactly what they're buying. The operator knows exactly what they're delivering. When the deliverable ships, the engagement is complete.
The productized offer eliminates the three retainer failure modes.
Scope elasticity is gone because the scope is fixed. A sprint ships what was in the SOW. Asks that are out of scope are scoped as follow-on engagements. The buyer and operator are aligned on what "done" means.
Attention drift is gone because the engagement has a clock. A 90-day sprint has 90 days of defined work. There's no month six because the engagement ends in month three.
The quiet cancellation is gone because the engagement doesn't "cancel." It completes. The completion is a discrete event. The buyer has a deliverable to look at, a result to measure, and a story to tell. That story is referral material. A completed sprint that shipped its promise is the cleanest referral source a practice can build.
The economics that usually favor retainers
The reason retainers persist despite these structural problems is economic. A $12K/month retainer running for 6 months produces $72K of revenue. A 90-day sprint at $40K produces $40K. Straight revenue comparison favors the retainer.
The comparison misses two things. First, the retainer consumes more of the operator's time because month four, five, and six are usually lower-quality engagement (attention drift) at the same cost basis. The sprint delivers its value in 90 days and returns the operator's time for the next engagement.
Second, the retainer's probability of renewal is lower than the probability of a completed sprint generating a follow-on engagement. A retainer that ends in cancellation produces zero incremental revenue. A sprint that ends in completion often produces a follow-on sprint at similar pricing, plus a referral pipeline that retainers don't generate.
When you model revenue over 18 months rather than 6, the math flips. The operator running sprints generates more revenue because the sprints compound into follow-ons and referrals, while the retainer either renews (rarely) or ends (usually, with no downstream value).
The trap inside the trap: "permanent retainer" as a model
Some fractional practices lean into the retainer as their core model. Everything is a monthly retainer. The idea is that predictable recurring revenue is more valuable than transactional revenue.
The theory holds for products that retain predictably (software subscriptions, insurance). It breaks for service retainers where the perceived value erodes every month. A SaaS product gets more valuable the longer the customer uses it. A fractional retainer gets less valuable the longer the engagement runs, because the initial problem got solved (or abandoned) and subsequent value is harder to articulate.
The operator running permanent retainers spends increasing energy each month convincing each buyer that the retainer is still worth paying for. That's sales work masquerading as delivery. The practice's effective margin collapses.
I've written elsewhere about why I stopped billing hourly and the math is similar. Hourly billing and retainer billing both optimize against the wrong axis. Hourly billing rewards more hours. Retainer billing rewards more months. Neither rewards better outcomes.
“Retainers optimize for more months. Productized offers optimize for better outcomes. The axis the buyer actually cares about is the second one.
”
The escape plan I'm running
I still run a few retainers. They're time-boxed. Every retainer I currently hold has a public sunset date of 2026-12-31. After that date, new retainer work stops and the productized ladder is the only front door.
The sunset date is a forcing function. Without it, the easy money of retainers would quietly absorb the practice's capacity while the productized ladder stayed under-built. The sunset date puts the productized work on a clock. By the end of 2026, every revenue stream has to route through a productized offer or a sprint, not a retainer.
The logic is stark. Retainers pay faster in the short term. Productized offers compound in the long term. A practice that doesn't set a forcing function drifts toward fast money because fast money is less cognitive load. The sunset date removes the drift.
During the sunset window (now through end of 2026), the remaining retainers are being explicitly transitioned. Most will become sprints (a defined deliverable replaces the open-ended cadence). Some will become advisory-only at a reduced cadence. A few will simply end because the engagement has run its course.
How to structure the transition for your own practice
If you're running a retainer-heavy practice and want to transition toward productized, the escape plan has four steps.
Step 1: put an end date on every retainer
Existing retainers need a termination point. Six months from today is usually enough runway to transition both sides. The conversation is: "I'm restructuring the practice toward productized engagements. This retainer will run until [date], at which point we'll either convert to a defined scope sprint or close out." Most clients understand.
Step 2: identify the sprint patterns emerging from current retainer work
Retainer work usually contains 2-3 recurring patterns that could become sprints. Review the last six months of retainer deliverables and look for the repeatable shapes. Those are your first productized candidates. The productization walkthrough covers the process in detail.
Step 3: price the productized offers higher than the retainer equivalent
The productized version of work should cost more than the retainer equivalent, not less. The premium reflects the certainty the buyer is paying for (scope, price, timeline). Most operators undervalue this and price productized at the retainer rate, which cannibalizes margin.
Step 4: decline new retainer inquiries past a specific date
Publish the sunset date on the availability page or equivalent. The public commitment forces the discipline. Without it, a well-paid retainer inquiry is too tempting to turn down when cash flow is tight.
What works better than retainers for recurring revenue
The argument for retainers is usually "recurring revenue stabilizes the practice." The argument is real. The solution, though, isn't retainers. It's recurring revenue from productized subscriptions or memberships, which retain on their merits because the product itself keeps delivering value.
An audit SKU that a buyer runs quarterly is recurring revenue without the retainer failure modes. A membership with monthly deliverables is recurring revenue. A productized advisory subscription with defined quarterly outputs is recurring revenue. All three produce the predictability retainers promise without the scope-elasticity and attention-drift problems.
The product suite at the top of this site includes these shapes. The operator's stack, the course, and the audit products all have recurring or renewing revenue structures that don't rely on retainer mechanics.
The buyer's view
Buyers who experience both retainer and productized engagements almost always prefer productized after the fact. The productized engagement is cleaner, more satisfying, easier to justify to their board, easier to explain to new hires. The retainer was easier to sign but harder to defend internally.
The buyer who insists on a retainer is usually doing so because they don't yet know what they want. That's a valid state, but the right product for that buyer is the audit-to-implementation bridge, not a retainer. The audit helps them define the problem; the implementation sprint solves it; no retainer required.
Frequently asked questions
Don't some work types genuinely need ongoing presence?
A few do. Truly novel work where the scope cannot be defined until discovery happens is one category. Crisis coverage during a specific event (an acquisition, a leadership transition) is another. For those, scope the engagement as time-boxed and named. "Six-month interim head of growth during the CEO transition" is a retainer, but it has a defined end condition. That's different from an open-ended monthly retainer with no termination logic.
What about implementation partners that bill monthly for multi-year platform engagements?
Those are usually projects, not retainers, even if the invoice cadence is monthly. A project has a defined deliverable and completion point. The monthly invoicing is about payment rhythm, not about engagement structure. As long as the engagement is scoped to a project, the structural problems I described don't apply.
Is there a minimum practice size where retainers start working?
Retainers work better at agency scale because the agency has headcount to absorb scope variance and a portfolio of retainers where the variance averages out. A solo practice has neither. For agencies of 10+ people, retainers can be a viable core product. For solo operators, they're usually a trap.
What if a client insists on a retainer and I don't want to decline?
Scope the retainer with defined monthly deliverables. "Monthly retainer of $X for these three specific outputs each month" converts the engagement into a recurring sprint. The scope elasticity problem is bounded. Attention drift can still happen but is easier to catch because the deliverable is explicit.
How do I have the sunset conversation with a long-term retainer client without damaging the relationship?
Start with the business reason. "I'm restructuring toward productized engagements because it produces better outcomes for buyers." Offer a transition path to a sprint or a reduced-advisory retainer. Give enough runway (6 months is usually right). Most clients appreciate the directness. The ones who don't are usually the ones for whom the retainer had already decayed and the conversation you're having is overdue.
Sources and specifics
- The 2026-12-31 sunset date is a public commitment, visible on the availability page.
- The three failure modes (scope elasticity, attention drift, quiet cancellation) are drawn from retainers I've run across the last four years.
- The escape plan's four steps are the ones I'm actively running in my own practice during the sunset window.
- The productized alternatives are live in the product suite, including the Operator's Stack mid-tier and the top-tier Operating System.
- The productization walkthrough covers the mechanical process of converting retainer patterns into sprint SKUs.