Business Models
Retainers vs Projects: Which Revenue Model Fits Your Business
Retainers smooth cash flow and cap upside. Projects pay more per engagement and leave you selling every month. Here's how to tell which one your work actually supports.
Two ways to structure the same expertise, and they produce very different businesses.
The choice isn't a preference. It follows from what your clients actually need — and picking the model your work doesn't support is how people end up with retainers they resent or projects they can't plan around.
The comparison
| | Project | Retainer | |---|---|---| | Revenue shape | Lumpy | Predictable | | Sales effort | Every engagement | Once, then renewals | | Cash flow | Feast and famine | Smooth | | Per-engagement value | Higher | Lower monthly, higher lifetime | | Capacity planning | Difficult | Straightforward | | Client relationship | Transactional | Embedded | | Main risk | Empty pipeline | Concentration and churn | | Scope discipline | Critical | Critical, and harder |
When projects are the right shape
The need has a beginning and an end. A migration, a rebrand, an audit, a build. When it's done, it's done — and dressing that up as an ongoing relationship is transparent.
The client doesn't have continuous need. Some clients genuinely need you twice a year. A retainer would be them paying for eleven months of nothing, and they'll work that out.
You're new to the client. Retainers ask for trust that hasn't been earned yet. A well-executed project is how you earn it.
The work is high-value and infrequent. Specialist engagements that command a large fee and recur rarely fit projects naturally.
The economics. Projects usually pay more per engagement — but compare effective rates, not headline ones. A $20,000 project that took 30 hours of selling isn't a $20,000 project; it's a $20,000 project with 30 unbillable hours attached. Amortize the sales cost before you conclude projects pay better.
When retainers are the right shape
The need is genuinely continuous. Monthly reporting, ongoing optimization, managed operations, always-on advisory.
The work is steady enough to plan around. If the workload swings from 5 hours one month to 45 the next, a flat fee will feel wrong to one of you every single month.
You want capacity predictability. Knowing three months out roughly what your delivery load looks like is the single biggest operational advantage of the model.
The relationship compounds. Some work gets materially better with accumulated context. Where that's true, the retainer isn't just a billing structure — it's the reason the work is good.
What kills retainers
Almost always the same thing: the client can't articulate what they got last month.
Retainers die quietly. Nobody complains. Then a budget review happens, someone asks what that recurring line item is for, and nobody in the room can answer confidently.
Three defenses:
Report monthly, unprompted. A short summary: what was done, what it produced, what's next. This is not admin — it's the mechanism by which the fee stays justified.
Bill for outcomes, not availability. "Access to our team" is not a value proposition; it's an invoice waiting to be questioned. Name what gets delivered.
Review the scope quarterly. Retainers drift. What you agreed twelve months ago rarely matches what you're doing now, and the drift is almost always in the client's favor.
What kills project businesses
The gap between projects. You deliver, you're busy, you don't sell. The project ends and the pipeline is empty. Two months later the cash flow shows it.
The fix is unglamorous and non-negotiable: sell while delivering. Protect a fixed block of selling time every week regardless of how busy delivery is. The weeks it feels least possible are the weeks it matters most.
Scope creep. Fixed price plus vague scope equals an unpaid overrun. Every project needs written deliverables, explicit exclusions, a revision count, named client dependencies, and a change-order rate. This is the same discipline that makes productized services work.
The hybrid most businesses land on
Very few stay purely one or the other. The common structure:
Project (entry) → Retainer (ongoing) → Project (expansions)
The project proves you can deliver and establishes the value that makes an ongoing fee defensible. The retainer smooths cash flow and deepens the relationship. Larger discrete pieces get quoted as projects on top.
This works because it matches how trust actually develops. Asking a stranger for a twelve-month commitment is a big ask; asking a client you've just delivered for is not.
A reasonable target: enough retainer revenue to cover fixed costs, with projects providing the upside. That combination means a slow month is survivable rather than an emergency.
Concentration is the risk nobody prices
Retainers create a specific danger: a small number of clients funding most of your business.
If one client is a large share of monthly revenue, you don't have a retainer — you have an employer who doesn't provide benefits, and who can end the arrangement with 30 days' notice.
Watch the concentration number as deliberately as you watch revenue. It should be one of the metrics in your weekly review once retainers are a meaningful share of income.
Choosing
Answer three questions about your actual client base, not your ideal one:
- Does the need recur monthly? No → projects.
- Is the workload steady enough to price flat? No → projects, or a capped retainer.
- Can you describe monthly value in one sentence a client would repeat to their boss? No → projects, until you can.
Three yeses means retainers will work. Any no means projects are the honest structure for now — and there's nothing wrong with that. Plenty of durable businesses never run a retainer.
What to do next
Look at your last twelve months of revenue by client. Mark which engagements had genuine continuous need versus which were discrete pieces you'd have preferred to make recurring. That split — real need versus your preference — tells you which model your business actually supports today.
Frequently asked questions
- What's a reasonable retainer length to ask for?
- Three months is the usual floor, because it takes that long for most work to show results and for the client to form a judgment. Twelve-month commitments are worth a discount if you can get them, but a long lock-in with a client who wants out produces bad delivery and a worse reference. Prefer a rolling term with 30 days' notice over a contract nobody wants to be in.
- How do I stop a retainer turning into unlimited work?
- Cap it explicitly — hours, deliverables, or scope of responsibility — and state what happens beyond the cap. An uncapped retainer is a fixed price with unlimited effort, which is the worst structure in this article. Track actual hours from month one even if you never show the client, because that data is your renegotiation evidence.
- Should I discount a retainer versus my project rate?
- A modest discount is normal and defensible — you're getting predictable revenue and lower selling costs in exchange. A deep discount is usually a sign the retainer isn't really wanted and you're buying the commitment. If you have to discount heavily to get the retainer, the client probably has project-shaped needs.
The Newsletter
WealthLink Weekly
Business. Money. Marketing. Real Estate. Technology. One email.
One email a week. Unsubscribe anytime.