Back to Blog
GoScript Journal

Handling Client Revisions Without Losing Margin

·7 min read·GoScript Team /Craft

Set the round limit before you start

Handling client revisions starts with a number. My standard quotes include two rounds of notes. Round one is the client's first full review, round two catches the fixes from that review. Anything past two rounds gets billed at an hourly or per-round rate.

Say the limit in the proposal and the contract so it is never a surprise. Clients rarely count their own rounds. When you point to the number in the agreement, the conversation stays calm and factual.

Collect notes in a single pass

Ask for all feedback at once, in one message or one timestamped list. Piecemeal notes arriving over five days turn a quick fix into five separate sessions. A single pass keeps you in one editing mindset and cuts setup time.

Give clients a simple way to leave timestamps, like a shared doc or just a list of times with comments. When notes are easy to give, they tend to arrive complete and organized instead of as a stream of texts.

Ten random notes cost more than one organized list. Ask for the list.

Separate fixes from new ideas

A fix corrects something from the brief. A new idea changes the brief. They look similar in an email but they cost very different amounts. Treat fixes as part of the included rounds and treat new ideas as new work with its own price.

When a note is really a new direction, reply with the added cost before you touch the timeline. Most clients drop the idea once they see the number, and the ones who want it pay fairly for the extra effort.

Guard your time on small tweaks

Batch small tweaks instead of rendering after each one. Five text changes can be done in one pass. Re-exporting for every comma wastes hours you cannot bill. Set a rule for yourself and apply it to every project.

If a client keeps opening the file for one more change, offer a maintenance rate. A small monthly retainer for ongoing tweaks turns unpredictable interruptions into planned income and stops the endless drip of one-off edits.

Close the project cleanly

After the final round, send the finished file and a short note confirming that the included revisions are complete. This marks the boundary clearly. If the client wants more, it is a new scope with a new price.

Deliver the master file only after the final payment clears unless your contract says otherwise. Holding the master until payment protects you and gives the client a clear reason to settle the invoice.

Key takeaways

  • State the revision round limit in the quote and contract
  • Ask for all notes in one organized pass
  • Treat new directions as paid work, not fixes
  • Batch small tweaks into a single render
  • Offer a retainer for clients who need constant changes

Turn this into your next script.

Analyze a channel, extract its structural DNA, and generate scripts engineered from patterns that actually work.

Analyze a Channel