PROCESS
How a project actually runs.
Six stages, every project, with real durations — not a vague "we’ll be in touch" between checkout and delivery.
STAGES
- 01
Discovery
Brief reviewed, scope confirmed against the package (or scoped fresh for Bespoke/Partnership), timeline agreed in writing.
2–3 days
- 02
Content & structure
Sitemap or product/content structure prepared and signed off before design starts.
3–5 days
- 03
Design
Visual design of key pages/screens, one structured revision round.
1–2 weeks
- 04
Build
Development on the agreed stack, tested as it’s built, not only at the end.
1–5 weeks
- 05
Review & revisions
Second structured revision round, QA pass, content proofing.
3–5 days
- 06
Launch & handover
Deploy, files and access handed over, Care Plan offered (never required).
1–2 days
What we need from you
What we need from you
| Discovery | A completed brief; answers within 48h keep the timeline on track |
| Content & structure | Page/product content, or a firm date for when it’ll arrive |
| Design | Feedback on the first design round within the agreed window |
| Build | Any late content changes flagged as early as possible |
| Review | Feedback on the second round within the agreed window |
| Launch | Confirmation of go-live timing and any DNS/hosting access needed |
Tools/handover
Tools/handover
| Design | Design files (source), shared for feedback |
| Build | Repository/project access, if applicable |
| Launch | Full source files, hosting/DNS access, admin credentials |
| Ongoing | Nothing further required — a Care Plan is optional, not a condition of ownership |
FAQ
How long does a project actually take?
Each package states a typical delivery window — from 10 days for a Conversion Audit to 9–10 weeks for a full store build. The clock starts once the brief and content deadline are agreed, not at checkout.
What slows a project down?
Almost always the same thing: content. Page copy and images arriving late pushes the whole timeline back by the same number of days. Everything else is inside this studio’s control.
Can I move the site to another host or developer later?
Yes. The static output this studio builds runs on any standard web host; nothing depends on a proprietary platform.
Who owns the site once it’s built?
You do. Every file — design source, code, content — is handed over at delivery. There’s no lock-in to keep using this studio afterward, including for hosting.