Retainer vs project pricing for agencies: which, when, and how to switch

TL;DR

Project pricing (fixed scope, fixed fee, defined end) is the right model for one-off deliverables, new relationships you haven't de-risked, and work with a genuine finish line. Retainer pricing (recurring monthly fee for ongoing scope or a capacity commitment) is what turns an agency from a series of transactions into a business with predictable revenue. Most agencies should run both — projects as the front door and the de-risking step, retainers as the destination — and the skill that compounds is converting proven project clients into retainers. The trap is staying all-project (you re-sell your whole revenue every month) or pushing a retainer before you've earned the trust (it churns in 90 days). Below: the trade-offs, the fit test, and the switch script.

---

Every agency owner eventually feels the difference in their gut: the month a big project wraps and the pipeline behind it is thin, versus the month a book of retainers renews itself while you sleep. Project work pays the bills; retainers build the business. But "just move everyone to retainers" is bad advice — the model has to match the work and the relationship, or you trade lumpy revenue for fast churn. Here's how to actually think about it.

The honest trade-offs

	Project	Retainer
Revenue	Lumpy — you re-sell every month	Predictable — MRR you can forecast
Cash flow	Front/back-loaded, gaps between	Smooth, recurring
Client commitment	Low — easy to start, easy to leave	Higher — both sides invest
Scope risk	Scope creep eats the margin	Scope drift eats the margin (different failure)
Sales load	High — always refilling the pipeline	Lower — renewals, not new sales
Best for	Defined deliverables, new/unproven clients	Ongoing work, proven relationships

Notice the margin killer is different, not absent: projects die by scope creep (the fixed fee, blown by "one more revision"); retainers die by scope drift (the fee holds while the asks quietly grow until you're servicing at a loss). Both are solved the same way — explicit scope and the discipline to enforce it — but you have to know which one you're fighting.

Which clients fit which

A client belongs on a project when:

• The work has a real finish line (a site build, a migration, an audit, a launch).
• You haven't worked together before — the project is the trust-building, de-risking step.
• The budget is one-time, not recurring (a grant, a launch budget, a one-off initiative).

A client belongs on a retainer when:

• The work is genuinely ongoing (SEO, paid media management, content, reporting) — there's no "done."
• You've proven value already (usually via a project) and both sides want continuity.
• The client's success depends on consistency — the thing that breaks when you stop is exactly what a retainer protects.

The single best retainer candidate is a happy project client whose results will decay without ongoing work — they've felt the value and they can feel what losing it would cost.

The switch: project → retainer

Most retainers are converted, not sold cold. The move, in order:

1. Time it to the win. Pitch the retainer when the project just delivered a result the client can see — not at a random renewal date. Momentum is the whole leverage.
2. Frame it as protecting the result, not buying more. "Here's what we built; here's what keeps it working / compounding. Without ongoing [X], here's what decays." You're selling continuity of a proven outcome.
3. Scope it tightly and name it. A retainer with vague scope is a future resentment. Define what's included, what's not, and the monthly capacity — write it down. (This is also what makes raising the rate later clean.)
4. Offer a clear commercial. A modest monthly that's obviously worth it beats a big number they have to agonize over. Land them on the recurring relationship first; expand once it's proven (again).
5. Set the renewal cadence on day one. Monthly/quarterly/annual term, a renewal date, and your own reminder to have the value conversation before it — not after they've started questioning the invoice.

The portfolio view

The goal isn't 100% retainer — it's a healthy mix: enough retainer MRR that your baseline is covered and predictable, enough project work to bring in new logos and de-risk them before you offer continuity. A useful gut check: if your retainer MRR covers your fixed costs (salaries, tools, rent), every project dollar is genuinely growth rather than survival. That ratio — not "retainer good, project bad" — is the number to manage, and it's why you want retainer value, cycle, and renewal date tracked on the client record instead of living in a spreadsheet or someone's head.

Where this fits

The model is only as good as your ability to see it: which clients are on retainer vs project, what each is worth, when each renews, and whether the mix is drifting toward all-project (survival treadmill) or healthy. That's exactly what Phloz puts on the client record — retainer value, billing cycle, renewal date, and an MRR rollup across the book, with a heads-up before each renewal so the value conversation happens on time. The CRM for agencies and pricing pages cover the workflow; the decision above is yours — but make it per client, deliberately, and convert your proven project clients before they drift away.