What is iterative proofing and why it protects your margin

The proofing nobody explained to you

Most proofings end the same way: the client sends three emails, you do five rounds of revisions, and the invoice covers only the first version. The rest - "small notes" that suddenly ate two evenings.

Iterative proofing solves this differently. Every round of feedback is its own document. The client gets a bill for the scope change before you sit down to work.

Three things an iteration changes

1. Pricing before work, not after the fact. The client sees specific hours ("+3 h for the new balcony layout") and either approves or rolls back the change. No disputes later.

2. Billing number for the bookkeeper. Each iteration has its own identifier (REV-2026-0042). You put it on the invoice instead of explaining "what I did during those 8 hours".

3. Versions on a timeline, not in email. V1, V2, V3 visible side by side. The client doesn't write "let's go back to what was in the first version" - they just click v1.

Why "just comment on the PDF" is not enough

A PDF with notes is a document without a commitment. The client can check off twenty pins and write at the end "oh and also move the entrance". Four hours of work are already on their way, and nobody knows about it.

An iteration closes the round. Either all notes from this round fit in scope, or you get "+X h" and the client knowingly approves the cost. There is no third option.

How to start

One link from email instead of a PDF. The client clicks straight on the render, writes what to change. You decide whether it fits the original brief. If not - you price the iteration. The whole process takes less than 10 minutes on your first project.

It's not magic. It's just writing the contract in a way that can't be excused with a single email.