Signing the contract is the start, not the finish. A good web design project runs on a clear, predictable process: discovery, planning, design, content, development, testing, and launch. Each stage ends in something you review and approve, and your own role at each step is bigger than most business owners expect. Knowing what that process looks like stops you worrying when the designer goes quiet for a week, and stops you being the reason the project drags.
This guide walks through the seven stages of a web design project in the order they happen, explains what you do at each one and what you should expect to receive, and gives you the honest signal of whether a project is on track or quietly slipping. If you are still choosing who to hire, read our guide to choosing a web designer first. This guide assumes you have signed on, or are about to, and want to know what comes next.
Key Takeaways
- A standard web design project runs seven stages: discovery, planning, design, content, development, testing, and launch. Each stage ends in a deliverable you review.
- Your two most important jobs are giving clear direction and content, and approving work at each checkpoint. The single biggest cause of delay is slow content and feedback, not a slow designer.
- You will take part in roughly three formal reviews: the design, a development preview, and a pre-launch test. Knowing where you have the most influence means you do not need to watch over the whole build.
- Small business websites typically take 4 to 8 weeks and ecommerce sites 10 to 20 weeks, figures agencies commonly quote, though your scope and how fast you supply content set the real pace.
- A healthy process tells you up front when you will see work and when you must respond. A worrying one says it will be in touch when the site is done.
Why the Process Matters as Much as the Design
The process is your first signal of whether a project is healthy. A clear, predictable process turns “waiting and hoping” into “knowing what happens next and what you need to approve.” Projects with a vague process are the ones that reach launch and discover the whole thing is pointed in the wrong direction.
The process is risk control. Every stage has a checkpoint where you review work before it hardens into something expensive to change. A correction made on a design concept costs little. The same correction made on a built page costs much more, and a correction after launch costs the most.
The process is also expectation management. When both sides know who delivers what and when, there is no room for the “I assumed that was included” argument that derails so many projects. A healthy process hands you a stage list with milestones, while a worrying one promises to be in touch when it is done. Our guide to web designer red flags covers the full list of warning signs; this guide focuses on what a good process looks like from the inside.
The 7 Stages of a Web Design Project
No matter who you hire, the project will almost always move through the same seven stages. Agencies and solo designers differ in how they run each stage, but the sequence is consistent, a point that holds across the Australian and international agencies whose published processes we reviewed. Here is the overview, then we break down each stage in turn.
| Stage | What you do | Typical time* |
|---|---|---|
| 1. Discovery and strategy | Answer questions, share your business and goals | 1-2 weeks |
| 2. Planning and structure | Confirm the page list and sitemap | 1-2 weeks |
| 3. Design (UX and UI) | Review design drafts and give feedback | 2-4 weeks |
| 4. Content | Supply or approve words, images and assets | 2-6 weeks (often runs alongside) |
| 5. Development | Walk the preview site and confirm it works | 3-12 weeks |
| 6. Testing and quality assurance | Test the site yourself before launch | 1-2 weeks |
| 7. Launch and handover | Confirm go-live and receive everything you own | Launch day plus follow-up |
*These durations are the ranges agencies commonly publish rather than independent research; one Australian agency whose published process we reviewed gives them in roughly these bands (Alspark, “The Complete Website Development Process Explained”, retrieved 2026-09-03). A full small business website typically lands in the 4 to 8 week range, and an ecommerce site in the 10 to 20 week range, but the real driver is scope and how quickly you deliver content and feedback, not the designer’s pace. The rest of this guide takes each stage in detail.
Stage 1: Discovery and Strategy
Discovery is where the designer gets to understand your business. This stage asks what your website must achieve, who it is for, who you are up against, and how you will know it has worked. The deeper this conversation, the less rework you will face later. “Tell me about your customers” matters far more than “show me some colours.”
Expect a questionnaire or a structured call, a review of your current site and your competitors, and a shared definition of what success looks like. Your job here is to be specific about your business goals and your customers, not just to say you want it to look good. The deliverable is a project brief or strategy summary, and this is the moment to check the designer has genuinely understood your business before anything is designed.
Be wary of a project that skips discovery and jumps straight to templates and colours. A design built before the designer understands the business almost always needs rebuilding. The depth of discovery is also often what separates one quote from another; our guide to comparing web design quotes shows how to spot the difference.
Stage 2: Planning and Structure
Planning turns “what the site will do” into “what pages it will have and how they are organised.” This is where the sitemap and the page list are settled, and it is the stage where adding a page later usually costs money or time. Confirm the page list now, and point out anything missing before the design begins.
Expect a sitemap, a list of every page with its purpose, and often rough wireframes showing where content sits on the page. The deliverable is the sitemap and page plan, and you should be asked to sign it off. A common miss is the page nobody thought of until launch: the FAQ page, the privacy or returns policy, or a page for a service you offer but forgot to mention. Catch those here and they are cheap to add.
Stage 3: Design (UX and UI)
Design is the first stage where you see the site. The designer presents a homepage concept and then inner-page templates, and you give feedback. This is the stage where your voice carries the most weight, because changing direction on a design draft is far cheaper than changing it after development.
Expect a homepage design, then inner-page templates, with a mobile view shown alongside the desktop one. When you give feedback, frame it around the business goal rather than personal taste. “This page needs to get people to call us” is useful feedback. “I do not like blue” is not. Give your feedback as one consolidated list per round rather than a stream of scattered messages, and check how many revision rounds your contract includes, because extra rounds are usually charged. Our guide to web design contracts covers how revision clauses are normally written.
Be wary of a project that shows you only the desktop version and never the mobile one. Most of your visitors will be on a phone, and a design that only looks right on a desktop is a design that is not finished.
Stage 4: Content
Content is the real reason most projects run late. The designer needs your words, images, and product or service details, and these almost always arrive more slowly than expected. Who supplies the content and by when is the single most important thing to settle before the project starts.
Expect the designer to give you a content template or a list of what is needed per page. You will supply the copy, your logo and photos, and any product or pricing information, unless you have paid the designer or a copywriter to produce it. This is the part you cannot hand off unless you have agreed to, so start writing early. Good design depends on good content, and placeholder text on a design draft tells you almost nothing about how the finished page will read.
A practical tip: at the very start of the project, ask exactly which assets you need to prepare, and put writing them into your own calendar. Do not wait for the designer to chase you. Your homepage and service page copy is also the foundation of your search visibility, so resist filling it with “welcome to our website.” If you serve a local area, our local SEO guide for Adelaide businesses explains why that copy matters for being found.
Stage 5: Development
Development turns the approved design into a working website. The designer builds the pages, the features, and the responsive layout, and you should receive a link to a development preview rather than sit in silence waiting.
Expect the front-end and back-end to be built, features like contact forms and maps and any ecommerce to be wired up, and the design to be adapted for phones and tablets. Your job is to walk the preview site the way a real customer would: fill in the contact form, click the buttons, and look at it on your own phone. Confirm that what is built matches what the brief promised. The deliverable is a working preview site plus a checklist of the features you were promised.
Be wary of two things here. The first is design changes made during development, which are expensive; the design should be locked before development starts. The second is a designer who will not show you a live preview and only sends screenshots, because screenshots can hide a great deal. The build stage is also where page speed and mobile experience are decided; if you want to understand that side in more depth, our guide to mobile UX and conversion covers it.
Stage 6: Testing and Quality Assurance
Testing is your last chance to catch problems before the site goes public. The designer runs a pass over functionality, browser compatibility, and speed, and you should run your own pass as a buyer would. A problem found here is cheap to fix. The same problem found after launch is an incident.
Expect the designer to test across browsers and phones, to check that every form and link works, to look at load speed, and to proof the content. Your job is to test the site end to end yourself: every button, every form, every link, the mobile experience, and the spelling. The deliverable is your sign-off, or a written list of what needs fixing first.
Be wary of pressure to “launch now and fix it later.” Minor cosmetic issues can wait, but the core paths cannot. If the contact form or the buy button does not work, the site is not ready, no matter how close the deadline feels. For a structured way to run that pre-launch pass, our website conversion audit guide walks through the checks worth doing on the paths that matter.
Stage 7: Launch and Handover
Launch day is more than the site going public. It covers the domain switch, the security certificate, submission to search engines, and a full handover of everything you own: the domain, the hosting, the admin access, and the accounts the site depends on. Before launch, what you confirm is not just that it looks right but that you will be in control of it.
Expect the domain to point to the new site, the SSL certificate to be active, and the site to be submitted to Google. Your job is to confirm the go-live timing, to test the live site for real, and to make sure you receive the handover items. That means access to the domain registrar, the hosting account, the website admin, and your email and analytics accounts. These belong to you, and you should hold the keys. Our guide to website ownership covers what you should own and how to make sure of it.
Most contracts include a short window after launch for fixing bugs at no charge, and ongoing maintenance is usually a separate arrangement. Be wary of a designer who goes quiet after launch or will not hand over the accounts. A project that ends with you holding everything is a project that ended properly.
Timelines: What’s Normal and What’s a Red Flag
Small business websites typically take 4 to 8 weeks and ecommerce sites 10 to 20 weeks, figures that agencies commonly publish, but the real driver is scope and how quickly you deliver content and feedback, not the designer’s pace. Knowing what a normal timeline looks like stops you worrying about a reasonable pace and stops you accepting a genuinely slipping one.
The ranges agencies commonly quote are a landing page in 1 to 3 weeks, a small business site in 4 to 8 weeks, a corporate site in 8 to 16 weeks, and an ecommerce site in 10 to 20 weeks, as one Australian agency’s published process puts it (Alspark, retrieved 2026-09-03). Treat these as rough guides, not promises. The variables that actually move a timeline are how fast you supply content, how fast you give feedback, and whether the scope grows mid-project.
The healthy sign is a designer who gives you a stage-by-stage schedule and keeps you updated without being chased. The red flag is a project where you are always the one asking what is happening, or where there was never a schedule to begin with. If you want the schedule to be enforceable, the timeline and delay clauses belong in your contract, which our contract guide covers.
Frequently Asked Questions
How long does it take to build a website?
Agencies commonly quote a landing page at 1 to 3 weeks, a small business site at 4 to 8 weeks, and an ecommerce site at 10 to 20 weeks. These are guides rather than guarantees, because the real pace depends on your scope and how quickly you supply content and feedback. A project where content arrives late will run long no matter how fast the designer works.
How involved do I need to be in the web design process?
You are most involved at two points: early on, when you explain your business and supply the content, and at each review checkpoint, when you approve the design, the preview, and the pre-launch test. You do not need to watch the whole build, but you cannot be a passenger either. Slow content and slow feedback are the most common reasons a project runs over.
What if I do not like the design?
Speak up at the design review stage, where changing direction is cheapest. Most contracts include one or two rounds of revisions, with extra rounds charged, so use them well. Frame your feedback around the business goal rather than personal taste, because “this needs to get people to call us” leads somewhere while “I am not sure about the colour” does not.
Do I have to write all the content myself?
Usually you supply the words, images, and product or service details, or you pay the designer or a copywriter to write them. Placeholder text tells you little about how a page will read, so settle who writes the content before the project starts. Writing it yourself keeps it authentic, but a professional copywriter is a reasonable investment if writing is not your strength.
What happens if the project runs over the timeline?
First work out why. If the scope grew or content arrived late, the delay is shared. If the designer has simply stalled, that is a different problem. What your contract says about timelines and delays determines who bears the cost, which is why those clauses matter before you sign. A good designer will flag a slipping timeline early rather than let you discover it.
Who owns the website when it is finished?
That depends on what your contract says and how the accounts are set up. Before launch you should hold the domain, the hosting account, the website admin access, and your analytics. Our guide to who owns your website explains what you should own and how to make sure you get it, and our contract guide covers the clauses that protect your ownership.
Conclusion
A healthy web design project is predictable: seven stages, a deliverable to review at each one, and your own content and feedback setting the pace. Knowing what the process looks like turns anxiety into participation and turns “waiting for an update” into “approving a milestone.” Before you sign, make sure the designer can describe their process as clearly as this. If you want a website built on a clear process with a handover that leaves you in control, our Adelaide team works exactly that way, and we will tell you honestly what your project involves. See our small business website development service or talk to us about your project.
