The Revision Round That Never Ends
A revision round isn't a feeling the client has about the draft. It's a counted, owned object — and the moment you stop treating it that way, feedback stops being work you can bill and starts being water finding every crack in the floor.
The email from the client said "just a couple of notes." Then a second email arrived forty minutes later from someone else at the same company, also with "a couple of notes," half of which contradicted the first set. Then a WhatsApp message from a third person who'd been cc'd somewhere upstream, asking if the lobby render could be "a bit warmer, you know, cozier." None of these people had agreed with each other. All three believed they'd sent feedback on round two.
This is the moment a lot of visualization studios, animation houses, and pitch-deck freelancers quietly start losing money, and it has nothing to do with how good the client's taste is. It's that nobody decided what a round is. Without that, every message that arrives feels to the client like a comment. To the studio, it's a new unbillable task with no name.
A round is an object, not a mood
A revision round is not the client's general sense that things could be better. It's a single counted thing with a beginning, an owner, and a closing. Concretely, a round is: one set of notes, consolidated from everyone who's allowed to give notes, delivered through one channel, responded to with one delivery. If that definition sounds obvious written down, it's because almost nobody enforces it in the moment a client is typing.
The failure isn't that clients give too much feedback. It's that feedback arrives as events instead of as a round. Three messages from two people isn't round two. It's three uncounted events that the studio has agreed, by not pushing back, to absorb as if they were free. The studio that treats every incoming message as its own tiny obligation will work the same hours as the one that enforces rounds — it will just never get paid for most of them.
The Elm Street tower, or how four rounds became eleven
A studio I worked with — six people, mostly architectural stills and walkthroughs — had a contract with a developer client that specified three rounds of revision per deliverable. Reasonable on paper. Here's what three rounds turned into on one residential tower project.
- Round one came in clean: one PDF, one person, numbered points. Closed in a day.
- Round two arrived as the PDF, plus a follow-up email two days later from the developer's marketing lead ("forgot to mention, can the sky be less gray"), plus a voice note from the architect's junior associate about a railing detail nobody else had flagged.
- The studio treated all three as round two, because saying no felt like it would sour the relationship over something small.
- Round three was the PDF. Then a fourth input arrived a week after round three was marked delivered, from the developer's boss, who hadn't seen any previous round and had opinions about the landscaping.
- Because nobody had said "round three is closed," the landscaping note got folded into what the client still called round three.
- By the time the project wrapped, the studio's internal time tracking showed eleven distinct feedback events. The contract said three. The invoice reflected three.
Nobody in that chain was acting in bad faith. The marketing lead genuinely thought a stray comment was a small addition to feedback already in motion. The developer's boss didn't know a round had closed, because nothing visible to him said so. The studio's producer, trying to be accommodating, kept absorbing inputs because each one, alone, looked too small to fight about.
That's the mechanism. Not one dramatic scope-creep moment — eight small ones, each individually reasonable, none of them counted.
"One more small change" is a sentence, not a size
The phrase that should make any studio owner's stomach drop isn't "this doesn't work." It's "can we just do one more small thing." Small is doing a lot of work in that sentence. It usually means: outside the counted round, requiring real time, framed as too minor to invoice. The shutter gets moved six inches. The sky gets warmed up half a stop. The text on a sign gets swapped. Each one takes fifteen minutes. None of them were in round two, three, or the eleven-event version of round three. All of them happened.
The fix isn't refusing small changes. It's refusing to let "small" exempt a change from being counted as part of a round, open or closed. A studio that says "happy to do that — I'll fold it into round three, which reopens it" is not being difficult. It's being the only person in the exchange who remembers that rounds are the unit the invoice is built on.
Consolidate the people, not just the notes
The three-messages-from-two-people problem is really a permissions problem wearing a feedback costume. The developer's marketing lead, the junior associate, and the boss were never supposed to be three independent sources of notes. Somebody — the producer, the architect, whoever owns the relationship — was supposed to be the single collection point, consolidating internal opinions before they reached the studio as one round.
This is where I'd rather talk about who gets to send feedback than about billing policy, because billing policy is downstream of it. A client contact who can see the work and raise a request is not the same role as a client contact who can quietly cc three colleagues into a feedback thread with no owner. If you give external people a way to ask for things — a single thread, routed to the people on your side who actually own the round — you've already solved half of the eleven-events problem, because there's one place notes land and one person who decides whether they're round three or round four. If instead feedback can arrive through any channel any contact happens to be using that day, you've built a system where the client organization's own internal disagreement becomes your unbillable overtime.
That's the practical argument for keeping external collaborators in a narrower lane than internal teammates: not because clients are less important, but because an undifferentiated channel turns every stray opinion into your scope. A client who can see the deliverable and send one request to the team that owns the round is a client who can still give you everything you need. A client whose marketing lead can text your junior designer directly is a client who has, without meaning to, made your contract's round count unenforceable.
What to actually say
The sentence that fixes most of this costs nothing and offends almost nobody, if you say it early: "Happy to take that — I'll log it as part of round three, and once I send the next version, round three's closed and round four starts from there." It names the object. It doesn't accuse anyone of scope creep. It just makes clear that a round is a thing with edges, the same way a delivery date is a thing with an edge, and feedback that arrives after the edge is a new round, not a footnote to the old one.
None of this requires the client to be less involved or less heard. It requires the studio to stop letting "a couple of notes" be the unit of account instead of the round. The client who sends three messages from two people isn't necessarily being unreasonable — they may not know a round closed at all. The studio's job is to make sure they can't not know.
