Choose the main business goal
Start with one primary action: an enquiry, a booking request, a product purchase or a consultation. Other actions can still exist, but the main goal helps guide page structure and design decisions.
Describe who should take that action and what they will need to know first. A technical buyer may need detailed specifications; a local service customer may need location, scope and a simple way to call.
Gather content and assets
Prepare your logo, service list, business contact details, approved photographs and existing website information. For an online store, organise product names, prices, variants and stock data in a consistent format.
Use only testimonials, client names, images and outcome figures that you have permission and evidence to publish. A good-looking placeholder is not a verified business result.
Decide how the site will be edited
A static HTML website is a practical option when the content is stable and the experience is primarily informational. A content management system may be more suitable when a non-technical team needs frequent editing.
Make that decision before design is finalised. Also discuss hosting, backups, account access and who will maintain the website after handover.
Agree on scope and launch checks
List the required pages, forms and integrations in writing. Clarify the number of design revisions, what is needed from your team and which third-party costs sit outside the build fee.
Before launch, test mobile navigation, form validation, contact details and key journeys. Confirm the intended domain and HTTPS setup. Keep a backup of the previous site before replacing it.
Further reading: MDN: HTML and accessibility
