← Back to blog

Cutting Revision Rounds With a Clickable Version

August 23, 2026

Revision rounds are where fixed-price agency work goes from profitable to not. The instinct is to tighten the contract; the cheaper fix is usually to change what the client approves in the first place.

A large share of revisions are not aesthetic disagreements at all — they are the client meeting the behaviour of something they only ever saw standing still.

Separate taste revisions from surprise revisions

Go through your last three projects and sort the change requests into two piles: things the client did not like, and things the client did not expect. The second pile is the expensive one, and it is preventable.

Surprises come from static approval — a flat screen cannot show what happens on click, on error, on empty, on a phone. Those four are where most of them live.

Show the four states nobody mocks up

  • Empty: the screen on day one with no data. Clients are consistently shocked by this one.
  • Error: what a wrong entry looks like.
  • Loading: what happens while something takes time.
  • Mobile: the same journey on a phone, which is where the client will first show it to their boss.

Put the demo in the contract

If your agreement defines revision rounds, define what a round is against: "revisions are counted against the approved demo linked in the sign-off email". That is a specific, dated artefact rather than a memory of a meeting.

It is not about being adversarial. Most scope disputes are two people honestly remembering different things, and pointing at the same link ends them in one message.

Where it does not help

A client who changes their mind because their own boss changed theirs will do it regardless of what they approved, and no artefact prevents that. Nor does this help with genuine taste disagreements, which are legitimate work.

The claim is narrower and still worth a lot: it removes the category of revision that comes from imagining, which for most agencies is the largest single one.

Frequently asked questions

How do you reduce client revision rounds?
Change what gets approved. Sort your last projects' change requests into "did not like" and "did not expect" -- the second pile comes from approving something static, and is preventable by showing the empty, error, loading and mobile states nobody mocks up.
Can a demo be referenced in a contract?
Yes, and it is worth doing: define revision rounds against "the approved demo linked in the sign-off email". That is a specific dated artefact rather than a memory of a meeting, and most scope disputes are two people honestly remembering differently.
What revisions does this not prevent?
Genuine taste disagreements, which are legitimate work, and a client whose own boss changed their mind. The claim is narrower: it removes revisions caused by imagining, which for most agencies is the biggest single category.

Keep reading

This is what Demorta does

Click through it — the same kind of demo you can record of your own product.

Try it on your own product

Record your first interactive demo free.

Five demos on the free plan, forever. No credit card, no trial countdown, no sales call. Install the Chrome extension, click through your product once, and you have a shareable link in about ten minutes.

Start free →