This question comes up at the start of almost every project. The honest answer is that it depends — but "it depends" isn't useful, so here's a clear breakdown of what actually drives the timeline.
The quick summary
| Route | Realistic timeline |
|---|---|
| DIY website builder | 4–10 weeks (content is the bottleneck) |
| Hiring a professional | 3–6 weeks from starting |
| Fast-track professional build | 1–2 weeks if content is ready |
The biggest variable in every case is content — specifically, how quickly the written text, photos, and decisions required to build the site can be provided and approved.
DIY: it takes longer than you think
Website builder adverts show someone creating a polished site in an afternoon. This is marketing, not reality.
Most business owners who build their own site go through stages that look something like this:
- Week 1: Choosing and setting up the platform, picking a template, connecting a domain.
- Week 2–3: Learning the editor, making basic design decisions, realising the template doesn't quite do what you wanted.
- Week 3–5: Writing content for each page — usually the hardest and most time-consuming part.
- Week 4–6: Adding photos (or realising you don't have the right ones and needing to take them), adjusting the layout, fixing things that break on mobile.
- Week 6–8+: Final tweaks, testing, convincing yourself it's ready.
Six to eight weeks is a typical timeline. Some people take longer; few do it properly in less than a month fitting it around a working week.
Working with a designer: a realistic timeline
A professional build generally moves faster and more predictably. A typical schedule:
| Stage | Duration |
|---|---|
| Brief, quote, and contract | 2–5 days |
| Content gathering from you | 3–7 days |
| Design (wireframe / mockup) | 5–10 days |
| Your design feedback | 2–3 days |
| Build | 7–14 days |
| Content review and revisions | 3–5 days |
| Final checks and launch | 1–2 days |
Total: approximately 4–6 weeks from first conversation to going live. With a fast client and content ready upfront, this can compress to 2–3 weeks. Complex sites with more pages or custom features take longer.
What slows projects down
This is the part most people don't account for — and it's nearly always on the client side rather than the designer's.
Content not being ready. This is the single biggest cause of delays on every professional web build. If you can't provide your page text and photos until four weeks into the project, the site can't be built until then. See our post on what you need before starting a website — having this ready before the project begins makes everything faster.
Slow feedback. A design is sent for review and sits in an inbox for two weeks. By the time the response arrives, the designer has moved to other work. Prompt feedback (aim for 48 hours on design reviews) keeps projects on track.
Changing scope mid-project. "Can we add a gallery page?" or "actually, let's change the menu structure" — even reasonable requests, when they arrive during the build phase, add time. Agree the scope before starting and stick to it.
Multiple decision-makers. If three people need to approve every design decision, timelines stretch. Designate one person to consolidate feedback.
How to be a fast, easy client
If you want your site done quickly, do these things:
- Have your content ready before the project starts. Text, photos, logo — all of it.
- Give clear, timely feedback. "The blue feels too corporate, can we try something warmer?" is useful. "I'm not sure about it" is not.
- Make decisions promptly. Don't sit on a domain name choice or logo approval for weeks.
- Limit the number of people who have approval sign-off. One person is ideal.
What to expect from us
At CloudLaunch, we aim for a 2–4 week build once content is in hand. We'll share a clear project schedule at the start so you know exactly what's happening and when. Get in touch to discuss your project.