The retainer trap

Here is how the retainer pitch usually goes: a company needs ongoing technical help. You're good at what you do. They want you available. You want predictable income. A monthly fee for X hours sounds fair to both sides. You sign.

The first month or two is fine. The work is real. The problems are new. You're solving things that matter to them.

Then it shifts.

What changes after month three

You've solved the interesting problems. What's left is either maintenance work that someone internal could do, questions that belong in a Slack thread with the engineering team, or decisions that don't actually require your expertise but feel safer with an outside opinion attached.

You're still billing. They're still paying. Neither side wants to say the obvious thing, which is that the value in the arrangement peaked two months ago.

This is not a bad-faith situation. Nobody is trying to extract money for nothing. The incentive structure just produces this outcome naturally. A retainer creates a relationship that both parties want to preserve. Preserving the relationship means staying relevant. Staying relevant means not solving the problem so completely that you're no longer needed.

You stop optimizing for the outcome and start optimizing for the continuation. The advice gets a little softer. The recommendations stay a little more open-ended. You stop saying "here's the answer" and start saying "here are three things to consider" — because a definitive answer ends the engagement and an open question keeps it going.

You may not do this consciously. The incentive is subtle. But it's there.

The calendar problem

Now imagine you've taken five retainers.

Your calendar is no longer yours. Five companies have claims on your time, each month, regardless of what they need that month. One of them has a quiet month — their engineering team is executing well, nothing is on fire. You still need to produce something to justify the invoice. So you produce something. It may or may not be what they actually need right now.

Another company has a crisis. But it's not crisis you're good at — it's an organizational problem, a hiring decision, a product question. Your retainer makes you feel like the right person to help anyway, because the relationship exists and the clock is running.

The five companies' needs don't align with the shape of your capabilities in any given month. A retainer is a fixed obligation; real problems arrive unevenly. The mismatch is structural.

At five retainers you're managing five relationships, five monthly deliverables, five invoices, five renewal conversations. The actual work — the thing you're good at — is now a fraction of your time. The rest is relationship overhead.

When retainers make sense

There are situations where recurring availability is the actual product. Security on-call is the clearest example: a company genuinely needs someone reachable at 2am if the system is compromised. The value is not the work performed per hour; it's the availability guarantee. A retainer is the right instrument for that.

The same logic applies to regulatory compliance roles, certain legal contexts, and infrastructure support for systems where downtime is expensive. The common thread: the client is buying readiness, not just output.

Most "fractional CTO" and "technical advisor" arrangements don't fit this description. What they're actually buying is periodic input from someone with a specific background. That input does not require ongoing availability; it requires good judgment applied on a schedule. And good judgment applied on a schedule is a project, not a retainer.

If the actual deliverable is "advice when asked," the retainer is adding a recurring invoice to something that could be a flat-fee engagement or a pay-per-session arrangement.

The alternative

A lump-sum transaction is honest in a way a retainer isn't.

You pay for a specific thing. I deliver the specific thing. The transaction ends. If the thing was useful, you come back for another specific thing. If it wasn't, you don't.

There's no incentive to make the problem seem more complex than it is. There's no incentive to leave open questions that bring you back next month. The deliverable is real and final.

This is how the products here work. The Playbook is $29. You read it; it either unblocks you or it doesn't. The Power Pack is $129. The templates either fit your problem or they don't. A time block is $500 or $2,500 depending on scope. We work for that number of hours. We produce a specific outcome. The engagement ends.

If you need another time block six months from now, you book one. I'm not sitting on your payroll in the meantime.

What this means for you

If you're evaluating technical help right now, the question to ask is: are you buying readiness or output?

If you need someone on call for a live production system, a retainer structure may be appropriate. Be explicit about what "on call" means — response time, scope, what constitutes a callout.

If you need a specific piece of work done, or a specific set of knowledge transferred, the retainer is the wrong instrument. It will cost more over time and produce softer outcomes because the incentives point away from finality.

I don't sell access. I sell outcomes. If you want me, you can buy a discrete block of my time, scoped to a real problem with a defined deliverable. When the block ends, you have the output and I'm off the clock.

That's the whole model. No subscription, no monthly check-in call, no invoice that arrives whether or not the month was productive.

Book a time block if you have a specific problem. The scope conversation happens before you pay anything.