the engine

Seven stages. Every one gated.

Most studios describe a process. This page shows ours running, with the checks that stop a build and what they produce when they do.

how a build runs

A gate is not a checklist item.

Each stage produces a file, and the next stage will not start until that file passes. A failing check reopens the stage before it. This is the part that is hard to fake, so it is the part we show.

  1. Discover

    Produces A written brief

    Gate You approve it. Nothing is assumed from a phone call.

  2. Research

    Produces A market and competitor read

    Gate You approve it. We name what we found and where.

  3. Plan

    Produces Archetype, style, stack and the section list

    Gate Locked before a line is written, so scope cannot drift quietly.

  4. Brand DNA

    Produces A validated data contract

    Gate A machine reads it. Any unfilled value halts the build and names itself.

  5. Build

    Produces A deploy-ready site

    Gate Copy is linted against a banned-language list before it can pass.

  6. QA

    Produces A written report

    Gate Load speed, contrast, links, responsive, security. A soft fail is a fail.

  7. Deploy

    Produces The live site and handover notes

    Gate Two passes. Nothing reaches a domain on one command.


what the gates catch

Real things that stopped real builds.

None of these are hypothetical. Each one is a check firing on a WBB build and holding it back until it was fixed.

Contrast

White text at 45% opacity failed AA in seventeen places.

Nested opacity multiplies. A colour derived to pass at full strength does not pass at half.

Weight budget

A logo shipped at 1,107 KB against a 250 KB ceiling.

One oversized image can cost more load time than every line of code on the page.

Secrets

The bundle was scanned for keys before every deploy.

A key in a static bundle is public the moment it ships. There is no taking it back.

Copy

Banned marketing vocabulary is rejected at build time.

Nobody has ever bought anything because a site called itself the best in its class.

Being built Client portal. Watch your build move through the seven stages instead of waiting for an email.

Watch it run on your own build.

Every stage above produces a file you get to read. Nothing is described to you second-hand.