What a brief should contain before the first pixel
Build a useful website project brief covering goals, audiences, pages, content, features, responsibilities, budget, timeline and approval rules.

A brief has one job: to let both the client and the agency tell, at the end, whether the work is done. Projects rarely go off the rails during development. They go wrong weeks earlier, on the day nobody wrote down what was expected.
We read briefs, and write them with clients, several times a month. The good ones fit on three or four pages. The bad ones run to thirty and still miss the point.
What a brief is really for
Most people treat it as paperwork, a file sent to three agencies so the quotes can be compared. That is its least interesting use. Its value shows up later, when a question lands mid-project. Was the Arabic version included? Who writes the rooms page? Should the booking form also trigger a WhatsApp message? If the answer is on paper, the conversation takes two minutes. If it is not, it can cost a week and a little goodwill.
So a good brief protects both sides. The client knows what they bought. The agency knows what it has to deliver, and can say without awkwardness that a new request needs a change order. If you are planning a new site, our website design page shows how the brief feeds each stage.
The six essentials
1. A measurable objective
“A beautiful modern website” cannot be checked. “Twenty qualified quote requests a month within six months” can. For a riad in the medina, the goal might be to move some bookings away from the big platforms and onto the riad’s own site. For an accountancy firm in Casablanca, it might be meetings with established SMEs instead of calls from students looking for an internship. A number steers every later decision, from page count to technology.
2. The person you are building for
One primary profile, described in concrete terms: where they come from, what they want, what makes them hesitate, which device they find you on. “Tourists” is too vague. “A couple in their mid-forties from Lyon planning a long weekend, comparing five riads on a phone in the evening, wanting to know whether the roof terrace is private” already writes half the home page. If there is a second audience, say Moroccan customers who book in Arabic or darija over WhatsApp, note it down, then decide which comes first.
3. The page list
Named, counted, each with the action you expect from the visitor: call, book, download a brochure, fill in a form. A page with no expected action is often a page you can live without. Settle the languages at this stage too. A site in French, English and Arabic does not cost three times as much, but Arabic reads right to left, and that has to be planned from the first design.
4. Who supplies the content
This is by far the most common cause of delay we see. Copy, photographs, menus, prices, legal pages: each batch needs an owner and a date. If the restaurant photos need reshooting, book the photographer when the contract is signed; the week before launch is too late. If the agency is writing the copy, the brief should say how many pages that covers and who signs them off.
5. Technical access
Domain name, hosting, Google Business Profile, Search Console, Meta Business Suite, Instagram. All of it in your name, ideally your company’s, with the logins in hand before kick-off. We regularly meet businesses whose .ma domain was registered by a former supplier who no longer picks up the phone. Getting it back can take weeks.
6. What “done” means
How many rounds of feedback are included on the design, then on the build. What counts as a fix (a bug, a typo, something that does not match the approved design) and what counts as a billable change (a new section, an extra feature). Written down plainly, this one paragraph heads off most end-of-project friction.
Constraints specific to Morocco
- Card payments: taking cards online usually means a CMI contract through your bank, and it takes time. Start the process alongside the build.
- Cash on delivery, still widely expected in e‑commerce, and how orders will be confirmed (a phone call, a WhatsApp message).
- Personal data: any form collects it, which brings Law 09-08 and the CNDP into play. Decide who writes the privacy policy.
- Languages, and right-to-left layout if Arabic is on the list.
- How your customers prefer to get in touch. For many local businesses a WhatsApp button matters more than a contact form.
What does not belong in it
First, technical choices imposed with no business reason behind them. “The site must be built on WordPress” only makes sense if someone on your team already knows how to run it. Otherwise, describe the need (“I want to update the restaurant menu myself every season”) and let the agency suggest the tool.
Then there are the contradictory visual references collected over months: a minimalist luxury site, a very colourful one, a third full of animation. Three annotated references (“I like how the prices are laid out here”) are worth more than a folder of twenty unexplained screenshots.
Finally, features listed “just in case”: a members' area, a blog, live chat, a comparison tool. Every line added out of caution costs budget that will be missing elsewhere, usually on the content, which is the part visitors actually read.
You know a brief did its job when, at handover, nobody needs to argue about it.
Write down the budget and the deadline anyway
Many clients are reluctant to name a budget in case the agency simply spends all of it. Fair enough. Without a range, though, the agency is guessing: it proposes too much or too little, and a round of emails is wasted. An honest range lets the agency build the best version that fits, and say clearly what falls outside it.
For timing, start from the date that genuinely matters: a restaurant opening, the start of high season, a trade fair in Casablanca. Then work backwards. A well-made brochure site usually needs several weeks between brief sign-off and launch, and most of that time depends on approvals and content, rarely on code.
Where to start
Set aside an hour and answer these in writing:
- What measurable change should the site bring within six months?
- Who is the main visitor, and what should they do when they arrive?
- Which pages, in which languages?
- Who supplies each piece of content, and by when?
- Are all the accounts in your name?
- What is the budget range, and which date cannot move?
Those six answers are enough to start a proper conversation. Send them as they are through our quote request and we will come back with the questions still missing.


