How does Dan Heselton run client projects?

Projects move through structured phases: discovery and scope, design and structure, build and integration, then launch and handoff—with one person accountable at each step.

What happens in the first week of a project?

The first week focuses on goals, audience, sitemap, and technical constraints so design and build decisions stay tied to measurable outcomes.

How I work

Listen first.
Build second.

Every project is different, but the rhythm is the same: get clear on what success looks like, design with intention, build clean, and hand off something you can actually run.

The phases

Timing shifts with scope. The order doesn't.

  1. 01 1–2 weeks

    Discovery

    I map your audience, constraints, and content reality. You leave this phase with a clear scope and a shared understanding of what success looks like. Not a vague brief.

  2. 02 1 week

    Strategy & IA

    Sitemap, key templates, component logic, and tone. For product work, this is where user flows get defined before any design starts.

  3. 03 3–4 weeks

    Design

    Visual system, responsive layouts, and interaction design. Reviews are structured so feedback stays actionable and the strongest ideas survive.

  4. 04 Varies by scope

    Build

    Front-end implementation with accessibility, performance, and editor ergonomics in mind. Webflow, React, Shopify, Supabase, or a hybrid—whatever fits the project.

  5. 05 1–2 weeks

    Refinement & launch

    Focused QA, content polish, analytics or form wiring, and a documented handoff. Launch is a milestone, not a disappearing act.

Collaboration

Ready to start?

Share what you are trying to fix, your timeline, and where the site or product needs to be in six months. If it is a fit, you will get a clear proposal; if not, you will still leave with a useful next step.

Start a project

© 2026 Dan Heselton. All rights reserved.

PrivacyTerms