Define the business job of the website
Begin with the change the business needs. A local service company may need visitors to understand its offer and make an enquiry. A specialist supplier may need a product catalogue that supports a sales conversation. A growing organisation may need a clearer identity and a content process that its team can maintain. Write down the primary audience, the questions they ask and the action they should be able to take. This gives the project a direction beyond a list of visual preferences.
Look for a clear discovery process
A useful discovery conversation explores the business, the audience and the information needed for the site. It should identify the pages, the content owners and the dependencies that affect the schedule. Ask how the partner will organise the navigation and how proposed design decisions connect with the brief. Examples of previous work can help you understand the approach, but the conversation should return to the needs of your own business. A clear scope makes it easier to assess proposals consistently.
Understand how content will be produced
The website needs accurate service descriptions, contact information and relevant evidence. Decide who will supply source material and who will write or edit it. Identify the photographs, brand files and project information that can be used publicly. Good content preparation reduces uncertainty later in the project. It also gives the design a stronger foundation because the interface can be built around the information people need rather than temporary text that may not fit the final purpose.
Assess the whole visitor journey
Review how the site works on a phone, how pages explain the offer and how a visitor reaches the enquiry form. Check that the form collects information the business can use and that a responsible person receives it. Search visibility depends on useful page content and a technically accessible website, so discuss page structure, metadata and indexing as part of the build. The experience should remain understandable even when the visitor enters through an individual service page rather than the homepage.
Agree ownership and maintenance
Document domain ownership, hosting access, administrator accounts and the process for future changes. Ask how backups are created and restored, how updates are handled and what the business team can edit. A project handover should make routine operation clear. The right partnership brings together a purposeful brief, an appropriate design and a practical system the business can continue to use.
Explore AI solutions, website development or prepare a project brief with Amsotics.
Bring your business question.
Share the goal, the constraints and what a better outcome would look like.
Start a Project ↗
