Most website budgets aren’t lost in the build. They’re lost before it starts, when a founder hands over a brief that says “modern, clean, a bit like our competitor’s, but better”.

That brief feels finished. It isn’t. Every gap in it gets filled later, by someone else’s guess, and you pay for every guess that turns out wrong.

This is what we think a founder should decide and write down before paying anyone to build a website, whether that’s an agency, a freelancer or an AI builder.

Why vague briefs cost money

Unclear scope is one of the most common reasons projects go wrong. In PMI’s 2018 Pulse of the Profession research, 52% of projects completed in the previous year experienced scope creep or uncontrolled changes to scope, up from 43% five years earlier. An earlier PMI study found that 47% of unsuccessful projects missed their goals because of poor requirements management.

The pattern scales up too. McKinsey’s research with the University of Oxford, covering more than 5,400 IT projects, found large projects ran 45% over budget on average and delivered 56% less value than expected. Your website is not a multi-million pound IT programme, but the mechanics are the same: unclear goals and shifting requirements turn into change requests, rework and invoices.

On a website project, that usually looks like this:

A page nobody planned for appears halfway through the build.

The booking system you assumed was “included” turns out to be a separate job.

The copy arrives late, so the design gets redone around it.

Launch day comes and nobody can say whether the site is working.

AI builders and templates won’t fix a weak brief

AI website builders and template sites are quick. They also build what you ask for, and not much else. Ask for “a professional site for my consultancy” and you’ll get one that looks like thousands of others, because that’s what the prompt described.

A poor brief used to get you a poor site slowly. Now it gets you one faster. The thinking still has to happen somewhere, and it’s cheaper to do it before anyone starts building.

What to decide before you pay anyone

1. The commercial goal, and how you’ll measure it

Start with money, not looks. What should the website do for the business? More enquiries, more sales, more booked calls, a higher conversion rate on a product you already sell?

Pick one or two goals and write down how you’ll measure them. “20 qualified enquiries a month through the contact form” is a brief. “Look more premium” is a mood.

If you don’t know your current numbers, say so. That’s useful information, and it tells whoever you hire that tracking needs setting up properly.

2. Who the site is for, and what they need to do

Describe the people you want to reach and what they need to do on the site. Book a call? Buy? Download something? Check your credentials before a pitch meeting?

Be specific. “Founders of service businesses who’ve outgrown a DIY site and want to book a call” gives a designer and a copywriter far more to work with than “SMEs”.

First impressions happen fast. Research from Google found people form a gut feeling about a website in under 50 milliseconds, and they tend to prefer designs that look simple and familiar for their category. Knowing who your visitors are is how you get that first impression right for them.

3. The pages and content you actually have

List the pages you need, and be honest about the content for each. Do you have the copy, the photos, the case studies, the testimonials? Or are you planning to “sort that out later”?

Missing content is one of the most common reasons website projects stall. If you need copywriting or photography, put it in the brief so it’s priced and planned, not discovered in week six.

4. Integrations and what you already pay for

Write down every tool the site needs to work with: your CRM, email platform, booking system, payment provider, shop, analytics. Note what you already pay for, so nobody builds or sells you something you already have.

This is where surprise costs hide, and a two-line note saves them.

5. Budget and timeline, stated honestly

Say what you can spend. A good agency or freelancer uses your budget to propose what genuinely fits, not to squeeze a full site into a small number or pad a simple one out. Hiding the budget doesn’t get you a better price. It gets you proposals that miss.

Give a real deadline too, and explain why it matters. A launch tied to an event is different from “as soon as possible”.

6. What success looks like after launch

Decide now what you’ll check one, three and six months after launch. Enquiries, conversion rate, sales, page speed. Then decide who looks at those numbers and what happens if they’re off.

A website isn’t finished at launch. That’s when you find out whether it works.

Your website brief checklist

Before you send a brief to anyone, check it covers:

One or two commercial goals, with how you’ll measure them

Your current numbers, or a note that you don’t have them

Who the site is for and the main actions they need to take

A page list, with the content you have and the content you don’t

Every tool and integration, and what you already pay for

Your real budget

Your real deadline, and why it’s that date

What you’ll measure after launch, and who owns it

When the brief is too big to write alone

For a small job, the checklist above is usually enough. For a full design and build, there’s often more you don’t know yet: what your analytics say, what your competitors are doing, what your current setup will and won’t support.

That’s what our N0BS Diagnostic is for. On larger website projects, it gives you a written brief, a sitemap and a firm price in 5 working days, catching what you didn’t know before it costs you thousands. The brief is yours, so you can take it to another agency if you’d rather.

If you want a rough idea of cost first, the Instant Quote tool on our pricing page gives you a range. And if you’d rather talk it through, get in touch.

Sources

Project Management Institute (PM Network), “Scope Patrol”, 2018 (citing PMI Pulse of the Profession 2018). https://www.pmi.org/learning/library/scope-creep-rising-11308

Project Management Institute, “Requirements Management: A Core Competency for Project and Program Success” (Pulse of the Profession in-depth report), 2014. https://www.pmi.org/learning/thought-leadership/pulse/core-competency-project-program-success

McKinsey & Company with the University of Oxford, “Delivering large-scale IT projects on time, on budget, and on value”, 2012. https://www.mckinsey.com/capabilities/tech-and-ai/our-insights/delivering-large-scale-it-projects-on-time-on-budget-and-on-value

Google Research (Javier Bargas-Avila), “Users love simple and familiar designs: Why websites need to make a great first impression”, 2012. https://research.google/blog/users-love-simple-and-familiar-designs-why-websites-need-to-make-a-great-first-impression/