When to add a paid revision cap to a service offer

A small team unpacking boxes in a new, half-empty office

Add a paid revision cap when your service offer needs a clear boundary between included feedback and work beyond the agreed scope. Define what counts as a round, price extra rounds before work starts, and review whether the boundary worked without turning feedback into a dispute.

When does a paid revision cap make sense?

A paid revision cap can help when requests repeatedly expand the agreed deliverable. Look at what clients ask for after seeing a draft. Are they correcting the work against the brief, or asking you to take it in a new direction? Those are different kinds of work, and your offer should make the difference clear.

An unclear limit can also create friction. If the offer does not say how many revisions are included, or what a revision means, both sides may assume different things. The disagreement can surface late, when the client expects more changes and you are trying to protect the time set aside for the project.

Before setting a cap, check whether the brief itself was unclear. A client may be asking for changes because the agreed deliverable was never specific enough. A cap will not fix that. It may make the conversation harder if it treats useful feedback as out of scope.

Set a boundary that fits the work and the relationship. Some projects need room to refine the result. Others can define a narrow set of included changes. The point of a paid revision cap is to make the boundary visible, not to discourage a client from raising a real problem.

What counts as one revision round?

Define a round before work begins. A practical starting point is one consolidated set of feedback on a draft you have presented. That makes the round easier to recognize than an open-ended promise to make changes until the client is satisfied.

Say who gathers the comments and how the client sends them. If several people review the draft, ask one person to collect their feedback and send it together. Make clear whether comments sent later count as another round, so the process does not depend on guesswork.

Your definition should also say what happens when a change is a correction rather than a revision. If your work misses an agreed requirement, explain how you will correct it. If feedback changes the direction or adds a new deliverable, describe that as a scope change that needs a separate agreement.

Example: A fictional design studio agrees to prepare a set of product pages. Its offer defines a round as one combined list of edits to the presented draft. It says that corrections against the approved brief are handled separately, while a new page or a different visual direction needs a scope discussion.

Keep the definition consistent in the offer, the estimate, and project messages. A client should not have to reconcile different versions of the rule. For a related way to define completion, read how to define done for AI work. Brainis turns your own acceptance criteria into Verify checks, authored once, composed into libraries, and enforced per domain. The Verify page explains that product capability.

Two co-founders talking through a plan on a rooftop at dusk

How should you price extra revision rounds?

Choose a charging method the client can understand before the extra work begins. You can set a fixed fee for each additional round, or charge an hourly rate. A fixed fee is easier to approve when the work is predictable. An hourly rate may fit better when the amount of work can vary widely.

Base the price on the work an extra round is expected to involve. Consider the time needed to review comments, make changes, and check the result. Say what the fee covers. If the feedback leads to a new deliverable or a larger change in direction, explain that it needs a separate scope and price rather than fitting inside the round fee.

The client should approve the charge before you start the extra round. State how they can approve it and what happens if they do not. Use the same price and approval terms in the offer, estimate, and request for approval. That gives both sides one clear account of what was agreed.

If you are deciding how to charge for an initial engagement as well, see how to price your first pilot. The useful principle is the same: describe what the fee covers before the work starts, and do not leave the client to infer the price from a later invoice.

How do you write the limit without inviting a dispute?

Write the limit as a description of the work, not as a warning. Name what the client receives and how many rounds of feedback are included. For each round, say that feedback should address the presented draft and the agreed brief.

Explain when and how the client should send consolidated comments. If the client has a preferred contact person, name that role in the process. Clear instructions reduce the chance that scattered messages become a disagreement about whether another round has started.

Then separate corrections from new requests in neutral terms. A correction brings the work into line with the agreed requirements. A new request changes those requirements, adds work, or changes the direction. If it is not clear which one applies, say that you will discuss the request with the client before deciding how to handle it.

Finally, state the fee for work beyond the included rounds and how the client approves it. Avoid language that suggests every new comment will automatically trigger a charge. The client needs to know the boundary and the next step, including how you will resolve an unclear case together.

A person setting up a first desk with a laptop and a notebook

How can you tell whether the cap worked?

After the engagement, review the process without treating the client as the problem. Start by asking whether the client understood the round definition before work began. If they did not, look at the wording and how you explained it.

Note where requests went beyond the agreed deliverable. Check whether you described the difference clearly, and whether extra work was priced and approved as stated. If the work proceeded without approval, identify where the process allowed that to happen.

Look for gaps in the original brief, too. A request that seemed out of scope may point to an unstated requirement or an assumption that neither side checked. The review should help you distinguish a weak boundary from a weak brief, since each needs a different change.

When the same ambiguity appears again, revise the offer language. A paid revision cap works when both sides can see what is included, what falls beyond it, and how to agree on the next step. If clients keep reading a phrase differently than you intend, change the phrase rather than relying on a longer explanation after the fact.

What should you change in your next service offer?

For your next offer, write down what the client receives and what counts as a round. State how feedback is gathered, what happens with corrections against the brief, and how a change in direction will be handled.

Choose the included limit and the price for work beyond it. Add the approval step before extra work starts. Make sure the offer, estimate, and approval request use the same terms, so the client sees one consistent boundary throughout the engagement.

Before you send it, read the wording from the client’s point of view. Could they tell what they receive, what they need to send, and when extra work would require approval? If not, make the language more specific without making it sound punitive.

After the first completed engagement, review what was clear and what was not. Adjust the offer where the process exposed a gap. A paid revision cap is useful when it helps both sides plan the work and discuss changes early, while leaving room to correct mistakes and handle uncertain requests fairly.