Skip to content
Pixellence Studio

(04)Process

A simple way of working, run by senior people.

Four steps, and a record of what each one leaves behind. A site and a product share the steps. They do not share the length.

  1. 011 to 2 weeks

    Discover

    Workshops, a reading of what is already live, and a technical look when the work is more than pages.

    A written scope, a plan and a fixed estimate. Build does not start before this is agreed.

  2. 022 to 4 weeks

    Design

    Flows, the phone layout and a system, checked before production code.

    Pages you can click through, and a system the engineering follows.

  3. 038 to 16 weeks

    Build

    Weekly releases to staging, so Friday is a build you can open.

    A build you can steer on staging, then the live release.

  4. 04Ongoing

    Evolve

    The same lead stays. The next page, language or feature is a written change, not a new project from zero.

    The site or the product stays current after launch.

(05)Inside each step

What we do, and what you keep.

  1. 011 to 2 weeks

    Discover

    • Sessions with the people who will use the site or the product
    • A pass over the current pages, the content and the constraints
    • A technical read when there is an API, a migration or a calculator

    You leave with

    A written scope, a plan and a fixed estimate. Build does not start before this is agreed.

  2. 022 to 4 weeks

    Design

    • The path that matters: a booking, a station list, a calculator, a sign-in
    • Homepage, inner pages and the phone, not a single desktop picture
    • A design system the build reuses, tested with the people who will use it

    You leave with

    Pages you can click through, and a system the engineering follows.

  3. 038 to 16 weeks

    Build

    • A staging link that moves every Friday
    • The forms, the inner pages and the phone layout, with the homepage
    • Tests around the release, and an API when the product needs one

    You leave with

    A build you can steer on staging, then the live release.

  4. 04Ongoing

    Evolve

    • A named person when something breaks
    • A short list of what comes next: a page, a language, a tool
    • Small releases that do not reopen the whole scope

    You leave with

    The site or the product stays current after launch.

(06)Two lengths

Same steps. Not the same job.

A public site

A clinic, a station network or a climate page. Discover is a few working sessions and a reading of what is already live. Design covers the homepage, the inner pages and the phone. Build ships the forms, the list or the calculator. Friday is still a build you can open. A site often finishes inside the build window, not at the far end of it.

A product

An app or a platform with an API. Discover includes the technical audit. Design is the flows and the system. Build uses the longer part of the 8 to 16 weeks, with staging every Friday and tests around the release. Cloud and data work sits in this track, not in a separate process.

  1. 01

    One lead

    The person in the first workshop is the person who designs and ships. There is no separate account layer to repeat the brief.

  2. 02

    Friday

    There is something running on staging. Progress is a build you can click, not a status slide.

  3. 03

    A written change

    The estimate is fixed before build. A new page or a new feature is written down and agreed before it is added.

Let’s build what’s next.

Start a project