How to Write a Website Brief: A Practical Guide for UK SMEs

Back to Blog

Commissioning a new website is one of the biggest digital investments a small business will make. Yet many projects go off track not because the developer did a poor job, but because the brief was vague, incomplete, or never written down at all. A well-crafted website brief is the single most effective way to ensure you get a site that actually serves your business. It saves time, reduces costly revisions, and gives your developer the clarity they need to deliver something you're genuinely happy with.

What Is a Website Brief and Why Does It Matter?

A website brief is a short document that outlines what you need from your new website. Think of it as the foundation of the entire project. Without one, you're essentially asking a builder to construct a house without blueprints and then wondering why the kitchen ended up where the bathroom should be.

A good brief doesn't need to be technical. It needs to be clear. It tells your developer who your customers are, what you want the site to achieve, and what success looks like. According to a 2024 survey by Clutch, 37% of small businesses cited "miscommunication" as the primary reason for project overruns. A written brief eliminates most of that risk before a single line of code is written.

Key takeaway: You don't need to be a web expert to write a brief. You just need to know your business, your customers, and your goals.

The Essential Sections Every Brief Should Include

You don't need a 40-page document. A strong brief for an SME website can be as short as two or three pages. Here are the sections that matter most:

• About your business: A short summary of what you do, who you serve, and what makes you different. A joinery firm in Cheshire serving commercial fit-outs has very different needs from a beauty salon in Manchester booking individual appointments.
• Project goals: What should the website actually do? Generate enquiries? Sell products? Provide information to existing customers? Be specific.
• Target audience: Describe your ideal customer. Are they searching on their phone during a lunch break, or researching suppliers at a desk? This shapes everything from design to content.
• Scope and pages: List the pages you think you'll need. Home, About, Services, Contact is a starting point, but consider whether you need a blog, case studies, a booking system, or a client portal.
• Budget and timeline: Being upfront about budget helps your developer propose realistic solutions rather than guessing. A rough timeline (even "we'd like to launch before September") is equally useful.
• Examples you like: Share two or three websites you admire and explain why. "I like the clean layout" is far more helpful than "make it modern."

Key takeaway: Structure your brief around these core sections and you'll give any developer a solid foundation to quote accurately and plan effectively.

Common Mistakes That Derail Projects

Even well-intentioned briefs can cause problems if they fall into a few common traps. Here's what to watch out for:

Being too vague about goals. "We want a professional-looking website" tells a developer almost nothing. Compare that with "We want to increase enquiries from local businesses by 30% over six months." The second version gives everyone a target to work towards.

Ignoring content. Many SMEs focus entirely on design and forget that someone needs to write the words, take the photos, and organise the information. If you don't have content ready, say so in the brief. A good developer can help you plan for it, but only if they know it's needed.

Design by committee. Getting input from your team is sensible. Having seven people with conflicting opinions approve every design choice is a recipe for delays. Nominate one or two decision-makers and name them in the brief.

Key takeaway: Clarity and honesty in your brief prevent the "that's not what I meant" conversations that cost time and money later.

How to Define Success Before You Start

One of the most overlooked parts of any website brief is defining what success actually looks like. Without this, you'll launch a site and have no way of knowing whether it's working.

Consider a plumbing company in Warrington that launched a new website last year. Their brief stated a clear goal: "We want at least 20 contact form enquiries per month within three months of launch." That single sentence shaped the entire project, from prominent calls to action on every page to a simplified contact form and local SEO strategy. Three months in, they were hitting 28 enquiries per month and knew exactly where the leads were coming from.

Your success metrics don't need to be complicated. They might include:

• Number of enquiries or quote requests per month
• Reduction in phone calls asking basic questions (because the website answers them)
• Online bookings replacing manual diary management
• Improved search engine rankings for key local terms

Key takeaway: Define one to three measurable outcomes in your brief. They'll keep the project focused and give you a way to judge return on investment after launch.

What Happens After You Send the Brief

A good developer won't just read your brief and start building. They'll come back with questions, suggestions, and possibly a few challenges to your assumptions. This is a positive sign. It means they're thinking about your project properly rather than just ticking boxes.

Expect a discovery conversation where your developer digs into the detail. They might suggest features you hadn't considered, or advise against something that sounds appealing but won't serve your users well. For example, you might want a full-screen video on your homepage, but if 70% of your visitors are on mobile with patchy 4G, that video could actually drive people away.

The brief isn't a contract set in stone. It's a starting point for collaboration. But without it, that collaboration has no foundation, and projects drift, budgets balloon, and timelines slip.

Key takeaway: Treat the brief as the beginning of a conversation, not the end of one. The better your starting point, the more productive that conversation will be.

Getting Started With Your Website Brief

Writing a website brief doesn't require any technical knowledge. It requires clarity about your business, your customers, and what you want to achieve. Spend an hour or two putting your thoughts on paper before you approach any developer, and you'll save yourself weeks of back-and-forth later. You'll also be in a much stronger position to compare quotes, because every developer will be responding to the same clear set of requirements.

If you're planning a new website or a redesign and want help turning your ideas into a clear brief, we're always happy to have an initial conversation. Get in touch with Task Ox and let's make sure your next web project starts on the right foot.