Ask how long a website takes and you'll hear "four to eight weeks" — true for most business sites, and completely unhelpful for planning. After a thousand launches, we can tell you where those weeks actually go, which ones flex, and the one bottleneck that blows more schedules than everything else combined.
Week 1: discovery and direction
One good call, straight questions: what does the business do, who buys, what should the site make happen, what do you love and hate. Then sitemap and structure. Rushing this week is how sites end up beautiful and useless.
Weeks 2–3: design
Custom concepts for the key pages, refined with your feedback. Two focused revision rounds beat ten scattered ones — the best clients react quickly and honestly ('this feels wrong' is useful feedback) rather than perfectly.
Weeks 3–5: build
The approved design becomes a real website: development, animations, responsive behavior, forms, SEO structure, and the machine-readable layer that search engines and AI assistants read. You review on a private staging link, on your own phone, in your own browser.
Weeks 5–6: content, polish, launch
Final copy and images go in, everything gets tested — every form, every device — redirects from old URLs get mapped, and the site goes live. Launch day itself is undramatic when the checklist is done; that's the point.
The thing that actually delays launches
Content. Not design, not development — the photos that never arrive and the 'About' paragraph nobody wants to write. It delays more launches than every technical issue combined. The fix: start gathering content the day you sign, and if writing isn't your thing, have the studio draft it and edit from there. Editing is easy; blank pages are hard.
When you have a hard deadline
A season opening, a launch event, a campaign. Tell the studio on the first call. Working backwards from a real date changes how the project is planned — and an honest studio will tell you immediately whether the date is achievable rather than discovering it with you in week five.