Crelivio
Web Development

How to brief a web developer: what to prepare before you ask for a quote

Crelivio12 min read

Most disappointing websites were not caused by a bad developer. They were caused by a vague brief. When a developer has to guess what you want, they fill the gaps with their own assumptions, and you find out which ones when the first draft arrives.

A website brief is a short document that tells a web developer or agency what you need, why, and by when. It does not need to be long or technical. It needs to answer a handful of questions clearly. Write it in plain language, send the same brief to every developer you ask for a quote, and the answers you get back will be easy to compare.

This guide covers what to put in a web design brief, a template you can copy, an example, how to talk about budget, how to compare quotes, and the red flags to watch for on both sides.

How long should a website brief be?

For a small business site of five to ten pages, one or two pages is enough. For a larger build with online payments, accounts or links to other software, expect four to eight. Clarity matters more than length. If a section does not change what the developer builds or charges, cut it.

What a website brief should cover

1. Your business in a few sentences

What you do, who you serve and where you operate. Include what makes you different from competitors, in your own words.

2. The goal of the website

Be specific about what the site must achieve. "Look professional" is not a goal. These are goals a developer can work with:

  • Get a set number of enquiries a month.

  • Let customers book a consultation without calling.

  • Sell products online across the country.

  • Be found on Google for the services we offer.

If you have several goals, rank them. The first one decides most design choices. Add how you will know it worked, for example enquiries per month or orders per week.

3. Your audience

Who will use the site? Describe two or three typical visitors: what they want, what worries them, what device they use and how they usually find you. A site for busy business owners on phones is built differently from one for researchers on desktops.

4. The pages you expect

List the pages you think you need, such as home, about, services, contact and blog. This is your page inventory. If you are not sure, say so and ask the developer to propose a structure. Mention any page that already exists and must keep its address, so you do not lose your Google rankings.

5. The content you already have

Say what is ready: text, logo, photos, videos, testimonials, price lists. Say what is not. Content is the most common cause of delays, so be honest about it, and agree who writes what. If you want the developer to write the copy, say so, because it changes the price.

6. Features you need

List anything beyond simple pages: contact forms, WhatsApp links, booking, online payments, customer accounts, a blog, a members area, connections to other software. Then sort them into three groups:

  • Must have. The site cannot launch without it.

  • Should have. Important, but the launch can go ahead without it.

  • Nice to have. Add later if budget and time allow.

This sorting is the quickest way to control cost, and it makes quotes much easier to compare.

7. Examples you like and dislike

Share three to five websites you admire and say why, and one or two you dislike. This communicates taste more clearly than any description. Point to the specific thing: the layout, the tone, the speed or the way it explains the offer.

8. Your brand

Share your logo, colours and fonts if you have them. If you do not have a brand identity yet, say so, because it changes where the design starts.

9. Search and visibility

Say whether you want the site set up to be found on Google, and for which services and places. Ask what is included, such as page titles, descriptions, site structure and speed work.

10. Who will update it

Do you want to edit text, add blog posts and change images yourself, or ask someone else to? That changes how the site should be built.

11. Budget range

See the next section, because this part trips up most people.

12. Timeline

When do you want to launch, and why? A fixed event or campaign date is a real constraint. A date picked at random can cause rush charges or poor quality.

13. Who decides

Name the person who approves the work and say how many people have to agree. Feedback from five people who disagree stalls projects. Choose one person to collect feedback and give one answer.

14. Access, ownership and handover

List what you can provide, such as your domain registrar login, current hosting, analytics and social accounts, and say who holds each. State that the domain, hosting account and website files should be registered in your name.

Should you put your budget in the brief?

Yes, as a range. A budget range helps a developer propose something that fits instead of a plan far too big or too small. A developer who gets no guidance will often quote for the middle of their range, and the quotes you receive will not be comparable.

If you do not know what to spend:

  1. Read what websites like yours cost. Our guide to what a business website costs explains what you are paying for.

  2. Ask two or three developers for a rough range before you write the final brief.

  3. Decide the most you are willing to spend, then ask what the developer can deliver for 70% of it. You will see what they would cut first, and that tells you what they think matters.

Think about the costs after launch too. Ask what you will pay each year for hosting, the domain, security updates and support.

What to consider if you are in Nigeria, the UAE or the UK

Most briefing guides online are written for American or European buyers. Depending on where your customers are, add the points that apply to you.

  • Currency. Ask which currency the quote is in. If it is in dollars and your income is in naira or dirhams, the cost can move before you pay. Agree when the price is fixed.

  • Payments. Say how customers will pay. In Nigeria that usually means a gateway such as Paystack or Flutterwave. In the UAE and UK, cards and Stripe are common. Ask the developer which they have set up before.

  • WhatsApp. If customers contact you on WhatsApp, say so, and ask for a click to chat button. Our guide on contact forms, WhatsApp and booking covers the setup.

  • Phones first. If most of your visitors are on phones, make that a requirement and ask to see a site the developer built on a phone. Our guide on mobile first websites explains why.

  • Language. If you need the site in English and Arabic, say so at the start, because right to left layouts change the design work.

  • Data protection. If you collect names and numbers, ask how the site handles consent and personal data under the law that applies to you, such as Nigeria's data protection law, UK GDPR or the UAE's rules.

  • Domain and hosting. Ask where the site will be hosted and which domain you will use, for example .com or .ng, and who registers it.

A short template you can copy

Fill in each line and send it to every developer you contact. If you are short of time, this is the one page minimum.

  1. Business: what we do, who we serve, where we work.

  2. Goal: the main thing the site must achieve, and how we will measure it.

  3. Audience: who visits and what they want.

  4. Pages: the pages we expect.

  5. Content: what is ready and what is not, and who writes the rest.

  6. Features: must have, should have, nice to have.

  7. Examples: sites we like and dislike, and why.

  8. Brand: logo, colours, fonts, or a note that we do not have them yet.

  9. Search: whether we want the site set up to be found, and for which services and places.

  10. Updates: who will edit the site.

  11. Budget: our range.

  12. Timeline: launch date and the reason.

  13. Decision maker: who approves.

  14. Access and ownership: domain, hosting, analytics, and who holds them.

A worked example

Here is a short brief for a made up business, so you can see the level of detail that works. The business is not real.

Business. A catering company in Lagos that serves weddings and office events. We want to be known for reliable service and clear pricing.

Goal. Get 20 event enquiries a month. We will count form submissions and WhatsApp clicks.

Audience. Brides and office managers, mostly on phones, who compare two or three caterers before they ask for a price.

Pages. Home, menus, past events, about, contact. The current address /menu must keep working.

Content. We have logo and 40 photos. We need menu descriptions and a short about page written.

Features. Must have: enquiry form, WhatsApp button. Should have: gallery. Nice to have: online payment for deposits.

Budget and timeline. A set range, with launch in eight weeks, before the wedding season starts.

Decision maker. The owner.

That is under 200 words, and a developer could quote from it.

How to compare quotes

When the quotes arrive, do not just look at the price. Put the same questions to each one.

  • Did they ask questions first? A quote with no questions behind it is a guess.

  • Does it match your must haves? Check each one is listed and priced.

  • What is not included? Content writing, photography, extra pages, SEO setup and training are common extras.

  • How many rounds of changes are included? And what does an extra round cost?

  • What happens if the scope grows? Ask how changes are handled. Extra work beyond the brief, called scope creep, should be agreed in writing with a price before it starts.

  • What do you pay every year? Hosting, domain, maintenance and support.

  • Who owns the website at the end? The domain, the files and the admin logins should be yours.

  • Can you see their work? Ask for live examples and a past client you can speak to.

Score each quote on these points out of five and add up the totals. It will not make the decision for you, but it stops the cheapest quote winning by default.

Questions to ask the developer back

  • How do you prefer to work, and how often will I see progress?

  • What do you need from me, and by when?

  • Who will be working on my project?

  • What is the process for approving the design?

  • What happens after launch if something breaks?

  • Can I edit the site myself afterwards?

Red flags

On the developer's side:

  • A quote that arrives with no questions asked.

  • A fixed price with no list of what it covers.

  • Pressure to decide quickly.

  • No mention of who owns the domain and the files.

  • An unwillingness to show real examples of finished work.

  • No written agreement.

On your side, a brief that has these problems will lead to trouble too:

  • Goals like "make it modern" with nothing measurable.

  • Five people with the final say.

  • A budget you will not share.

  • Features that keep being added after the quote is agreed.

What if you do not know what you need?

You can still brief a developer. Write a one page version with your business, who your customers are, what you want visitors to do, and a few sites you like. Then ask the developer for a discovery call before they quote. A good developer will ask you the rest of the questions in this guide and turn the answers into a proposal.

Common questions

What is a website brief and why do I need one?

A website brief is a short document that explains what you need from a website, who it is for and what it should achieve. It gives every developer the same information, which makes quotes comparable and reduces guesswork.

What should a web design brief include?

Your business, goals, audience, pages, content, features, examples, brand, search needs, who updates the site, budget, timeline, who decides and what access you can provide.

How long should a website brief be?

One or two pages for a small site. Four to eight for a larger build.

Should I share my budget?

Yes, as a range. It lets the developer suggest what is achievable and makes proposals easier to compare.

Is a website brief the same as a requirements document?

They overlap. A brief explains the goals and the context in plain language. A requirements document lists the exact features and technical details. Small businesses usually need only the brief, and developers often write the detailed requirements from it.

Who writes the brief, me or the developer?

You write the first version, because only you know your business. A good developer will ask questions and help you tighten it.

Can I change the brief once the work starts?

Small changes are usually fine. Large changes in scope often change the price and the timeline, so agree how that will be handled before you begin.

Can I brief an agency without a formal document?

Yes, you can brief by call or message. Even so, write down what was agreed afterwards, so both sides have the same record.

Want a brief written with you, not alone?

If you are not sure what to put in the brief, we can go through it together. Our free one hour consultation walks through these same questions: your goals, your customers, the pages and features you need, and a realistic budget. We then send a quote based on your answers, with what is included and what is not set out clearly. If you already have a brief, send it with your request and we will quote from it.

Book a free consultation, send us your brief and ask for a quote, or see how we build business websites.

Related reading

Liked this? Good. Now imagine what we could do for your brand. Let’s put this thinking to work.

Start a Project

Ready to build a brand that actually works?