A Conversion-Focused Web Design Brief

How to Write a Web Design Brief That Converts

A web design brief is the document that tells a designer what to build and why. It is the cheapest part of a website project and the most expensive one to get wrong. Most briefs describe a website: a page list, a few competitor sites the owner likes, a note about wanting it to feel modern and clean. Very few describe a result. A brief that never says what has to change in the business gives everyone on the project an equal right to an opinion, and the loudest opinion usually wins.

This guide covers what belongs in a conversion-focused brief, the order to work through it in, how to handle content and technical standards before they turn into delays, and how to tell when a brief is not ready to send. It pairs with our free template, The Conversion-Focused Web Design Brief, which turns all of this into 32 questions you can fill in and hand to any agency.

What a Conversion-Focused Brief Does Differently

The structure is the strategy. A conversion-focused brief is not a longer brief, it is a differently ordered one. Four things set it apart.

It starts with the business, not the sitemap. The first question is what has to change commercially, not how many pages there will be. Everything downstream is a trade-off, and you cannot judge a trade-off without knowing what the site is for.

It names one buyer. Sites written for everyone convince nobody. One named decision maker changes the tone, the page length, the reading level and the proof you need.

It commits to numbers before anyone designs anything. A baseline and a target turn a subjective review into an objective one. Without them, the project gets judged on taste at the end, which is the worst possible time.

It treats content and approvals as part of the build. These are the two things that actually delay web projects. Briefing them properly is not admin, it is scheduling.

Start With the Commercial Case

If you cannot say what has to change in the business, the project has no way of succeeding or failing. It just finishes. Four answers make the commercial case.

Say what has to change. Not “the site is outdated”. Something closer to “we win plenty of small jobs and almost none over $50k, and we need the site to make us credible to procurement teams at larger builders”. That single sentence sets the priority order for every decision that follows.

Write down your current numbers. Sessions a month, enquiries a month, conversion rate, average sale value. Rough is fine. Absent is not. Without a baseline there is no way to prove the project worked, and no way to spot it quietly going backwards. If you are not confident the numbers you have are accurate, fix that first, because a rebuild measured against broken tracking tells you nothing. This is what GA4 and GTM analytics consulting is for.

Work out what a lead or a sale is worth. This is the number that settles more arguments than any other, and most businesses have never calculated it. If a lead is worth $2,000, spending a week getting the enquiry flow right is obviously correct. If it is worth $40, it is not. It also tells you what the whole project is allowed to cost.

Define success at 90 days, and name who checks it. Pick two or three measures tied to the business, not ten tied to the dashboard. Enquiry rate, quote requests above a certain value, mobile load time. Then name the person who reviews them monthly. A named person and a named number stop the project being judged on whether the boss likes the shade of blue.

Name the Buyer and the Action

Once you know what the business needs, work out who has to be convinced and what you want them to do.

Describe one person, not an audience. Their role, roughly their age, where they are when they read your site, and how they buy. A facilities manager checking on a phone between site visits needs a different page to a homeowner researching on a laptop at night.

List what they are worried about before they contact you. Every unanswered worry is a reason to leave. Naming the top three tells the designer exactly what has to appear high on the page and what belongs next to the form. Most of the time it is not price. It is whether you are big enough, whether you will turn up, and whether the quote will hold.

Pick one primary action per page. Two competing calls to action split attention and both lose. Decide whether the win is a booked assessment, a phone call, a quote request or a purchase, and make everything else secondary. This matters most where the traffic is paid, which is why a dedicated landing page design usually outperforms sending ad clicks to a general service page.

Add a lower commitment option. Most first-time visitors will not buy today. Without a smaller yes, such as a pricing guide or a checklist, they leave with nothing and you have already paid for the click.

Agree the form fields in the brief. Every field costs you enquiries. Sales usually wants more, marketing wants fewer, and the argument is much cheaper to have now than after the form is built. Ask for what you need to make the next call. Ask for the rest on the call.

Design the handover, not just the form. Write down where the enquiry goes, who gets it, on what device, and how fast they respond. The best converting website in your industry cannot survive a two day reply.

Sort Proof and Content Before the Build Starts

Design earns attention. Proof earns the enquiry. Content is also the single most common reason web projects run late, and the section most briefs leave blank.

Audit the proof you already have. Reviews, client logos you have permission to name, licences and accreditations, project photography, staff credentials, years in business, volume handled. If it exists, the design should be built around it rather than having it added at the end. Our design portfolio is a useful reference for how much heavy lifting real work photography does compared to stock.

Assign the proof you do not have. Case studies and testimonials are slow because they need other people. Name an owner and a date at the start of the project, not the week before launch.

This is where the biggest gains usually sit. When we rebuilt the site for a national sports surface installer, the old one was a digital brochure that hid an impressive portfolio. The rebuild put that portfolio to work with a project map showing installations across Australia, plus a court visualiser that turned browsing into enquiries. You can read the full story of the Kangaroo Courts design build. Neither of those features came from a design trend. They came from knowing what proof existed and what the buyer needed to see.

Say who is writing the words, and whether it is their actual job. “We will handle the content ourselves” is the most expensive sentence in web projects. Not because it cannot work, but because it is almost never anyone’s real responsibility.

Be honest about what already exists. Reuse, rewrite and write from scratch cost very different amounts. An honest audit of the current pages is the difference between a quote that holds and one that does not.

Put a date on content, and a consequence. Agree up front what happens if a page is late. Do you launch without it, launch in stages, or move the date? Deciding now turns a vague delay into a simple decision.

Brief the Technical Standards, Not Just the Look

If it is not in the brief, it is not in the quote, and it will not be in the website. Five things belong here.

Name the platform and what has to stay. What it is built on now, who controls the hosting and the domain, what is licensed, and what was custom built by someone who has left. Access delays stall more projects than technical problems do. If you are staying on the same platform, say so, because a WordPress development project that inherits an existing theme is a different job to one that starts clean.

List the integrations. CRM, accounting, inventory, bookings, payments, email platform. Integrations are where budgets hide. One awkward connection can cost more than the rest of the build, and it is far better to find that out before the quote than after.

Set performance targets in writing. Core Web Vitals thresholds are a Largest Contentful Paint under 2.5 seconds, an Interaction to Next Paint under 200 milliseconds, and a Cumulative Layout Shift under 0.1, measured on real mobile visitors. Speed is not a technical nicety. In work Deloitte and 55 ran for Google, a 0.1 second improvement lifted progression from form to submission by 21.6% on lead generation sites. It is also cheapest to buy at build time rather than to retrofit later.

Put accessibility in the brief. In 2025 the Australian Human Rights Commission set out that organisations should conform with WCAG 2.2 at a minimum of Level AA. That guidance is not legislation, but the obligation it interprets is, and the Disability Discrimination Act 1992 covers private businesses providing goods and services, not just government.

Protect what already works. A redesign is a migration. Export your top landing pages by organic traffic and by conversions, and list the URLs that must be preserved. It takes ten minutes and it is the most effective way to stop a rebuild quietly undoing years of SEO work.

Decide Who Decides

Projects rarely fail on craft. They fail on decisions, or on the person who was never in the room turning up at the end.

Name the approver and one deputy. The most expensive person in a web project is the director who sees it for the first time two days before launch. Decide who signs off, who can stand in, and how ties get broken.

Consolidate feedback into one document per round. Three people sending separate comments on the same design is how a two round project becomes a five round one.

State the budget. Withholding it does not get you a better price. It gets you a proposal for a different project, and a comparison between quotes that are not comparing the same thing.

Set a deadline that is tied to something real. A trade show, a season, a lease. A made-up date just adds pressure to the wrong parts of the project.

Keep some budget for after launch. A website is not finished on launch day. It is only measurable from launch day. The teams that get the best results keep a small monthly amount for testing headlines, shortening forms and fixing the pages the data says are leaking, on top of the website maintenance that keeps the thing secure and updated.

The Bottom Line

A good brief is not a longer document. It is a document that answers commercial questions before design questions. Say what has to change in the business, put a number on it, name the one person you have to convince and the one action you want from them, sort proof and content before the build starts, write the technical standards down, and agree who decides. Do that and the quotes you get back will be closer together, the project will start on time, and you will be able to tell at the end whether it worked.

If you want to work through it properly, download The Conversion-Focused Web Design Brief. It turns everything above into 32 questions, each with an example of a weak answer and a strong one, and space to write yours. There are more practical templates and calculators in our resources library.

And if you would rather not do it alone, that is what our web design services built around conversion are for. Head to our web design page to see how we scope, design and build sites that are measured on enquiries rather than compliments.