You went looking for the stages so you would know what is supposed to happen and in what order. Maybe you are about to commission a site and want to brief somebody properly. Maybe you are three weeks into a project and quietly wondering whether something got skipped. Either way you found nine articles all promising the seven stages of web development, and all listing different sevens. One opens with information gathering, another with discovery, another with briefing. One of them, under a heading that says seven, lists six. So instead of a map you have nine maps that disagree, and no way to tell whether the process you were quoted is thorough or thin. The stages themselves are real and the order is genuinely settled. The number is not. What follows is what each part of the work actually does, which parts a small project can honestly compress, and where a skipped stage turns up again later at a worse price.
Key Takeaways
Nine pages on the front page of that search list different sevens, and one lists six under a heading that promises seven. No standards body publishes a seven-stage web lifecycle.
The UK government's service manual and NIST's system development life cycle both describe phased delivery. They agree on the shape of the work and not on a count.
Discovery skipped becomes revisions. Content skipped becomes a stalled build. Testing skipped becomes a customer finding the fault for you.
Why does every article list a different seven?
Because seven reads well in a headline, and the work does not naturally divide into any particular number.
Look at what the front page actually contains. One list runs information gathering, planning, design, content writing and assembly, coding, testing, review and launch. Another runs discovery, planning, design, content creation, development, testing, ongoing optimisation. A third begins with a briefing and an analysis phase before planning is even mentioned. A fourth folds requirements gathering out of discovery into its own stage, which is a reasonable choice, and produces a different seven as a result.
Then count the one titled "The 7 Stages of Website Development Every Business Owner" and read its own summary: planning, design, development, testing, launch, maintenance. That is six. Nobody is being dishonest. The number in the title is doing marketing work and the list underneath is doing the real work, and they were written by different halves of somebody's brain.
There is a genuine standard-shaped thing here, and it is worth knowing about because it is more useful than any of the sevens. The UK government publishes a service manual describing phased delivery, including how the discovery phase works, how beta works, and what happens once a service is live. NIST similarly documents a system development life cycle. Both are real, both are public, and neither has seven stages, because the count was never the point.
What does each stage actually do?
Here is the sequence as it genuinely runs, described by what each part is for rather than by where somebody drew the boundary. Read it as work that has to happen, not as a chart to obey.
The work, in the order it actually happens
- 1
Discovery
Working out what the site is for, who it is for, and what has to be true for it to be a success. Cheapest possible time to change your mind, and the stage most often sold as optional.
- 2
Planning and structure
Deciding what pages exist and how somebody moves between them. This decides more about whether the site works than the visual design does.
- 3
Content
The words, photographs, product information and proof. The stage that stalls more projects than every technical problem combined, because everyone assumes somebody else is doing it.
- 4
Design
How it looks and feels, applied to a structure that already exists. Designing before the structure is settled is how a project acquires three rounds of revisions nobody budgeted.
- 5
Build
Turning the design into a working site: code, content management, forms, integrations, performance.
- 6
Testing
Real devices, real browsers, awkward inputs, the form actually arriving. This is where you find the fault instead of a customer finding it.
- 7
Launch and what follows
The move itself, including keeping old addresses working, then measuring, fixing and improving. Not a finish line, a handover.
Notice that only one of those is what most people mean when they say web design. The visual work sits in the middle of a process that is mostly about deciding, gathering and checking, which is exactly why quotes for the same site can differ so widely: they include different amounts of the rest of it.
Which stages can a small project honestly skip?
Some of them, and pretending otherwise would be dishonest for a five-page brochure site. What matters is knowing which compressions are safe and which ones simply move the cost.
Discovery can shrink to a single conversation and one page of notes when the business is straightforward and the owner already knows what the site must do. It should not disappear, because something has to record what success looks like, but it does not need a workshop.
Formal structure work can collapse into a page list when there are eight pages. It cannot be skipped when there are eighty, or when there is any kind of category or service hierarchy, because that is precisely when people get lost.
Design can legitimately mean choosing and customising an existing template. That is a real answer for plenty of businesses, and it is not a lesser one when the alternative is spending the same money proving your brand is unique in a market where nobody is comparing.
Testing cannot be skipped, and neither can the launch work, and those are the two most commonly cut. Both are invisible when they go well, which is why they are easy to leave out of a cheap quote and expensive to leave out of a project.
What happens when a stage gets skipped?
It comes back. That is the whole reason the sequence exists, and it is more useful to a buyer than any list of names.
| Skipped | Where it turns up instead | What it costs by then |
|---|---|---|
| Discovery | In revisions, halfway through design | The rework, plus the argument about whose fault it is |
| Structure | After launch, as visitors who cannot find anything | A rebuild of the section, and lost enquiries in the meantime |
| Content | As a stalled build waiting on your photographs | Timeline, and often a fixed price becoming an hourly one |
| Design decisions | As endless small changes with no reference to settle them | Rounds nobody counted, and a tired relationship |
| Testing | As a customer telling you the form does not work | Trust, and every enquiry that silently failed first |
| Launch care | As pages that used to rank returning errors | The traffic you already had, and the work to win it back |
| Measurement | As nobody being able to say whether it worked | The next decision, made on feelings instead of evidence |
That last row is the quiet one. Google and analytics can be connected so you can see what people searched for and what they then did, and if nobody sets that up you are choosing to run the next three years on impressions. Similarly, after launch you can ask Google to recrawl a changed page rather than waiting and hoping.
How do you use this when talking to a provider?
Take it into the conversation as questions rather than as a checklist to enforce, because a good provider will have their own version of this sequence and it will not match anybody's seven either.
Ask which of these stages their price includes, and specifically whether discovery and testing are in or out. Ask who writes the content and when they need it, because that answer determines your timeline more than their availability does. Ask what happens at launch to your existing addresses. Ask what measurement is set up before they hand over, and who looks at it afterwards.
You can check some of it yourself before you even talk to anybody. Run your current site through Google's page speed tool and read what it says about the real-world experience rather than the score, remembering that Google states plainly that good page experience does not guarantee ranking. And whatever gets built, the standing advice from Google has not changed in years: ranking systems reward helpful, reliable, people-first content, which is a content problem rather than a build problem, and it belongs in the third stage, not the last one.
Do you know what each stage is for?
1. A provider offers a lower price by removing the discovery stage. What have you actually bought?
2. Which stage stalls more small projects than any other?
3. Why do published lists of the seven stages disagree with each other?
Pick an answer to begin.
Frequently Asked Questions About the Stages of Web Development
Q: What are the 7 stages of web development?
The commonly cited sequence is discovery, planning and structure, content, design, build, testing, and launch with what follows it. That is a fair summary of the work, but treat the number as a convention rather than a standard, because published lists disagree with each other and at least one lists six under a heading promising seven.
Q: Is there an official standard for these stages?
Not for web development specifically. There are real published lifecycles, including the UK government's service manual phases and NIST's system development life cycle, and both describe phased delivery without arriving at seven. If a provider tells you their seven is the industry standard, they are describing their own process, which is fine as long as it is stated as that.
Q: Which stage takes the longest?
In practice it is usually content, and not because writing is slow. It is because content depends on the client rather than the provider, and it is the one part of the project that cannot be worked around. The businesses whose builds run to time are almost always the ones that had their words and photographs ready before design started.
Q: Can stages happen at the same time?
Yes, and on most real projects several do. Content production usually runs alongside design, and testing starts well before the build is finished. What cannot sensibly overlap is design and structure, because designing pages before deciding what pages exist produces revisions rather than progress.
Q: What does the launch stage actually involve?
More than pressing a button. Checking the site on real devices, making sure forms deliver to a real inbox, keeping existing page addresses working so search results and links survive the move, and confirming that measurement is recording. On a rebuild, that address work is the single most consequential item in the stage.
Q: Do I need all seven stages for a simple five-page site?
You need all the work, in a much smaller quantity. Discovery might be one conversation and a page of notes, structure might be a list of five pages, and design might mean customising a template. Testing and launch care do not scale down in the same way, and they are the two most often removed from a cheap quote.
Q: What comes after launch?
Measuring what people do, fixing what the first weeks reveal, and improving the pages that carry the most weight. Treating launch as the end is how a site slowly stops being accurate, and it is the reason maintenance appears as a stage in several of the lists rather than as an afterthought.
What This Means for You
There is no canonical seven, and knowing that is more useful than memorising anybody's version. The work is real: decide, structure, gather, design, build, check, launch and keep watching. What matters for your project is which of those a quote includes, which ones your own job can honestly compress, and where the ones you cut will show up again, because they always do.
Take the four questions into your next conversation and you will learn more in ten minutes than another article can teach you, because you will be asking about your project rather than reading about a general one.
At Web Leveling we run all of it and we tell you which parts your project genuinely needs, including when the answer is fewer than somebody else quoted. Our web design work is hand-built and fast, the content and search work sit inside the process rather than being sold back to you afterwards, and everything ends up in your name. We work with small and medium businesses across the country and overseas, wherever they are. If you want to know which stages your current quote actually covers, send it to us and we will mark it up honestly.
Terms
The stage names, translated
Tap a term to see what it means.
Discovery. Working out what the site is for and what success would look like. Sometimes called briefing, information gathering, or requirements.
Information architecture. What pages exist and how somebody moves between them. Usually the cheapest stage to get right and the most expensive to get wrong.
Wireframe. A rough layout showing what goes where, before anything is styled. Made to be argued with, which is the point.
Prototype. A clickable version used to test whether people can actually complete a task, before the real thing is built.
Quality assurance. Structured checking on real devices and browsers. Different from a glance at the finished site on the designer's laptop.
Staging. A private copy of the site where changes are checked before the public sees them.
Post-launch. Measurement, fixes and improvement after the site is live. Present as a stage in most published lists, and absent from most cheap quotes.