From Idea to Launch: The Complete Custom Website Process

Most business owners commission a website maybe once every five years, so the process feels mysterious. Here's what actually happens, week by week, on a typical custom build I run.

Week 1: Discovery and strategy

Before any design or code, we map the business goals. What does success look like in 12 months? Who's the customer? What do they need to see, in what order, to convert? This is the most important week — every later decision flows from it.

Week 2: Information architecture and wireframes

Now we sketch the structure. What pages exist? How do they connect? What's on each page, in what hierarchy? We work in low-fidelity wireframes here — boxes and labels, no colour, no fonts. The point is to settle structure before we get attached to visual choices.

Week 3: Visual design

With structure approved, we build the visual identity: typography, colour, spacing, component library, hero treatments. We design key page templates fully (homepage, services/product, about, contact, blog detail) so you see the system end to end.

Weeks 4-5: Frontend development

Designs become real, responsive code. This is also where micro-interactions, animations, and polish come in. We build mobile-first and test on real devices, not just browser tools.

Week 6: CMS integration and content

For sites with a content management system (and most do), we wire up the admin panel so the team can update content independently. Real content goes in — placeholder text disappears.

Week 7: SEO, performance, and accessibility

Meta tags, structured data, sitemaps, Core Web Vitals tuning, accessibility audits. The last 20% of work that takes 50% of the difference between a fine site and a great one.

Week 8: QA, soft launch, hard launch

Cross-browser testing, real user testing, redirect mapping (critical for SEO), staging review, then go-live. Soft launch first — only the team has the link. Then hard launch with email + social rollout.

What changes the timeline

• Speed it up: shorter content, fewer pages, faster client decisions, single decision-maker.
• Slow it down: committee approvals, late content delivery, scope changes mid-build, complex integrations.

The single biggest factor

Decision speed. A project where I get answers within 24 hours ships in half the time of one where I wait 4-5 days for each round of feedback. The work doesn't take long — the wait does.

Ready to start? Let's talk about your project.