Design around the visitor's situation

A person seeking urgent help needs different information from someone researching a planned installation. A shop visitor may need to compare dimensions before considering delivery. We define those situations before deciding the page structure, navigation or visual treatment.

The brief records the business identity, approved facts, available photography and priority journeys. It also identifies what the site should not imply, such as unsupported availability, services or a location where customers cannot actually visit.

Make important choices straightforward

Page layouts should explain the offer, reveal relevant detail and provide a clear next step without making readers work through decorative sections. Mobile spacing, readable text, keyboard access and understandable form labels are part of that design work.

Images need a purpose and permission to use them. Real product or job photographs can answer practical questions; decorative imagery must not be presented as proof of staff, premises or completed work.

  • Plan a clear route from each priority page to the appropriate next step.
  • Design empty, loading, validation and failure states where the journey needs them.
  • Check long headings and real content on small screens.

Protect what an existing site already does

A redesign begins with a URL and content inventory. Useful pages, established contact destinations and important search entry points should not disappear because a new template has fewer sections. Any necessary URL changes need a deliberate mapping.

Technical requirements include crawlable content, accurate page titles, sensible internal links and consistent indexing signals. Platform and maintenance decisions are made around the business's editing needs and available support, not around novelty alone.

Agree what launch readiness means

The scope separates design approval, implementation, testing and launch authority. Before release, the agreed checks cover representative devices, contact journeys, important links and search-critical settings. A successful button click is not evidence that an enquiry reached its intended recipient.

The handover should leave you with access arrangements, editing responsibilities and a record of outstanding items. Hosting, ongoing maintenance and additional integrations are explicit decisions rather than assumptions hidden inside the word website.

Common questions

Can you improve a site without replacing it?

Yes. A focused content, navigation or template improvement may be the better brief. The initial review should establish whether a rebuild is justified.

Is SEO included in the design process?

Search requirements inform structure and launch checks. Ongoing research, content development and performance review need their own agreed scope.

Will the site be easy to maintain?

Maintenance needs form part of the brief. We agree who will edit content, manage technical updates and handle any integrations before choosing the implementation approach.