Detects scope creep and converts it to paid work using the new-request test, a one-yes courtesy budget, a word-for-word change-order script, and a relationship-preserving no. Use when a freelancer says "the client keeps asking for little extras", "this project has doubled and the price hasn't", "how do I say no without losing the client", "they want one more quick thing", "can I charge for this add-on", or "the retainer hours are gone but requests keep coming". Do NOT use for writing the contract clauses that make this enforceable - use statement-of-work-writer instead; this skill enforces at delivery time what that skill establishes at signing.
---
name: scope-creep-defense
description: Detects scope creep and converts it to paid work using the new-request test, a one-yes courtesy budget, a word-for-word change-order script, and a relationship-preserving no. Use when a freelancer says "the client keeps asking for little extras", "this project has doubled and the price hasn't", "how do I say no without losing the client", "they want one more quick thing", "can I charge for this add-on", or "the retainer hours are gone but requests keep coming". Do NOT use for writing the contract clauses that make this enforceable - use statement-of-work-writer instead; this skill enforces at delivery time what that skill establishes at signing.
---
# Scope Creep Defense
Scope creep never arrives as a demand; it arrives as a compliment - "you're so good at this, could you also just..." - and each individual yes is small enough that refusing feels petty. The costly mistake this skill prevents is the accumulation: ten small yeses that turn a fixed-price engagement into an unpaid custom one, followed by resentment the client never saw coming because nobody told them the meter existed. The defense is not saying no more often; it is converting requests into revenue through a process the client experiences as professionalism.
This skill pairs with statement-of-work-writer - it enforces the inclusions, exclusions, and change-order clause written there, and it is nearly toothless without them. Worked example: Maya, a freelance brand designer on a $4,900/month Brand System Retainer (up to 36 hours, 2 revision rounds per deliverable) with a DTC hot-sauce brand.
## Operating procedure
### Step 1: Collect the inputs
1. The signed SOW: inclusions, exclusions, revision limit, change-order clause. If no SOW exists, the honest answer is that scope cannot creep past a boundary that was never drawn - do statement-of-work-writer first and apply this skill from the next request onward.
2. The specific request, verbatim if possible.
3. Courtesy budget status: has the one free yes for this project already been spent?
4. Hours consumed against the retainer or budget this cycle. Label estimates as guesses.
### Step 2: Run the new-request test
Every new request gets sorted within one business day - speed matters, because an unanswered request silently becomes an assumed yes. Three gates, in order:
1. **Is it in the SOW?** Check inclusions honestly - the test loses all credibility if genuinely in-scope work gets treated as creep. In scope: do it, no ceremony.