Scope Creep
Scope creep is the gradual growth of a project beyond what was originally agreed, through extra pages, features or revisions added without a matching change to the budget or timeline. On web design projects it usually arrives as small, reasonable-sounding requests that add up to unpaid work.
How Scope Creep Happens
Scope creep rarely starts with a big ask. It starts with “while you’re in there.” A client asks for one more page, then a newsletter signup, then a third round of changes to the homepage. Each one is small, so you say yes, and by launch you’ve done a week of work nobody is paying for.
Common sources on web projects:
- A scope that says “website” instead of listing pages and features.
- Unlimited revisions, or no stated number of revision rounds.
- Late content. Copy that arrives after the design is done often means redesigning around it.
- New stakeholders who join near the end with their own opinions.
Scope Creep on Squarespace Projects
Squarespace makes some requests feel smaller than they are. Adding a page or a block takes seconds, so clients assume a new section takes seconds too. It doesn’t, once you count the copy, images, layout on mobile and SEO settings.
Features like online stores, member areas and scheduling also sit one click away in Squarespace. Each can turn a brochure site into a much bigger project, so name them in your scope as included or not included.
The handoff is another weak point. If the client can edit the site themselves, decide in advance whether fixing something they changed after launch is part of the project or new work.
How to Keep Scope Under Control
- Write the scope as a list: pages, features, number of revision rounds, and what happens after launch.
- Treat anything outside that list as a change request, with a price and a timeline before you start.
- Collect feedback in batches instead of one message at a time.
- Offer a care plan for ongoing changes after launch, so they have a home that isn’t the original project.
The full process is in our guide to preventing scope creep on web design projects.
Bridge helps at the request stage, not the contract stage. When a client asks for something extra, you can set that task to Fixed cost or Hourly and the client pays through your Stripe account before or after the work. Bridge doesn’t write contracts or proposals, so your scope document still lives elsewhere. See client payments.
Common Mistakes
- Saying yes to small extras without writing them down, which makes it awkward to charge for the tenth one.
- Waiting until the end of the project to bring up extra costs.
- Treating every extra request as scope creep. Some are worth doing for free, as long as you decide that on purpose.
Common Questions
What is an example of scope creep in web design?
A client hires you for a five-page site, then asks for a blog, an online store and a fourth round of homepage changes, all without changing the price or deadline.
How do you politely tell a client something is out of scope?
Point to the agreed scope, say the request isn’t included, and give a price and timeline to add it. Clients usually accept a clear quote more easily than a vague no.
Is scope creep always bad?
Not always. Small favors can be good for the relationship. It becomes a problem when the extra work is unplanned, unpaid and pushes back the deadline.
Chat directly
on Squarespace.
Bridge helps you stay connected with the clients you manage. Chat directly and make every conversation count.
