How to Brief a Web Developer (With a Free Checklist)

Most website projects that go wrong don’t fail on code. They fail in the first week, when the business owner and the developer each walk away from the kick-off call with a different picture of the finished site. A clear website brief closes that gap. It doesn’t need to be long or polished. It needs to answer the questions a developer will otherwise have to guess at, and guesses are where budgets and deadlines drift.

What a website brief is (and what it isn’t)

A brief is a short document, usually two to four pages, that explains why you need a website, who it’s for, what it must do and what constraints apply. It is not a technical specification. You don’t need to know whether the site should use a page builder or a custom theme, or how the database is structured. That’s the developer’s job. Your job is to describe the business problem and the outcome you want.

Why a written website brief saves money

When you ask three developers for a quote without a brief, you often get three numbers that are wildly different. One pictured five pages and a contact form. Another pictured a booking system and a members’ area. A brief makes quotes comparable, which is the first step if you’re weighing options like those in my post on choosing between a freelancer and an agency.

It also protects you later. If a feature was in the brief and the quote, it’s in scope. If it wasn’t, both sides know it’s an addition. That single line between “agreed” and “extra” prevents most disputes I’ve seen in 16+ years of building sites.

The sections every brief should cover

1. Your business in a paragraph

What you sell, who buys it, where you operate and what makes you different from the competitor down the road. Keep it plain. “We’re a family-run plumbing company covering North Leeds, mostly emergency call-outs and boiler servicing” tells a developer more than a mission statement does.

2. The goal of the website

Pick one primary goal and, at most, two secondary ones. Examples: get phone calls, collect quote requests, sell products online, take bookings, or give existing customers information so they stop ringing the office. The primary goal shapes the layout of every page, so be honest about which one matters most.

3. Your audience

Describe two or three types of visitor. What are they trying to do when they land on your site? Are they mostly on phones? Are they comparing you with others, or have they already been referred?

4. Pages and content

List the pages you think you need. A typical small business site has Home, About, Services (sometimes one page per service), Contact, and perhaps a blog or portfolio. Then say who is writing the words and supplying the photos. “Content will be ready” is the most optimistic sentence in web development. If you need help with copy, say so up front; it changes the timeline. My guide on writing website content that converts is a good starting point if you’re doing it yourself.

5. Features and functionality

List what the site must do beyond displaying pages. Be specific:

  • Contact or quote form (what fields, and where should submissions go?)
  • Online booking or appointment scheduling
  • Online shop (roughly how many products, and do you need shipping rules or tax calculations?)
  • Newsletter sign-up connected to an email platform
  • Member login or gated downloads
  • Live chat or a chatbot

Mark each one as “must have” or “nice to have”. That lets a developer quote a core version and price the extras separately.

6. Design direction

Share two or three websites you like and say what you like about each one. “I like the clean layout of this one” and “I like how this one shows prices” are both useful. Also share anything you already have: a logo, brand colours, fonts. If you don’t have a logo yet, it’s worth sorting that first; there’s more on why in this post on logo design.

7. Technical details you already know

Do you already own a domain? Where is it registered? Do you have hosting, an existing website, or business email tied to the domain? Who has the login details? Missing access is one of the most common causes of launch-day delays, so list what you have and what you’ll need to track down.

8. Budget and timeline

Many people leave the budget out because they worry a developer will simply quote up to it. In practice, a range helps a developer suggest what’s realistic. If you’re unsure what’s reasonable, my breakdown of what a small business website costs covers typical ranges. For timeline, give a target date and say whether it’s fixed (a trade show, a product launch) or flexible.

9. After launch

Who will update the site? Do you want training? Do you need ongoing maintenance, backups and updates? Answering this early affects which platform and build approach makes sense.

Common mistakes in a website brief

  • Describing the solution instead of the problem. “I need a pop-up on every page” is a solution. “People leave without contacting us” is the problem, and there may be a better fix.
  • Listing every possible feature as essential. If everything is a must-have, nothing can be prioritised when budget runs short.
  • Leaving out the awkward details. If a previous developer left the project half-finished, or the old site was hacked, say so. It changes the approach.

Your free checklist

Copy this into a document and fill in each line. Short answers are fine.

  1. Business name, what you sell, and where you operate
  2. Primary goal of the website (one only)
  3. Secondary goals (up to two)
  4. Two or three typical visitors and what each wants
  5. List of pages
  6. Who writes the text and who supplies the photos
  7. Features: must-have list
  8. Features: nice-to-have list
  9. Two or three websites you like, and why
  10. Existing brand assets (logo, colours, fonts)
  11. Domain, hosting and email: what you have and who controls access
  12. Budget range
  13. Target launch date, and whether it’s fixed
  14. Who will maintain the site after launch
  15. Anything that went wrong with a previous website

Send that to a developer and you’ll get a more accurate quote. It also gives you a fair way to compare proposals, which matters if you’re following a process like the one in how to hire a freelance web developer in India.

Frequently Asked Questions

How long should a website brief be?

For most small business sites, two to four pages is plenty. Length matters less than clarity. A one-page brief that answers every item on the checklist is more useful than ten pages of general description.

What if I don’t know what features I need?

Describe what you want visitors to be able to do, and what tasks currently take up your staff’s time. A good developer will suggest features that match. That’s a normal part of the early conversation.

Should I share my budget in the brief?

Yes, as a range. It helps the developer propose something realistic rather than guessing, and it saves both sides time if the project and budget don’t match.

Need help?

If you’ve got a rough brief, or even just a few notes, I’m happy to look it over and suggest what’s missing. I’ve built 500+ custom WordPress themes for clients in the USA, Canada, the UK and India, and I handle both website design and website development. You can see past projects on my portfolio page, or send me your brief and I’ll reply within 24–48 hours.

Services That Can Help

Estimate Project