My process

Seven clear steps that take the project from first conversation to launch without confusion.

1. Discovery & brief

alignment

We begin with the essentials: what the website needs to achieve, who it needs to speak to and what success should look like. This stage keeps the project focused before any design decisions are made.

What comes out

  • Clear project brief
  • Initial timing direction
  • Defined priorities for the build

What I need from you

  • Availability for a discovery chat
  • Existing ideas, notes or references
  • Honest context around goals and blockers

2. Scope & quote

clarity

Once the direction is clearer, I turn it into a structured scope. That means deciding what is included, what the site needs to do and how the project should be phased so the quote stays understandable.

What comes out

  • Documented scope
  • Quote with clearer boundaries
  • Projected timeline overview

What I need from you

  • Approval or adjustment requests
  • Any budget or priority constraints
  • Confirmation to move ahead

3. Structure & content plan

planning

Here the site starts to take shape. I organise the structure, map out sections and define the content hierarchy so the page flow feels logical, readable and easier to build well.

What comes out

  • Page structure and sitemap logic
  • Wireframe direction for layout flow
  • Content checklist for each section

What I need from you

  • Reference sites or examples you like
  • Draft copy, assets or rough ideas
  • Feedback on the proposed flow

4. Visual direction

design

With the structure in place, I develop the visual language of the site. This is where typography, panel treatment, spacing rhythm and visual mood are refined to match the project goals.

What comes out

  • Visual direction and style choices
  • Refined interface composition
  • Review-ready design states

What I need from you

  • Feedback gathered in one clear pass
  • Brand references if available
  • Decisions on preferred direction

5. Build

development

This is where the approved direction becomes a working website. I build the front end carefully, test responsiveness and integrate the features needed without losing clarity or performance.

What comes out

  • Responsive coded interface
  • Interactive sections and features
  • Stable build ready for review

What I need from you

  • Content handoff if still missing
  • Useful review notes as checkpoints
  • Confirmation of feature priorities

6. Review & polish

testing

Before launch, I review the site carefully across layout, usability and technical details. This stage is about catching issues, tightening the experience and making sure the final version feels complete.

What comes out

  • Revision updates applied
  • Accessibility and usability checks
  • Cleaner final presentation

What I need from you

  • Consolidated feedback
  • Final approval on key pages
  • Confirmation that launch can proceed

7. Launch & support

handoff

Once everything is approved, I prepare the site for launch and final checks. After go-live, I stay focused on stability, key tracking points and practical support for the first phase after release.

What comes out

  • Live website and final checks
  • Basic analytics and monitoring setup
  • Post-launch support direction

What I need from you

  • Access to hosting or deployment details
  • Go-live confirmation
  • Any final launch-day priorities

Project formats

Three common directions, each scoped to keep the build clear, focused and easier to manage.

Landing page

A focused page crafted to present your idea and drive action.

  • Up to 3 sections
  • Responsive design
  • SEO-ready structure
  • 1 revision round

Multi page

An organised site with multiple pages and clear hierarchy.

  • Up to 6 pages
  • Blog or portfolio module
  • SEO & performance audit
  • 2 revision rounds

Immersive build

A more cinematic web build with stronger interaction, layered motion and a more immersive navigation experience.

  • Unlimited pages
  • Immersive 3D interactions
  • Ongoing maintenance
  • Priority support

Frequently asked questions

Clear answers around timing, content, revisions, hosting and what happens after launch.

How long does a project usually take?

The timeline depends on the size and complexity of your project. A single landing page can usually be designed and built in about 10–15 days once all content is ready. A multi-page site or a small portfolio typically takes 20–30 days. If your project includes complex animations, CMS integration or 3D interactions, expect around 30–60 days. Things that can extend the timeline include waiting on content, late feedback, or new features added mid-project.

Example timeline

  • Discovery & planning: 3–5 days
  • Visual design: 5–10 days
  • Development & integration: 10–20 days
  • Review & revisions: 3–5 days
  • Launch & optimisation: 2–3 days

If you need to move faster, a "fast track" is possible when you have all content ready and can provide feedback quickly. We'll discuss the options during our discovery call.