Chapter 6: Build Your Scope Creep Detector Gem
Marcus and the 47-Email Thread
The email thread was 47 messages deep.
Marcus scrolled through it again, trying to understand what the client actually wanted. Three weeks into a $45K brand film project, and they were still debating the creative direction.
"We love the modern feel, but can you make it more... classic?"
He'd asked for clarification. They'd sent more words that clarified nothing.
His editor was waiting for direction. His producer was waiting for him to align the client. His CEO was waiting for him to close this phase so they could invoice.
Everyone was waiting for Marcus.
This is what he'd wanted, right? Creative Director. The title on his door. The seat at leadership meetings. The equity stake.
Except he'd spent zero hours this month actually being creative. He was a translation layer—converting client confusion into team direction—and he was burning out doing work that felt like it should be systematizable.
"Just tell me what you want," he muttered at the screen. "Tell me in clear terms so I can tell my team in clear terms."
But clients don't work that way. They speak in feelings. His job was to translate feelings into specifications.
What if something could help him do that translation?
The Margin Killer
Here's how studio margins die:
- Client signs off on project scope
- Revision requests come in
- Each request seems small ("can you just...")
- You say yes to be accommodating
- Project takes 2x longer than planned
- You're frustrated, client thinks they got a deal
The problem isn't the clients. They don't know where the line is. The problem is that YOU don't have a systematic way to evaluate whether a request is in scope.
The Scope Creep Detector solves this.
What You're Building
Input: A client revision request (email, message, or call notes)
Output: Assessment in three categories:
- IN SCOPE: This falls within what was agreed. Do it.
- OUT OF SCOPE: This is new work. Quote it separately.
- NEEDS CONVERSATION: This is ambiguous. Clarify before deciding.
Plus: A suggested response to the client for each category.
Exercise 6.1: Create the Scope Creep Detector Gem
Goal
Build the Gem with minimal hand-holding.
Time: 10 minutes
Steps
Create a new Gem named "Scope Creep Detector"
Write instructions using the formula from Chapter 4:
- Role
- Task
- Output Format
- Style Guidelines
- Business Context
Your output format should categorize requests into exactly three buckets
Include suggested client responses for each category
Use this as your starting template (customize it):
## Role
You are a scope assessment assistant for a creative studio. You help evaluate whether client revision requests fall within the original project scope.
## Task
When I paste a client revision request, assess whether it's:
- IN SCOPE (part of what we agreed to do)
- OUT OF SCOPE (new work requiring additional budget)
- NEEDS CONVERSATION (unclear, need to clarify before deciding)
## Output Format
**ASSESSMENT: [IN SCOPE / OUT OF SCOPE / NEEDS CONVERSATION]**
**REASONING:**
[2-3 sentences explaining why you categorized it this way]
**KEY FACTORS:**
- [Factor 1 that influenced your assessment]
- [Factor 2]
**SUGGESTED RESPONSE TO CLIENT:**
[A professional message I can copy and send]
## Style Guidelines
- Be direct and confident in your assessment
- If there's genuine ambiguity, choose "NEEDS CONVERSATION" - don't guess
- Suggested responses should be warm but protect our boundaries
- Keep total output under 150 words
## Important Context
For context on what's typically "in scope" for creative projects:
- IN SCOPE: Color corrections, minor text changes, timing adjustments, file format changes
- OUT OF SCOPE: New concepts, additional locations, new interviews, different music, additional lengths
- GRAY AREA: "Can you add one more scene?" (depends on complexity)
## My Business Context
[Add your typical project types and common scope issues here]
- Save the Gem
Exercise 6.2: Test With Real Revision Requests
Goal
Validate the Gem on actual client communication.
Time: 10 minutes
Steps
Find 3 recent revision requests from clients (emails, messages, etc.)
Run each through the Scope Creep Detector
For each, assess:
| Request | Gem's Call | Your Call | Match? |
|---|---|---|---|
| #1: ________________ | _________ | _________ | Y / N |
| #2: ________________ | _________ | _________ | Y / N |
| #3: ________________ | _________ | _________ | Y / N |
- If the Gem and you disagree, who's right?
- You: The Gem needs better instructions
- Gem: You might be over-accommodating (this is common!)
Iterate if Needed
If the Gem consistently miscategorizes:
- Add more examples to the "Important Context" section
- Be more specific about your boundaries
- Include common phrases clients use that signal scope creep
Common Scope Creep Phrases
Train your Gem to recognize these patterns. Add them to your instructions if they're not catching them:
| Client Says | Usually Means | Category |
|---|---|---|
| "Can you just..." | Seems small, often isn't | Check carefully |
| "While you're at it..." | Adding to original scope | Likely OUT OF SCOPE |
| "We were thinking..." | New idea not in brief | OUT OF SCOPE |
| "One small change..." | Could be small, could be big | Assess specifics |
| "Actually, what if we..." | Direction change | NEEDS CONVERSATION |
| "This isn't quite what we imagined" | Misalignment with brief | Review original agreement |
Exercise 6.3: Test the Suggested Responses
Goal
Make sure the responses are actually usable.
Time: 5 minutes
Steps
Look at the "Suggested Response to Client" for each test
For each, rate:
| Response | Would you send as-is? | Edits needed? |
|---|---|---|
| #1 | Y / N | _____________ |
| #2 | Y / N | _____________ |
| #3 | Y / N | _____________ |
- If responses need heavy editing:
- Add tone guidance: "Sound helpful, not defensive"
- Add your typical phrasing
- Specify what kind of language your clients respond to
The Upgraded Scope Creep Detector
After testing, a strong version might look like this:
## Role
You assess client revision requests for [STUDIO NAME] to protect project scope and margins.
## Task
Categorize requests as IN SCOPE, OUT OF SCOPE, or NEEDS CONVERSATION.
## Output Format
**ASSESSMENT: [CATEGORY]**
**WHY:** [2 sentences]
**SUGGESTED RESPONSE:**
[Ready-to-send message]
## Categorization Guidelines
IN SCOPE (do without discussion):
- Requests matching original brief terms
- Minor adjustments clients typically expect
- Technical fixes (color, format, compression)
OUT OF SCOPE (new quote needed):
- Work not mentioned in brief
- "While you're at it" requests
- Additional deliverables
- New concepts or directions
NEEDS CONVERSATION (clarify first):
- Ambiguous requests
- "Can you just..." (need to understand scope)
- Client dissatisfaction with agreed work
## Response Tone
- Acknowledge their request positively
- Be clear about next steps
- Never make them feel wrong for asking
- If out of scope: frame as "happy to help with additional quote"
## My Boundaries
[List your specific common scope issues]
Why This Gem Matters Most
The Brief Builder saves time. The Scope Creep Detector saves money.
Consider: If you accidentally absorb 5 hours of out-of-scope work at $150/hour = $750 lost
If this Gem helps you catch one scope creep request per project, and you do 3 projects per month:
- Monthly protection: $2,250
- Annual protection: $27,000
This isn't theoretical. Studios consistently undercharge because they don't have a system for evaluating requests.
Exercise 6.4: Real-Time Practice
Goal
Use the Gem on a request that came in TODAY (or recently).
Time: 5 minutes
Steps
Check your email or messages for the most recent client feedback or request
Run it through the Scope Creep Detector
Do you agree with the assessment?
If you don't have a recent request:
- Check old projects for a request that caused friction
- Run it through and see if the Gem would have helped
Reflection
Would having this Gem have changed how you handled past scope issues?
Write one specific example: ________________________________________________
Knowledge Check
Before Chapter 7:
What are the three categories the Scope Creep Detector uses?
- ________________________
- ________________________
- ________________________
Did the Gem agree with your judgment on test requests? Your answer: __/__ (matching / total)
How much margin erosion might this Gem prevent annually? Your estimate: $________________________
Chapter Time: ~30 minutes
Next: Chapter 7 — Self-Assessment Checkpoint