Website design agency in London.
Give every visit a next step.

That first answer becomes the website brief. On an enquiry site, we count a button click and a completed form as two different things, and agree which inbox a good enquiry should land in. You can then check the agreed measure after launch.

The stages below run in that order, without fixed week numbers, because two parts of the project behave differently. Scope and design take as long as the decisions take: the page list, the content you supply, the approvals. The build is the fixed part, two weeks for a marketing site and two to four weeks for a custom or ecommerce build, counted from the day the design is signed off. You hear from us at least weekly throughout, and whenever something needs your decision.

Bring the existing site, account access, brand assets and whoever can approve the work. We review the current content and note what must survive the rebuild. You approve the primary action, the scope and the measurement plan.

The risk here is an unclear brief. A contact page, recruitment portal and customer login each need their own work. We decide which belong in this release. If the requirement is a single campaign destination, our landing page and website comparison helps settle the boundary before design starts.

Next, we organise the route from arrival to action. The page plan names the sections of the site, how they connect and what each needs to say. For a service page, that might mean an explanation, relevant work and a way to enquire. Navigation labels need to make sense without someone from your team explaining them.

The URL list records which pages stay, merge or retire. Any changed address gets a proposed destination for review. This sits within the rebuild's SEO foundation. For a wider search brief, we can scope ongoing SEO alongside the website.

You sign off the page list, navigation and responsibility for each piece of copy or imagery. We flag missing content before it becomes an empty space in a finished design.

This is where we catch a service page that has a title but no substance. If selling it takes a conversation, we need the useful parts in the copy: the problem, the fit and the next step.

Here you see how the site will read and behave. We design key pages with representative copy, images and calls to action. You review mobile layouts alongside wider screens, including forms, menus and the message a visitor sees after submitting an enquiry.

Your established brand assets guide the layouts. If those need their own brief, brand identity and design sits alongside this project. The website phase applies the agreed identity to the pages people will use.

Useful feedback names the obstacle: the booking route is hard to spot, the service description is vague, the form asks for information your team never uses. We turn those observations into design changes.

Approval covers the key layouts and interactions, with your real copy in place. That neat two-line placeholder may become a five-line service name. We resolve the awkward breaks here, then carry the approved design across the site.

The preview site puts your approved designs into use: your team can follow the enquiry route, try the editing controls and read the content where visitors will see it. Try a routine edit too. We choose from Next.js, Webflow, Shopify and Framer against the brief agreed at the start.

During the build, we connect the forms and tools in scope, set up analytics and prepare the SEO foundation. We test pages with the intended images and integrations in place. Adding an unbriefed booking tool at this stage means agreeing the extra work and revisiting the schedule.

Google's current Core Web Vitals guidance recommends Largest Contentful Paint within 2.5 seconds and Interaction to Next Paint at 200 milliseconds or less for a good user experience. Google also recommends measuring the 75th percentile of page loads, with mobile and desktop assessed separately. We use those benchmarks to set performance targets for your site. We report preview test results and live site readings separately, because they measure different things.

You review the working pages against the approved designs and try the main visitor tasks. We record corrections before the launch review. A marketing site build runs two weeks. A custom or ecommerce build runs two to four, because the integrations and the purchase path need their own checks.

The launch review follows the whole journey. We submit test enquiries, check where they arrive and confirm what analytics records. For a store, we test the agreed purchase path. We check links, mobile layouts and the destinations prepared for old URLs.

You approve the finished content and the visitor tasks before launch. We also confirm access to the accounts needed to run the site. The handover documentation explains routine edits, the tracking setup and where the site's settings live. Your team tries an ordinary update before we close the handover.

A launch can still fail a practical check: an enquiry might reach an unattended inbox, or an old campaign link might send visitors to a retired page. We check those routes on the live site as well as the preview. A failed check stays on the correction list until the route works.

Movement Labs asked us to rebuild its website in 2021. It operates CrossFit Aldgate and CrossFit Farringdon, two gyms in central London, and wanted a foundation that would hold up longer. IT and performance maintenance are still with us.

We return to the measure agreed at the start. Are the intended actions being recorded, and do those records match the enquiries, bookings or orders your team receives? We check the measurement before deciding which parts of the site need attention.

A broken form needs a fix; a service page with few enquiries needs investigation. We check the visits, the message and the path to the form before suggesting another design change. For a continued testing programme, conversion rate optimisation gives that work its own scope.

You review the findings and approve any follow-on work. The optional monthly maintenance retainer keeps technical upkeep on an agreed schedule. Maintenance and new features need separate decisions.

The first review ends with dates for each agreed fix and test. The handover notes show which upkeep your team does and which we do.