How to run white-label revision rounds without killing margin

If you cannot define a round in a sentence, you cannot invoice one. Operational definition: a revision round is one consolidated written list of in-scope feedback, submitted after a named milestone (usually agency-approved staging), that the partner implements as a single pass. Ten Slack messages over six days are not a round. They are a leak.

Feedback that arrives as a stream is design-by-chat. Feedback that arrives as a list is a professional service.

It rarely says “unlimited” in the PDF. It says “includes revisions,” “until you’re happy,” or nothing at all. Account managers then fill the silence with yes because a launch date is close and a competitor’s proposal was softer.

If your sales motion cannot survive a revision cap, the problem is packaging, not the partner. Productized offers (page counts, templates, two rounds) exist so white label can be priced. Bespoke invention with a smile is a different SKU. Price it like one.

The default that works: you buy one partner round for internal/agency QA defects, and you buy two client rounds that you have actually sold. You do not show the client the partner’s first staging if it still fails your checklist. That first pass is not “using up” the client’s goodwill. It is you doing your job.

If you skip agency QA, the client becomes round 0 and you will spend partner hours on typos you should have caught. That is not a revision policy. That is unpaid QA staffed by a customer. The same failure shows up when three AMs each promise “a quick look” on different days: the partner experiences four rounds while the client believes they used one. Count passes on the partner’s clock, not on the client’s memory.

Retainer capacity makes this worse if you do not tag rounds. Reserved hours disappear into “small tweaks” that never hit a change order. If you already measure retainer ROI, extra passes should be a weekly leading indicator—not a surprise in month three.

A revision adjusts work that was in the brief and the approved design. A change request adds or replaces scope: a new template, a third locale, a CRM field nobody mentioned, a shop filter that was “implied.” If you treat changes as revisions, you will train clients to discover the product on staging.

Write the test into the SOW in plain language. Then train account managers to say, “That’s a change; here is the quote,” without sounding like a villain. The villain move is saying yes, absorbing the partner’s invoice, and resenting the client later.

The partner should not receive six stakeholders in a thread. You collect, you contradict the contradictions, you send one list. If two executives disagree, that is your political problem until it is written as a single instruction.

1. 01

   Open a window

   Tell the client: feedback due by date, in the shared doc or ticket, not in email side channels. Late feedback starts a new clock.

2. 02

   Consolidate

   One owner merges comments, kills duplicates, marks out-of-scope items as change-order candidates.

3. 03

   Send a numbered list

   Each item: page, current behavior, requested behavior, in-scope or quote. Screenshots welcome. Speeches not welcome.

4. 04

   Partner executes one pass

   No drip feeding mid-pass unless something is blocking. Drip feeding is how one round becomes three.

5. 05

   Agency QA, then client

   You check the list was done. Then the client sees it. Do not outsource your QA to them.

Loom videos are fine as attachments to the list. A 22-minute Loom with no timestamps is not a list. Ask for timestamps. Your future self is an account manager with two other launches.

Clients should not see broken nav, lorem in a footer, or a form that 500s. That is not “transparency.” That is you spending brand equity so a developer can get a reaction. White label exists so the partner can be messy in a place the client never visits.

If the client insists on watching the build like a livestream, you are not running white label. You are running a show. Charge for the show or refuse it. Daily client walkthroughs during construction will consume rounds as theater.

Numbers below are illustrative, not a quote. They exist so you can see why “just one more pass” is a P&L event.

You did not “keep a client happy.” You spent about $2,300 to avoid a 20-minute commercial conversation. Sometimes that is a rational account decision. Record it as a discount. If you do it every time, you do not have a revision policy. You have a habit.

Price the extra round on the client side above the partner’s extra so AM time is covered. If you pass through at cost, you are still donating coordination. The ROI calculator is built for this kind of line—use it when extra rounds become a pattern, not a story.

Opening the feedback window

“Staging is ready for your review. This is round 1 of 2 included in the SOW. Please add all in-scope feedback to the doc by Thursday 4pm your time. We will consolidate Friday and the partner will implement next week. Requests that add pages or integrations will be quoted before they are built.”

When something is a change

“The extra pricing table isn’t in the approved sitemap. We can add it as a change: [fee], [days], [what it does to the launch date]. If we skip it for v1, we can schedule it after launch. Which do you want?”

When the window is used up

“Round 2 is complete against the list we confirmed. Further visual passes are an extra round at [fee], or we can park items in a post-launch backlog. I need a written choice so we do not stall the launch date you already announced.”

Say no (or quote) when the request is new scope, when rounds are exhausted, when feedback is a fight between stakeholders you have already asked to resolve, or when the file is being used to reopen a closed design. Spend a round on purpose when you missed something in the brief, when a defect escaped agency QA, or when a strategic account’s launch is worth a recorded discount.

Record discounts in the project file. Otherwise every AM will believe extras are free because last time was free. Finance cannot manage a policy that only exists in folklore.

The SOW language belongs next to MSA and IP as commercial terms, not as a surprise. Kickoff should repeat the number of rounds, the tool for feedback, and the extra-round fee. Clients forget PDFs. They remember the last thing you said on the call.

If you are still choosing a partner, ask how they define a round on the discovery call. If they smile and say unlimited, they are either inexperienced or planning to recoup it somewhere you will not like.

When you want a partner that already treats rounds as operations, start a partnership conversation. Bring a recent SOW that went badly. The useful discussion is how to stop that pattern—not a tour of frameworks.

Clients do not remember your Git hygiene. They remember whether feedback felt respected and whether the launch date held. A tight round process does both: they are heard once, fully, and the site ships. A sloppy process makes them repeat themselves and then surprise-bill them. That is how you lose the retainer you were trying to protect.

White label is supposed to make this easier, not foggier. Your agency still owns the relationship. The partner owns a pass against a list. If you keep those jobs in separate lanes, margin survives. If you merge them in a group chat, you will hire extra people to manage a process you never wrote down.