Operating ProcedureExecution layer

Revision Round Budgeting (Delivery)

A sequence with 7 steps: Set a hard revision ceiling in the client agreement before generation starts.

By InnovaAI ResearchPublished

What are the steps?

sequence

Revision Round Budgeting (Delivery)

  1. 01

    Set a hard revision ceiling in the client agreement before generation starts

    Two rounds is the common break point for a $1,500 to $3,500 build; anything past that converts a fixed-fee project into hourly work. Write the ceiling into the statement of work, not the kickoff call.

  2. 02

    Log the first draft's generation inputs so later edits trace back to a known baseline

    Record the prompt, source URL, or Figma file used, plus the platform and plan tier. When a client asks why a section reads a certain way, you can show the input rather than re-litigate the copy.

  3. 03

    Triage round-one feedback into content, layout, and scope buckets

    Content edits (headline wording, service descriptions) cost minutes. Layout edits (section reordering, new page types) cost hours. Scope additions (booking systems, member areas, multi-language) are a change order, not a revision.

  4. 04

    Route content edits to the client's own team where the retainer allows it

    Platforms with white-label CMS access let a client edit their own text after handoff. Training that habit in round one removes the most common source of unbilled revision requests.

  5. 05

    Price round three and beyond at a published hourly or per-round rate

    Quote the rate at kickoff so the number is never a surprise. Agencies that quote revision overage only after the fact absorb the argument instead of the fee.

  6. 06

    Run a pre-launch pass that separates defects from preferences

    Broken forms, missing alt text, and mobile overflow are defects and get fixed at no charge. Color and font preferences after round two are billable. Naming the distinction in writing ends most disputes.

  7. 07

    Reconcile actual hours against the estimate within five business days of launch

    Compare build hours, revision hours, and platform cost against the original quote. If the same client type runs over three projects in a row, the pricing model is wrong, not the client.