An inventory with commercial judgement
Identify pages with demand, enquiries, links or information customers use. Each receives a decision: retain, improve, combine or retire with a justified destination.
——
Website redesign to clarify your offer, improve customer journeys and plan a transition with content, SEO, forms and data checked before launch.
Web design
Start by understanding what the current website contributes and what needs to change.
A website redesign starts with concrete business questions: which enquiries you want, which pages already help generate them and where the journey loses momentum. We review content, search, navigation, forms and maintenance to define a proportionate intervention. That may mean a new architecture or focused improvements to selected templates; the decision follows the evidence. Transition is part of the project: what remains, how old URLs relate to new ones and which journeys need verification before launch.
Identify pages with demand, enquiries, links or information customers use. Each receives a decision: retain, improve, combine or retire with a justified destination.
Organise navigation, services and evidence around buying questions. Visitors should understand their fit and find the next step without touring the entire website.
Content, redirects, forms, analytics and editorial permissions belong in the initial scope. This lets us check the new website against real tasks before opening it.
For a proposal, bring your current website, priority services, examples of useful enquiries and tasks your team cannot complete with today’s system. We use that material to define templates, content, integrations, languages and ownership. The proposal should distinguish first-phase delivery from work prepared for a later stage, with clear dependencies and acceptance criteria.
The inventory connects existing URLs with their business value. A page may receive few visits while answering an important question before contact; another may attract many people who do not fit the offer. Review those situations with the commercial team. For pages that change, define a coherent destination and a reason. Images, documents and links people already use belong in the review too.
Use representative content while defining the design: a real service, a project with complete information and a recurring customer question. This reveals whether the hierarchy explains the offer, whether evidence appears at the right moment and whether the team can maintain it. CMS fields and components should support that work. Define who prepares, reviews and approves each content type so publication does not depend on a single person.
Before launch, review a complete journey: arrival, reading the service, exploring a project and using the contact route. Check forms and agreed destinations, mobile behaviour, links, URL transition and search tags. After publication, review issues and compare available signals with the starting point. Follow-up informs adjustments; commercial outcomes need assessment through enquiries and the business’s response as well as visits.
Not resolved — gathered. The current site, who you are addressing, what you offer, what material exists and who decides. The first phase separates what blocks progress from what can be settled while building.
By journeys and decisions, not by number of screens. We agree what a person has to be able to do, what content supports it and what stays out of this phase. That is what gets costed.
Less than feared, but at specific moments. Two or three decision sessions and access to whoever knows the business. The rest moves forward without status meetings that decide nothing.
The journeys that matter are tested on mobile and desktop, along with forms, real-world speed, accessibility and anything that has moved since the previous site. The checklist comes from the scope, not from a generic template.
By the quality of the enquiries that arrive and by what the team manages on its own. More traffic without better conversations is not an improvement, and it is worth saying so up front.
You get documentation on how each part is edited and a prioritised list of what was deferred. From there, either the team runs it or we agree a phased follow-up.
A selection of work showing context, decisions and outcomes.
Tell us where things stand and we can assess the most useful approach for the project.
