Built Beyond You ยท Free Tool
The Cyber
Scope Creep Script.
3 lines your team can use when a project starts expanding after the quote is accepted.
Scope creep rarely starts dramatically.
It starts with: "Could you just..." "While you're in there..." "It should only take a minute..."
The client is reasonable. The request sounds reasonable. But if your team doesn't know what to say next, the work routes back to you.
Use this before another small request becomes founder-funded delivery.
The phrases that usually start it
"Could you just..."
Sounds small. Often isn't.
"While you're in there..."
Assumes the work is already paid for.
"Can we add..."
Skips the conversation about what that changes.
"It should only take a minute..."
The client's estimate of your delivery time.
The 3 scripts. Tap to open. Copy to use.
1
When to use
The request is clearly outside the agreed scope
โผ
"Happy to look at this. It sits outside the agreed scope, so before we move on it, we'll map the impact on timeline, fee and delivery. Then you can decide whether to add it properly or keep the current project as agreed."
Why it works
Doesn't say no.
Doesn't absorb the work.
Moves the decision back to timeline, fee and delivery impact.
2
When to use
The request sounds small but may create extra work
โผ
"We can check that. Before we treat it as a quick addition, we'll confirm whether it changes the original delivery path, creates extra review work, or affects the agreed timeline. If it does, we'll give you the options before anything changes."
Why it works
Slows the automatic yes.
Gives the team permission to check.
Stops "quick" becoming invisible work.
3
When to use
The team needs to escalate before answering
โผ
"I don't want to give you a quick answer and create confusion later. I'm going to check this against the agreed scope and come back with the right next step: include it, price it separately, or park it for a later phase."
Why it works
Protects the team from guessing.
Gives the client confidence.
Makes escalation sound professional, not hesitant.
The decision rule. Check these 3 things first.
1
Does it change the outcome?
Yes: needs a scope decision before anyone says yes.
2
Does it change the work required?
Yes: needs a timeline or fee decision.
3
Does it require your judgement?
Yes: needs escalation before the client gets an answer.
Pick the right response
Include it
Already covered, genuinely small, doesn't affect timeline, quality or margin.
Price it
Adds work, complexity, meetings, reporting, review or delivery load.
Pause it
Scope is unclear or the request could pull the project off track.
Escalate it
The team needs founder judgement before committing to anything.
deirdremartin.ie ยท The Built Beyond You System
