Start with what visitors need to do
Before choosing a layout, we work out who is coming to the site and what they need from it. A company site may need to explain several services and qualify enquiries. A campaign landing page may need to support one offer and one action.
That distinction shapes the page structure, content and functionality. Visual character matters, but it should help people understand the business rather than compete with the task.
A project you can explore
Our own website brings an interactive service explorer and a project brief into the same experience. The detailed pages give visitors the information they need before getting in touch.
What do you need to build?
- Company & service websites
- Give people a clear view of your offer, with service pages, project examples and an enquiry route. We plan the navigation and content around the questions a prospective customer needs answered.
- Landing pages
- Present one offer to a defined audience. A launch or campaign page needs a clear message, supporting evidence and an action that works on a phone as well as a desktop.
- Website redesigns
- Improve an existing site while accounting for useful content, working features and established URLs. The scope includes what to retain, what to rebuild and where old addresses should lead.
- Custom web experiences
- Add an interaction with a purpose: explore services, prepare a project brief or compare a set of inputs. We define the behaviour and test it with keyboard, touch and reduced-motion preferences.
What a website project can include
- Content & site structure
- A page plan, navigation and the information each page needs. We identify what is already usable, what needs rewriting and what must be supplied before launch.
- UX & visual design
- Responsive page layouts, clear reading order, accessible controls and a visual direction consistent with your brand. You review representative pages before the design expands.
- Development & integrations
- The agreed pages and interactions, connected to the services the project needs. Forms, publishing tools and other integrations are scoped explicitly, including account ownership and recurring costs.
- Search & launch foundations
- Crawlable pages, descriptive titles, internal links, canonical URLs, sitemap and correct status responses. These help search engines understand the site; rankings still depend on relevance, competition and evidence.
- Testing & handover
- Checks of the key journeys, mobile layouts and launch configuration, followed by source files or agreed editing access and instructions for the people responsible for the site.
Choose how you will manage the website
The editing needs help determine the build. A company site that changes occasionally may suit a lightweight static website. A team publishing regularly may need a content management system, reusable page layouts and a review process. We agree on who will make changes and what they need to edit before choosing the tools.
The same applies to functionality. A contact route, booking tool or CRM connection needs a defined destination and someone responsible for the account. A login, payment flow or customer portal changes the scope and needs its own requirements; it is not implied by a standard company website.
The proposal identifies domain and hosting ownership, source or editing access, third-party licences, recurring charges and any ongoing support. You should know how the site will be updated after launch.
Content, design, build, launch
Agree on the job. We map the pages, functions and launch requirements. Content ownership, review rounds and acceptance criteria belong in the scope.
Review the direction. A representative page establishes the typography, layout and visual language. You can see the work in progress and address problems before every page is built.
Test the real journey. We check the important actions, such as navigating to a service, reading on a phone and making an enquiry. A form is only finished when its submission or email behaviour is understood and tested.
Connect and hand over. The launch includes the agreed domain and hosting setup. We explain the editing route, account responsibilities and any ongoing maintenance.
What affects the cost and timing?
Page count is only part of the answer. Custom interactions, unfinished copy, integrations, content migration, multiple languages and the number of approval stages all affect the project. A simple launch page with final content differs substantially from a redesign with several connected systems.
Our website brief guide helps you describe the requirements before asking for a quote. If you have an existing site, include its address and explain what is not working.
For a first discussion, send your audience, the pages or functions you need, the content already available and any fixed launch date. Prepare a website project brief.
The content and the work behind the site
If the offer is hard to explain, start with brand strategy and messaging. If the website creates repetitive administrative work, a separate automation project can improve what happens after an enquiry arrives.
Questions about the build
Can you redesign an existing website?
Yes. We first review the existing content, useful URLs, functionality and any available search data. A redesign should account for redirects and preserve valuable content rather than discard it without checking.
Will I be able to change the site later?
Yes. We agree on the editing and ownership model before development. Depending on the project, that may mean a content management system, an editable source handover or an agreed support arrangement.
Are domains, hosting and paid tools included?
They are identified in the proposal. Registration, hosting, email and specialist software may have separate recurring charges; the scope should say who owns and pays for each account.
Does a new website guarantee Google rankings?
No. Technical foundations make the site easier to crawl and understand, but competitive search visibility also needs useful content, a clear market and genuine evidence of the business’s work.
Do you build custom interactions?
Yes, when they serve the project. We consider performance, keyboard access, mobile use and reduced-motion preferences alongside the visual effect.
How will I review the work?
You review the page structure and design direction before the full build. Working previews let you check the content and key interactions, with feedback stages agreed at the start.