Skip to content

Insights

Before the design: what your website needs to say

A practical brief starts with your customers, the decision they are making and the next step you want them to take.

Website planning3 min read

Guidance from Clara, an independent web design, development and search studio in Norway.

A website brief you can fill in

Use these prompts for a first conversation. Unknown answers are useful too: they identify what the project needs to resolve. Include existing URLs and describe the business outcome before requesting particular features.

  • Business and audience: what we offer, who needs it, and where we can deliver it.
  • Main action: what a visitor should be able to enquire about, book or buy.
  • Current website: what works, what fails, and which pages customers already use.
  • Content and proof: approved services, photographs, project examples and who can confirm the facts.
  • Tools: existing booking, payment, email, customer database or stock systems and the required connections.
  • Project boundaries: decision maker, preferred timing, investment range, must-have functions and ongoing responsibilities.

Choose the main job

A hotel needs a visitor to understand the stay and check availability. An insulation business needs a property owner to recognise the service and request an assessment. Both need a website, but the content and decisions are different.

Write down the main action your site should support. Then describe the customer who takes it, what they already know and what they need to understand first. This is more useful than starting with a list of visual effects.

Collect the questions from real conversations

The questions you answer before a sale are a strong starting point for website content. Group them by service or audience and identify which ones affect the decision to enquire.

  • What does the service include, and who is it for?
  • Where is it available?
  • What affects the price or timing?
  • What evidence would help someone trust the business?
  • What happens after the first enquiry?

Show the business you actually have

Gather current service descriptions, approved project examples, useful photographs and genuine customer feedback you have permission to use. Flag anything out of date or difficult to substantiate.

A specific example of work can say more than a broad claim about quality. Describe the context and the work accurately; only use a commercial result when you can support it.

Separate a link from an integration

Linking to an existing booking page is different from building a booking engine. An enquiry form is different from a customer account system. Name the tools you use and explain what should happen between them.

This helps define the build and the running costs. It also identifies accounts, permissions and information needed before development can begin.

Make the practical boundaries visible

Share your preferred timing, investment range, decision maker and any fixed launch date. List what must be ready for launch and what can follow later.

The result does not need to be a long document. A useful brief gives the project a clear purpose and leaves room for a recommendation on the best way to achieve it.

Explore all guides

Your next move

You’ve built the business.
Let’s build what’s next.

A new website, better search visibility or help looking after your site. Tell Aron what you’re working on and where you need help.

Tell Aron about your project

No finished brief needed. No obligation.