How we build matters.
A website is the result of hundreds of small decisions. Our approach makes sure they all support the same goal.
Structure first. Design second. Performance throughout.
We don’t start with a theme.
We start with questions.
What does the business offer?
Who is the website for?
What are people trying to understand?
What does the business want them to do?
What’s missing from the current experience?
Those answers decide what gets built. The visual direction comes later.
Structure, words, design. In that order.
01
Structure before screens
Good information architecture makes a website feel obvious. Visitors shouldn’t have to reverse-engineer your company to find the service they need.
We work out the hierarchy first: what belongs on the homepage, what needs its own page, how services relate and where the important paths lead. That structure is also a stronger foundation for content and search.
02
Write before decorating
Designing around placeholder copy creates the wrong constraints. We establish the core message early, so the layout responds to the content instead of forcing it into arbitrary spaces.
Copy and design still evolve together. But the website always knows what it’s trying to say.
03
Design with a job to do
We like beautiful websites. But beauty isn’t enough.
The design should establish hierarchy, communicate quality, make information easier to absorb and give the business the right visual presence. We aim for work that feels considered, not decorated.
The process, step by step.
- 01
Understand
We start with the business: your services, customers, goals, current website and what needs to change. We ask the questions that need answering before anyone starts designing.
- 02
Structure
We decide which pages are needed and what each one must achieve. The goal is a clear information architecture, not pages added because other websites have them.
- 03
Write
We shape the message and develop the core website copy, giving the design something meaningful to work around.
- 04
Design
With the structure and message clear, we build the visual system around them. Typography, spacing, imagery and interaction make the content easier to understand, not harder.
- 05
Build
The approved direction is developed in Astro, with responsive behaviour, accessibility, CMS requirements, technical SEO and performance considered throughout.
- 06
Test & launch
We check the details across devices, review forms and links, configure the agreed search infrastructure and prepare the website for launch.
The technology follows the need.
Why Astro?
Lightweight by default, flexible where it counts
We specialise in content-led business and marketing websites, and Astro is particularly well suited to that work.
It produces lightweight pages without unnecessary client-side JavaScript, while still letting us add interactive functionality where a project genuinely needs it. That means more control over the finished experience.
WordPress isn’t bad
It simply isn’t our default
No single technology is right for every website. WordPress can be an excellent choice for sites that benefit from its ecosystem and publishing workflow.
For the focused business sites we usually build, we prefer Astro’s leaner approach. We choose the tool for the result we want, not because a platform is familiar.
Content management
A CMS is a tool, not a requirement
We don’t install one automatically because that’s how websites have traditionally been built. First we establish what content changes, who changes it and how often.
If the business needs an editing interface, we integrate Sanity or EmDash with a content model built around those needs. If it doesn’t, we keep the architecture simpler.
Performance without giving up control
Fast to load. Easy to keep current.
Choosing Astro doesn’t mean choosing a website nobody can edit. Astro gives us control over how the public site is built and delivered; a CMS gives your team control over the content they’re responsible for.
When required, we connect the two deliberately, so the site stays fast and carefully structured while the business keeps its content up to date.
SEO is part of the architecture.
Technical SEO isn’t a button.
Search engines interpret websites through the same decisions visitors experience: hierarchy, content, links, semantics and performance. So we consider search while planning and building the website, rather than handing it over as a problem for later.
The result is a site with the technical fundamentals in place from launch.
Performance in everything.
Performance lives in the code. But also in:
The message.
The navigation.
The content.
The mobile experience.
The path to an enquiry.
A website should be efficient at doing its job, as well as efficient at loading the page.
That’s the standard we work to.