How Many Revision Rounds Should Freelancers Include?

"Just a few tweaks" arrived as seventeen separate comments across Figma, email, and a voice note. Round one. Then round two looked like round one with different adjectives. Round three was "final final" until it was not.

You priced a build. You delivered a unlimited opinion processing service.

Revision rounds are not a petty limit. They are how fixed-price work stays fixed.

Why revision limits belong in the proposal

Every round costs you:

• Context reload on the file or branch
• Meetings to "talk through" feedback that should have been written
• Ripple effects — one color change becomes twelve component updates

Without a cap, the client optimizes for perfect. You absorb the search cost. Put the number in the freelance proposal next to the deliverable, not buried in terms nobody reads.

Practical revision counts by project type

These are starting points, not laws. Price up if stakeholder count is high.

| Work type | Typical included rounds | Notes | | --- | --- | --- | | Marketing site (5–8 pages) | 2 after staging review | One content pass, one polish pass | | Product UI in Figma | 2–3 on major flows | Define what "major flow" means | | Backend / API | 1 after acceptance tests | Objective criteria reduce subjective loops | | Bug-fix warranty window | Separate from revisions | Fixes for agreed scope, not redesign |

Pair rounds with scope clients cannot misread so "change the whole layout" is clearly a new phase, not round four.

Define what a round actually is

Vague policy creates arguments.

Write something like:

• One round = one consolidated feedback document or Figma comment pass due within 5 business days
• Feedback applies to the deliverable named in the milestone (staging URL, Figma file, PR)
• New features or net-new pages are change orders, not revisions

How to handle round three without sounding rigid

Scripts:

• "Happy to keep going — additional rounds are $X each or we can bundle the rest as a polish phase."
• "I can fold these into round two if we freeze copy by Friday; otherwise they slot as a change order."
• "These notes look like new scope (extra template + CMS fields). I will send a quick estimate."

Tone stays warm. Boundary stays firm. That is the same skill as using change orders without sounding difficult.

Revision rounds only work if done is defined.

WorkFocus helps freelance developers keep today's delivery tied to the milestone you sold — not the last comment thread.

Try WorkFocus free

Tie revisions to a definition of done

Rounds without "done" are infinite.

For each milestone, state done explicitly:

• Deployed to staging with checklist items passable
• Client sign-off email or tracked approval in the project tool
• Production release after final round, not before

When feedback tries to reopen signed-off work, you can point at acceptance — not attitude.

When unlimited revisions are a mistake you chose

Some freelancers offer unlimited rounds to win the deal. Know what you bought:

• You must charge more upfront to cover the risk
• You need brutal scope walls elsewhere — exclusions, change orders, no new pages
• You still need a feedback format or you will drown in chaos

For most solo developers on fixed bids, capped rounds plus clear change orders is the sustainable model. Same foundation as avoiding scope creep.

The bottom line

Include one to three revision rounds depending on deliverable type, define what counts as a round, and price anything beyond that. Clients who respect process still get excellent work — they just batch their feedback like adults.

If your week keeps losing hours to unscoped tweaks across clients, try WorkFocus free — so the work you agreed to stays visible while new feedback waits its turn.