The Web Design Process: Every Stage From Brief to Launch

Commissioning a new website is a significant investment, and the web design process behind it largely decides whether the finished website does its job or simply looks different from the old one. A well-run website design process moves from brief to launch in a set order, with each stage producing something you can review and sign off before the next begins. The stages below follow how Priority Pixels structures its web design services for UK organisations, from the first planning meeting through to support once the website is live.

For decision makers at mid-sized businesses and public sector bodies, knowing the order of the work matters as much as knowing what it involves. It shows when your team will be needed, which decisions become hard to reverse and where projects tend to lose time, which in most cases is while waiting for content.

The Stages of Web Design

Most professional web design projects follow six stages. The first five take the website from an idea to a live launch, and the sixth covers the care it needs once real visitors arrive.

1. Strategy and planning, where goals, audience, the brief, the sitemap and content needs are agreed.
2. Creative exploration and concept design, where wireframes become visual designs that your stakeholders review and approve.
3. Web development, where the approved designs are built into a working website with its content management system, content and integrations.
4. Testing, where the website is checked across browsers and devices, against accessibility standards and for speed, forms and security.
5. Launch, where the domain is pointed at the new website, redirects go live and analytics and Search Console are connected.
6. Post-launch care, where the website is monitored, issues are fixed and performance is tuned as part of ongoing support.

Each stage ends with an agreed output, such as a signed-off sitemap, approved designs or a tested build. Treating those outputs as formal checkpoints keeps the project on schedule, because a change of direction costs far less at the wireframe stage than it does once development has started.

Discovery, Strategy and Planning

Strategy and planning is the stage where the goals, audience and scope of the project are agreed before any design or code is produced. It usually starts with a kick-off meeting to agree objectives, identify the stakeholders who need a say and settle how success will be measured. Limitations such as a fixed launch date or a system the website must connect to are raised here too.

A clear brief makes this stage much quicker, and our website design brief template sets out what to include. From the brief, the team builds a sitemap of every page and the user journeys between them, which becomes the backbone of the build.

Existing copy, photography, brand assets and third-party tools are reviewed at this point, and accessibility requirements are identified upfront. Search visibility belongs here too, because page hierarchy and information architecture decide how easily search engines and AI tools can understand what you offer. Google’s guidance on AI features in Search confirms that the same foundational SEO practices apply to AI Overviews, and our article on how web design affects SEO covers the design decisions that make the most difference.

Creative Exploration and Concept Design

Concept design is the stage where the agreed structure is turned into a visual direction your stakeholders can respond to. It starts with wireframes, which set out the hierarchy of each key page and show how navigation, calls to action and page sections will behave.

Once the layout is agreed, high-fidelity designs apply your brand identity to the pages, with colours, typography, imagery and interface components drawn from your brand guidelines. Desktop and mobile designs are produced side by side, with accessibility and legibility considered throughout rather than checked at the end. Some teams also turn key screens into a clickable prototype so stakeholders can try interactions before anything is built.

Using real content in the designs wherever possible avoids surprises, because a layout built around placeholder text can struggle when the final copy arrives. Development begins once a final concept is signed off, since reopening design decisions during the build is a frequent cause of rework and delay.

How the Website Development Process Works

Web development is the stage where the approved designs are turned into a fully working website. On a WordPress project that means coding the templates, configuring the content management system and connecting any systems the website depends on.

Priority Pixels builds every website from the ground up in HTML5, CSS3 and PHP rather than using themes or page builders, following the same approach as our bespoke WordPress development work. Editing is set up through Advanced Custom Fields so your team can update content without technical knowledge. Content is loaded during this stage, and forms, site search and integrations with tools like HubSpot or Google Tag Manager are configured and tested.

Development is also the right point to deal with privacy. Any form that collects personal data needs a clear privacy notice and a lawful basis under UK GDPR, and analytics or marketing tags that set cookies need consent under PECR. The ICO’s guidance on cookies and similar technologies explains that you must tell people about cookies and get their consent, with an exception for cookies that are strictly necessary for a service the user has requested. Setting up the consent tool alongside the tags avoids a rushed fix later.

Testing Before Launch

Testing is the stage where the finished build is checked methodically before anyone outside the project sees it. It’s also the last sensible point to make structural changes before the website goes live.

Cross-browser and cross-device checks come first. A typical test plan covers Windows, Mac, iOS and Android with Chrome, Safari, Firefox and Edge, and testers work through menus, forms and content blocks as a visitor would. You’ll be invited to review the website at this point too, and any changes are documented.

Accessibility deserves particular attention. WCAG 2.2 is the current W3C standard and level AA is the benchmark most organisations work to. For public sector bodies it’s a legal requirement under the Public Sector Bodies Accessibility Regulations 2018, and the government’s accessibility requirements for public sector websites confirm that websites must meet WCAG 2.2 AA and publish an accessibility statement. Independent website accessibility audits help where you need evidence of compliance.

Performance testing should use the measures Google uses. The Core Web Vitals assess loading through Largest Contentful Paint, responsiveness through Interaction to Next Paint and visual stability through Cumulative Layout Shift, and they’re far easier to fix before launch than after.

Launching the New Website

Launch is the stage where the finished website is moved to its live server and made public, and it needs careful coordination to avoid downtime and protect search visibility. The development site is backed up and transferred, then DNS is updated to point the domain to the new server.

When the new website replaces an existing one, redirects are the most important part of launch day. Every old URL that has changed needs a permanent 301 redirect to its closest equivalent, otherwise visitors land on error pages and the search visibility the old website built up can be lost. Google’s documentation on moving a site with URL changes recommends server-side permanent redirects mapped from each old URL to its new one.

Our SEO migration checklist for website redesigns sets out those steps in order. Analytics and search tools are connected at the same time, with Google Tag Manager and Google Analytics configured or transferred, the new XML sitemap submitted in Google Search Console and the cookie consent tool checked on the live domain. A final round of checks confirms the SSL certificate is active, forms are routing correctly and no errors are appearing in the live environment.

Monitoring and Support After Launch

The first weeks after launch are when real visitors find the issues that testing missed, so post-launch care should be planned as a stage of the process rather than an afterthought. Uptime and error monitoring, Search Console reports and analytics show whether the website is behaving as expected and whether the redirects are doing their job.

Performance tuning continues once there’s real traffic to measure, because field data from people using the website often differs from lab tests. WordPress core, plugins and server software also need regular updates to stay secure, and a WordPress support and maintenance arrangement gives you a team that can fix problems quickly and make small improvements as your needs change.

What You Need to Provide and When

Your team’s input is needed at every stage, and the availability of content has more influence on the timeline than almost anything else. You don’t need every page written before the project starts, because placeholders can be used during design and you’ll be told exactly when final text and images are needed, which is during development.

The table below shows what you’ll be asked for at each stage and what you should receive. Planning for these points early lets your team set aside time for reviews.

The most useful thing you can do is name one person with authority to approve work at each checkpoint, because projects move quickest when feedback arrives on time and in one place. If writing content is a concern, copywriting support can be added to the project, and our website redesign planning guide covers the internal preparation in more detail.

How Long the Web Design Process Takes

Most Priority Pixels projects take between eight and twelve weeks from deposit to launch. The exact timeline depends on the size of the website, how quickly content is available and how fast feedback comes back at each review, and a clear schedule is agreed early so everyone knows when their input is needed.

Larger websites with complex integrations or a significant migration will take longer, and it’s better to plan for that from the start than to cut testing short to hit a fixed date. Testing and redirects are the stages most often compressed under deadline pressure, yet they protect your search visibility once the website is live. Priority Pixels designs every website in-house for B2B and public sector organisations, and each project follows the same structured process from strategy to launch, so you always know what comes next.