Consulting Retainers and Project Fees: A Billing Guide

Consulting income has a feast and famine reputation it doesn't have to keep. The difference between a consultant who sweats every month and one who doesn't is rarely the hourly rate; it's the billing structure. Retainers smooth revenue into something you can plan a life around, and well-structured project fees stop big engagements from becoming interest-free loans to your clients. Most healthy consulting practices end up running both at once.

Two Models, Two Kinds of Predictability

A retainer sells ongoing access: a monthly fee for a defined slice of your capacity, whether that's a set number of hours, a set of responsibilities, or priority availability. A project fee sells an outcome with edges: an audit, a strategy, an implementation, priced as a whole. Retainers give you predictable revenue; project fees give the client a predictable cost. New consultants usually start with projects, because they're easier to sell to a client who hasn't worked with you. The retainer conversation gets easy later, at the moment a project ends and the client asks what happens now. That's the door. Walk through it with a number.

Retainers: Bill in Advance, Always

The retainer invoice goes out before the month it covers, not after. On the 25th for the month ahead, or the 1st, due on receipt or net 7. This isn't greed, it's the definition of the arrangement: the client is reserving capacity, and reservations are paid up front, the way rent is. Billing in arrears quietly converts your retainer into ordinary hourly billing with extra steps and 45 days of float. Three more terms worth locking in writing: a minimum commitment of three months so the relationship survives its first lull, 30 days notice to cancel or resize, and an annual rate review date. Then send the same clean invoice every month from a consultant invoice template, same format, same lines, so approval becomes a habit on their side rather than a decision.

What Happens to Unused Hours

Every hours-based retainer eventually meets the quiet month, and the client asks whether unused hours roll over. Decide before they ask. Use it or lose it is the standard and the right default, because the retainer buys reserved capacity, not banked labor; you turned other work away whether they called or not. If that feels harsh for a client you like, allow a partial rollover with an expiry, say up to 25% of hours rolling into the next month only. What kills consultants is the unlimited bank: eighteen months in, a client shows up expecting a free week of work from hours that expired in your head but not in the contract. A gentler companion policy: send a short monthly usage summary with the invoice, so nobody is surprised in the first place.

Project Fees: Milestones Beat Halves

For fixed fee projects, the lazy default is half up front, half at the end, and on a six week project that's fine. On anything longer, the back half becomes a balloon payment that arrives just as the client's attention has moved on, and it makes your final weeks strangely tense. Milestones fix this: a third at kickoff, a third at the midpoint deliverable, a third at final delivery. Each payment ties to something the client can see, and no single invoice is big enough to be scary. Anchor milestones to deliverables rather than dates, so a client-side delay pauses the work instead of your revenue. And keep scope edges sharp: workshops, extra stakeholder interviews, and revised final reports beyond round one are add-ons with prices, not favors. The full pattern is in deposit invoices and progress billing.

Reading Which Model the Engagement Wants

Some engagements tell you what they are. Defined outcome, defined end: project fee. Ongoing advice, recurring need, no natural finish line: retainer. The dangerous ones are projects that refuse to end, drifting month to month on ad hoc invoices; that drift is your cue to propose a retainer, which the client usually welcomes because their budget wants predictability as much as yours does. The reverse read matters too: a retainer client who suddenly needs a big defined chunk of work, like a hiring push or a system rollout, should get that scoped as a separate project fee on top, not silently absorbed into the retainer until you resent it.