Many website projects begin with a page list and end with a debate about the homepage. The missing ingredient is usually the same: nobody wrote down what the site is for, who will maintain it and how success will be judged.

The business outcome, in one sentence

A useful brief can finish this sentence: 'This website exists so that ___.' An enquiry volume target, a shorter sales cycle, fewer repetitive support questions, a credible presence for partnerships — the outcome should be specific enough that a design decision can be tested against it.

The audience, including the one you forgot

Most businesses describe their buyer well and their secondary audience poorly. Yet secondary audiences often create the most friction: existing customers looking for support, candidates evaluating the company, distributors checking stock, journalists verifying claims.

Write down every group that will land on the site, what they already know and what they need to do next. The navigation and page structure should follow from those answers, not from an internal org chart.

The content reality

Design built around placeholder text is design built on a guess. Before layout begins, we ask which content exists, who writes it and how long approval takes. If photography, product data or testimonials do not exist yet, the design should not depend on them.

This is also where honesty matters. If a page requires claims the business cannot support, it should not be in the plan. A shorter site with real substance is better than a complete sitemap filled with generic copy.

The operational owner

Someone inside the business must own the site after launch. That person needs access to the domain, hosting, content system, analytics and form destinations. Handover is not a zip file; it is a working set of accounts, documentation and a short walkthrough.

  • Who can approve a content change?
  • Who receives form submissions, and what happens next?
  • Who renews the domain, certificate and hosting?
  • Which analytics and advertising accounts exist, and who owns them?
  • What is the support path if something breaks?

Integration expectations

A website is rarely standalone. Payments, CRM, inventory, email, WhatsApp, analytics and advertising all need to connect. A good brief identifies which systems exist, who administers them and what data must move. Discovering an integration late is one of the most reliable ways to blow a budget.

What success looks like after launch

Launch is a date, not a result. Agree in advance which measures will be reviewed and when: enquiry quality, form completion, page performance, search visibility, return visits. Then plan a review period where those measures actually change something.

The best website briefs are uncomfortable. They force decisions about audience, ownership and measurement before those decisions can be avoided.

If a partner is not asking these questions, they are probably preparing to design whatever you describe — which is not the same as building what the business needs.

Written by the Lobryx Technologies team. If you would like this thinking applied to your business, start a conversation.

Discuss your project