How many revision rounds to promise (and how to phrase them)

Revisions are where fixed-price projects go to die.

Not because feedback is bad. Because “one more round” has no definition, no owner, and no end state. The client thinks they are helping. You think you are being nickel-and-dimed on time. Everyone is tired, and the proposal never said what a round actually was.

Promising revision rounds is not about being stingy. It is about defining how you collaborate so the work converges. The right number depends on deliverable type, price, and timeline. The right phrasing matters as much as the number.

Use this alongside out of scope paragraphs, fixed-price pricing, and payment terms so revisions, scope, and money tell one story.

What counts as a revision round (define this first)

Before you pick “2” or “3,” define a round:

One revision round means one consolidated batch of feedback from your side, sent in one message or document, within [X] business days of delivery. I implement that batch and return an updated deliverable. Staggered comments over a week count as multiple rounds unless we agree otherwise.

That definition does more work than the number alone.

Also define what a round is not:

• New features or pages
• New audience or strategy after copy was approved
• “Try a totally different direction” after concepts were approved (often a new concept round, not a revision)

Clients are not stupid. They often just have never freelanced before. Teach the process in one paragraph.

How many rounds by project type (practical defaults)

These are starting points, not laws. Adjust up for higher fees, down for sprints.

Work type	Typical included rounds	Notes
Logo / brand mark	2-3 concept rounds, then 2 polish rounds on chosen direction	Separate “concepts” from “polish”
UI mockups (single flow)	2 rounds on approved wireframe	Wireframe approval is round 0
Landing page build	1-2 rounds on staging	Content readiness affects count
Long-form copy (per piece)	2 rounds on approved outline	Outline approval saves chaos
Short email or ad set	1-2 rounds	Keep feedback bundled
Video edit (short)	2 rounds on rough cut, 1 on fine cut	Name cut stages
Bug fix	1 verification cycle	New bugs are new scope

For 48-hour sprints, one consolidated round within hours is normal. For long RFP-style projects, rounds may attach per milestone instead of globally.

Copy-ready phrasing (mild to firm)

Mild (relationship-first, still clear)

This quote includes two revision rounds on each milestone deliverable. Please send consolidated feedback in one pass so we stay on timeline. Additional rounds are available at [$] or [$]/hour if needed.

Standard (most freelancers)

Included: 2 revision rounds per deliverable after you approve the outline/wireframe. A round is one batched feedback list within 3 business days. New scope or new directions after approval are quoted separately.

Firm (low-budget or high-risk posts)

Included: 1 revision round on staging, then final polish of agreed tweaks only. Further changes or extra concepts are billed as add-ons before work continues.

Pick the tone that matches the client and platform. Non-native English mistakes often include vague “unlimited revisions” phrasing that sounds generous but reads as unprofessional.

Separate “concept rounds” from “revision rounds”

Designers and brand freelancers should split language:

Concept phase: up to 3 initial directions based on the brief.

Revision phase: 2 rounds of refinements on the selected direction (color, type, spacing), not unlimited new concepts.

Writers can mirror:

Outline approval (not counted as a revision round).

Draft 1 + 2 revision rounds on the approved outline.

Without separation, “round 7” becomes “another concept.”

What to say when the client asks for unlimited revisions

Marketplaces sometimes attract posts that say “unlimited revisions until satisfied.” You can answer without mockery.

I do not offer unlimited revisions because timelines and quality suffer. I do offer enough structure to reach approval: [X] rounds with clear batched feedback. In practice, well-organized projects finish in [Y] rounds. If you need a retainer-style collaboration with ongoing tweaks, I can quote a monthly block instead.

That redirects extremes to a real product: retainer hours.

Extra rounds: price them in advance

Name the overflow before it happens:

Additional revision rounds beyond those included: [$ flat per round] or [$]/hour with a 1-hour minimum, confirmed in writing before I begin.

Flat per round is easier for clients than open hourly for feedback chaos.

Tie overflow to scope and out-of-scope rules when the “revision” is actually a new page or feature.

Feedback rules that make rounds work

Add operational rules next to the number:

• Feedback due within [X] days
• One stakeholder consolidates comments (or you charge for conflict resolution)
• Approved files are marked “approved” in writing
• Minor typos after approval may be grouped as one micro-pass (your choice, state it)

Example block:

Please consolidate feedback from your team into one document. Conflicting comments may require a short call billed at [rate] or extra time. Approval of milestone 2 requires written sign-off on milestone 1.

Examples embedded in a full proposal section

Revisions: 2 rounds included on the staging site after launch to staging. Each round is one email with all changes listed. I will implement and redeploy within 2 business days. Additional rounds are $[X] each. Changes that add pages, integrations, or new sections are out of scope and quoted first.

Revisions: 2 rounds on draft copy after outline approval. Structural changes after draft approval (new sections, new audience) are scoped as a new milestone.

Revisions: 1 round on rough cut, 1 on fine cut. Color grade and export included after fine cut approval.

Readers can copy the shape, not just the numbers.

Mistakes freelancers make

“Unlimited revisions” to win the bid. You buy anxiety and train the client to never decide.

No definition of a round. Numbers are meaningless.

Ten rounds on a $200 job. Your margin is gone before round three.

Treating scope changes as revisions. Call it out early: “That is a great add-on; here is the quote.”

Charging emotionally instead of in writing. Resentment shows. A pre-agreed round price keeps tone neutral.

FAQ

Is two rounds enough for picky clients?

Often yes, if outline/wireframe approval is strict and feedback is batched. Picky without process needs tighter rules, not infinite rounds.

Should revisions be per milestone or per project?

Per milestone is clearer on multi-phase work. Per project is fine for single-deliverable jobs.

What if they send a Loom video instead of a list?

State whether video feedback counts as a round if it replaces a written list, or whether you will transcribe it into tasks (billable over X minutes).

Do revision limits apply after launch?

Define a warranty window separately: e.g., 14 days for bug fixes you caused, not new features.

Before you send

Use the proposal checklist and confirm:

• Number of rounds stated
• Definition of a round (batched, timed)
• Concepts vs revisions separated if relevant
• Price for extra rounds or scope changes
• Aligns with out-of-scope and payment sections

Revision rounds are a collaboration tool. Promise enough structure to finish, not enough vagueness to never ship.

---

Bottom line: define what a round is, promise a sane number for the deliverable type, and price overflow before round four becomes a lifestyle.