The process · async by default · 4–7 days typical
From a sentence,
to a real site,
in writing.
Every step in writing — brief, preview, change requests, sign-off. A live homepage on a real URL by the end of day one, then we iterate by message until you’re ready to ship. Typical build is four to seven business days.
Index of steps
The arc · five steps · ~4–7 days
on consecutive days · iterate inbetween
Day 0
The brief
A short form, in writing.
About 20 minutes. Your business in a sentence, what the site needs to do, who it’s for, any existing brand you’ve got. No mood boards, no slide decks, no discovery call. If you’ve picked modules from the pricing page, those carry across.
Quiet facts
Day 1
The preview
A live homepage on a real URL.
By end of the next business day, you’ll have a working homepage at a temporary URL — your palette, your copy, your real images where you’ve sent them, placeholders where you haven’t. Click through it on your phone, on a laptop, send the link to a partner. React in writing.
Quiet facts
Day 1–N
Iterate
By message. Loom on request.
Send the next thing you want changed and we’ll do it. We reply within one business day, with a deployed update at the same URL. Most builds settle in two or three rounds; some go longer. A Loom from us if a change needs more context than a screenshot.
Quiet facts
Day N
Ship
The site goes live on your domain.
You sign off in writing. We connect your domain, run a final QA pass on mobile + desktop, ship the code to production. The temporary URL retires. You get a one-page launch checklist (analytics, search console, redirects) and a Loom tour of your custom admin.
Quiet facts
Day N+
Ownership
The lot transfers to your name.
On final payment, the repo, the domain, the hosting account, the admin — all transferred to your name. No platform fee, no per-seat charge, no lock-in. Keep us on a Care plan if you want, or take the lot and run it yourself. See what handover looks like.
Quiet facts
The shape · in plain English
What we do ask for, and what we don\u2019t.
Every async-first promise on the homepage gets boring fast unless it’s specific. Here’s what we actually want from you, and what you never have to give us.
What we ask for.
What we don\u2019t.
A day in the build · transcribed
What one day actually looks like.
Names changed, edits true. A typical thread from brief sent to preview-shipped is five or six messages — short, asynchronous, with deploys between them.
v · After Day N
The lot transfers to you.
Repo, domain, hosting, admin, sample contract — your name, on final payment. No platform fee, no per-seat. See exactly what handover looks like.
0 · Before Day 0
Start with a sentence.
Twenty minutes of the brief form is enough to get a preview by this time tomorrow. Start a brief →