How We Run a Web Project, From Brief to Launch

Every website we build follows the same simple rhythm: understand, design, build, launch, improve. The details change from client to client, but having a shared process means nobody is ever guessing what happens next – least of all the client.

A good process does not slow creativity down. It removes the uncertainty so the team can spend its energy on the work that matters.

01 Discovery: questions before pixels

We start with a workshop. Who are the visitors, what do they need, and what does success look like in six months? We audit the existing site, look at analytics and talk to the people who answer customer emails – they know the real problems better than anyone.

02 Content and structure

Before any visual design we agree on a sitemap and draft the key page content. Designing around real words, instead of placeholder text, leads to layouts that actually fit the message.

• A sitemap everyone signs off on
• Wireframes for the most important templates
• A content plan with owners and deadlines

03 Design and prototype

We design the core screens first, then turn them into a clickable prototype. Testing it with five real users usually uncovers the biggest problems in a single afternoon, while changes are still cheap.

The best feedback comes from watching someone use the design, not from asking whether they like it.

Kelly Adams, Creative Director

04 Build, launch and improve

Development happens in short cycles on a staging site the client can always see. After launch we monitor speed, search rankings and conversions for the first month, then plan the next round of improvements together.