Web Design
The Web Design Process: What to Expect When You Work With a Studio
Key takeaways
- Agree on goals and structure before visuals, and on visuals before code.
- A detailed questionnaire with examples is the best way to get a strong first design.
- Two to three structured revision rounds is a common standard; extra rounds are often billed.
- Send consolidated feedback from one decision-maker each round.
- Keep the domain, platform and data in your own accounts.
What are the steps in a web design process?
A professional web design process usually runs through eight stages: discovery, a design questionnaire, sitemap, wireframes, design rounds, development, QA, and launch. Each stage ends with something you approve, so decisions are made once and the project stays on schedule.
Names vary from studio to studio, but the logic is the same: agree on goals and structure before visuals, and agree on visuals before code. Changing a sitemap is cheap; changing a built page is not.
The web design process at a glance
Here is what happens at each stage, what you get, and what you need to do. Timelines vary with scope; a small site moves faster than a large store.
| Stage | What happens | Deliverable | Your role |
|---|---|---|---|
| 1. Discovery | Goals, audience, scope, platform, timeline | Agreed scope and proposal | Explain goals, budget, and constraints |
| 2. Design questionnaire | Structured brief on brand, style, competitors, must-haves | Completed brief | Answer in detail; share examples you like |
| 3. Sitemap | List of pages and how they connect | Sitemap / page list | Confirm pages and priorities |
| 4. Wireframes | Low-detail layouts showing structure and content order | Wireframes for key templates | Review flow and content, not colors |
| 5. Design rounds | Visual design of key pages, then revisions | Approved designs (often in Figma) | Give consolidated feedback each round |
| 6. Development | Building the approved design on the platform | Working site on a staging or preview link | Provide final content, access to accounts |
| 7. QA | Testing on devices and browsers, forms, checkout, speed | Fixed issues list | Test as a real visitor; report bugs |
| 8. Launch | Domain connection, redirects, final checks, go live | Live site and handover | Approve launch; learn to edit content |
What happens during discovery?
Discovery is where the studio learns what the site must achieve and confirms the project is a good fit. Expect a call or a written exchange about goals, audience, scope, platform, budget, and timeline.
Good questions to expect: What should a visitor do on the site? Who are your best customers? What is not working on your current site? Which platform are you on, and why? The output is a clear scope and proposal, so both sides agree on what is being built before work starts.
Why do studios use a design questionnaire?
A questionnaire turns vague taste into a usable brief. It captures your brand, tone, colors, fonts, competitors, sites you admire, and must-have features in one place, so the designer is not guessing.
The most useful answers are specific. "Clean and modern" helps far less than "we like how this site uses large product photography, and we dislike busy homepages." Links and screenshots are gold.
What are a sitemap and wireframes?
A sitemap is the list of pages and how they relate. A wireframe is a simple layout that shows the structure of a page and where content goes, before any visual design.
The Nielsen Norman Group describes wireframes as a common UX deliverable for presenting page-level layout ideas. Their value is focus: reviewing a gray box layout makes you think about content order and user flow, not colors.
Some studios combine wireframes with the first design round for smaller sites, especially when a clear brand already exists. For larger sites and stores, separate wireframes usually save time later.
How many design revisions are normal?
Two to three structured revision rounds is a common standard for website design projects. Extra rounds are usually available, but they are often billed separately.
A round means you review the design, send all your feedback together, and the designer delivers an updated version. Designer and educator Paige Brunton, for example, recommends structuring revisions as defined rounds (her example package includes three) rather than counting individual tweaks, so feedback is complete and the timeline stays predictable.
To get the most out of each round:
- Collect feedback from every decision-maker before sending it.
- Describe the problem, not just the fix ("the price is hard to find" rather than "make it red").
- Prioritize: separate must-change items from nice-to-haves.
- Comment directly on the design file when possible.
Our take: if you are on your fourth round, the issue is usually the brief, not the design. Go back to the goal and the questionnaire answers.
What happens in development, QA and launch?
Development turns approved designs into a working site, QA tests it thoroughly, and launch makes it live with redirects and final checks in place.
During development, the site is built on a staging or preview link so you can watch progress without affecting your current site. This is when final content, product data, and account access are needed.
QA should cover phones, tablets, and desktop browsers; forms and email notifications; checkout and payments for stores; page speed; basic SEO settings; and accessibility basics. W3C's current recommended accessibility standard is WCAG 2.2, a helpful reference for contrast, focus states, and alt text.
Launch includes connecting the domain, setting up 301 redirects from old URLs if you are replacing a site, submitting the sitemap to search engines, and a short handover so your team can edit content.
What should clients prepare before a project starts?
The fastest projects are the ones where content and access are ready early. Prepare as much of this as you can:
- Brand assets: logo files, colors, fonts, brand guidelines if you have them.
- Content: page copy, product descriptions, team bios, FAQs, legal pages.
- Images: high-quality product and lifestyle photography; stock imagery only where needed.
- Examples: three to five sites you like and why, plus competitors.
- Accounts and access: domain registrar, platform account, analytics, email marketing tool, payment provider.
- One decision-maker: a single person who consolidates feedback and approves each stage.
Make sure accounts are in your company's name. Your platform, domain, and data should belong to you, not to whoever builds the site.
How long does the process take?
Small brochure sites often take a few weeks; larger sites and online stores commonly take one to three months. The biggest delays usually come from waiting on content and feedback, not from design or development. For store timelines specifically, see how long it takes to build a Shopify store.
How we can help
Our process follows the same shape: you book a discovery call, fill in our design questionnaire, and receive a first design version in under a week, with up to three revision rounds before development and launch. We set everything up under your own accounts. See our Shopify store design service or web design for simpler non-Shopify sites.
Send us your store URL and we'll email you the fixes that matter most. No call needed.
Frequently asked questions
How many revisions should a web designer include?
Two to three rounds of revisions is common for website design. A round means you send all feedback at once and receive an updated version; additional rounds are often available at extra cost.
What is the difference between a wireframe and a mockup?
A wireframe shows layout and content order with little or no visual styling. A mockup (or design) shows the final look: colors, typography, imagery, and spacing.
What do I need to give a web designer before starting?
Your logo and brand assets, page copy, images, examples of sites you like, and access to accounts like your domain and platform. A single decision-maker for approvals also speeds things up.
Who should own the website accounts?
You should. The domain, platform account, analytics, and payment provider should be registered to your business, with the designer added as a collaborator or staff account.
Why does my web design project take longer than planned?
The most common causes are late content, slow or fragmented feedback, and scope added mid-project. Preparing content early and consolidating feedback keeps timelines on track.