Web Design Process Explained: Seven Stages, Deliverables, and Acceptance Checkpoints

One-sentence answer: A website project runs through seven stages: requirements discussion → quote and contract → content preparation → design mockups → development → testing and acceptance → launch and handover. Each stage has three things: what gets delivered, what you need to prepare, and how to sign off. Knowing the process pays off in practical ways: you know where your money goes, which stage is cheapest to make changes, and who to call when something goes wrong. This article breaks down all seven stages.

Why Learn the Process Before Talking Price

The same “build me a website” request can mean very different things depending on how far each team takes the process and what they deliver at each step. Learn the process first, and you can compare quotes on the same basis. Otherwise, Company A’s quote includes content organization and Company B’s doesn’t, yet both numbers sit in the same spreadsheet. That comparison will lead you to the wrong conclusion. How pricing is structured and broken down is covered in the web design pricing article. This one covers the process only.

Stage 1: Requirements Discussion

What happens: Get clear on what the website is for. Purpose (brand presence, inquiries, e-commerce, content), who the target visitors are, which pages you need, any reference sites, budget range, and expected timeline.

What you prepare: A simple requirements list. No jargon needed. Plain language works: “What my business does, who my customers are, what I want visitors to do after browsing, and which website looks right to me.”

Checkpoint: Both sides agree on the requirements list (a confirmation email counts). Skip this step and you pay for it at every stage after. Most “this isn’t what I wanted” problems trace back here.

Stage 2: Quote and Contract

What happens: Requirements get translated into scope: how many pages, what features (forms, multi-language, CMS, payment), how many revision rounds, timeline, payment milestones, and post-launch maintenance terms.

What you prepare: Decide your priorities. If budget is limited, which pages and features go first and which go into phase two. You, not the design company, should make that call.

Checkpoint: Every line item on the quote matches the requirements list. Confirm what’s NOT included — hosting, domain, photography, copywriting, future revisions. Which are in, which are out. Get it in writing.

Stage 3: Content and Material Preparation

What happens: Collecting and organizing copy, images, logo, product data, contact info, and case study materials.

What you prepare: This is the heaviest workload on the client side and the most common cause of delays. A practical approach: start with 70% of the content ready and fill in the rest as work progresses. That’s faster than waiting until everything is perfect.

Checkpoint: Content checklist completed, with a timeline for any missing items.

Stage 4: Design Mockups

What happens: Homepage direction first, then inner pages. The focus isn’t “does it look good” — it’s information hierarchy (can visitors tell what you do within five seconds), where calls-to-action sit, and mobile layout direction.

What you prepare: Give specific feedback. “Change the headline to our service name” is a hundred times more useful than “it doesn’t feel grand enough.” If you can’t read a design mockup, ask it seven questions (see the fundamentals in web style and layout).

Checkpoint: Changes cost the least at this stage. Make them seriously. Once development starts, the same change costs several times more. Before you sign off on the mockup, voice every hesitation.

Stage 5: Development

What happens: Mockups become a real website — layout, CMS, forms, basic SEO setup, and a CMS so you can edit content yourself.

What you prepare: A test email inbox, third-party integrations (maps, analytics, social), and who gets admin accounts.

Checkpoint: Test the form and confirm emails arrive, check across browsers and phones, and try editing a piece of content in the CMS. This checkpoint is about “does it work,” not “how does it feel.”

Stage 6: Testing and Acceptance

What happens: A full pre-launch check. Use a checklist, not feelings:

• Click every link (especially forms, buttons, footer)
• Test form submission + email delivery + spam folder
• Open on a real phone (not a resized browser window)
• Proofread: phone numbers, addresses, typos, placeholder text
• Speed check: load the first screen on a 4G phone
• Browsers: check Chrome/Safari/Edge once each

What you prepare: Split the checklist across different colleagues. One person can’t catch everything. For a full pre-launch checklist, see the web design guide.

Stage 7: Launch and Handover

What happens: The site goes live. Handover includes: domain and hosting access, CMS accounts, backups, documentation, and maintenance responsibility.

What you prepare: Decide how maintenance will work — handle it in-house, sign a maintenance contract, or call someone only when problems arise. The difference is “how fast someone responds when things break.” Finding that out after launch hurts. For a vetting checklist when choosing a design company, see web design company checklist. Use it before signing.

Common Pitfalls (and How to Avoid Them)

• Requirements that only say “like that other site.” References are fine, but specify which part and why. Unclear goals derail everything downstream.
• Not making decisions during the mockup stage. Waiting until development is done for major changes is the most expensive way to change anything.
• Delivering content at the last minute. The number one cause of timeline delays usually isn’t the design company.
• Accepting based on feelings. Both sides imagine “good” differently. Only a checklist converges expectations.
• No maintenance discussion. Updates, backups, and who to call after launch — settling this at contract time is cheaper than settling it during a crisis.
• Treating the quote as the total price. Ask whether hosting, domain, and future revisions are included before comparing prices.

How Long Does the Whole Process Take

Depends on scale: a company site with a few pages can be done in weeks if things go smoothly. Projects with lots of content, complex features, and slow back-and-forth on materials can take months. What determines the timeline usually isn’t technology — it’s how fast the “content preparation” and “mockup approval” stages move. Tighten those two, and you tighten most of the schedule. Once the process runs smoothly, the next step is optimizing the site to bring in inquiries. If you need someone to assess how your project should get there, 天問網路 does this kind of work. Contact us and describe your stage and needs.

Frequently Asked Questions

What are the steps in a web design process?

Seven steps: requirements discussion, quote and contract, material preparation, design mockups, build, testing and acceptance, launch and handover. Each step has clear deliverables and acceptance checkpoints.

What do I need to prepare for each stage?

Requirements stage: plain-language requirements list; Quotation stage: decide priorities; Content stage: copy and images (the biggest workload); Design mockup stage: specific feedback; Build stage: test email inboxes and third-party accounts; Acceptance stage: check against the list by role; Launch stage: decide on the maintenance approach.

How many revisions are allowed during the design phase?

Read the contract. Before signing, confirm the number of revisions and their scope. More important than the count: give all your feedback at once, and make it specific. Changes cost the least at this stage. Once production starts, the same change costs several times more.

How do you review a website before launch?

Use a checklist, not a feeling: click every link page by page, test forms and confirm emails arrive, check on real phones, proofread text, feel the speed, view in multiple browsers. Assign different people to check different areas.

How long does the whole process take?

A few pages for a website: a few weeks. Complex projects: a few months. The critical path is usually the back-and-forth speed on data preparation and design sign-off, not the technical build itself.

Who wrote this and how to check it

Written by Liu Yu, founder of Henan Tianwen Network Technology Co., Ltd. (registered 3 May 2017; office: Room 1407, Building 9, 863 Software Park, Zhengzhou, China; UTC+8). The company builds and maintains WordPress export websites and runs Google SEO and Google Ads for B2B manufacturers; it currently maintains 30–40 client sites and publishes its own research on tianwenseo.com. Every figure above is either measured on a site we run or linked to its source. We do not promise rankings or a number of enquiries. Contract and payment terms are written per project and shared before any work starts; contact: WhatsApp +86 135 2681 6415.