How we work

Discovery, strategy, delivery, and growth, in that order.

Engagements run on a clear, repeatable structure. Each phase produces concrete artifacts you can read, react to, and reuse. No surprises at the end.

  1. 01

    Discovery

    Listen first. Make sure the project is the right one before scoping anything.

    What happens
    Stakeholder interviews, technical audit of the current site, review of analytics and existing materials.
    What you get
    Written brief that captures goals, constraints, audience, and unknowns. Honest read on whether to proceed.
  2. 02

    Strategy

    Translate the brief into a plan you can actually execute against.

    What happens
    Information architecture, technical architecture, content model, and a delivery plan with milestones.
    What you get
    Scope document, architecture diagram, timeline, and a fixed-fee or retainer recommendation.
  3. 03

    Delivery

    Build in small, shippable increments. Stay visible the entire time.

    What happens
    Two-week sprints with weekly demos. Written changelog after every meaningful change. Async-first communication, scheduled syncs only when they earn their keep.
    What you get
    Working software in your hands, plus the documentation, training, and access handover that makes it yours.
  4. 04

    Growth

    A site is not done at launch. Operate it like a product.

    What happens
    Maintenance, performance tuning, security work, accessibility audits, and AI augmentation as new opportunities open up.
    What you get
    A site that gets better month over month, with a partner who already knows the codebase.

Preparation

Before we start.

A short checklist of what helps me move fast in Discovery. None of these are required to inquire, they just shorten the runway.

Start a project

  1. The why One sentence on why you are doing this now.
  2. The audience Who the site (or feature) is for, in concrete terms.
  3. The win The single outcome that would make this engagement a win.
  4. The constraints Hard dates, regulatory needs, brand rules, existing infrastructure.
  5. The data Access to current analytics, or the closest equivalent.
  6. The references Two or three sites you admire, with one line each on why.