This is a demonstration, not client work. No client has been engaged for this project and no results are claimed. It exists to show the scope and shape of a typical engagement.
Business website
Marketing site for a service business
Demonstration scope: a structured multi-page site for a business with several distinct service lines and a clear enquiry path.
Overview
The project
A service business with four distinct offerings had no online presence. Customers were describing what they needed by phone, and the business was spending time explaining basics before it could quote anything.
This demonstration shows how that situation is typically approached: the offering is broken into separate pages, each written for a different reader, with the enquiry path made obvious on every page.
Objectives
What it needed to achieve
- Explain each service line without a salesperson having to translate it
- Make it obvious how to get in touch from every page
- Be usable on a phone, since most enquiries would arrive from one
- Be editable without a developer
- Be understandable to a search engine
Scope
What was, and was not, included
Scope boundaries matter more than scope size. This is where the work deliberately stopped.
Included
- Information architecture across four service pages plus supporting pages
- Responsive layouts from small phones to large desktops
- An editor so pages and images can be updated in-house
- Enquiry form routed to the correct inbox with visible failure handling
- Per-page metadata, canonical URLs, sitemap and robots configuration
- Performance and accessibility pass before launch
Not included
- Writing all page copy from scratch
- Photography or video production
- Ongoing content marketing
- Paid advertising management
Challenge
A growing service business had no online presence and needed to explain several distinct offerings clearly to audiences that did not know the difference between them.
Solution
A structured information architecture with one page per service, enquiry forms routed to the right inbox, an editor for routine updates, and layouts verified from small phones to large desktops.
Implementation
How it was approached
Discovery established that the four offerings were being confused with one another, so the primary work was writing and structuring rather than visual design.
Each service page was built to be read on its own, with a shared enquiry path rather than page-specific forms.
Layouts were checked at each breakpoint rather than only at desktop width, and keyboard operation was tested as part of the build.
Technical search foundations were added from the start — metadata, canonical URLs, sitemap and structured data — rather than retrofitted later.
Technology
What it was built with
Screenshots are published only once imagery has been supplied and authorised. None are shown for this entry.
Related services
What this project drew on
The service lines this kind of engagement usually involves.
Building something similar?
Tell us what you have in mind and we will come back with questions, an approach and a written scope.