MADEBYZLATA← All posts
2026-11-20 · small-businesspricingprocess

Why I don't sell retainers

A retainer is the easiest money in this business and I still won't take it. If nothing needs maintaining, I'd rather the thing be finished.

Monthly recurring revenue is the shape everyone in this business is told to want. A number that arrives whether or not you did anything that month. Predictable, bankable, and easy to sell because it sounds like insurance.

I don't sell retainers. Not because I'm above them, but because the version most small businesses get offered is not maintenance. It's a subscription to my attention.

Two kinds of retainer, only one of them is honest

There is a real retainer. It covers work that genuinely runs every day and will break without someone watching it: a server that needs patching, an integration that syncs money, a phone system that has to answer at seven in the morning. Something is alive, it has a pulse, and if it stops there is a cost within the hour. Charging monthly for that is fair, because the obligation is real every day.

Then there is the other kind. The work is finished. Nothing is alive. And the retainer exists to keep the door open so the client can call me when they think of the next thing.

That second one is the one I get asked for, and it's the one I decline.

The test I use

It's one question.

If nobody touched this for a month, would anything break?

If the answer is no, then what I'm being asked to sell is availability. Availability is a real thing, but it isn't maintenance, and it shouldn't be priced like a utility bill. A utility bill implies something is being delivered continuously. Nothing is. I'm just being paid not to be busy elsewhere.

Answered honestly, most of the things I build fail that test on day one. A script that turns a stack of supplier PDFs into a quote sheet is finished when it's finished. It doesn't need a monthly visit. It needs to be correct on the day I hand it over, and then it needs to run quietly until something upstream changes.

What's wrong with being paid anyway

The obvious answer is nothing — the client offered.

The less obvious answer is that it changes what I want. If a monthly cheque depends on the problem staying slightly unfixed, then every small improvement gets a second thought. Not a conscious one. That's the dangerous kind. You start leaving the manual step in because it's the thing you'd be called about. You stop writing the paragraph of documentation that would let someone else do it.

I know how that ends because I've been on the paying side of it. At the cabinet shop, six of us and me at twenty-two, we had suppliers we paid for access rather than output. Nothing was ever wrong enough to cancel, and nothing was ever fixed enough to stop paying. It was the least examined line on the expenses sheet, and it went on for years.

The two-person shop version

The businesses I most want to work with are the ones with nobody whose job is process. The owner writes quotes at nine at night, answers the phone at seven, does the books on Sunday.

For that person, a retainer is not a convenience. It's another bill that arrives with nothing attached to it, on a month when the work was already done. And it quietly turns a one-off fix into a permanent cost of doing business, which is the opposite of what they hired me for.

There's also a subtler cost. A retainer makes the shop feel like the problem is being handled, when what actually happened is the problem got rented instead of solved. The manual step is still there. Nobody has written it down. The one person who knows how the thing works is still the only person who knows.

What I sell instead

A fixed piece of work with a defined end.

We write the job down as it happens for a week — every step, including the stupid ones. Then we decide what to remove, what to simplify, and what to build. Usually one thing gets built. Sometimes three steps disappear and nothing gets built at all, and that's a good outcome, not a refund.

Then I hand it over. That means the files, a short written page on how it works, what it assumes, and what to do when it breaks. If the shop wants to change it later without me, they can. That is the point.

I do come back. I charge for the visit when it happens, at the rate it's worth that week. A support visit priced honestly is usually cheaper over a year than twelve months of a retainer nobody thought about.

Where I might be wrong

If a thing I build needs daily care, I'll say so before I build it, and then a retainer is the correct shape. I'm not pretending every project can be handed off clean and forgotten.

But that should be a finding, not a default. The default in this trade is to attach a monthly fee to anything that has been delivered once, and call it support.

Recurring revenue is a business model. That's fine. It's just not the same thing as service, and the two get mixed up constantly in a way that costs small businesses real money.

So: no retainer for a thing that is finished. If I can't explain what the monthly fee buys, in one sentence, with a list of what would break without it, then there shouldn't be a monthly fee.

That's a harder business to run. It's also the only one where I can tell someone their job is done and mean it.