# Scope Creep Defense > 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. - Skill: `skillmedev/scope-creep-defense` (Agent Skill) - Install (CLI): `npx skillmds@latest add skillmedev/scope-creep-defense` - Raw SKILL.md: https://api.skillmd.com/api/skills/skillmedev/scope-creep-defense/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Docs & Writing - Author: SkillMedev (https://skillmd.com/u/skillmedev) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/skillmedev/scope-creep-defense --- # 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. 2. **Is it a small courtesy?** Under roughly 30 minutes, one-off, and the courtesy budget is unspent → grant it (Step 3). 3. **Otherwise it is a change order.** Route to the script in Step 4. A third revision round beyond the 2 in the SOW is a change order too, not a courtesy - revision limits erode fastest. ### Step 3: Spend the courtesy budget - visibly **One small yes per project (or per retainer quarter), then convert.** The single courtesy is relationship lubricant; the discipline is spending it *visibly*, so goodwill is banked instead of leaking silently: > "That one's outside our scope, but it's small - I'll just take care of it this time. Anything along these lines in the future, I'll write up as a quick add-on." Both halves matter. The gift builds the relationship; the flag sets the boundary. A courtesy granted silently registers as "this stuff is included," which manufactures the next five requests. ### Step 4: Convert with the change-order script Word-for-word, adaptable to email or a call. Tone: enthusiastic, not defensive - the freelancer is glad the client wants more, and more has a price. > "Great idea - I can definitely do that. It's outside what we scoped in the SOW, so let me write it up as a quick change order so we're both clear on cost and timing. For [FILL: the request], it'd be $[FILL] and add [FILL: X days / it'd slot into next month's hours]. Want me to send that over for a yes?" Then send the one-paragraph change order per the SOW's clause: description, price, schedule impact, sign-off line. Price it at the freelancer's standard add-on rate - Maya uses $150/hr, the same additional-rounds rate in her SOW - never at a discount "because they're already a client." Two outcomes, both wins: they sign (paid work) or they drop it (scope defended), and either way the client learns requests have prices, which prevents the next three. ### Step 5: The relationship-preserving no For requests the freelancer cannot or should not take even as paid work (outside their competence, ethically off, or capacity-breaking past the 80 percent utilization red line from retainer-pricing-calculator): > "I want this to go well for you, and honestly this piece is outside what I'm best at - I'd be charging you to be mediocre. [FILL: referral / 'I can recommend someone who does exactly this.'] Where I can add real value is [FILL: in-scope alternative], and I'd rather over-deliver there." The structure: affirm the goal, decline the task with a reason that serves the client, redirect to strength. Never a bare "that's not in the contract" - technically true and relationally corrosive. ### Step 6: Watch the retainer burn rate On retainers, creep hides in hours instead of deliverables. Track consumed hours weekly and surface them in the budget/hours block of client-status-reporting - creep against a visible number rarely becomes a dispute. At 80 percent of monthly hours consumed with more than a week left, flag it in that week's report and offer the choice: defer to next month or add hours at the stated rate. If the retainer overruns 2 consecutive months, the tier is mis-sized - go to productized-service-designer to re-scope, or raise-your-rates-playbook if utilization is the real problem. ## Worked contrast: the same request, two ways Client, day 20: "Love the new templates! Could you also design the trade-show booth backdrop? Should be quick for you." - **Bad (silent yes):** Maya spends 9 hours on the backdrop, blows past her 36 retainer hours, delivers her actual scope late, and the client - told nothing - now believes environmental design is included. Effective rate drops, resentment starts. - **Good (the process):** Booth design is on her SOW exclusions list, it is far over 30 minutes, and her courtesy yes went to a favicon tweak in week 2. She runs the Step 4 script; the client signs a $1,350 change order (9 hrs x $150) slotted after this month's deliverables. Revenue up, scope intact, client happy - and now aware that requests are welcome and priced. ## Concrete thresholds - New-request test verdict within 1 business day. - Courtesy budget: one yes per project or retainer quarter; courtesy ceiling ~30 minutes; always granted visibly. - 2 revision rounds standard (per statement-of-work-writer); round three is a change order. - Change orders at the standard add-on rate, never discounted; no out-of-scope work before sign-off. - Retainer flag at 80 percent of hours consumed with over a week remaining; re-scope after 2 consecutive overrun months. ## Deliverable A verdict and artifact for each incoming request: in-scope (do it), courtesy (granted with the visible-flag language), or a sent change order with price and schedule - plus a running courtesy-budget and hours log the freelancer can consult before answering the next "quick thing." ## Do NOT - Do not answer scope-adjacent requests instantly in chat; classify first - the reflexive "sure!" is where margins die. - Do not grant courtesies silently; unflagged generosity is indistinguishable from included scope. - Do not cite the contract as the first move ("per section 2..."). The script leads with enthusiasm and clarity; the SOW is the backstop, not the opener. - Do not discount change orders for existing clients; it teaches that pushing scope lowers prices. - Do not treat a climbing pattern of change orders as a nuisance - three or more accepted change orders on one engagement means the client wants a bigger tier; upgrade them via productized-service-designer. ## Quality bar The defense is working when: every request in the log has a verdict within a day; at most one unpaid courtesy exists per project; every out-of-scope yes has a signed change order behind it; and retainer hours were surfaced to the client before hitting 100 percent, not after. ## Neighbors statement-of-work-writer writes the clauses this skill enforces. client-status-reporting is where hours and change orders get surfaced weekly. Repeated creep pressure with high utilization is a pricing signal - see raise-your-rates-playbook.