● Free guide

How to Handle Scope Creep as a Freelancer

"Can you just also…?" is where freelance profit goes to die. Here are the exact responses and AI prompts that protect your price, your timeline, and the relationship — without sounding difficult.

Rule 1: separate "in scope" from "a new request"

Before replying, decide: is this covered by the agreed deliverables? If yes, do it. If no, it is a new request and gets a new quote — never a silent favor.

Template: hold the line kindly

That's a great addition. It wasn't part of the original scope ([link deliverables]), so I'll treat it as a small add-on: $[X], ~[time]. Want me to fold it in now, or keep it for a phase 2?

Template: scope doc that prevents it

Turn this request into a clean Scope of Work: "[REQUEST]".
Output: Objectives, Out-of-scope, Deliverables, Revision policy (max 2 rounds), Timeline, Fixed price $[X]. Flag any ambiguity I must confirm.

AI prompt for any creep message

A client asked for extra work beyond our agreed scope: "[MESSAGE]". Draft a calm, firm 3-sentence reply that (1) confirms I'll handle it, (2) states it's a paid add-on at $[X] with [time], (3) offers to start once approved. No blame, no apology.