Our Process
Discovery
We start by learning the business rather than the brief: what you sell, who buys it, what usually convinces them, and what the site has to achieve to be worth building. We look at the companies you compete with so the result does not blend into them.
- The business
- Audience
- Goals and brand
- Requirements
Structure
Before anything visual, we agree what pages exist and how someone moves between them. Most sites that feel confusing are structurally confused rather than badly designed, so this stage does more for the result than it looks like it should.
- Pages
- Navigation
- Information hierarchy
- User journey
Design
We set a visual direction and build it out into full page designs, at desktop and mobile widths. Typography, spacing and layout carry most of the weight. You see and approve the design before a line of production code is written.
- Visual direction
- Typography
- Layouts
- Interface components
Development
The approved design becomes a real site. Components are built once and reused, animation is kept to what serves the content, and forms and third party services are wired up and tested with real submissions.
- Responsive build
- Interactions
- Forms
- Integrations
Testing
We go through the site on real phones and desktops, across the major browsers. Every form gets submitted and every link followed, and we check keyboard navigation, performance and contrast rather than assuming they are fine.
- Responsiveness
- Performance
- Accessibility
- Browsers
Launch
Final refinements, then we deploy, connect the domain and confirm everything works in production. You get the code, the accounts and a walkthrough of how to change the things you will want to change yourself.
- Final refinements
- Deployment
- Handover
- Ready for users
Every project runs this way
Whether it is a new website, an online store or a rebuild of something that already exists. The depth of each stage changes; the sequence does not.