Retainer vs. Project Billing: When to Use Each

Retainers and project fees are often treated as interchangeable billing structures. They aren't.

They solve different problems, create different incentives, and reward different kinds of firm behavior. Using the wrong structure for the wrong engagement is one of the most common sources of unnecessary margin loss at services firms.

This piece is our framework for when to use each, the mistakes that cost firms money, and how to run hybrid engagements that combine both.

What each structure is for

Retainers

Retainers work when the client needs ongoing capacity for work that can't be fully scoped in advance. Fractional CFO services. Ongoing design support. Monthly marketing operations. IT managed services — see our retainer profitability playbook for MSPs for the IT-services angle. The work is variable but consistent.

The retainer gives the client predictable cost and guaranteed capacity. It gives the firm predictable revenue and the freedom to flex staffing within the engagement.

Project fees

Project billing works when the deliverable is bounded. A 10-week strategy engagement. A system implementation. A specific research report. The scope is defined, the deliverable is clear, and both parties want cost certainty for that specific thing.

Project billing creates accountability for outcomes, not hours. That's both its strength and its risk.

The biggest retainer mistake

The single most common and most expensive retainer mistake: treating unused hours as the client's property.

Client signs a 40-hour-per-month retainer. In February, they use 28 hours. The firm reflexively offers: “We'll carry the 12 hours into March.”

This is a gift. The retainer exists to pay for capacity, not hours. The client wasn't buying 40 hours; they were buying ready-to-go capacity for 40 hours' worth of work they might or might not use. If they didn't use it, the firm held the capacity anyway. That's what they paid for.

Carrying hours forward converts the engagement from a capacity deal to an hours deal, silently, at the firm's expense. And once carryover starts, it's hard to stop — clients come to expect it.

Retainers should have an explicit “use-it-or-lose-it” clause, communicated up front. The firm is selling availability, not hours.

The biggest project mistake

On project engagements, the mirror-image mistake: accepting scope expansion without a change order.

The project was scoped for 10 weeks. In week 6, the client asks for an additional module. The project lead, wanting to keep the relationship warm, agrees without renegotiating.

This is the scope creep pattern documented in our playbook, and it's specifically fatal on fixed-fee projects because the firm is now delivering more work for the same revenue.

Every project change should generate a change order. Not because the firm is being rigid — because the client needs to see the tradeoffs clearly. Silent scope expansion helps nobody.

Utilization looks different for each

A subtle point that trips up a lot of firms: utilization math works differently for retainer vs. project work.

• Retainer utilization should be measured as retainer hours consumed vs. retainer hours sold. A retainer running at 80% consumption is healthy.
• Project utilization should be measured as project hours delivered vs. project hours budgeted. A project running at 110% is in trouble.

When firms roll both into a single “utilization” number, they lose the ability to see which engagement type is driving which outcome.

See our utilization piece for why slicing the number properly is the entire game.

When to use which

Five questions that usually answer it:

1. Is the work bounded? Yes → project. No → retainer.
2. Does the client want cost certainty? Yes → project or fixed retainer. No → T&M.
3. Is capacity the product? Yes → retainer. No → project.
4. Will scope change significantly? Yes → retainer or T&M. No → project.
5. Is the engagement recurring or one-time? Recurring → retainer. One-time → project.

The most common mistake firms make is defaulting to whichever structure the salesperson is most comfortable pricing, not the structure that fits the engagement.

Hybrid engagements

Some engagements combine both: a base retainer plus project fees for bounded deliverables. These work well when the firm is disciplined about separating the accounting.

A clean hybrid looks like:

• Monthly retainer for ongoing support, capacity, and advisory.
• Separate project fees for each discrete deliverable.
• Time tracked separately against each, with clear boundaries.
• Utilization and margin reported for each independently.

A messy hybrid looks like: retainer hours mysteriously covering project work, or project fees absorbing retainer-level advisory time. In either direction, the firm loses margin because the accounting is unclear.

The rule: every hour logged to a hybrid engagement should be unambiguously tagged to retainer or project. If you can't tell after the fact, that's a tracking failure with direct financial consequences.

The real point

The structure you use changes the incentives for every person on the engagement. Retainers reward the firm for efficiency and the client for consumption. Projects reward the firm for predictability and the client for defined outcomes.

Pick the structure that aligns with the engagement, enforce it cleanly in your billing and tracking systems, and don't let the default settings of your practice dictate a one-size-fits-all approach.

Both structures are powerful when used well. Both are expensive when misused.

Octayne's Billing & Invoicing handles retainer, project, and hybrid billing natively, with separate utilization and margin tracking for each. Book a demo to see both models live on your data.