Fourteen stages. Seven gates. You decide where.

Agents carry a site from the client consult to a live release, and through every edit after it. You sign off at the gates you choose, and every step is on the record.

block · explorer

stages · A to N · 14 · open any stage

A · Intake

Start a project and hand over the raw material: the consult transcript, the client’s current site, a competitor or two, their documents. Kept word for word.
Makes: the project and its captures
B · Brief

Agents turn the consult into a brief where every point quotes the client, then say where the evidence is thin and how risky the build looks.
Makes: a brief digest, a diagnostic, a risk assessment
C · Foundational strategy

What the client sells, a competitive review scored on a strategy canvas, and a positioning that says where the client can win.
Makes: products and services, a strategy canvas, positioning
D · Core strategy

The goals and must-haves, the personas, the customer journey, the brand book and the content bible, each checked against the brief.
Makes: personas, a journey, a brand book, a content bible
E · Web strategythen G1

What the site must do, any web apps, and the site map. Then a review pack for the first gate. Approve it and the strategy is set.
Makes: a functionality map, a site map · Gate 1: strategy
- gate · G1strategyawaitingapproved
F · Wire specthen G2

A plan for every page: its blocks, the job each one does, who it serves and a budget for every line, with every must-have housed somewhere.
Makes: a plan for every page · Gate 2: the wire spec
- gate · G2wire specawaitingapproved
G · Asset specthen G3

Every line of copy, written to its budget and the brand’s words, plus an inventory of every image, icon and video, a visual system and briefs.
Makes: page copy, asset briefs · Gate 3: the asset spec
- gate · G3asset specawaitingapproved
H · Production

Images and video generated to their briefs, icons from a chosen set. Each attempt is kept, judged against its brief and approved before use.
Makes: images, icons and video, approved in batches
I · Design directionthen G4

Two or three home pages built from the real copy and assets, side by side at desktop and mobile. You pick the one the site is built in.
Makes: two or three directions · Gate 4: your pick
- gate · G4design directionawaitingapproved
J · Web app studiothen G5

Each web app is specified in a conversation: the agent asks, you answer and confirm the spec. Then it is built and tested against its checks.
Makes: an app spec and a built app · Gate 5: each app
- gate · G5each web appawaitingapproved
K · Site buildthen G6

Every page built in the chosen direction, apps embedded, assets fitted, and the whole site checked page by page and breakpoint by breakpoint.
Makes: the built site · Gate 6: the built site
- gate · G6built siteawaitingapproved
L · Extraction

The built site becomes tokens, blocks and page models you can edit, and its render is checked against the build before anything moves on.
Makes: tokens, blocks, page models, page templates
M · Publishthen G7

A release with its sitemap, meta tags and 404 page, checked and approved, then deployed to Cloudflare Pages. The domain is bound on its own sign-off.
Makes: a release, a deployment · Gate 7: the release
- gate · G7releaseawaitingapproved
N · Maintain

People and agents edit copy, assets and layout as drafts, design changes come with before-and-after shots, and every release can be redeployed.
Makes: drafts, design changes and the next release

block · gates

Seven gates, and you choose who holds each

A gate is where the work stops until someone decides. Hold the gates that matter to you and delegate the rest by policy; the record shows who decided, and on whose authority. Change an approved artefact and its gate reopens.

gate · G1 · strategy
Gate 1, strategy: the positioning, personas, brand, content plan and site map.
gate · G2 · wire spec
Gate 2, wire spec: every page’s blocks, what each is for, and its line budgets.
gate · G3 · asset spec
Gate 3, asset spec: every line of copy, and the brief for every image and video.
gate · G4 · design direction
Gate 4, design direction: which of the two or three home pages the site is built in.
gate · G5 · each web app
Gate 5, each web app: its spec confirmed, its checks passed, its preview tried.
gate · G6 · built site
Gate 6, the built site: every page at every breakpoint, with the check’s findings.
gate · G7 · release
Gate 7, the release: what changed since the live site, page by page, before it deploys.

block · after_launch

After launch, the site stays yours to edit

Click a block and edit its slots, with the budget and the brand’s banned words checked as you type. Ask the model for a design change and see before-and-after screenshots first. Edits stay drafts until you approve a release, and any earlier release can be redeployed.

A clay page frame with one block lifted out and being swapped, the rest of the page untouched

block · people_and_agents

People and agents run the same tools

A button you click and a command an agent runs go through the same door. Each is a named tool run, recorded with who ran it, what it read and what it wrote. So any version can be traced, compared and replayed.

block · pilot_cta

next · /pilot

Run your next site through it

The pilot is free and places are limited, offered in rounds. Apply with your name, email and role.

Apply for the pilot

block · footer

aptiweb

This site was built by aptiweb, through its own pipeline. See the build record.