The most common reason a project goes badly is not skill. It is that nobody agreed what happens when. So here is our schedule, published, with the parts that need you marked clearly.
Ten weeks is the shape of a full marketing site. A landing page is two, a platform is fourteen. The stages are the same either way.
Week 1 — Discovery
We work out what problem the site is actually solving, which is often not the one in the brief.
- A half-day workshop with the people who own the outcome — not their deputies
- An audit of your analytics, your search performance and your competitors
- A written problem statement that we both sign off on
What we need from you: the right people in the room for half a day, and read access to your analytics.
Week 2 — Planning
Scope, architecture and a roadmap with dates on it.
- Sitemap, technical architecture and the full list of integrations
- Fixed scope — with an explicit out-of-scope column, which is the one that prevents arguments in week eight
- A dated milestone plan and one named point of contact on each side
What we need from you: one decision-maker. Not a committee. A committee can review; only one person can decide.
Weeks 3 – 5 — Design
Art direction first, then the real screens.
- Two art-direction routes, of which you choose one and we refine it
- Every breakpoint and every state designed — loading, empty, error, not just the happy path
- A component library handed over in Figma that you own
What we need from you: your copy, or a decision to have us write it. This is the deadline that slips most often, and it is the one that pushes everything else.
Weeks 6 – 9 — Development
You watch it get built.
- A live preview URL from the first week of this stage, updated continuously
- A twenty-minute demo call each week. No deck — the actual thing
- Performance and accessibility checked on every release, not audited at the end
What we need from you: twenty minutes a week, and feedback within two working days.
Week 10 — Launch
- Cross-device QA and a full accessibility pass
- Analytics and conversion tracking verified before cutover, so you do not lose a week of data finding out it was wrong
- The repository, a written runbook and thirty days of support
A preview URL from week six is the single thing clients tell us changed how the project felt. Not because it was faster — because there was never a moment where they did not know what they were getting.
What happens if something slips
We tell you the same week, with a revised date, and we say which of the two causes it was: something took longer than we estimated, or something we needed did not arrive. Both happen. Neither improves by being mentioned late.
If you want this run on your project, book a call and we will map your scope onto these stages with real dates before anyone signs anything.