Website Blueprint
This is for organisations that already know a restructure or rebuild is needed — and now need a clear plan to execute it properly.
↳ THE STARTING POINT
When the bones need rethinking.
Some websites don't need to be rebuilt from scratch. They need someone to step back, work out what's actually there, and produce a clear plan for how it should be restructured — one that any capable team can pick up and execute.
That's this.
Not sure what's wrong yet? Start with a Website Diagnosis first.
↳ WHAT THIS INVOLVES
Foundations first. Surface later.
A Blueprint defines the structure, content and logic of the site before anything is designed or built.
Most web projects fix the surface without fixing the thinking underneath — new design, same confused structure, same inside-out content. A tidier version of the same problem.
A Blueprint starts differently.
Before any structural decisions get made, the content gets reframed. Most organisations have spent years describing what they do from the inside out — organised around their own structure rather than the problems their users are trying to solve. Getting to genuine clarity takes honest conversations, good questions, and sometimes the willingness to confront gaps in the offer itself. It's slow work, but it's the work that makes everything else stick.
From there, the structural plan follows: information architecture, navigation, page purpose, content hierarchy, user pathways. Clear decisions about what stays, moves, combines or goes. The deliverable is a concrete document — specific enough that any competent team can build from it without needing to reinterpret the strategy as they go.
↳ THE PATTERN
Problems that make a Blueprint necessary tend to look the same.
Services or offerings that overlap or compete with each other. Navigation that's grown without clear logic. Content that's duplicated, buried or out of date. A homepage trying to do too much — or too little. Pages that read like internal documents rather than web pages written for real people. A site structure that made sense three years ago but no longer reflects what the organisation actually does.
If any of that sounds familiar, a Blueprint is probably the right next step.
↳ WHAT GETS DELIVERED?
A diagnosis, a roadmap, and a clear path forward.
You get:
Site architecture and navigation structure
Page-by-page plan (purpose, hierarchy, content requirements)
User journeys across key pathways
Content structure and messaging direction
Implementation-ready briefing document
