A considered way to rebuild

A practical route from existing site to elevated experience

The process is structured enough to keep decisions moving and flexible enough to respond to what the current website reveals. At each stage, owners know what is needed from them and what the stage is intended to produce.

The work, made manageable

A practical route
from old to useful.

Each stage leaves space to make decisions before they become harder to change.

01 /

Discovery

We review the current website, its content, audiences, goals, technical context, and known points of friction. We identify what should be protected, what needs attention, and which decisions will have the greatest effect.

What you bring

Access to the current website and relevant tools where available, existing brand and content materials, business priorities, audience knowledge, and a candid view of what is difficult today.

What this stage creates

A shared set of priorities, a clearer site structure, and an agreed basis for design and build decisions.

02 /

Design

We turn priorities into page layouts, navigation, content hierarchy, visual direction, and responsive interaction patterns. The work considers clarity, accessibility, brand fit, and the actions visitors need to take.

What you bring

Feedback on proposed structure and layouts, preferred brand references, required content, important user journeys, and decisions about what to keep or revise.

What this stage creates

A coherent design direction and page system that shows how the rebuilt website will work across common screen sizes.

03 /

Build

We implement the approved direction in the chosen website environment, creating reusable components, organising content, and addressing technical foundations such as responsive behavior, metadata, links, forms, and accessibility details.

What you bring

Approved designs, final or near-final content, access to the chosen platform and integrations, functional requirements, and timely review of working pages.

What this stage creates

A working website that can be reviewed in context, with content and functionality assembled for launch preparation.

04 /

Launch and handover

We prepare the release by checking content, links, redirects, forms, indexing settings, responsive layouts, and other agreed launch details. We then provide practical guidance for ownership and ongoing updates.

What you bring

Final approval, domain and hosting access when required, redirect decisions, launch contacts, content sign-off, and confirmation of who will manage the site afterward.

What this stage creates

A controlled handover with a launch-ready website, documented owner tasks, and clarity about the checks and responsibilities that continue after release.

Before we begin

Thoughtful
answers.

Do we need to know exactly what is wrong before starting?

No. A useful starting point is a clear description of what feels difficult, outdated, or limiting. Discovery can turn those observations into specific priorities and can also identify issues that are easy to miss from inside the website.

Can useful parts of our current website stay?

Yes. Existing content, URLs, visual elements, integrations, and workflows are reviewed rather than automatically discarded. Keeping something is sensible when it supports visitors, owners, or the website's wider purpose.

What should we provide during the project?

Owners are most helpful when they provide context, source materials, access details, decisions, and focused feedback. They also need to identify who can approve content, design, technical access, and launch-related choices.

What happens after handover?

The owner takes responsibility for agreed ongoing tasks such as publishing content, reviewing forms, maintaining integrations, and keeping access secure. Handover should make those tasks understandable and identify any items that need specialist support.

A good process starts with context.

Tell us what
the site needs.

We will use the current website and your priorities to map a sensible next step.

Start a conversation