Retainer vs. Project: The Economics That Determine Which Model Wins for Your Agency

A founder I talked to last year was running a $3.4M development agency entirely on projects. New client every quarter, solid delivery, good referrals. On paper, the business looked healthy.

Then I asked him to pull his revenue by month for the previous two years and lay it out on a spreadsheet.

The line looked like a seismograph during an earthquake. Peaks in Q1 and Q3. Valleys in Q2 and Q4. His highest month was $480K. His lowest was $61K. Same team. Same expenses. Wildly different revenue.

He'd been running a business that was perpetually one slow quarter away from a crisis. He just hadn't seen it framed that way before.

The retainer vs. project question isn't a philosophical one about what's better for clients. It's a financial architecture question. And the answer has very different implications depending on where you are in your growth trajectory.

What the Economics Actually Look Like

Most founders talk about retainers like they're obviously better. Recurring revenue, predictable cash flow, deeper client relationships. All true. But the math is more nuanced than the talking points suggest.

Projects generate higher revenue concentration. A well-priced project at $150,000 funds three months of operations in one engagement. The margin on a focused, scoped project, where your team knows exactly what they're building, often runs 40–55%. You're not leaving efficiency on the table managing an ongoing relationship.

Retainers generate lower per-month revenue but higher lifetime client value. A $12,000/month retainer at 35% margin doesn't look as impressive as a $150K project. But if that retainer renews for 24 months, you've generated $288K in revenue with a fraction of the sales effort. The customer acquisition cost amortizes over years instead of quarters.

The break-even point, where retainer lifetime value exceeds project-by-project revenue, typically hits around month 14 of an ongoing engagement. Before that, project economics often win. After that, retainer economics compound.

📊 Chart: Retainer vs. Project Revenue Trajectory — Single project ($150K, one-time) vs. retainer ($12K/month, 24 months) plotted over 24 months. Show cumulative revenue and margin.

SVG source: Chief of Stuff/skills/charts-retainer-vs-project.svg

Caption: The project wins month one. The retainer wins month fourteen and every month after.

The Hidden Costs Each Model Carries

Neither model is free. The costs just fall in different places.

Project-based agencies carry high sales overhead. Every new engagement requires a new discovery process, a new proposal, a new negotiation. If your average sales cycle is six weeks and your close rate is 30%, you're spending roughly 20 weeks of effort for every project you land. At founder-level opportunity cost, that's expensive.

They also carry utilization risk. Between projects, team members sit idle or get pulled into low-margin gap-fill work. Founders I work with at pure project shops typically see 15–25% of their total capacity under-utilized in any given quarter. That's paid overhead generating nothing.

Retainer-based agencies carry delivery overhead instead. Long-term clients develop expectations. Scope creep is the constant threat. A $10,000/month retainer that's functionally delivering $18,000 worth of work is a margin problem hiding inside a recurring revenue number. I've seen founders celebrate retainer growth while their margins quietly compressed to 15%.

Retainers also carry concentration risk. Three clients at $15K/month each represents 100% of your revenue. When one exits, and they always eventually exit, you've lost a third of your business overnight with no immediate replacement in the pipeline.

The Revenue Concentration Trap is what kills otherwise healthy retainer agencies. They optimize so hard for recurring revenue that they stop building new client acquisition muscle. Referrals dry up. The pipeline atrophies. One departure triggers a scramble.

Which Model Fits Which Stage

The right model depends heavily on where your agency sits in its growth arc.

Under $1M revenue: Projects almost always make more sense. You're still validating your positioning, building your portfolio, and proving delivery capability. Retainers at this stage often lock you into underpriced engagements with clients who signed before you understood your own value. Take the projects, learn what you do best, raise your rates.

$1M–$3M revenue: This is the transition zone. You've proven you can deliver. Now the question is whether you can build predictability. Start converting your best project clients into retainers, not all of them, but the ones where ongoing engagement is genuinely valuable. Target 30–40% recurring revenue in this band. Enough to stabilize cash flow. Not so much that you stop developing new relationships.

$3M–$8M revenue: Recurring revenue should be your primary architecture at this stage. New project work serves as a pipeline for retainer conversion, not as the core revenue model. Agencies that stay project-heavy above $3M tend to plateau, they can't scale team and sales simultaneously without the predictability that retainers provide.

The transition isn't linear. Most agencies oscillate, they'll push hard into retainers, lose a big one, then scramble back to project work. The founders who navigate it well treat the two models as a portfolio, not a binary choice.

The Conversion Playbook

The mistake most founders make is trying to sell retainers to clients who just hired them for a project. That conversation almost never works. The client is in project mindset. They're evaluating outputs. They haven't yet experienced the ongoing value you'd provide.

The agencies with the highest retainer conversion rates don't pitch retainers at all. They demonstrate ongoing value throughout the project and let the client ask for continuation.

This means two things practically.

First, surface ongoing opportunities during delivery. When you find something outside scope that would meaningfully improve the client's outcomes, note it explicitly: "This isn't in the current scope, but we're seeing a performance issue in the data layer that's going to cause problems at scale. We could address this in a Phase 2 engagement." You're not upselling. You're showing that your involvement produces insights the client wouldn't generate on their own.

Second, structure your projects with a natural Phase 2. A build engagement that ends with "here's what we'd focus on in the first 90 days of an ongoing relationship" is far easier to convert than one that ends with "let us know if you need anything else." The client should exit the project with a clear picture of what continued engagement looks like, not because you told them, but because they experienced it.

📊 Chart: Project-to-Retainer Conversion Funnel — Stages from project close to retainer conversion, showing where most agencies lose clients and what interventions change the outcome.

SVG source: Chief of Stuff/skills/charts-retainer-conversion.svg

Caption: Retainers aren't sold. They're earned during the project.

The Decision Framework

If you're trying to determine the right mix for your agency, start with three questions.

What does your team capacity look like between projects? If you're regularly carrying idle capacity, you need more recurring revenue to smooth utilization. If you're consistently at capacity, project economics are probably serving you fine.

What's your current client concentration? If your top three clients represent more than 60% of revenue, you have concentration risk regardless of whether they're on retainers or projects. Diversification matters more than model type at that point.

What's the nature of the value you deliver? If your best work happens at the beginning of an engagement, discovery, architecture, positioning, projects probably match your delivery model. If your value compounds over time through ongoing relationship and accumulated context, retainers are the right vehicle.

Most agencies need both. The founders who thrive aren't the ones who went all-in on one model. They're the ones who understood the economics of each and built a portfolio that reflects their actual delivery strengths.