What seven years of freelance taught me about scope.
Scope creep isn't a contract problem — it's a conversation problem. Here's how I learned (slowly, painfully) to keep projects on the rails without turning every change request into a negotiation.
I spent the first three years of freelance writing better contracts. Cleaner deliverable lists, tighter milestones, sharper change-order language. None of it stopped projects from going sideways. The fourth year, I started having different conversations — and almost everything got easier.
Scope is a story two people tell each other about what's going to happen. When the story drifts, the project drifts. The contract is just where the story is written down.
The three failure modes I kept hitting
- Implicit assumptions. The client thought "responsive design" included tablet. I thought it meant phone + desktop. Neither of us checked.
- The ambiguous "small change." "Can we just add a search field?" is two days of work and a re-architecture of the data layer.
- Unspoken success criteria. The deliverable shipped. The client was unhappy. We'd never agreed on what "good" looked like, only on what "done" meant.
The questions I ask now
Before I quote, I make sure both of us can answer these out loud:
- What does success look like 90 days after launch? Not at handoff. After.
- What's deliberately out of scope? A "no" list is more clarifying than a "yes" list.
- Who decides when something is done? One person. Named.
- What do we do when we disagree? Decide the process before you need it.
The cheapest hour you'll spend on any project is the one before kickoff, asking the questions that feel almost too obvious to ask.
Mid-project: the "small change" reflex
When a client asks for a small change, I now do three things, in order, every single time:
- Acknowledge. "Got it — let me think about what that involves."
- Translate. "Here's what that touches: X, Y, and Z. Two of those are within scope, one isn't."
- Offer a path. "We can do A this week without affecting timeline, or B as a follow-up. Which would you prefer?"
That third step is the one I missed for years. Saying no without offering a yes feels rigid; saying yes to everything is how you bleed margin. Offering two specific paths makes the conversation collaborative instead of confrontational.
The end-of-project ritual
Two weeks after every project, I send the client a short email. It says three things:
- What I'm proud of from the project.
- One thing I'd do differently next time.
- One question I'm curious about — usually about how the work has landed since launch.
About 60% of the time, that email turns into a follow-on engagement. The other 40% of the time, it turns into a referral six months later. Either way, it's the highest-ROI fifteen minutes of any project I run.
Closing thought
The freelancers I respect most aren't the ones with the airtight contracts. They're the ones whose clients describe them as "easy to work with" and mean it as the highest praise. That reputation isn't built in clauses. It's built in conversations — the ones you have before, during, and after the work, especially the awkward ones.
Get good at the conversations. The contracts get a lot less interesting.
