Revisions are where agency margins die quietly. Not in one dramatic moment — gradually, over many batches, as extra rounds of changes get absorbed into fixed-price contracts that were scoped for two rounds and are now on their fourth.
The problem isn't clients. Clients ask for revisions because they have opinions and standards, which is exactly what you want in a client. The problem is process — specifically, the absence of one.
What a revision actually is (and what it isn't)
This distinction is where most agencies lose money. A revision is a change to a deliverable that was within the agreed scope. A new request is work that wasn't in the original scope, regardless of how the client frames it.
"Can you change the caption color on clip 3?" — revision.
"Can you add subtitles to these 5 clips in our brand font we haven't shared yet?" — new request.
"Can you recut this clip entirely because we changed our minds about the hook?" — depends on your contract, but often new request.
The issue is that clients don't make this distinction — not because they're trying to get free work, but because they don't understand what the scope covers. Your contract and your revision process need to make it explicit.
The contract language that protects you
Every retainer should specify: number of revision rounds per delivery batch, what "one round" means (all feedback collected and submitted at once, not piecemeal), the window for submitting revision requests after delivery, and the rate for additional rounds.
The language that works:
"Each delivery batch includes two (2) rounds of revisions. A revision round consists of all feedback submitted together within 48 hours of delivery. Feedback submitted after the 48-hour window or split across multiple messages constitutes a new revision round. Additional revision rounds are available at $[X] per round, invoiced at the end of the month."
The 48-hour window and the "all feedback at once" rule are the two most important clauses. They prevent the slow drip of notes that turns two revision rounds into six without anyone consciously deciding that.
How to collect revision feedback without losing your mind
Email and Slack are the wrong channels for revision feedback. Both create long threads where feedback gets buried, referenced incorrectly, and missed. You end up re-reading an entire thread to confirm you addressed everything before re-delivery.
Better approaches:
Timestamped comments on a video review link. Tools like Frame.io or a shareable review link let clients leave feedback attached to a specific moment in a specific clip. No ambiguity about which clip, which moment, what the note refers to.
A structured feedback form. A Google Form or Notion form with fields for: clip number, timestamp, what to change, and why. Forces structured thinking. Prevents "I just feel like this could be better" without specifics.
A single feedback document per batch. Ask clients to put all their notes in one shared doc. You review it, confirm you've addressed everything, and close it when done. One document, full history, no scattered threads.
When to push back on a revision request
There are two situations where pushing back is correct: when the request is outside scope, and when fulfilling the request would compromise the quality of the deliverable.
Out of scope is straightforward — reference the contract, note the additional rate, confirm whether they want to proceed. Don't absorb it.
Quality concerns are harder. If a client asks you to use a clip that cuts off mid-sentence because they prefer that moment, you have a choice: fulfill the request and note your concern, or push back and explain why it's likely to hurt their performance. Most experienced agencies recommend noting your professional opinion clearly once, then doing what the client asks. You're not the content director — you're the production partner. Their brand, their call.
The revision spiral: how to spot it before it's expensive
A revision spiral is when rounds multiply because the client's actual problem isn't being solved. They ask for one change, you make it, they ask for another, you make it, and you're now on round six because the underlying issue — they don't actually like the source footage, or the product changed, or someone senior wasn't consulted — was never addressed directly.
The signal: when revision requests start contradicting previous revision requests. "Make it more energetic" followed by "make it calmer" is not about the clips — it's about something else.
The right move: stop the batch, get on a 20-minute call, and ask "what outcome are we trying to achieve with these clips?" That question surfaces the real issue faster than another revision round ever will.
Common questions
How many revision rounds should a video agency offer?
Two rounds per batch is standard. Define each round clearly: all feedback submitted at once within 48 hours of delivery. Additional rounds at a flat fee prevent the scope from expanding indefinitely.
How do you handle clients who keep asking for revisions?
Enforce the revision clause in your contract. Log each round, note when the allowance is reached, and offer additional rounds at the contracted rate. If a client is in a genuine spiral of conflicting feedback, get on a call — the issue isn't the clips.
What's the best way for clients to submit video revision feedback?
Timestamped comments on a video review link (Frame.io or similar) or a structured feedback form. Both force specific, clip-level feedback that's easier to act on than vague email notes.
Scale your short-form without the babysitting
Most revision requests for AI-processed video are technical — wrong format, wrong caption style, wrong crop. Skapo stores client configurations so those errors don't reach the client in the first place.
Try it freePosted by the Skapo team — June 2026