Client work / Case studyWebsite design
& development
We design and build custom websites, from content structure and interface design through development and launch.
For companies, organisations and teams replacing an existing site or building something new.
Discuss your website
02 / How information turns into actionEvery page is part
Every page is part
of a conversation.
Design connects what you want to say with what someone needs to know. Follow a visitor’s questions to see how the website responds.
Choose a question to explore its role in the page.
Message + hierarchy
Make the offer clear.
A visitor should recognise what you offer and whether it is relevant to them. Clear language and a deliberate hierarchy give the first screen a useful job.A clear introduction helps visitors recognise what you offer and whether it fits their needs.
Illustrative page structure↗
YOUR BRANDWork About Contact
A considered first impressionGood work. Clearly explained.A focused introduction, followed by the services and information your audience came to find.
Explore services↗Clarity → Confidence → A next step
An illustrative journey, adapted to each project.
03 / Content has to come from somewhereA website is only as clear
A website is only as clear
as what it has to say.
- Existing website
- Brand material
- Services
- Photography
- Sales material
- Rough notes
Website
What you do.The work behind it.A way to get in touch. ↗
Who determines the content?
You bring the knowledge of your business. We work through the material together and recommend what belongs on the website.
- What already exists
- What is useful
- What is outdated
- What is missing
- What deserves its own page
- What can be removed
Together, we agree what needs writing, updating or creating, and who will provide it.
What you need to bring
You don’t need finished website copy before the project starts. What we do need is access to the knowledge, material and people required to understand the business.
04 / Desktop isn’t mobile with less spaceSame website.
Same website.
Different conditions.
● ● ●Desktop / Website↗
Independent design studioObjects.
With presence.
With presence.
Considered pieces for everyday spaces. Explore the collection, the materials and the thinking behind each object.
Explore the work ↗09:41Mobile↗
Independent design studioObjects.
With presence.
With presence.
Considered pieces for everyday spaces.
Explore the work ↗The important part stays first.
DesktopSpace for context, supporting copy and a wide composition.
MobileA shorter introduction, a clear next step and a deliberate reading order.
An illustrative website. Navigation, text, imagery, forms and spacing are considered for the conditions in which people use them.
05 / What development actually addsMost of the website
Most of the website
isn’t visible.
Beneath the surface
- Image loading→optimised
- Forms→validated
- Keyboard interaction→supported
- Routes→tested
- Deployment→verified
The finished design is the starting point. Development gives it the behaviour, structure and resilience it needs in use.
Fast
Image treatment, font loading, rendering and scripts all shape how quickly a page becomes useful.
Accessible
Meaningful structure, readable contrast, keyboard behaviour and clear interactions help more people use the site.
Reliable
Forms, navigation, routes and critical interactions are tested, including what happens when something goes wrong.
Maintainable
Organised components, clear content models and a considered handover make future changes easier to understand and deliver.
Built for what happens after launch
The implementation should still make sense when something changes six months later.
06 / Search should not be an afterthoughtA website needs to work
A website needs to work
for machines too.
Search engines, browsers and measurement systems need to understand the site as clearly as people do.
One websiteTwo ways to read it ↙ ↘
People
- Clear structure
- Useful links
- Readable content
- Fast pages
Search /
systems
- Metadata
- Canonical URLs
- Sitemap
- Structured data
- Crawlability
- Redirects
These technical foundations help systems find, interpret and measure the site. They do not guarantee search rankings.
After launch
Where appropriate, we also configure analytics and search measurement so launch doesn’t become the point at which visibility stops.
07 / What happens after handoverYou shouldn’t need us
You shouldn’t need us
to hold the keys.
Your website / Your access
Depending on the project, handover can include the following. We agree what is included, who needs access and who will manage each part.
AMUI
Your team ↙
Project handoverYour website / Your access
- 01 / Handover item
Production deployment
The live website and how it is released.
- 02 / Handover item
Source repository
The project code and access to its repository.
- 03 / Handover item
Domain configuration
The domain settings and where they are managed.
- 04 / Handover item
Hosting access
Access to the environment running your website.
- 05 / Handover item
Analytics
Access to the measurement property we configure.
- 06 / Handover item
Search Console
Access to your website’s search reporting.
- 07 / Handover item
CMS accounts
Publishing access for the people managing content.
- 08 / Handover item
Documentation
The guidance needed to run, update and maintain the site.
Agreed scope. Clear responsibilities.
Support is a choice
If you want ongoing support, we can provide it. The website should not depend on that arrangement in order to remain yours.
08 / Content management
Publishing regularly?
Websites with frequently changing content may need an editing system behind them. We use Payload CMS where it makes sense, designing the editing model around the content rather than attaching a generic admin panel afterwards.
Payload CMS & Next.js09 / What we buildDoes your project
Does your project
belong here?
Landing pages
Focused campaign or proposition.
Company websites
Services, work, company and conversion.
Content-driven websites
Projects, insights, people, publications.
Website redesigns
Existing sites that need structural, visual or technical change.
10 / Your websiteStart with
Start with
what you have.
Send us the current website, what needs to change and any constraints we should know about.
Discuss a website