The Website Project Process: What Happens From Kickoff to Launch

The two questions everyone actually asks

Before anyone signs off on a website, two questions are really running the show: what happens? and how long does it take? Fair questions — you're about to spend real money on something you can't hold, run by people you've just met. Not knowing the process is the single biggest reason a project feels stressful.

So here's the whole thing, plainly: the stages a good website project moves through, roughly how long each takes, and — just as importantly — what you'll be asked to do along the way. A website is a collaboration; the smoothest projects are the ones where the client knows what's coming.

Before the clock starts — proposal and scope

Nothing good happens without a clear scope. Before any timeline begins, a good studio turns your brief into a concrete proposal: what's being built, what it costs, and when it'll be done. Fixed price, so there are no surprises halfway through.

This is where you push and prod. Ask what's included and what isn't. Make sure the must-haves are in and the nice-to-haves are clearly parked. Once you're both agreed and the deposit's paid, the clock starts — and having done the thinking here is what keeps everything after it calm.

Stage 1 — Discovery and planning (roughly week 1–2)

The foundation. We dig into your business, your customers and your goals, agree the site's structure (what pages, in what order), and settle exactly what success looks like. For a bigger build — a portal or a platform — this stage is longer and more detailed, because getting the logic right on paper is far cheaper than fixing it in code.

• What we do: research, sitemap, project plan, and a shared understanding of the goal.
• What you do: share what you know, hand over any content you already have, and be honest about what's worked and what hasn't.

Stage 2 — Design (roughly week 3–5)

Now it takes shape visually. We design the key pages, agree the look and feel, and refine it with you before a single line of code is written. You'll see real designs, give feedback, and sign them off. This is the cheapest, easiest point to change your mind — moving a button in a design takes a minute; moving it after build takes longer — so this is the stage to be involved and decisive.

• What we do: design the pages, present them, refine on your feedback, get sign-off.
• What you do: review properly, gather feedback from anyone who needs a say, and approve so the build can start clean.

Stage 3 — Build (roughly week 5–9)

The heads-down stage. We turn the approved designs into a real, working website — clean custom code, built to be fast and to be found, not a stack of plugins bolted together. It's the quietest stretch for you: most of the work is ours. Towards the end we'll want your final content and any last assets so we can pour them in.

• What we do: build the site properly — the code, the speed, the search foundations, the responsiveness across devices.
• What you do: get your final content and images over on time. This is the number-one thing clients underestimate, and the number-one cause of delay — content, not code, is usually what holds a project up.

Stage 4 — Testing and launch (roughly week 9–12)

The final push. We test everything — across browsers and devices, checking forms, speed, links and search setup — then, once you've done a final review and paid the balance, we go live. A good studio doesn't vanish at launch; they watch the site settle in and are on hand for the inevitable small tweaks in the first week or two.

• What we do: thorough testing, a final review with you, the launch itself, and post-launch support.
• What you do: a proper final check, sign-off, and settle the final payment so go-live isn't held up.

How long, and how you pay

For a typical brochure or marketing website, the whole thing runs about 10–12 weeks from kickoff to launch. A custom platform or portal is more like 12–16 weeks, because the discovery and build stages carry more weight. The single biggest variable isn't the studio — it's how quickly content and feedback come back from your side.

Payment is normally staged so it tracks the work, not loaded up front. Ours runs 30% to start, 40% before launch, and 30% on go-live — you're never paying for a finished thing before you've seen it. That structure exists to keep both sides honest and the project moving.

What a good process feels like

You should always know what stage you're in, what's next, and what's needed from you. No radio silence, no surprise invoices, no "it'll be ready when it's ready." A website is a serious investment, and the process should feel like a serious studio running it — which is exactly how our studio runs a project: a clear scope, defined stages, and standards (we hold our builds to the kind of quality that's earned Awwwards recognition) that don't slip just because a deadline's close.

If a studio can't tell you clearly what their process is before you commit, that tells you something about what working with them will be like. The process is the product, as much as the finished site.

FAQ

How long does it take to build a website?

A typical brochure or marketing site takes around 10–12 weeks from kickoff to launch. A custom platform or portal is more like 12–16 weeks. The biggest factor in staying on schedule is how quickly you get content and feedback back to the studio.

What are the stages of a web design project?

Broadly: discovery and planning, design, build, then testing and launch — with proposal and scope agreed before the clock starts, and support after go-live. Each stage has a clear output you sign off before the next begins.

What do I need to provide during a website project?

Mostly content and decisions: your business knowledge up front, feedback and sign-off at the design stage, and your final text and images before the build wraps. Getting content ready early is the single best thing you can do to keep a project on time.

How is a website project paid for?

Usually in staged payments that track the work rather than everything up front. A common split is a deposit to start, a payment before launch, and the balance on go-live — so you're never paying in full for something you haven't seen working.

Why do website projects get delayed?

Most often because content and feedback are slow coming from the client's side, or because the scope wasn't clear at the start and keeps growing. A tight scope and prompt responses are what keep a project running to schedule.