In this article · 6 sections
A website that was meant to take two weeks is still unfinished after three months. Both sides are frustrated: the owner thinks the agency is slow, and the agency feels the project keeps changing. The cause is usually scope creep: many small additions that, together, double the work.
Here's how to recognise it and keep your project on track.
What scope creep looks like
- "Can you add a page for each of our 20 cities?"
- "Let's add online booking as well."
- "My brother thinks the colours should be different." (after design approval)
- "We decided to add Hindi and Punjabi versions."
Each request sounds small. But a booking system or three language versions can be as much work as the original website.
Why it happens
- The brief was vague. If it wasn't written down, nobody can say what was agreed.
- Too many decision-makers. Feedback from five people arrives at different times and contradicts itself.
- Ideas arrive late. Seeing the site live sparks new ideas. That's natural, but it needs a process.
- Content arrives late. The design is approved, but text and photos arrive weeks later, sometimes in a completely different shape.
How to prevent it
Write down the scope
List pages and features before work begins. Our website brief template helps.
Name one decision-maker
One person collects feedback from everyone else and sends a single, combined list. This alone can halve a project's timeline.
Give feedback in rounds
Instead of sending changes one message at a time over two weeks, review the whole design and send all comments together. Agree on a number of revision rounds, usually two, before work starts.
Be specific
"Make it more premium" is hard to act on. "Use a darker background in the hero, larger headings and fewer colours" can be done in an hour. Screenshots with arrows help a lot.
Keep a "phase 2" list
When a new idea comes up, ask: "Is this needed for launch?" If not, add it to a phase 2 list. Launch first, see what customers actually use, then build phase 2. Many phase 2 ideas turn out to be unnecessary.
Send content early
Text, photos, logo, prices and contact details should be ready before design starts, or at least before development. Placeholder text often hides layout problems that show up later.
When the scope genuinely needs to change
Sometimes the business changes mid-project: a new service, a new branch. That's fine. Ask the agency for a written change estimate (extra cost and time), approve it, and update the timeline. Treating changes as a formal, small step keeps everyone honest.
A realistic timeline for a small business site
| Stage | Typical time |
|---|---|
| Brief and quote | 1–3 days |
| Content collection | Depends on you |
| Design and first review | 3–5 days |
| Revisions | 2–4 days |
| Development and testing | 3–7 days |
| Launch and handover | 1 day |
The biggest variable is content. Teams that have everything ready launch in about two weeks; teams that don't can take months.
The payoff
A focused launch gets your website working for you sooner. Every week a finished website sits waiting for "one more change" is a week of lost enquiries.
We plan every project with a fixed scope, two revision rounds and a phase-2 list. Start your project with a clear plan.