Start a project ع
Start a project

contact.chokri@gmail.com

November 19, 2026

How to Write a Website Project Brief Before Contacting Any Designer

What to put in a website project brief: ten sections, a copyable template, common mistakes, and why it makes quotes more accurate.

A document page with one highlighted line

“I want a website for my company. How much?”

Almost every designer gets this message every week. And there is no real price to give in reply, because it says nothing about the project: not the goal, the audience, the size or the deadline.

The answer is a project brief: a page or two explaining what you want, written before you contact any designer or agency. It doesn’t need to be perfect or technical. It just needs to be clear.

Why a brief is worth your time

  • More accurate quotes: a designer prices what they understand, not what they imagine.
  • Comparable offers: when everyone gets the same brief, you compare like with like.
  • Less time in meetings: half the questions are answered in advance.
  • Clarity for you: writing a brief forces you to think about things you may not have settled yet.

What to put in the brief

Ten sections that cover everything a designer needs to understand your project:

1. Who are you?

Two sentences about your business: what you offer, to whom, and since when. Not a marketing pitch, just a simple explanation.

2. What is the goal of the project?

The most important section. What do you want to happen after launch? More enquiries? Bookings? Sales? A more professional look for corporate clients? Fewer repetitive phone calls? Try to choose one main goal.

3. Who is your audience?

Who will use the site? Individuals or businesses? In which country? What are they looking for when they arrive? And what worries them before they contact you?

4. What is the current situation?

Do you have a site today? What don’t you like about it, and what works well? If you don’t have one, how do customers reach you now?

5. Pages and features

A rough list of the pages you expect and the features you need: a contact form, bookings, a shop, user accounts, or a connection to another system. It is fine to say “I don’t know, I need a recommendation”.

6. Content

Is the text ready? Do you have real photos? Or do you need someone to write and photograph? This changes the time and cost a lot.

7. Languages

Arabic only? Arabic and English? Arabic and French? And which one is the main language?

8. Examples you like, and why

Two or three links to sites you like, and more importantly: exactly what you like about them. “I like it” doesn’t help much; “I like that the prices are clear from the first page” helps a lot. Add an example of what you don’t like too.

9. Budget and deadline

A rough budget range, the launch date you need, and whether it is tied to a specific event. Many people hide their budget for fear it will be exploited, but sharing it helps the designer propose a solution that fits, rather than an ideal one you can’t afford.

10. Who decides?

Who will review and approve the work? One person or a committee? This affects the number of review rounds and the timeline.

A quick template you can copy

  • Business: …
  • Main goal of the project: …
  • Audience: …
  • Current situation: …
  • Expected pages and features: …
  • Content ready? Yes / partly / no
  • Languages: …
  • Examples I like, and why: …
  • Rough budget and deadline: …
  • Decision-maker: …

Common brief mistakes

  • Describing the solution instead of the problem: “I want an app” instead of “my customers struggle to book”. A clear problem can lead to a simpler, cheaper solution than you imagine.
  • Too long: twenty pages of detail where priorities get lost. A page or two is enough to start.
  • Everything is “important”: if everything is a priority, nothing is. Rank things.
  • A different brief for each designer: which makes comparing offers impossible.

Don’t wait for the perfect brief

If these sections feel like a lot, start with three: what you offer, what the goal is, and who it is for. A short, clear brief is far better than nothing, and better than a long brief that never gets sent.

A good designer will help you fill in the rest by asking the right questions. And once your brief is ready, you’ll know what to ask before you sign and what drives the cost of your project.

In short

A brief is not a formal document; it is a thinking tool. It makes you clearer about what you want, makes the designer more precise about what they propose, and makes the whole project less full of surprises.

And you can start now: the form at the bottom of this page asks you to describe your project in just two sentences. The details can come later.

Start a Project

Have a project in mind? Let's talk about what you need.

Whether you are defining a new digital product, improving an existing experience, building a website, or need support with a specific digital project, send me a brief overview and I'll suggest the best way forward.

A short brief is enough to start. I'll get back to you within two working days.

Your email is used only to reply to this message.

Direct

What happens next

  • I read the brief and reply within two working days
  • A 30-minute call to understand the situation
  • A written proposal with scope and a fixed price
Download CV