Customer Impact

Website & Development

How to Write a Strong Website Brief or RFP (with Template)

Copy for AI

A strong website brief pins down goals, scope and requirements, so agencies quote without guessing.

Start from your business goal and the leads you want.

Describe what the site has to do and for whom, and be clear about budget, timeline and who decides.

The verdict: a sharp website brief or RFP is your best lever on the final cost. It brings better quotes, fair comparisons and fewer change requests.

You’ll find a copy-ready template at the end.

Want to see the whole journey first? Read our guide to having a B2B website built.

What exactly is a website brief or RFP?

A website brief is a document that describes what you want built, why, and under which conditions.

Brief vs RFP

An RFP, a Request for Proposal, is in practice the same document.

It’s just formally sent to several agencies, each asked to submit a proposal and a price.

The difference is mostly one of degree:

  • Brief: a working document for one agency you already trust.
  • RFP: a document to weigh a few partners on approach and price.

Always write it down

For a B2B website of any size, a written document beats a verbal sketch.

That holds even if you only talk to one agency.

Writing it forces you to think about what you really need.

A story, not a specification

A good brief isn’t a specification full of technical prescriptions.

It’s a clear story about your company, your customers and the result you’re after.

The conditions it has to meet come on top.

Why does a good brief produce better quotes?

Because agencies can price what they understand.

A sharp brief delivers three things: better quotes, fair comparisons and fewer change requests. That’s no coincidence; it’s the direct result of clarity.

Realistic prices instead of guesses

When agencies know your goal and what’s in and out of scope, they give a realistic price and timeline.

Without that, you get a shot in the dark.

Wildly diverging quotes often have less to do with the agencies than with the document.

Two partners who understood something different can’t be compared fairly. Our guide to comparing website quotes shows how to line them up.

Fewer change requests

The biggest win lies in avoiding change requests.

They almost always come from something that wasn’t, or was only vaguely, in the agreements. For example:

  • An extra language: nobody counted it.
  • A CRM connection: assumed, never written down.
  • More pages than expected: “just a few extra”.
  • Missing content: text that didn’t exist yet.

What you fix up front is included in the price.

What you leave open gets added later, often at a rate you can no longer compare.

So a good brief isn’t paperwork.

It’s where you control the final cost.

The usual surprises are listed in the hidden costs of a website.

Which parts belong in a strong website brief?

Goals, audience, scope, content, technology, timeline and budget. Not every part needs the same detail, but none may be missing.

About you and the goal

  • Context about your company. What do you do, for whom, and what makes you different? An agency that grasps your positioning builds a site that builds trust with your B2B visitors instead of a neutral brochure.
  • The goal of the site. Be concrete and businesslike. In B2B that usually means more and better leads: enquiries, intakes or quote requests.
  • Your audience and their task. Who comes to the site and what do they want to do there? The sharper you describe that, the more targeted the structure and copy.

“A more modern look” is a consequence, not a goal. Describe instead which behaviour you want to prompt in visitors.

How to turn that goal into measurable targets is in our guide to website KPIs.

What gets built

  • Scope. The number of pages or page types, languages, and what explicitly does and doesn’t belong.
  • Content. Who supplies text, imagery and video? Does it exist already or does it still have to be made?
  • Functional requirements. What the site has to do: a form that sends to your CRM, a blog, multilingual support, an appointment tool.

Name what’s out of scope. That prevents most disputes later.

Content is in practice the biggest cause of delay, so name that too.

Tip: describe the function, not straight away the product.

How, when and for how much

  • Technology and integrations. Existing systems it has to connect with, your analytics, your email tool.
  • Timeline. A target date and the reason behind it.
  • Budget. Dare to give an order of magnitude.
  • Decision process. Who’s the point of contact and who signs off?

If you have a platform preference, or an aversion, say so. But leave the choice open where possible.

A trade show or a product launch is a real deadline. “As soon as possible” isn’t.

An indicative budget helps agencies make a fitting proposal instead of guessing. Our guide to website cost helps you set the range.

Fastest lever: a small team that decides quickly speeds up any web project more than anything else.

How do you fix scope and requirements without prescribing the solution?

Describe the problem and the desired result, not the technical solution.

That’s the difference between a brief that leaves room for expertise and a specification that rules out the best ideas.

Goal, not prescription

Compare two sentences:

  • Prescription: “We want a dropdown menu with six items.”
  • Goal: “Visitors must find our three service groups from every page.”

The first prescribes a navigation choice that may not be the best one. The second describes the goal and lets the agency propose the best form.

The UK government’s Service Manual on user stories uses the same logic. It says “the most important part of a user story is the goal”, because it makes sure you solve the right problem.

Its format works well for brief requirements too: “As a… I need to… So that…”.

That way quotes stay comparable on approach. Not on who executed your prescription most neatly.

Here’s what a brief should fix and what it should leave to the agency:

WEBSITE BRIEF What you fix, what they propose YOU FIX Goal and leads Audience and their task Scope, in and out Budget and deadline Hard requirements THE AGENCY PROPOSES Structure and navigation Design and components Platform choice Technical solution Planning per phase Fix the problem and the limits. Leave the solution open, so quotes compare on approach.

The platform question

The same goes for the platform.

Customer Impact is platform-agnostic. We choose case by case between Webflow, WordPress or a custom or headless setup, based on your goals, team, budget and growth plans.

So a good brief rarely forces a platform. Here are two of the usual candidates:

WordPress.org homepage presenting the open source publishing platform, one of the platforms a website brief or RFP can leave open for the agency to propose WordPress.org, October 2026. The open source option, with hosting and maintenance arranged separately.

And the hosted alternative:

Webflow homepage presenting its visual website platform, an alternative an agency can propose in response to a website RFP Webflow’s homepage, October 2026. The hosted option, with a monthly site plan.

Describe your requirement instead, such as “our marketing team must publish pages without a developer”. Then let the agency argue which platform fits.

Our guide on which CMS to choose explains the trade-offs.

Firm on the non-negotiables

Be firm on the points that aren’t up for debate:

  • A required CRM connection: name the system.
  • Legal accessibility duties: for example under the European Accessibility Act if you sell online to consumers.
  • A language that must be added: with the date it’s needed.

Those are real requirements that must be in black and white.

For accessibility, name the standard. W3C’s WCAG overview puts the current version at WCAG 2.2, with conformance levels A, AA and AAA.

Our guide to European Accessibility Act compliance covers what applies to you. A quick first scan of your current site is the free WCAG checker.

For the CRM, name the tool and what has to flow where. HubSpot is a common example:

HubSpot free CRM page, an example of a CRM a website brief should name as a hard integration requirement for the contact form HubSpot’s free CRM page, October 2026. Name the CRM in your brief, plus which form fields must land where.

Our guide to HubSpot website integration shows what that link involves.

Rule of thumb: keep a firm requirement and a preference clearly apart. It helps the agency make the right trade-offs.

How do you make sure you’re ready as the client?

By having content, access and decisions lined up before the build starts.

Most web projects don’t stall because of the build. They stall because the client can’t deliver or decide on time.

Three readiness checks

Check client readiness up front on these points:

  1. Content: do text and imagery exist, and who writes and approves?
  2. Access: domain, hosting, analytics and your current CMS.
  3. Decisions: who signs off on branding, copy and technology?

Don’t count on content too lightly.

It’s often the longest part of the journey.

Access may still have to be requested from a previous supplier. Who holds what is covered in who owns my website.

Agree internally on decisions, so the agency doesn’t wait on five opinions.

Realistic expectations

A site is a lever for leads, not a miracle cure.

It works best inside a larger whole: strong content, a clear value proposition and good UX. Whoever has that in mind up front writes a more realistic brief.

What happens after you send the brief is set out in our website development process.

Brief template to copy

Below is a template to adopt and fill in. Keep it short and concrete; a few sentences per part is often enough.

The ten parts

  1. About us: what we do, for whom, what makes us different.
  2. Goal of the site: which concrete result (for example more enquiries) and which behaviour we want.
  3. Audience: who comes, and which task those visitors want to complete.
  4. Scope: number of pages or page types, languages, what explicitly does and doesn’t belong.
  5. Content: what already exists, what still has to be created, and who supplies it.
  6. Functional requirements: must-haves versus nice-to-haves, clearly separated.
  7. Technology and integrations: systems that have to connect, platform preferences or aversions.
  8. Timeline: target date and the reason behind it.
  9. Budget: an indicative amount or range.
  10. Process: point of contact, who signs off, and how you evaluate quotes.

One step more professional

Add your wireframes or a rough sitemap if you already have them.

Also say how you weigh the quotes: on approach, B2B experience and price together, not on price alone.

Next step: send the brief with a website quote request, and prepare your questions to ask a web design agency.

Once you pick a partner, the brief feeds straight into the website contract and SLA.

Frequently asked questions about a website brief

What is the difference between a brief and an RFP?

In practice little. A brief is your document with goals, scope and requirements. An RFP is that same document, formally sent out to multiple agencies with the request to submit a proposal and a price. The content is largely the same.

Do I have to mention a budget in my brief?

Yes, at least an order of magnitude. An indicative budget helps agencies make a fitting proposal. Afraid you’ll pay too much by naming it? Ask for a breakdown per part, so you see where the money goes.

How do I prevent change requests?

By fixing scope, content and the decision process up front. Change requests almost always arise from what was not, or only vaguely, in the agreements. Explicitly name what’s out of scope; that prevents most disputes.

How long should a brief be?

As long as needed, as short as possible. For a B2B site a few pages often suffice. Completeness and clarity count, not the length.

The short summary

A strong website brief or RFP gets you realistic, comparable quotes and fewer change requests.

Describe the problem and the result, not the technical solution. And be ready with content, access and decisions.

Unsure whether your document is complete? See our web design agency page and put your plan to us.

Contact us with your draft brief, and we’ll point out the gaps that would cost you later.

Free website scan

Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.

Where should we send your report?

We only use your details for your scan. No spam, unsubscribe anytime.