Scope creep almost never announces itself. It arrives as a reasonable-sounding request, and by the time you recognize the pattern, you’re already three unpaid additions in. These six scenarios are ones most freelancers encounter — and each one has a specific way it could have been handled.
Scenario 1: The extra page (web design)
You quote a 5-page website: Home, About, Services, Blog index, Contact. The client signs off. Three weeks in, they say: “We actually need a Testimonials page too — can you add that before we launch?”
This is the most common scope creep scenario in web design. The client isn’t being malicious — they just didn’t think of it until the site was taking shape. The problem is that “5-page website” is in the proposal, and “6 pages” isn’t.
What it costs: One full page of design, responsive layout, and copy integration. Depending on the project, that’s 3–6 hours — $225–$450 at a $75/hr rate.
How to handle it: “That’s not included in the original 5-page scope. A testimonials page would be a change order — I can estimate it at around $X and add it to the timeline. Want me to put that together?” If you have your original Waco3 proposal to reference, you can pull up the deliverables list and show them exactly what was agreed on.
Prevention: List the specific page names in the proposal, and add a note: “Additional pages are available as change orders at $X per page.”
Scenario 2: The revision that became a rewrite (copywriting)
You quote a landing page. The brief is clear, you deliver the copy, and the client sends back “a few notes.” The notes are a complete restructuring of the argument, a new tone, three new sections, and a request to cut the existing hero section entirely.
This isn’t a revision. It’s a new brief. But the original scope said “2 rounds of revisions,” and the client believes they’re within their allotment.
What it costs: A full rewrite is often 60–80% of the original project cost in time.
How to handle it: “A revision round means incorporating your feedback on the existing draft — structural changes and new sections are outside what’s included. I can handle these as a change order, or we can prioritize which changes are most important within the original revision scope.” You’re not saying no to the feedback — you’re distinguishing between revision and redirection.
Prevention: Define what a revision round means: “One round of revisions = one set of consolidated feedback applied to the existing structure. New directions or structural changes are handled as change orders.”
Scenario 3: Strategy becoming implementation (consulting)
You’re hired to develop a marketing strategy — two weeks of research, a written recommendations document, and a presentation. Somewhere in week two, the client starts asking you to “just start on the email sequences” and “set up the automation” while you’re finishing the strategy.
What it costs: Ongoing implementation work is entirely outside the engagement, and it has no defined end point.
How to handle it: “I want to make sure we finish the strategy deliverable well — implementation is a separate engagement and I’d want to scope that out properly before starting. Let me complete the strategy document first, and we can talk about next steps from there.”
Prevention: Define what the engagement produces: “This project delivers a written strategy document and presentation. It does not include implementation of the recommendations.”
Scenario 4: Feature additions (development)
You’re three weeks into a four-week build. The spec has a defined feature list. The client now wants to add user authentication, export to PDF, and an email notification system — all described as “quick additions.”
None of these are quick. Each one is a multi-day feature. But the client doesn’t know that, and if your original proposal didn’t specify that the feature list was locked, they have a reasonable case that these are part of “building the app.”
What it costs: User authentication alone can be 10–20 hours depending on the stack. The full list is likely 30+ hours of additional work.
How to handle it: “These are substantial features that weren’t in the original spec. I want to build them right rather than rush them in — let me spec out each one and we can decide which to include in a change order versus phase 2.”
Prevention: Include the feature list as a numbered spec in the proposal. Add: “Features not listed in the spec are out of scope and will require a change order.”
Scenario 5: The extra brand deliverable (branding)
You’re hired to design a logo. The deliverables: primary mark, color palette, typography, and a style guide. Final files are delivered. The client then asks for a “secondary logo for dark backgrounds,” a favicon version, and a set of social media templates.
These are legitimate brand needs — but they’re not in the original scope.
What it costs: A secondary logo variation and dark-background version: 3–5 hours. Favicon optimization: 1 hour. Social media templates: varies widely but easily 8–15 hours.
How to handle it: “Those are natural next steps for the brand — they’re not included in the original delivery, but I can put together a package estimate if you’d like to continue. What’s your priority?”
Prevention: Be explicit about what format files are delivered in and what isn’t included: “This project delivers the primary logo mark in 5 formats. Dark-background versions, icon variants, and social templates are separate deliverables.”
Scenario 6: Ongoing “quick questions” (any field)
This one is subtler. You’ve finished the project, sent the final invoice, and the client keeps emailing with questions, requests for “minor updates,” and asks to “hop on a quick call.” None of these are big asks individually. Collectively, they’re ongoing support work you aren’t billing for.
What it costs: If each interaction takes 20–30 minutes and happens twice a week, that’s 3–4 hours a month of unbilled work — indefinitely.
How to handle it: “I’m glad the project was useful — for ongoing support and updates, I offer a monthly maintenance package. I can send over details if you’d like to explore that.” This converts an open-ended drain into a recurring revenue stream.
Prevention: Include a post-project support clause in your contract: “This project includes X days of post-delivery support. Ongoing support after that period is available at $X/hour or as a monthly retainer.”
The pattern across all six scenarios is the same: a vague original agreement creates room for the client to reasonably expect things you didn’t plan to include. The fix in each case starts at the proposal — with deliverables specific enough that the line between included and extra is clear from day one.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
