Most first-time clients don't know what actually happens between saying "let's build a website" and the site going live. Knowing the shape of it in advance makes the whole process feel a lot less like a black box.

1. Discovery — more talking than building

The earliest stage is mostly conversation: what the business actually does, who it's for, what similar sites already exist, and what "done" realistically looks like. Skipping this to jump straight into design usually costs more time later in revisions.

2. Planning the structure

Before any visual design starts, the pages and their purpose get mapped out — what goes on the homepage, what a services page needs to cover, where a visitor should end up if they want to get in touch. This is the site's skeleton.

3. Design

This is where color, type, layout and imagery come together into something that actually looks like the future website. Expect at least one or two rounds of feedback here — first impressions are useful, but refinement usually improves the result meaningfully.

4. Development

The approved design gets built into an actual, working website — responsive across devices, with real navigation, forms, and content in place rather than placeholder text.

5. Review and testing

Before anything goes live, the site gets checked across different devices and browsers, links get tested, forms get submitted to make sure they actually arrive somewhere, and any rough edges get smoothed out.

What tends to slow this stage down

  • Content (text, images) not being ready when development needs it
  • Feedback arriving in scattered messages instead of one clear round
  • Scope quietly expanding mid-project without adjusting the timeline

6. Launch

Going live is usually less dramatic than people expect — domain pointed correctly, final checks done, and the site becomes publicly visible. The real work often continues just after this point: watching how it performs, fixing anything that only shows up under real traffic, and planning the next round of improvements.

A web project that goes smoothly usually isn't the one with the fewest problems — it's the one where expectations were clear from the start, so nothing that came up felt like a surprise.