Stages of Building a Website — Step by Step

You are commissioning a website for the first time — or the third time — and once again you feel like you are in a dark room. The agency says “we’ll deliver the design in three weeks,” then goes silent for a month. Or the reverse — they deliver something in two weeks, but it is not at all what you had in mind.

Most problems in client–agency collaboration do not arise from bad faith. They arise from a lack of common language and from the client’s unfamiliarity with the process. When you know what should be happening at each stage of building a website, you can control the project, ask the right questions, and catch delays before they become costly.

This article walks you through all six stages — from the first conversation to the handover of the finished site.

Why Knowing the Process Protects You as a Client

When a client does not know the website development process, the contractor has a natural informational advantage. They can cut corners without your knowledge, skip testing, deliver a graphic design without the wireframing that should precede it. The result? A site that looks “nice” in a preview but completely fails to meet business objectives.

Knowing the process acts as insurance. You can verify the schedule, understand invoices, assess the quality of deliverables, and — most importantly — enforce the commitments in the contract. A client who asks “do we have approved wireframes before the graphic design stage?” is not a difficult client. They are a partner.

Stage 1 — Brief and Discovery

Discovery is the foundation of the entire project. At this stage the agency — or sole contractor — should be asking you questions, not presenting ready-made solutions. A good brief uncovers: the business goal of the site, the target audience, competitors, existing assets (logo, photos, content), and constraints (budget, deadline, integrations with other systems).

What to expect:

• A questionnaire or discovery workshop (online or in person)
• Competitor analysis — at least three industry websites
• Defining the site’s KPIs (conversion, time on site, number of enquiries)
• A preliminary URL architecture and sub-page structure

Red flag: if the contractor jumps from the first conversation straight to a graphic design — without an approved brief — the project is heading in the wrong direction.

Discovery typically takes 3 to 7 working days. For larger projects — up to two weeks.

Stage 2 — Information Architecture and Wireframing

Before anyone touches a design tool, a wireframe should be created — a black-and-white sketch of element placement on the page. A wireframe has nothing to do with colours or fonts. It concerns the hierarchy of information: what the user sees first, where the CTA button is, how the navigation looks on a mobile device.

Information architecture (IA) answers the question: how does the user navigate the site to reach where you want them to go? Poor IA means users get lost — and leave.

Deliverables at this stage:

• Sitemap — all sub-pages and their relationships
• Wireframes for key views (home page, service page, contact)
• Description of user journeys (user flows)

Wireframing is quick — for a standard company site it takes 3–5 days. But skipping it costs weeks of corrections at later stages, because by then changing the content layout means a full redesign.

Stage 3 — UI/UX Graphic Design

Only here do colours, typography, and images come in. Based on the approved wireframes, the designer creates high-quality mockups in Figma (or another tool). The design should cover at minimum:

• The home page in desktop and mobile versions
• A template for an interior page (e.g. a service page)
• A blog article template (if applicable)
• Interactive states: hover, focus, active state

Good UI/UX design is not a matter of taste — it is a matter of conversion. Clear typographic hierarchy, WCAG AA contrast, adequate button size on mobile are elements that directly affect how many people contact you from the site.

Your role as a client: approve the design before moving forward. Every change after coding begins is many times more expensive than a change in Figma.

The stage typically takes one to three weeks, depending on the number of templates and rounds of revisions.

Stage 4 — Coding and Development

Development is the conversion of the graphic design into a working site. Technology paths diverge here: WordPress, bespoke code (e.g. Astro, Next.js), page builders (Webflow, Wix). Each approach has different implications — not only in terms of cost, but also performance and security.

What happens in this phase:

• Setting up the development and staging environment
• Coding HTML/CSS/JS templates
• CMS (content management system) or framework integration
• Connecting forms, analytics, third-party integrations
• Image and asset optimisation for Core Web Vitals

Development is the longest stage. Depending on the complexity of the project it takes two to eight weeks. Ensure you have access to the staging environment — the site before it goes live — so you can monitor progress continuously.

Stage 5 — Testing and QA

Quality Assurance (QA) is the systematic verification that the site works correctly in every scenario. This is a stage that many agencies treat as an afterthought or skip entirely — “we’ll test after launch.” That is a mistake that costs clients reputation and money.

Minimum QA checklist:

• Browser testing: Chrome, Firefox, Safari, Edge
• Mobile device testing: iOS (Safari) and Android (Chrome)
• Form and conversion path verification
• Load speed check (Lighthouse, PageSpeed Insights)
• SSL and redirect verification
• Accessibility testing (WCAG 2.2)
• SEO crawl — are all pages indexable?

QA typically takes 3–7 days. If critical bugs are found — longer, because fixes require re-testing. Ask for a QA report — a tick-list is evidence that the work was done.

Stage 6 — Deployment and Handover

Launch is more than clicking “publish.” A professional deployment includes:

• Migration from the staging server to production
• DNS configuration and propagation verification
• SSL certificate activation
• Google Analytics / Plausible configuration
• Adding the site to Google Search Console
• Creating and submitting sitemap.xml to Google
• Transferring access credentials (CMS, hosting, domain, analytics)

Handover is often neglected. You should receive: complete documentation, access to all systems (on your own account, not the agency’s), source files of the graphic design, and a CMS user guide.

Without these elements you are dependent on the contractor — every minor change requires their involvement and a payment.

How Long Does Each Stage Take? Timeline

The table below shows realistic times for a standard company website (5–15 sub-pages):

Stage	Name	Minimum time	Typical time	Depends on
1	Discovery / Brief	3 days	5–7 days	Client availability, project complexity
2	IA and wireframing	3 days	4–5 days	Number of templates
3	UI/UX design	7 days	10–14 days	Number of revision rounds
4	Development	10 days	14–30 days	Technology, integrations
5	Testing and QA	3 days	5–7 days	Number of bugs, platform
6	Deployment	1 day	2–3 days	DNS configuration, migration
Total		27 days	40–66 days

The realistic delivery time for a company website is 6–10 weeks. Projects that promise a finished site in two weeks typically skip the discovery, wireframing, or testing stages.

What Happens When You Skip Stages — Real Costs

Every skipped stage defers costs — with interest.

Skipping discovery → graphic design does not address business needs → a redesign is required after a week’s work → additional cost: 20–40% of the project budget.

Skipping wireframing → graphic design is revised repeatedly because the content layout is wrong → cost: 2–4 weeks of delay and extra designer hours.

Skipping testing → bugs discovered by users after launch → lost conversions, emergency fix costs, negative first impressions on clients.

No access handover → every site change requires contacting the agency → cost: hundreds of pounds for every minor tweak, for years.

The sum of these costs easily exceeds the original project budget. Saving on stages is an illusion — the costs do not disappear, they only shift in time and grow.

How QA10 Runs the Process (Difference vs a Typical Agency)

Most web agencies work reactively — they receive a brief, create a design, deliver a site. QA10 runs the process differently: we start from an analysis of business objectives, not aesthetics.

What sets our approach apart:

— Every project begins with a discovery session involving the business owner or decision-maker, not just the person responsible for marketing.

— Wireframes are a mandatory stage that requires written approval before work on the graphic design begins.

— We conduct QA testing on real mobile devices, not just a browser emulator.

— We hand over full technical documentation and provide CMS training — your team should be self-sufficient.

— We build sites using Astro — a framework that achieves better Core Web Vitals by default than WordPress. Data from our deployments shows a “Good” rate of 67% vs 38% for WordPress.

— We work in short sprints with status visible to the client at every stage. No black box.

FAQ

How much does it cost to build a website for a small business? Cost depends on project complexity and technology. A simple brochure site (5–7 sub-pages) is in the range of £1,500–4,000. An expanded company site with CMS, blog, and integrations — £4,000–12,000. E-commerce projects and platforms start from £10,000 upwards.

Can I have a site ready in two weeks? Technically yes — but it involves skipping discovery, wireframing, and full QA. Such a site may look good but rarely achieves business objectives. The realistic delivery time for a good company site is 6–10 weeks.

Who should write the website copy — me or the agency? Best approach: you provide the subject matter expertise and key messages, the agency edits and optimises for SEO. Copy written entirely by the agency without knowledge of your business is typically generic and converts poorly.

What is a CMS and do I need one? A CMS (Content Management System) is a panel through which you independently edit content on the site without needing to know how to code. You need it if you plan to update the site regularly — adding articles, changing prices, publishing news. If the site is a brochure without frequent changes — it is not essential.

After launching the site, do I need ongoing maintenance? Yes. A website requires hosting, domain renewal, software updates (especially with WordPress), and security monitoring. Neglecting these leads to downtime, hacks, and SEO penalties. More on this topic in the article on website maintenance costs.

How to Manage the Project as a Client — Practical Tips

Even if you hire an agency and do not want to get into technical details, a few principles will help you avoid the most common pitfalls:

Require a schedule with checkpoints. Before signing the contract, ask for a detailed schedule with delivery dates for each stage and an approval method. A schedule that says “site ready in 6 weeks” is not a schedule — it is a declaration without accountability.

Agree the number of revision rounds upfront. The standard is 2–3 rounds of revisions on the graphic design stage and 1–2 rounds after development. Revisions beyond this scope should be priced separately — and that is normal.

Do not approve the graphic design without checking it on a phone. Even if the Figma mockup looks great on a computer screen, always ask for a preview of the mobile version. This is your right, not an additional service.

Keep access to all systems. Domain, hosting, CMS panel, Google Analytics, Search Console — everything should be registered on your account or company email account. Never on the agency’s account. This is one of the most common mistakes made by companies that change contractors.

Ask for a QA test report. A good agency conducts tests systematically and can show you a list of checked items. If the report does not exist — the tests probably were not done.

Plan a CMS training session. Before the site handover, ask for at least a 60–90 minute session on using the panel. A recorded tutorial video is a bonus that will allow your team to manage content independently.

Summary

The stages of building a website are not bureaucratic invention — they are a proven way to deliver a product that meets business objectives.

Discovery → wireframing → UI/UX design → development → testing → deployment. Six steps that protect your budget and time.

If you are looking for a contractor who will walk you through this process step by step — take a look at our website creation service.

Explore QA10’s website creation service →