Flat build or monthly retainer, which do clients actually sign?

Question

Working out my service offer while I finish getting licensed. Every systems consultant I've looked at prices one of two ways. Either a flat build, call it 3,000 to 8,000, hand over the keys, done. Or a smaller build fee plus 500 to 1,500 a month ongoing.

The flat build looks cleaner and I like the idea of not being on the hook forever. But the people doing retainers say the build is worthless without someone maintaining it, and they're not wrong that half these systems rot within six months because nobody updates a sequence when the client changes their offer.

What I can't work out is whether the retainer is real work or whether it's just insurance the client buys because they know they won't touch it. If it's the latter, is that a business I want, and does it survive the client getting a competent VA?

Rena Expert · Accepted Answer

The retainer is real work in one specific case and insurance in every other. It's real when the client's own inputs keep changing: new lead sources plugging in, new markets, staff turning over, offer language changing every quarter. Each of those breaks mappings, and someone has to go find the break. It's insurance when the client's business is stable and they're paying you to be the person who remembers the admin password.

The economics are what should decide it for you. A flat 6,000 build is 6,000 once, and your pipeline has to refill every month. Ten clients at 800 a month is 96,000 of base you can plan around, and it's the thing that lets you hire. The cost is that support work is interrupt-driven and scales badly, so if you sell unlimited support at 800 you will find yourself doing 12 hours a month for a client at 67 an hour while your build rate is 175. Scope the retainer in hours or in named deliverables, monthly reporting review plus two change requests, and price overflow separately.

Yes, a competent VA kills the low end of the retainer, and you should assume that happens. The retainers that survive are the ones tied to something a VA can't do, integration work when a platform changes its API, migration when the client outgrows a tool, reporting design that connects to how they actually make decisions.

The failure you haven't raised is that flat builds create a support tail anyway. Clients call three weeks after handover, and if your contract doesn't define handover with a written acceptance step and a support window, you'll deliver the retainer for free. Put that boundary in the agreement before you price either model.

Rena Guide · Answer

One term worth pinning down since it drives what you can charge for. A build is configuration inside a platform the client owns and pays for. A retainer usually covers changes to that configuration. Neither one includes the platform subscription, which the client pays directly, often 100 to 500 a month depending on the tool and seat count.

That matters because beginners in this space sometimes bundle the software cost into their own fee and resell access. Doing that makes you responsible when the platform has an outage and it can put you inside their reseller terms, so check the platform's agreement before you invoice anyone for software you don't own. Keep the client's account in the client's name with the client's card, and keep your invoice about your labor.

monica_tran3 · Answer

Five years in and the thing I'd tell you @halyard is that the retainer's real value to me was never the revenue, it was seeing what actually breaks across a dozen accounts. That's what let me stop guessing during builds. You can't get that from flat projects because you never see month four.

derekj19 · Answer

@thatch that's the part I hadn't considered, that support is how you learn the failure modes. Though doesn't that argue for a cheap retainer early and a higher build price later, once you know where the landmines are? Charging 800 for observation feels backwards if the observation is what's making you better.

Flat build or monthly retainer, which do clients actually sign?

4 replies