How a website project moves from brief to launch

The decisions, content and feedback that keep a website project moving, and what your team contributes at each stage.

Define the result before the pages

Agree the audience, business goal and useful next action. Then list routes, languages, integrations and content responsibilities. A written scope makes it easier to distinguish a correction from a new requirement.

Prepare content alongside the structure

Your team provides product knowledge, approved claims, images and access to relevant systems. We organise that material around the visitor's questions. Waiting until the end for copy makes design decisions less reliable and usually delays approval.

Review concrete work

Page structures lead to design, reusable components and a working preview. Feedback is most useful when one decision-maker combines it into specific changes. Review representative pages and real content before repeating patterns across the site.

Plan the handover

Before launch, agree redirects, content freeze, access, enquiry routing and who maintains the site. Your team should know how to change everyday content and who handles larger changes. The schedule depends on scope and approvals rather than a universal number of weeks.