Start with the customer’s decision.
A useful website explains who the service suits, what is offered, the supporting evidence and the next action. List the questions customers ask before contacting you. Group related answers before choosing the number of pages.
Pattern one: several services, one company.
Dream Heights explains residential, commercial and industrial, and utility-scale solar applications. Solutions, process explanations, FAQs and enquiry routes provide context before a quotation.
For a multi-service business, define what each customer should prepare for a discussion. Distinguish illustrative imagery or concepts from completed work. The Dream Heights project note concerns the website; the client’s solar imagery is illustrative.
Pattern two: choose the support, then choose a time.
Ain’s Little Cells separates Excel coaching, templates and custom help. Coaching has a booking journey; template and custom-work discussions use WhatsApp. Interactive workbook previews use labelled sample data.
For appointment services, plan availability, confirmation, slot conflicts and cancellation together. Decide whether payment happens on the website or is arranged separately.
A brief you can use.
- The main customer and the decision they need to make.
- Services, products or appointment types to explain.
- Real materials available and permission to use them.
- The main action and who handles the resulting enquiry.
- Editing, integrations, languages, handover and recurring costs.
Inspect examples with a purpose.
Open the related project notes below for screenshots, workflow explanations and links to the real websites. Use the patterns relevant to your requirements; agree the final design and functions in your project scope.
A checklist before redesigning an existing website.
Start with the pages already receiving search clicks, enquiries or useful links. Record their purpose and decide where each will live after the redesign. Map changed URLs to relevant replacement content.
Inventory approved copy, project evidence, forms and booking rules. Agree domain and account access, content ownership, editing, handover and recurring fees. Test enquiry and booking journeys in each supported language before launch.
Keep a dated baseline and check redirects, search indexing and received enquiries after the change. Separate deployment checks from later evidence of search or business performance.
- Which useful URLs and customer questions must be preserved?
- Which content and project claims can be supported?
- Who owns accounts and manages updates after handover?
- What acceptance checks cover the full customer journey?