Agency Retainer Pricing Models That Actually Hold Up

Most agencies do not lose money on retainers because their rates are too low. They lose money because the retainer was sold on a handshake, the scope lived in nobody's head, and three months later the client genuinely believes unlimited revisions were part of the deal.

I have watched a perfectly healthy 8,000-a-month retainer turn into a loss by month two, not because the price was wrong, but because nobody wrote down what "a video" actually included.

Picking the right pricing model is half the battle. Defending it with evidence is the other half. Here is how to do both.

The three retainer shapes worth knowing

There are really only a few retainer structures that survive contact with real clients. Most of the disasters are just one of these three, set up badly.

For video teams, deliverable-based is usually the safest because everyone can count the output. Four videos is four videos. Hours banks feel flexible, but they invite scope arguments unless you report usage every single week. "I thought we had hours left" is the most expensive sentence in this business.

Price for profit, not for comfort

Start from your fully-loaded cost per hour, not the rate you wish you charged. Then add everything the client never sees: the producer, the project manager, storage, software, and the senior review pass that makes the work actually good.

A retainer that only covers editor time will bleed you dry by month two. That is not pricing. That is volunteering.

Walk the math once and it stops being abstract. Say a four-video monthly retainer eats forty production hours. Your editor costs 40 an hour loaded, so that is 1,600 in pure edit time. Now add the producer and project manager at maybe twelve hours combined, the senior review pass at three, storage and software amortized across clients, and the account-management tax of status calls and scope chats. Suddenly your real cost is closer to 3,200, not 1,600. Price that retainer at 4,000 and you have a thin but real margin. Price it at 2,500 because a competitor did, and you are paying for the privilege of the work. The editor-only number is a trap because it is the only number that is easy to see.

The other number people forget is their own time selling and managing the account. Every retainer comes with a tax of status calls, scope conversations, and the slow drip of small requests that never quite make it into a brief. If you priced as if the work were pure production, that tax comes straight out of your margin. Bake an account-management line into the number, even a quiet one, because the relationship costs hours whether you charged for them or not.

Then build in a buffer of fifteen to twenty percent for the round of revisions you know is coming. If you never use it, the client thinks you are a hero. If you do, you are covered instead of cornered.

Write scope that survives a quarter

Vague scope is the most expensive thing in your contract. Spell out exactly what one deliverable includes: how many edits, how many rounds of feedback, what turnaround looks like, and the precise line where a request stops being a revision and becomes a brand-new project.

That boundary is everything. If you do not define when work moves out of the retainer and into a separate quote, the client will assume the answer is "never."

The clearer the boundary, the less you have to police it. A written scope is not bureaucracy. It is the thing that lets you say "that is a new project" without it feeling personal.

There is one more model decision that quietly decides your margin: how you handle the month the client underuses the retainer. If you let unused deliverables roll over, you have just turned a predictable retainer into an unpredictable liability that stacks up and lands on you all at once in month four. Write a clear use-it-or-lose-it rule, or cap the rollover hard. Clients push back on this exactly once, and they push back far less than they will when they have banked twelve videos and want them all next Tuesday. Protect the cadence and you protect the margin.

Where PlayPause fits

Retainers stay profitable when feedback stays contained, and feedback stays contained when it lives on the actual frame instead of in a rambling email thread.

This is the quiet part nobody connects to pricing. A vague note like "the middle feels off" triggers a guess, which triggers a wrong edit, which triggers four more rounds you never charged for. Specific notes do not.

PlayPause keeps every revision round pinned to the exact frame, so comments are precise instead of open to interpretation. Approval locks mark a version as signed off, which gives you a clean, dated line for when a later request becomes new scope. And with version stacks plus a record of who approved what, you defend your retainer boundary with evidence, not memory.

The bottom line

The model matters: pick deliverable-based for video unless you love reporting hours. But the real margin lives in the boundaries. Price from your loaded cost, build a buffer, write scope that names the line, and keep feedback specific enough that one round stays one round.

Do that and the retainer holds up, quarter after quarter, instead of quietly eating you alive.

If scope creep keeps turning your retainers into charity, run your revision rounds through PlayPause and let an approval lock draw the line for you.