Tarjeeh
Start a project

How to prepare a website brief for a Dubai business

Turn a website idea into a clear project brief: audience, pages, Arabic content, enquiry journeys and practical acceptance checks.

Website Development3 min read

A useful website brief explains who the site serves, what visitors need to do, which content is ready and how the finished work will be checked. Start with the business journey, then agree the pages and features. This gives a development team something concrete to estimate and reduces decisions being made late in the build.

Start with one visitor and one useful outcome

Describe your main customer in plain language. A facilities manager checking maintenance services needs different information from a shopper comparing products. Write the question that brings that person to your website and the next action you want them to take. A project enquiry, a telephone call and an online order are different journeys and need different page content.

Include the areas you actually serve and the languages your team can support. For a Dubai business, mention relevant service locations without creating a separate near-identical page for every neighbourhood. List a primary outcome and a secondary contact option; this makes the navigation and calls to action easier to agree.

Make a page and content inventory

For every proposed page, note its purpose, owner and required material. A service page may need an explanation of the work, scope boundaries, project photographs and a contact route. Identify what already exists, what needs rewriting and what needs permission before publication. Original business information is more useful than a collection of competitor screenshots.

Google’s SEO Starter Guide supports understandable site organisation and descriptive links. Apply that principle by giving each page a distinct job. A helpful planning sheet can contain these columns:

  • Page name and the visitor question it answers.
  • Approved text, images and the person responsible for each item.
  • Primary action and any information the visitor must provide.
  • Dependencies such as product data, translations or external accounts.

Specify the enquiry journey, including failure cases

Write down what happens after a visitor selects WhatsApp, submits a form or taps an email link. Identify the receiving number or mailbox and who will respond. Decide which fields are essential, how errors are explained and what the visitor sees after sending. A thank-you message alone does not prove the team received the enquiry.

Ask for a complete test from a customer device to the receiving destination. Include an incorrect phone number, an empty required field and a slow connection. Keep personal information out of URLs and avoid collecting details that your team does not need for an initial conversation.

Plan English and Arabic together

Provide approved names, addresses and service terminology in both languages when the site is bilingual. Explain whether both versions need the same pages and features. Arabic layout needs its own visual review: text direction, form alignment, mixed phone numbers and translated button labels all affect usability.

Treat the language switch as part of the brief. It should keep a visitor on the equivalent page where a translation exists. Include real Arabic copy early enough to check line breaks and content length before approving the design.

Agree what a finished website means

Create a short acceptance checklist before development starts. Include the supported screen sizes, working contact routes, correct page titles, image clarity and who can update the site. Record domain and account ownership, handover material and any ongoing services separately from the build scope.

Ask for assumptions and exclusions in writing. Product imports, booking systems, payment processing and customer accounts can change the project substantially. A focused first release with explicit checks is easier to assess than a long feature list whose responsibilities are unclear.

Common questions

Do I need every page written before requesting a quotation?

You can start with a page inventory and sample content. Mark missing items clearly so the team can separate content work, design and technical development in the proposed scope.

Should a website brief include a fixed delivery date?

Include your target date and explain any external event behind it. The team can then review content availability, integrations and approvals before confirming a realistic delivery plan.

Sources and further reading

Prepared with AI assistance and checked against the sources listed above. Planning examples are illustrative; your project scope is agreed separately.