How to Cap Revision Rounds for Retainer Clients Without Starting a Fight

Every agency we talk to has a version of the same client, the one on a monthly retainer who started out asking for two rounds of notes on the explainer video and is now, four months in, sending a fifth pass of "just a couple more tweaks" on a deliverable that was supposed to close out last Tuesday. Nobody agreed to this in writing, it just happened, one reasonable-sounding request at a time, and now the editor assigned to that account is quietly eating hours that were never billed for. If that sounds familiar, you're not managing a difficult client, you're managing a revision policy that was never actually written down.

Why "unlimited revisions" quietly destroys retainer margins

Retainer pricing only works if the labor per deliverable is roughly predictable, and revisions are the one variable that agencies almost never cap explicitly. We see this constantly with teams who scope a retainer around "two videos a month" and never define what a video actually costs in revision time, so the client anchors on the first round being free and generous, and every round after that just feels like more of the same free and generous thing. At the end of the day, an agency running six retainer clients at three unbilled revision rounds each is quietly running a seventh account for free, they just haven't done the math on it yet.

The fix isn't telling clients no more revisions, it's setting a number before the relationship starts drifting, because a cap that gets introduced after six months of unlimited access reads as a punishment, while a cap that's part of the onboarding conversation just reads as how the process works.

The real reason clients keep asking for "just one more pass"

Most clients aren't trying to extract free labor, they're anxious about approving something that might get criticized by their own boss later, so another round of notes feels like insurance rather than indulgence. That's worth sitting with for a second, because if you treat every extra revision request as an attempt to take advantage of you, you'll write a policy that feels adversarial, and clients can smell that from a mile away. A cap that's framed as "here's how we make sure you get exactly what you need, efficiently" lands completely differently than a cap framed as "here's the limit before we start charging you," even though the underlying rule is identical.

Setting a number that actually protects both sides

For most retainer arrangements, two structured rounds per deliverable is the number that holds up, one round for direction correction and one round for polish. A single round is usually too tight for anything with stakeholders beyond the immediate contact, and four or more starts to blur the line between revising and re-editing from scratch. If your retainer covers heavier format work, like a monthly cut-down for Social Media, you might build in a third round specifically for brand or compliance review, but the core creative rounds should stay at two.

Writing the cap into the SOW without it reading like a threat

The language matters more than the number. Instead of "clients are limited to two revisions," try something closer to "each deliverable includes two rounds of structured feedback, which covers the vast majority of projects, additional rounds are available and billed separately so we can keep turnaround fast for everyone on retainer." That second version tells the client the cap exists to protect turnaround speed, which is something they actually want, rather than protecting your margin, which is something they don't particularly care about.

What happens when a client blows through the cap

You need a pre-decided answer for this before it happens, not one you're improvising over email while frustrated. The cleanest structure we've seen agencies use is a small grace allowance, a genuinely minor fix like a typo or a color shift doesn't count against the round count, but any note that touches structure, pacing, or messaging does. Everything past the included rounds gets billed at a pre-agreed flat rate per round rather than an hourly rate, because clients trust a flat number and distrust an open-ended hourly clock. If pricing that extra round is the part you're still figuring out, we wrote a full breakdown on charging for extra revision rounds that walks through how to set that number so it doesn't feel like a penalty.

Making the revision process itself feel structured, not restrictive

A revision cap only feels fair if the client can see exactly what they're using it on, and this is the part most agencies get wrong, they cap rounds but still run feedback over email threads and Slack messages where nobody can tell what counted as "round two" versus a follow-up clarification. This is basically the whole reason we built PlayPause the way we did, every comment lands on an exact frame with a timecode attached, so when a client says "this is round two," everyone including the client can actually see the full history of what round one covered and what changed because of it. That visibility does more to prevent revision creep than any clause in a contract, because ambiguity is what let scope creep in, in the first place.

Agencies running review workflows through an Approval Workflow tend to see fewer disputed rounds for exactly this reason, the system itself becomes the record, so nobody has to rely on memory or a buried email to settle what's included.

Communicating the policy without starting a fight

Introduce the cap in the kickoff call, not in an email after round three when the client is already annoyed. Say it plainly and pair it with the benefit: "we do two structured rounds per video, that's what keeps your turnaround at three business days instead of three weeks, and if you need more we'll always tell you the cost before we start." Clients respond well to structure when it's presented as the thing that makes the whole engagement move faster, and poorly when it's presented as a rule they broke.

• State the round cap in the kickoff call, not mid-project
• Separate minor fixes from full revision rounds in writing
• Give a flat price for extra rounds up front
• Use a review tool that timestamps every round automatically
• Revisit the cap at renewal, not mid-cycle

If you're dealing with a client who seems to genuinely struggle to commit to a decision within those two rounds, that's usually a different problem wearing the same costume, and we've written specifically about coaching indecisive clients toward a faster yes, because sometimes the fix isn't a stricter cap, it's better reassurance language.

Rolling out a cap on a client you already have

The harder version of this problem isn't a new client, it's the existing retainer account that's been running on unlimited revisions for a year and has no idea a cap is coming. Don't spring it mid-project, and don't apologize for it either, because apologizing signals that you think you're taking something away rather than fixing something that should have been there from the start. The cleanest move is to introduce it at renewal, frame it as an update to how the engagement runs going forward, and pair it with something the client actually gets in return, like a faster turnaround commitment or a dedicated editor now that rounds are predictable. We've watched agencies do this with accounts that had been open-ended for over a year, and the resistance was almost always smaller than expected, mostly because most clients had no idea the current setup was unusual in the first place, they assumed two or three rounds was standard everywhere.

It also helps to have a neutral third party doing the enforcing, so to speak, rather than you personally being the one who says no. When the round count lives inside a shared review tool instead of in your head or your account manager's memory, the conversation shifts from "our agency is capping you" to "here's what the project shows, we're on round three of two included, want us to proceed at the standard extra-round rate." That small shift, letting the system state the fact instead of a person delivering the news, removes a surprising amount of the emotional charge from what used to be an awkward conversation.

Where this saves the relationship, not just the margin

The agencies that hold retainer clients longest aren't the ones who say yes to everything, they're the ones whose process feels predictable, and a clearly stated revision cap is one of the simplest ways to build that predictability. StudioBinder's blog has covered how much scope clarity affects client retention on ongoing production work, and our own experience matches that closely, the clients who stay longest are the ones who always know exactly what they're getting and exactly what it costs to get more.

Set the number, put it in writing before the first deliverable, and give clients a tool where the round count is visible instead of implied. Contact PlayPause if you want help mapping a revision cap onto your actual retainer workflow, or take a look at PlayPause pricing to see how flat per-workspace pricing makes it easier to build revision policies that don't punish you for growing your retainer roster.