9 Sections Every B2B Website Brief Template Needs

Published 8 November 2026 · Last updated and fact-checked November 2026

Short answer: A website brief tells a designer what to price. A website brief template needs nine sections: goal, buyers, decision owner, pages, content, references, integrations, technical standards and budget. In the NaPiRE survey of 228 companies on software projects, 48% ranked incomplete or hidden requirements among their five worst problems.

A head of marketing opens a blank Google Doc on a Tuesday. Three web designers want a brief by Friday, and the CEO has one note so far: make it look more modern.

Most templates I found will not help that person. In a small audit on 8 November 2026, I ran a word search across six competing pages for this phrase. None mentions redirects or Core Web Vitals. Two mention a CRM, and one mentions B2B at all. Several other results for the phrase sit on unrelated domains, which tells you how much care went into them.

So this template is written from the buyer's chair. It covers what a B2B team has to settle, who settles it, and what breaks when a line stays blank. One caution on the evidence: nobody has studied website briefs as their own category. The closest research is on software requirements, and I say so wherever I use it. The time estimates and the rules are mine.

Key takeaways

• In the NaPiRE survey (Naming the Pain in Requirements Engineering), incomplete or hidden requirements were the most cited problem across 228 companies on software projects, named by 109 of them, or 48%.

• A usable goal has four parts: one metric, today's number, a target and a date, which follows Locke and Latham's goal research.

• Google says to keep redirects for "generally at least 1 year" in its site move guide, so old URLs belong in the brief.

• web.dev sets the speed targets to write down: LCP 2.5 seconds, INP 200 milliseconds and CLS 0.1.

• The full template takes about 6 hours to complete by my estimate, spread across three or four people.

1. Business goal: best for stopping a redesign that only changes the look

The goal section names one business result the site must change, with today's number beside it. It suits any team that cannot yet say why the rebuild is happening. Locke and Latham's review of 35 years of research supports specific, hard goals over vague ones.

• Write: one sentence

• Include: metric, today's number, target, date

• Pull the number from: your CRM, not memory

• Time: 30 minutes

• Owner: head of marketing

The 2002 study by Locke and Latham reviewed work goals, not websites, so treat this as a borrowed principle. It transfers well. "A more modern site" gives a designer nothing to check a decision against. "Raise demo requests from organic visits from 18 a month to 30 a month by 31 March" lets anyone in the room test a layout, a form or a headline. The 18 and the 30 there are placeholders; use your own.

Pick the number closest to revenue that the website can move by itself. Sales-accepted leads are usually a better choice than raw form fills, because a form that attracts the wrong people can raise submissions and lower pipeline. Traffic is a poor goal for most B2B sites. A page can gain visits from people who will never buy.

Write down what must not get worse too. If organic leads pay for the company today, the brief should say that a redesign may not lower them. If your company runs on EOS®, this number belongs on the Scorecard, with one named person accountable for it. A goal without an owner is a wish with a spreadsheet attached.

2. Buyers and their questions: best for pages that have to do the selling

This section lists who buys, what they need answered before talking to sales, and the words they use. It suits B2B companies where several people weigh in on a purchase. Pirolli and Card's 1999 information foraging paper explains why those words matter: people follow cues that promise an answer.

• Limit: 2 or 3 buying roles

• Per role: top 3 questions

• Source: sales calls and lost deals

• Keep: the buyer's exact words

• Time: 60 minutes

Not personas. Skip the stock photo and the imaginary hobbies. A designer needs to know which questions decide the sale, because those questions become your page list and your navigation labels.

The fastest source is a sales rep's memory of the last five deals. Ask what the buyer wanted to know before the first call, what nearly killed the deal, and which phrases kept coming up. Also list the 2 or 3 vendors buyers compare you with, and note in their words why they chose you or them. Then read your lost-deal notes. If a buyer said "we got burned by our last vendor," that sentence is worth more than any tagline workshop.

Write each question the way a buyer would type it. "How long does setup take" is useful. "Implementation excellence" is not, since nobody has ever searched for it. Then name the page where the answer should live. If a question has no page, you have found a gap in the site before anyone has charged you to find it.

One limit is worth stating. The 1999 study by Pirolli and Card modeled how people hunt for information in general, and it did not test B2B sites. I use the idea as a working rule for labels and page names, and I would test any headline that matters on real buyers.

3. Decision owner: best for companies where everyone has an opinion

The decision owner section names the one person who approves the work, who else may comment, and how fast. It suits leadership teams with several strong opinions. In the NaPiRE survey of software projects, 41% of 228 companies ranked communication flaws between the project team and the customer among their worst problems.

• Decision owner: 1 named person

• Reviewers: 4 at most

• Response time: 2 business days

• Late feedback: moves the launch date

• Time: 15 minutes

Fifteen minutes to fill in, and it protects the rest of the schedule. Two people with final say is the same as nobody having it, because the designer ends up refereeing the argument.

The limits here are my working rules, not study findings. Four reviewers keeps every department that matters in the room. Two business days keeps a 6-week project from turning into a 12-week project. Pick your own numbers, but pick them before work starts, and write down what happens when a deadline slips.

Staats, Milkman and Fox gave this problem a name, the team scaling fallacy: people underestimate how much efficiency a group loses as it grows. That 2012 study looked at teams doing tasks, not website approvals, but the pattern will feel familiar to anyone who has watched a homepage go through nine rounds of comments.

In an EOS® company, the Integrator is the natural decision owner, and the Visionary can review the homepage and the positioning. Legal review deserves its own line, with a date, because legal comments tend to arrive at the worst possible moment. Name the person now.

4. Pages and scope: best for getting quotes you can compare

The scope section lists every page and template, sorted into must have, later and out of scope. It suits anyone collecting more than one quote. Across 228 companies on software projects in the NaPiRE survey, 48% ranked incomplete or hidden requirements among their top five problems, the most cited of 21 listed.

• Must have: pages needed at launch

• Later: phase 2, priced separately

• Out of scope: written down by name

• Count: unique templates and total pages

• Time: 60 minutes

"It is also the most cited problem overall," Méndez Fernández and colleagues wrote of incomplete and hidden requirements in Empirical Software Engineering.

The 2017 survey covers software projects, and a website is a smaller, simpler thing. It asked respondents to rank the five most critical of 21 listed problems. The shape of the risk holds anyway. Two designers can read "new website, about 20 pages" and send quotes thousands of dollars apart, and both can be honest. One pictured 20 copies of three templates. The other pictured 20 unique layouts, a resource library and a calculator.

Count templates separately from pages. A blog with 200 posts is one template and one migration job. Then write the out-of-scope list, which is the part nearly everyone skips. Write "no customer portal," "no German version," or "no blog migration" if those are true. A bidder who reads that cannot pad the quote with guesses, and cannot claim later that the portal was never mentioned.

Moving targets ranked third in the same survey, at 33%, level with underspecified requirements. Not enough time followed at 32%, and communication flaws within the team at 27%.

"51% of the organisations that cited Moving Targets as a problem stated that it led to project failure," Méndez Fernández and colleagues wrote in Empirical Software Engineering.

So any page added after sign-off should come with a price and a new date. If you need a formal process with bidders, my website redesign RFP example builds on this section.

5. Content: best for launches that keep slipping

The content section records, page by page, whether copy is kept, rewritten or new, who writes it and when it is due. It suits teams without a full-time writer and takes about 45 minutes by my estimate. I have not found research on website copy delays, so treat this section as my working rule.

• Status: keep, rewrite or new

• Named writer: per page

• Subject expert: per page

• Assets: photos, logos, case studies

• Time: 45 minutes

I treat content as the section most likely to delay a website launch, and it has nothing to do with design. In the NaPiRE survey of software projects, time overrun (about 10%) and rework (about 9%) were the most cited effects of incomplete requirements, and on a website project missing copy is where I expect that to show up first. Layouts can be finished in weeks. A case study that needs a client's sign-off cannot be rushed by anyone on the project.

Go through the current site and mark each page. Keep means the copy can move over as it is. Rewrite means the facts are right and the words are not. New means somebody has to find out what to say first, and that usually means an interview with a subject expert who is already busy.

Put a name and a date on every line. "Marketing" is not a writer. If the honest answer is that nobody has time, say so in the brief and ask each bidder to price the writing separately. That number will be useful even if you decide to write the copy yourself.

List the assets as well: headshots, product screenshots, logo files, customer logos you have permission to show. Permissions are the quiet delay here, so check them now. If your approved proof is thin, tell the designer early. A page can be built around two strong case studies, and it cannot be built around twelve you may not name.

6. References: best for showing taste without dictating the design

The references section lists three to five sites and says exactly what is worth borrowing from each. It suits teams with strong visual opinions. In the NaPiRE survey of software projects, 25% of 228 companies ranked stakeholders struggling to separate requirements from known solution designs among their worst problems.

• Sites: 3 to 5

• Per site: one thing to borrow

• Add: why it helps your buyer

• Also list: 1 or 2 sites you dislike

• Brand files: logo, type, colors, rules

"Make it look like Stripe" is not a reference. It is a design decision made by someone who has not seen the options, and it hands the designer a target that belongs to another company with another buyer.

Jansson and Smith named this design fixation in a 1991 paper in Design Studies. Designers shown an example tended to reproduce its features, flaws included. The 1991 study used engineering design tasks, so read it as a warning rather than a measurement of websites. The warning still applies to a Pinterest board.

The fix takes one line per site. Write the link, the one thing worth keeping, and why it helps your buyer: "their pricing page puts the three-year cost in a single table, and our buyers ask for that." Now the designer knows the job the reference is doing and can solve it a better way.

Add a site you dislike and explain why. It is often the most useful line in the whole document. If you have an approved brand system, attach it and say which parts are fixed. If you do not, say that too, because a logo refresh hiding inside a website project changes the price.

7. Integrations and tracking: best for keeping lead source through to the CRM

This section lists every system the site must talk to and every action you need to count. It suits B2B teams reporting pipeline by channel. Google Analytics calls those counted actions key events, and each one needs a definition your sales team agrees with before anyone builds a form.

• CRM: name, plan and admin contact

• Forms: fields and routing rules

• Key events: form, booking, call

• Lead source: carried into the CRM

• Logins: who holds each admin account

• Editing: who updates pages after launch

"A key event is an event that measures an action that's particularly important to the success of your business," Google Analytics Help wrote in its help article on key events.

My rule, not a study finding: 3 key events is enough for most B2B sites, a qualified form, a booked call and a phone call. Newsletter signups can be counted, but keep them apart from anything you report as a lead.

The line that gets dropped most often is the path from website to CRM. A form fills in, a record appears, and the lead source reads "direct" or nothing at all. Six months later nobody can say which channel paid for itself. I cover the setup in my website lead tracking guide, and the brief only needs the requirement: every lead reaches the CRM with its source attached.

In my 8 November 2026 audit of six competing pages, 2 of the 6 mentioned a CRM at all, so this section is usually missing from a template you download.

Write down the admin contacts too. It sounds like housekeeping until the project stalls for a week because the only person with access to the domain registrar left the company in 2023. Domain, DNS, hosting, analytics, tag manager, CRM and booking tool: one name each.

Then state the form fields you truly need. Sales will ask for more than marketing wants, and my guide to form length can settle that argument. Settle it here, not during the build.

8. SEO, speed and accessibility: best for sites that already earn traffic

This section sets the checks for handover: Largest Contentful Paint (LCP) of 2.5 seconds, Interaction to Next Paint (INP) of 200 milliseconds, Cumulative Layout Shift (CLS) of 0.1, Web Content Accessibility Guidelines (WCAG) 2.2 AA, and a redirect map. Google's site move guide advises keeping redirects for "generally at least 1 year".

• Redirect map: every old URL to one new URL

• LCP: 2.5 seconds or less

• INP: 200 milliseconds or less

• CLS: 0.1 or less

• Accessibility: WCAG 2.2 AA

"It's important to map your old site's URLs to the URLs for the new site," Google Search Central wrote, and it also warns site owners to "expect temporary fluctuation in site ranking during the move."

Export your top pages from Search Console before you write this section. Those URLs need a named destination on the new site, and a redirect to the homepage does not count: Google's guide tells owners not to send many old URLs to one unrelated page. Ask each bidder who builds the map, who tests it and who watches rankings after launch. In that same audit, 0 of the 6 pages mentioned redirects.

Speed targets give you something to check at handover. web.dev measures LCP, INP and CLS at the 75th percentile of page loads. Name them in the brief and ask for a report on the finished site.

"LCP should occur within 2.5 seconds of when the page first starts loading," web.dev stated in its Web Vitals guide.

Accessibility needs a stated version. The W3C published WCAG 2.2 on 5 October 2023, and it has 13 guidelines at three levels. AA is the level I would ask for.

"W3C encourages you to use the latest version of WCAG," the W3C Web Accessibility Initiative wrote in its WCAG overview.

The legal picture is less tidy, and this is not legal advice, so ask counsel if your risk is high. The Department of Justice points businesses open to the public to WCAG as helpful guidance without making it a rule.

"The Department of Justice does not have a regulation setting out detailed standards," the US government stated on ADA.gov.

9. Budget and deadline: best for proposals that fit the real limit

State a budget range and a launch date with the reason behind it. Hiding the number makes bidders guess, and the proposals stop being comparable. A field experiment with 46 software outsourcing companies found a client's stated cost expectations moved estimates less than laboratory studies had implied.

• Budget: a range, not one figure

• Includes: build, content, tools

• Separate: yearly running costs

• Deadline: a date and the reason for it

• Time: 20 minutes

"The effect sizes in the field settings were much smaller than those found for similar manipulations in laboratory settings," Jørgensen and Grimstad reported in IEEE Transactions on Software Engineering.

Many buyers leave the budget out because they fear every quote will rise to meet it. The study paid 46 companies to estimate the same five software projects, and one version of the specification mentioned a client's unrealistic low-cost expectations. It did not test website budgets. It does weaken the case for hiding a number, and hiding one has a cost you can see: bidders guess, and you pay to read proposals that were never going to fit.

A range also tells a designer what kind of project this is. My fixed-price builds run $3,250, $4,850, $6,950, $9,750 and $14,999, and the brief decides which one fits. Ask each bidder to separate the one-time build from yearly costs such as hosting, licenses and maintenance. My website redesign cost guide breaks those lines down.

Then give the date a reason. "A trade show on 12 May" is a real deadline, and "the CEO wants it soon" is a preference. A brief that states its limits honestly gives the designer something to design around.

Website brief template: what to write in each field

Copy these nine rows into a document and fill in the third column. Each row is written for a B2B team hiring an outside designer. The owner column tells you who to chase, and the done test tells you when a section can stop being edited, which matters when several people share the file.

The same template as a form to paste into a document:

• 1. Goal: Metric ___ / Today ___ / Target ___ / Date ___ / Must not drop ___

• 2. Buyers: Role ___ / Top 3 questions in their words ___ / Page that answers each ___ / Vendors they compare ___

• 3. Decision owner: Approver ___ / Reviewers, 4 at most ___ / Response time ___ / Legal contact and date ___

• 4. Pages: Must have ___ / Later ___ / Out of scope ___ / Templates ___ / Total pages ___

• 5. Content: Page ___ / Keep, rewrite or new ___ / Writer ___ / Due date ___ / Assets and permissions ___

• 6. References: Link ___ / One thing to borrow ___ / Why it helps our buyer ___ / Sites we dislike ___

• 7. Systems: CRM ___ / Forms and routing ___ / Key events ___ / Admin contact per system ___ / Who edits after launch ___

• 8. Standards: Top URLs and redirect owner ___ / LCP, INP, CLS targets ___ / WCAG level ___

• 9. Budget and date: Range ___ / What it includes ___ / Yearly costs ___ / Launch date and reason ___

Is your website brief ready to send?

Count the sections in your brief that pass the done test. That count decides what happens next, and it takes two minutes. It is a judgment rule of mine, not a validated score, so adjust the cut-offs if your project is unusually small or heavily regulated.

If sections 1, 3 or 9 are open, hold the brief whatever the count says. A designer can price missing copy as an assumption. A project with no goal, no decider and no budget cannot be scoped, because nothing says what the work is for, who approves it or what it may cost.

Frequently asked questions

Buyers tend to ask these five questions once the template is open and the blank fields are staring back at them. Each answer stands on its own, so you can paste one into an email to a colleague who is asking the same thing and needs a straight answer.

What should a website brief include?

A website brief should include a business goal, the buyers and their questions, one decision owner, a page list with exclusions, a content plan, references, integrations, technical standards, and a budget with a deadline. Those nine sections give a designer enough to price the work accurately.

How long should a website brief be?

I aim for two to five pages in a B2B website brief. Completeness matters more than length, so answer every section in plain sentences. By my estimate the work takes about 6 hours across three or four people. A short brief with real numbers beats a long brief without them.

What is the difference between a website brief and an RFP?

A brief describes the project: goals, buyers, pages, standards and limits. A request for proposal adds the buying process around it, such as bidder questions, deadlines, scoring and contract terms. Write the brief first. You can send it alone to one or two designers, or attach it to an RFP.

Should I put my budget in a website brief?

Yes, give a range. Without one, bidders guess at the project size and you compare proposals that solve different problems. In a field experiment with 46 software outsourcing companies, stated cost expectations moved estimates less than laboratory studies suggested. Ask each bidder to itemize.

Who should write the website brief?

The head of marketing should own the document, because the goal and the buyers sit there. Sales supplies the buyer questions, operations supplies the systems, and leadership sets the decision owner and budget. A designer can help you finish it, but your team has to make the decisions in it.

Who should fill in this template with you?

Your own team can complete all nine sections without outside help, and the goal, decision owner and budget have to come from inside the company anyway. Bring in a designer when the blanks are technical, such as a redirect map or a CRM connection, or when your team disagrees and needs someone to force the choice.

"A project with no goal, no decider and no budget cannot be scoped, because nothing says what the work is for, who approves it or what it may cost," said Joshua Jackai, founder of Demand Designer.

I build conversion-focused B2B sites at fixed prices from $3,250 to $14,999, and I work from this same list. Snappy Kraken, a marketing platform for financial advisors, went from Figma to HubSpot in 21 days, and that work contributed to a 30% rise in marketing-qualified leads. Five of the companies I have shipped work for run on EOS®: Copy Chief, Y Scouts, Snappy Kraken, Advisor Websites and Course Concierge.

If you are not sure the website is the problem at all, start with the free Pipeline Leak Scorecard. It takes about 15 minutes with your site open. When you are ready for the project plan, my website redesign checklist picks up where this brief stops.

EOS® is a registered trademark of EOS Worldwide. Demand Designer is not affiliated with or endorsed by EOS Worldwide.

Sources

Peer-reviewed research

• Jansson, D. G., and Smith, S. M. (1991). Design fixation. Design Studies, 12(1).

• Jørgensen, M., and Grimstad, S. (2011). The impact of irrelevant and misleading information on software development effort estimates: A randomized controlled field experiment. IEEE Transactions on Software Engineering, 37(5).

• Locke, E. A., and Latham, G. P. (2002). Building a practically useful theory of goal setting and task motivation: A 35-year odyssey. American Psychologist, 57(9).

• Méndez Fernández, D., Wagner, S., Kalinowski, M., Felderer, M., Mafra, P., and colleagues (2017). Naming the pain in requirements engineering: Contemporary problems, causes, and effects in practice. Empirical Software Engineering, 22(5).

• Pirolli, P., and Card, S. (1999). Information foraging. Psychological Review, 106(4).

• Staats, B. R., Milkman, K. L., and Fox, C. R. (2012). The team scaling fallacy: Underestimating the declining efficiency of larger teams. Organizational Behavior and Human Decision Processes, 118(2).

Industry, vendor and government sources (not peer reviewed), read 8 November 2026

• ADA.gov, US Department of Justice. Guidance on web accessibility and the ADA.

• Google Analytics Help. About key events.

• Google Search Central. Site moves with URL changes.

• W3C Web Accessibility Initiative. WCAG 2 overview.

• web.dev. Web Vitals.