The Website Design Process: Steps, Timescales and What to Expect

If you have never commissioned a website before, the process can feel like a black box. You send an enquiry, some conversations happen, and at some point a website appears. Knowing what actually goes on in between makes the project far less stressful, helps you plan your own time and content, and makes it much easier to tell a well-run project from a chaotic one.

This guide walks through the seven steps that almost every professional website project follows, from the first enquiry to the weeks after launch. For each one it explains what the designer does, what you need to do and how long it typically takes. It then gives realistic timescales for each type of website, explains what most often causes delays and shows how to keep your project on schedule. It is based on how we run projects at DigitalPod, but the sequence is much the same wherever you go.

The Seven Steps at a Glance

1. Enquiry, discovery and requirements
2. Proposal, quote and agreement
3. Planning the structure
4. Design
5. Development
6. Testing and client review
7. Launch and aftercare

Step 1: Enquiry, Discovery and Requirements

Everything starts with an enquiry. The designer's job at this stage is to understand your business, who the website is for, what it needs to achieve and what you already have. Expect questions about your customers, your competitors, the pages and features you think you need, your existing branding and content, your budget and your timescale. A designer who asks few questions is either guessing or planning to give you something generic.

What you need to do: give as clear a picture as you can. A short written brief makes this stage much faster, and our guide on how to write a website design brief includes a template. Be honest about your budget and about the state of your content.

How long it takes: a few days to a week, and much faster if you arrive with a brief.

Step 2: Proposal, Quote and Agreement

With the requirements understood, the designer sends a proposal. It should set out what will be built (pages, features, what is and is not included), a fixed price or a clear pricing basis, payment terms, a realistic timescale and the terms of business. Read it carefully and check that the scope matches what you asked for. If anything is unclear, ask now rather than halfway through the build.

Once you accept, a deposit is paid and the project is booked in. At DigitalPod the deposit is 50% of the project fee, with the remaining 50% due on completion, and our terms of business are published on the website. Our guide on how to find and choose a website designer covers what to look for in a proposal, and our questions to ask a website designer cover the things to confirm before you sign.

What you need to do: review the proposal, agree the scope in writing, pay the deposit and confirm who at your end will be making decisions.

How long it takes: a few days, depending on how quickly you can review and decide.

Step 3: Planning the Structure

Before anything is designed, the designer plans how the website fits together: a site map showing every page and how they link, a plan for what each page needs to contain, and a content plan listing what exists, what needs writing and who is writing it. This is also where any functionality is thought through in detail, such as how a booking flow or a members' area will work step by step.

Good planning is invisible when it works and painfully obvious when it is skipped. Pages that nobody can find, forms that ask the wrong questions and a navigation that confuses visitors usually trace back to a project that jumped straight to the visuals.

What you need to do: review the site map and page plans, confirm they cover everything your customers need, and start gathering content against the content plan. Content started now arrives in time; content started during development does not.

How long it takes: a few days.

Step 4: Design

Now the website starts to take shape. Many designers begin with wireframes, which are simple layouts showing where headings, text, images and buttons sit on each page without any colour or styling. Once the layouts make sense, visual mockups are produced showing exactly how the finished pages will look: colours, typography, imagery, buttons and spacing, usually for the home page and a handful of key templates first. If your startup needs a logo and brand identity as well, it is designed at this stage so the website and the brand develop together.

You review the designs, give feedback and the designer revises them. Most proposals include a set number of revision rounds. When you are happy, you approve the visuals, and that approval is the signal for development to begin. Nothing should be coded before this point, because changes are quick and cheap in a design file and slow and expensive in a built website.

What you need to do: look at the designs on a phone as well as a desktop, gather feedback from everyone who has a say and send it as one consolidated response, be specific about what you want changed and why, and give a clear written approval when you are happy.

How long it takes: one to three weeks including revisions. Two rounds of feedback that each take a week add two weeks, so this stage runs largely at your pace.

Step 5: Development

With the designs approved, the developer builds the website: the page templates, the navigation, the forms, any databases or admin screens, and the responsive layouts that make everything work on every screen size. We build with modern technology such as Next.js rather than templates or page builders, which is why our sites load fast and can be extended later. If the designer and developer are the same people, as they are at DigitalPod, this stage tends to run more smoothly because nothing is lost in a handover.

During development your content is added to the pages. Expect regular progress updates, and in many projects a link to a work-in-progress version so you can see pages as they come together.

What you need to do: deliver any outstanding content and images promptly, answer questions as they come up, and resist the urge to redesign pages that have already been approved. Changes at this stage are possible but they cost time and sometimes money.

How long it takes: two to three weeks for a brochure site, longer for admin dashboards, booking systems, members' areas or e-commerce, where development can run to eight weeks or more.

Step 6: Testing and Client Review

Before launch, the website goes onto a private test server. The designer tests it across devices and browsers, checks every form, link and button, measures loading speed, proofreads the content and makes sure the technical foundations search engines look for are in place. Then you are invited to review it.

This is your chance to try everything as a customer would: submit the forms, make a test booking, read every page on your phone, check the spelling of your own address. Anything that is not right is noted and fixed, and once you are satisfied you give final approval. At DigitalPod the remaining 50% of the fee is paid at this point, before the site goes live.

What you need to do: test thoroughly, report everything in one list rather than drip-feeding issues, and sign off when it is ready.

How long it takes: one to two weeks, including your review and the final fixes.

Step 7: Launch and Aftercare

Launching means pointing your domain name at the new website, which involves changing DNS settings with whoever controls your domain. If you are replacing an existing site, old page addresses are redirected to their new equivalents so that visitors and search engines are not sent to dead pages. Analytics and Google Search Console are set up or transferred, the sitemap is submitted, and a final check is made on the live site.

What you need to do: provide domain access in good time, check the live site, keep the handover details somewhere safe, and start telling people about your new website.

How long it takes: a day or two, provided the domain login has been found in advance.

Typical Timescales by Type of Website

Adding the steps together, the figures below assume an experienced designer or small studio, a clear brief and a client who responds within a couple of days. They run from the agreed brief to the website going live. For a week-by-week schedule and the five things that set your timescale, see our guide to how long a website takes to build.

Agencies with several people working at once do not necessarily finish faster. Larger teams add meetings, handovers and approvals, and the waiting time for content and feedback is the same whoever builds the site. A redesign of an existing website takes roughly as long as a new one of the same size, with a little extra for migrating content and setting up redirects, as our website redesign guide explains.

Why "Your Website in a Week" Usually Means a Template

Some services promise a finished website in a few days. What they deliver is a template with your logo, colours and text added. There is no discovery, no custom design to approve, no planning of the structure around your customers, and very little testing. That is fine if a template is what you want, but it is a different product from a custom-designed website and should be priced accordingly. A proper design process cannot be compressed into a week without skipping the steps that make the website work. Our comparison of custom websites and website builders explains the trade-offs.

How DigitalPod's Four-Stage Process Maps Onto These Steps

On our startup website design prices page we describe our process in four stages, because that is how clients experience it. The seven steps above fit inside them like this:

We give every client a realistic completion timeline once the visuals have been approved, because that is the point at which the scope is fixed and the development work can be planned accurately. During the build we send regular progress updates, and because the same people design and build each website there are no handovers to wait for between stages.

What Most Often Causes Delays

In our experience the same handful of issues account for almost every website that runs late:

1. Content arriving late. By a wide margin the biggest cause. A website cannot be finished without the words and images for each page, and writing content always takes longer than people expect.
2. Slow feedback. Designs or a test site sitting unreviewed for two or three weeks stop the project dead.
3. Changing scope. Deciding part way through that the site also needs a shop, a blog or a members' area is a new project, not a tweak, and often changes decisions already made.
4. Too many decision-makers. Five people giving five sets of feedback means extra revision rounds and compromises that then get revised again.
5. Skipping approval. Starting development before the visuals are signed off leads to expensive rework.
6. Third-party integrations. Payment providers, booking tools, CRMs and email systems all need accounts, approvals and testing, and some of that waiting is outside anyone's control.
7. Domain and DNS access. Nobody can find the login for the domain name on launch day.
8. Waiting for photography. Professional photos booked late hold up the pages designed around them.

How to Keep Your Project on Schedule

• Content first. Start writing page text and gathering images as soon as the site map is agreed, or sooner. Rough drafts are fine; they can be polished while the design is in progress.
• One decision-maker. Collect opinions internally, but have one person give the designer a single, consolidated response.
• Batch your feedback. Review everything, then send one list. Drip-fed comments over several days cause rework.
• Agree the scope in writing. Keep a separate list of extras for a second phase rather than adding them mid-project.
• Respond within a couple of days. The designer's timescale assumes you will. If you know you will be away, say so up front.
• Sort out access early. Domain registrar, hosting, analytics and any accounts for integrations.
• Book photography at the start. Or agree to launch with existing images and swap them later.

If you have a date the website must be live by, such as a launch event, a trade show or the end of a contract with your current provider, work backwards from it. Take the typical timescale for your type of site from the table above, add two weeks of contingency, and that is the latest date the brief needs to be agreed. Tell the designer about the deadline at the first conversation; a realistic designer will say whether it is achievable and what they need from you to hit it, and will usually suggest launching with the essential pages and adding the rest afterwards if time is tight. If you are launching a new business, our startup website checklist lists everything to have ready.

What Happens After Launch

After launch the designer should hand over everything you own: logins, the domain and hosting details, source files or a code repository, and any documentation for an admin area. Agree what support is available for questions and small changes, and whether you want ongoing hosting and maintenance. We offer managed cloud hosting from £20 per month, which also means we can make fast changes to your site whenever you need them. Smaller updates to a site built on a solid foundation, such as adding a page or a new feature, are usually a matter of days rather than weeks.

If you would like to see how we run a project from the first conversation to launch, take a look at our startup web design service, or contact us with a few details about your project and we will tell you exactly what would happen next and how long it would take.