Decide what visitors should do
List the main actions your website should support. For a company site, these could include learning about services, requesting a quotation, sending a project enquiry or finding contact information. Give those actions a priority order so the design has a clear purpose.
Organize the content around real questions
Think about what a visitor needs to know before contacting you. Explain the company, the service categories and how a request is handled. Use accurate company details and approved material. Customer names, photographs, testimonials and partner badges should only be used when you have the appropriate permission.
Separate requests from confirmed purchases
If a service needs a custom scope or quotation, describe the website action as a request. Explain when the team will confirm the scope, pricing and commercial terms. The words on the button and the confirmation message should match the actual business process.
Plan where information comes from
Identify which content is maintained in the website and which information comes from a connected business system. Product prices, order requests and enquiries may need to use a shared backend. Discuss what should happen if a connected service cannot be loaded and provide a practical contact path.
Review the complete visitor journey
Check the route from the home page to a service, from the service to the request form and from the form to its confirmation. Review mobile navigation, keyboard interaction and the clarity of the contact details. A page can look attractive while still making the visitor journey difficult.
Prepare for delivery and future updates
Agree on the hosting destination, the files or source code being delivered and who will maintain the content. Define the checks required before publishing. Keep the responsibilities for the public website and the separate company admin workspace clear so future updates remain manageable.
Have a related requirement?
Discuss it with TCW →
