Website Design Process: 7 Steps From Brief to Launch
Last updated: November 18, 2026
The website design process has seven steps: discovery and brief, sitemap and content, wireframes, visual design, build on a staging site, testing and client review, and launch. Each step ends with something the client signs off, so later steps do not reopen earlier ones. Plan more than one round for feedback and testing.
This guide is for agencies and freelancers who design and build websites for clients. It follows the order most projects take, says what each step produces and who approves it, and points out where projects slip. In PMI’s 2018 Pulse of the Profession, erroneous requirements gathering was one of the top three causes of project failure, which is why the process starts with questions, not designs.
The 7 Steps at a Glance
| Step | What happens | Output | Client signs off |
|---|---|---|---|
| 1. Discovery and brief | Learn the goals, audience, and constraints | A written brief | The brief |
| 2. Sitemap and content | Decide the pages and what goes on each | Sitemap and content plan | The page list |
| 3. Wireframes | Lay out each page type without visual design | Wireframes | Layout and hierarchy |
| 4. Visual design | Apply type, color, imagery, and components | Design files for each page type | The look |
| 5. Build on staging | Build the approved designs on a private site | A working staging site | Nothing yet |
| 6. Testing and client review | Test, collect feedback, fix, and run UAT | Fixed issues and UAT results | Ready to launch |
| 7. Launch and handover | Go live, check, and hand over | The live site and handover notes | Project complete |
1. Discovery and Brief
Discovery is where you learn what the site must do before anyone designs it. The UK government’s service manual says to understand users, constraints, and opportunities first, and is blunt about the order: “You should not start building your service in discovery.” For a client site, constraints include who controls the domain and hosting, which tools the site must connect to, and any legal or accessibility requirements.
Start with a website design questionnaire, follow up on a kickoff call, and write a short brief: goals, audience, the one action visitors should take, how success will be measured, and who approves the work. The client signs the brief.
2. Sitemap and Content Plan
List every page, group them into navigation, and decide what each page must say. Agree who writes the copy and when it is due, because every later step depends on it. Plan redirects for old pages that still get visits. The client signs off the page list, which also becomes the scope you price against.
3. Wireframes
Wireframes show the layout and order of content for each page type, without color or imagery, so the review stays on structure. The UK guidance describes the stage after discovery, alpha, as a short phase in which solutions are prototyped and tested with a small group to get early feedback. On a client site, a clickable wireframe of the main pages does the same job. The client signs off the layout and hierarchy.
4. Visual Design
Apply the brand to the approved wireframes: type, color, imagery, and components with all their states. Check color contrast and focus states against WCAG 2.2 now, while changes are cheap. Present one page type first and get it approved before designing the rest, so the client’s taste is settled early. The client signs off the look, with the revision rounds agreed in the plan.
5. Build on a Staging Site
Developers build the approved designs on a staging site, a private copy that only the team and client can open. Hand over the design with every state and screen width, not just the desktop mockups, and keep the client informed without asking for feedback on unfinished pages. Nothing is signed off here; this step ends when the build is ready to test.
6. Testing and Client Review
The UK government’s assurance guidance says test schedules “should not assume success at first pass, and allow time for faults identification and rectification.” Plan at least two rounds: the team tests first, using a test plan and a website QA checklist, then the client reviews and runs user acceptance testing.
Client feedback arrives in this step, and so do requests for new work. Keep every comment in one list, sort fixes from new work, and close each round with a recap; see how to manage client feedback and how to handle scope creep. The client signs off that the site is ready to launch.
7. Launch and Handover
Move the site live, then check it on the real domain: forms deliver, redirects work, analytics record visits, and pages meet the “good” Core Web Vitals thresholds (LCP of 2.5 seconds or less, INP of 200 milliseconds or less, CLS of 0.1 or less). Hand over logins, a short guide for editing content, and a list of known issues with dates. Agree who maintains the site from here.
Where the Website Design Process Slips
- Content arrives late. Design and build wait for copy, or get redone when it lands.
- A new reviewer appears. Someone who missed discovery reopens an approved design. Name one approver at the start.
- Feedback is scattered. Comments in email, chat, and calls get missed or done twice.
- New work hides in feedback rounds. PMI found scope creep on 52% of the projects in its 2018 survey.
- Testing gets squeezed. The fixed launch date eats the time planned for the second round.
A website project plan puts dates, owners, and feedback rounds against each step, so these show up as risks before they become delays.
Where a Feedback Tool Helps
Steps 6 and 7 run on feedback. In OverlayQA, clients open a review link and comment on the staging or live site with no account or extension, and click Done reviewing when their round is finished. Each comment arrives as an issue with a screenshot, the page address, browser, and screen size, in the same list as the bugs your team finds, and issues sync both ways with Jira, Linear, and other trackers.
Frequently Asked Questions
What are the steps of the website design process?
Discovery and brief, sitemap and content, wireframes, visual design, build on a staging site, testing and client review, and launch and handover.
What is the first step in designing a website?
Discovery: learning the goals, audience, and constraints, usually through a client questionnaire and a kickoff call, and writing a brief the client approves.
How long does the website design process take?
It depends on the number of pages, how quickly content arrives, and how many feedback rounds are included. Build the timeline from those three numbers rather than a typical figure.
What is the difference between web design and web development?
Design decides what the site looks like and how it works for visitors, in steps 1 to 4. Development builds it, in step 5. Testing, review, and launch involve both.
Where does client feedback fit in the process?
At the end of every step, as a sign-off, and most heavily in step 6, when the client reviews the built site. Agree the number of rounds per step in the project plan.
What happens after a website launches?
Check the live site, fix what launch revealed, hand over logins and an editing guide, and agree who maintains the site. Measure it against the success measure from the brief.
Run the review step on the page itself. With OverlayQA, clients comment on the staging site with no account, and every comment and test finding lands in one tracked list.