1. Who is the website for?

Choose your main audience and the task they want to complete. A potential customer comparing suppliers needs different information from an existing customer looking for support. Start with the most important journey, then add secondary paths.

2. What should visitors do next?

Give each page a useful next step: explore a service, read a relevant case study or outline a project. Keep the primary action easy to find. A form should ask only for information needed to start the conversation.

3. What can you show, rather than claim?

Prepare a clear service description, real project material and contact details. For a case study, explain the problem, your contribution and the outcome you can substantiate. Ask for permission before publishing client names, logos or private project information.

4. Which languages and connections are needed?

List the markets you serve, the languages your team can support and any systems the website must connect to. Separate website translation from customer support availability. For each connection, identify the data, destination and person responsible.

5. Who will keep it useful?

Decide who updates articles, checks forms and maintains contact details. Agree on mobile behaviour, accessibility checks and a review process. A website is easier to run when ownership is clear before launch.

Have a project in mind?

Tell us about your current workflow and what you want to improve.