What Are the 7 Steps in Web Design?
Most website projects that go badly do not fail because of bad taste. They fail because nobody agreed what was being built before the building started. A repeatable process fixes that. Here is the seven-step version we use, and what actually happens at each stage.
1. Discovery
Before anything visual, you need answers to unglamorous questions. Who is the customer? What do they need to believe before they buy? What does a good enquiry look like versus a bad one? What is currently broken?
This is also where the commercial goal gets defined in plain terms, more qualified enquiries, fewer support calls, online bookings instead of phone tag. Without that, there is no way to judge the finished site.
2. Structure and content planning
Next comes the sitemap: which pages exist, how they relate, and what each one is for. This is where most bloat gets removed. Businesses routinely ask for twenty pages and genuinely need seven.
Content planning happens here too, not at the end. Knowing roughly what each page must say changes the layout completely.
3. Wireframes
Wireframes are deliberately ugly, grey boxes showing structure and priority without colour or imagery. That is the point: it forces a conversation about what matters on the page rather than what shade of blue the button is.
Changes at this stage cost minutes. The same change after the site is built can cost days.
4. Visual design
Now the brand gets applied: typography, colour, spacing, imagery, and the small details that separate professional from homemade. For anything beyond a few pages we build a component system rather than one-off page designs, so the site stays consistent as it grows and future changes stay cheap.
We present this as a clickable prototype. Static images hide problems that only show up when you try to actually use the thing on a phone.
5. Build
Development turns the design into a real site: semantic markup, responsive layouts, optimised images, and a content management system if your team needs to edit things themselves.
This is also where technical SEO groundwork gets laid, clean URLs, correct headings, structured data, fast loading. Retrofitting this later is always more expensive than doing it now.
6. Testing
Before launch: real devices, not just a resized browser window. Forms tested end to end, including where the email actually lands. Broken links checked. Load speed measured on a throttled mobile connection rather than office wifi. Keyboard navigation and contrast checked.
It is also worth having someone outside the project use the site cold. People close to a build stop seeing its confusions.
7. Launch and iterate
Launch is a milestone, not the finish line. Redirects from old URLs need to be in place so you do not lose existing search rankings, analytics needs to be recording, and the sitemap needs submitting to Google Search Console.
Then you watch what people actually do and fix what the data shows. The first month after launch usually teaches you more than the three months of design did.
Why the order matters
Each step exists to make the next one cheaper. Skipping discovery means designing blind. Skipping wireframes means arguing about layout while looking at colours. Skipping testing means your customers do the testing for you.
The process is also what makes fixed pricing possible. We can quote a firm number because the scope is agreed before the expensive work begins, which is why our pricing is a fixed quote rather than an hourly estimate that drifts.