00Guides
A one-week build is a scoping outcome. Most of what makes it possible happens before any design starts.
A week is realistic because everything that would otherwise stall the build is settled first. The structure comes from how buyers search, the real content is written, and the scope is bounded with its exclusions named. The build week is then pure execution.
A page should exist because a real query or buying question needs it. Before anyone opens a design tool, write the URL map and the single job of each page. This is search-led design, and it is the cheapest decision you will make.
If you cannot say in one sentence what a page is for and what search demand it answers, it is not ready to be designed. Cut it or merge it now, while that costs nothing.
The single biggest cause of slipped launches is missing copy and assets. Placeholder text also hides structural problems, because lorem-ipsum fits any layout while real words do not.
Have the offer, the proof you can stand behind, and the contact path written before the build week starts. Real content surfaces the hard questions early, when they are still cheap to answer.
A one-week build is a bounded scope. Write down what is in (page count, forms, analytics) and, just as importantly, what is deferred (a CMS, a blog, bespoke illustration).
Naming the exclusions in writing is what stops mid-week drift. Anything not on the list is a deliberate decision for the next iteration.
Decide the conversion and the events that prove it during the build, not after. A site that launches without analytics produces a gap in the data that cannot be reconstructed later.
The goal is day-one behaviour informing decisions immediately.
The repository, the deployment and the analytics should be in your own accounts from day one. This is a scoping decision too: confirm where everything lives before the work starts so there is nothing to untangle at hand-over.
The patterns that turn a one-week build into a one-month one.
The service and the answers that go with this guide.
The scoped engagement this guide describes, priced up front.
Why the structure is decided before the design.
What a starter website costs and who owns the code.
Tell us what you are launching. You get a fixed scope before anything starts.