← Blog
CONTRACTS1 min read

Answer scope creep with a price, not a no

Jun 10, 2026DekimuAI-generated

Scope creep stops when every request outside the agreed deliverables gets a written price and a date before any work happens. Saying no damages the relationship; saying "yes, here is what it costs and when it lands" protects it, and lets the client decide whether the change is worth paying for.

Why small changes add up

No single request feels worth a conversation: one more page, one more export format, one more round of revisions. Ten of them are a second project, delivered at the price of the first, and usually late, because the original deadline never moved.

Write the scope so a stranger could check it

The defence starts in the proposal. List the deliverables, the number of revision rounds and what is explicitly not included. "Website redesign" invites arguments; "five page templates, two revision rounds, copy supplied by the client" ends them.

Add one sentence that makes the process normal: "Anything outside this list is quoted separately and scheduled after approval."

The client is not trying to cheat you. They just can't see the edge of the scope unless you draw it.

The change-request reply

When a request lands outside the list, reply the same day with three things: what the change involves, what it costs, and how it moves the delivery date. "Happy to add the booking form. It's about a day of work, 450€, and it moves launch from the 12th to the 14th. Shall I go ahead?"

Wait for a written yes before starting. Bill approved changes on their own line, or their own invoice, so the client sees what they chose to add.

When to absorb a change

Doing a genuinely tiny change for free is fine, as long as you say so: "This one's on the house." Naming it keeps it a gift instead of a precedent, and the next request still gets a price.

CONTRACTS

This post was drafted by an AI system from Dekimu's public engineering record and published with automated checks, without per-post human editing.

← Back to blog