A simple framework for scoping a website project

Why projects fail

Across hundreds of website design projects we've delivered, the failure pattern is consistent: scope creep. The brief that started as a 12-page brochure site grew to include a customer portal, a blog, an integration with a CRM, multilingual support, and a custom calculator — without anyone re-evaluating the original budget or timeline.

Good scoping means having clear answers to a small number of questions before the project starts. Get these right and the rest follows naturally.

The five-question framework

We walk every new client through these five questions during discovery. Skip any one and you're setting yourself up for surprises later.

Question 1: What is this website for?

Surprisingly few briefs answer this directly. "A new website" isn't a goal. "Generate 30 qualified leads a month from organic search" is a goal. "Reduce inbound support enquiries by 40% by adding self-service content" is a goal.

If you can't articulate the website's primary job in one sentence, you're not ready to brief an agency. The goal shapes every subsequent decision — design, content, technology.

Question 2: Who is it for?

"Anyone interested in our products" is too broad. Real audiences have specific characteristics: who they are, what they're looking for, what objections they bring, what would make them act.

Two or three concrete user profiles — with names, jobs, and motivations — clarify content priorities far more than vague audience descriptions.

Question 3: What does success look like?

Specific, measurable outcomes. Not "more enquiries" but "30 form submissions a month from organic search by month 6 post-launch". Not "better SEO" but "ranking top-3 for ‘website design Bury St Edmunds’ within 12 months".

Without measurable success metrics, no one knows whether the project worked. And without that knowledge, you can't make sensible decisions about where to invest next.

Question 4: What's in scope — and what isn't?

Every brief should have an explicit "not in scope" section. This is where you record the features that came up in early conversations but won't be in this build — the customer portal, the multilingual support, the custom calculator.

Documenting what's not being built is at least as valuable as documenting what is. It prevents scope creep and makes it explicit when new requests are genuinely new (and need their own budget).

Question 5: What's the realistic budget and timeline?

Both should be realistic, not aspirational. A budget set 50% below market rates produces compromised work. A timeline that doesn't allow for proper discovery, design, build, testing, and content production sets up everyone for failure.

If your dream scope doesn't fit your realistic budget, the right answer is reducing scope — not squeezing the same scope into less money. A focused, well-executed v1 beats a sprawling, half-finished v1 every time.

What an agency expects from a brief

When clients come to us with answers to those five questions, the project starts well. When they don't, our first job is essentially walking them through these questions before any design work can begin.

Either approach is fine — but answering the questions yourself gets you better quotes from agencies, because we can be more specific about effort and cost.

When to involve an agency in scoping

If you can answer questions 1-3 yourself but struggle with 4-5, that's the right time to bring in an agency for a paid scoping engagement. Two or three days of structured workshops can save weeks of false starts later.

If you can't even answer 1-3 confidently, do that thinking yourself first. No agency can replace the strategic clarity that has to come from the business owner.

Frequently asked questions