Introduction: Why Most Website Projects Go Wrong

After 25 years of building websites for businesses of every size, I can tell you with absolute certainty that the number one reason website projects fail has nothing to do with design or code. It’s misaligned expectations.

The business owner pictures one thing. The agency builds another. Six months and tens of thousands of pounds later, nobody’s happy. The website technically works, but it doesn’t perform. It doesn’t generate leads. It doesn’t communicate what the business actually does. And the whole process felt like pulling teeth.

This guide exists to prevent that. Whether you’re commissioning your first website or redesigning one that’s underperforming, understanding how the process actually works (and what your role is at each stage) is the single most important thing you can do to protect your investment.

A website is not a brochure. It’s a business tool. Every decision should be measured against one question: does this help us achieve our commercial objectives?

Phase 1: Discovery and Strategy

This is where the real work happens, and it’s the phase most business owners want to skip. Don’t. Every hour spent in discovery saves ten hours in revisions later.

What Happens in Discovery

A good agency will spend time understanding your business before touching a single pixel. This isn’t a formality. It’s the foundation everything else is built on.

• Business objectives: What does success look like in 6 months? 12 months? Revenue targets, lead volume, market positioning.
• Audience profiling: Who are your actual customers? Not demographics on paper, but real behaviour patterns, pain points, and decision-making triggers.
• Competitive analysis: What are your competitors doing online? Where are they strong? Where are the gaps you can exploit?
• Content audit: What existing content do you have? What needs to be written from scratch? Content is the single biggest bottleneck in web projects.
• Technical requirements: Integrations, CRM connections, booking systems, e-commerce, membership areas. Surface these early or pay for them later.

What You Should Prepare

Come to the discovery phase with clarity on these five things:

1. Your top 3 business objectives for the website (not design preferences, business outcomes)
2. A list of 5 to 10 websites you admire and, critically, why you admire them
3. Access to your analytics (Google Analytics, Search Console, any CRM data)
4. Brand assets: logo files, brand guidelines, photography, approved copy
5. A realistic budget range and timeline. Agencies need this to scope properly. Withholding budget doesn’t get you a better price. It gets you a mismatched proposal.

The discovery phase typically takes 1 to 2 weeks for a standard business website and 3 to 4 weeks for complex web applications or e-commerce builds.

Phase 2: Information Architecture and Wireframing

Before anyone designs what the site looks like, they need to design how it works. Information architecture (IA) is the structural blueprint of your website. It defines what pages exist, how they’re connected, and how users flow through them.

Sitemap

A sitemap is a visual hierarchy of every page on your website. It shows the relationship between pages and helps you see whether your navigation makes sense before a single wireframe is drawn.

Common mistake: business owners want to organise the site by internal department (About Us > Our Team > Our History > Our Values). Users don’t care about your org chart. They care about solving their problem. Organise by user need, not company structure.

Wireframes

Wireframes are low-fidelity layouts that show the placement and priority of content on each page. They look like grey boxes with placeholder text. This is intentional. The goal is to nail the structure without getting distracted by colours and fonts.

Your feedback at this stage should focus entirely on:

• Is the right content in the right place?
• Does the page hierarchy match what our users need?
• Are the calls to action prominent enough?
• Is anything missing that our audience would expect?

Do not give visual design feedback on wireframes. “The button should be green” is not wireframe feedback. “The call to action should come before the testimonials” is.

Phase 3: Visual Design

This is usually the stage business owners get most excited about, and most opinionated about. Both are fine. But understand what’s being decided here and what isn’t.

Design Concepts

Most agencies present 2 to 3 design concepts based on the agreed wireframes. These are full-colour, high-fidelity mockups of key pages (usually the homepage and one interior page). They establish:

• Typography: The fonts used for headings, body text, and interface elements
• Colour palette: Primary, secondary, and accent colours applied to real content
• Visual tone: Photography style, iconography, spacing, and overall personality
• Component design: How buttons, forms, cards, and navigation elements look

How to Give Useful Design Feedback

The single most destructive sentence in web design is “I’ll know it when I see it.” Here’s how to give feedback that actually moves the project forward:

1. Reference the objectives, not your personal taste. “Our audience is corporate CFOs, does this feel premium enough?” is infinitely better than “I don’t like it.”
2. Be specific about what’s not working. “The hero section feels cluttered” gives the designer something to work with. “It needs more pop” does not.
3. Consolidate feedback. Contradictory feedback from five stakeholders kills projects. One person owns the final sign-off.
4. Trust the process. Design decisions are informed by user research and conversion best practices. If your designer pushes back on something, listen to why before overruling.

Phase 4: Development and Build

Once the design is approved, development begins. This is where the visual mockups become a functional website. For most business owners, this phase is largely invisible, but understanding what’s happening under the hood helps you ask better questions.

Frontend vs Backend

Frontend development is everything users see and interact with: the layout, animations, responsive behaviour, and interactive elements. Backend development is everything behind the scenes: the content management system, database, server configuration, forms, integrations, and security.

A well-built website should:

• Load in under 2 seconds on a standard connection
• Score 90+ on Google’s Lighthouse performance test
• Work flawlessly on mobile, tablet, and desktop
• Be editable by non-technical staff without breaking the layout
• Be secure, backed up, and monitored

Content Entry

This is where projects stall. The design is done, the development is done, and the agency is waiting for content. Written copy, professional photography, team bios, case studies. If these aren’t ready when development finishes, your launch date slips.

Start writing content during the design phase, not after. Assign one person in your team as the content owner. If you don’t have the capacity, hire a copywriter. Your agency should be able to recommend one or provide this service.

Phase 5: Testing and Launch

Quality Assurance

Before launch, every page should be tested across browsers (Chrome, Safari, Firefox, Edge), devices (iPhone, Android, iPad, desktop), and screen sizes. Forms should be submitted and confirmed. Links should be clicked. Load times should be measured. Accessibility should be checked.

Ask your agency for a QA checklist and sign off on it before going live.

Launch Day

A good agency handles the technical launch: DNS propagation, SSL certificates, redirects from old URLs, analytics setup, and search engine indexing. You should have a launch plan that includes:

1. Social media announcement
2. Email to your customer base
3. Google Business Profile update with the new URL
4. Internal team briefing so everyone knows the new site is live

Phase 6: Post-Launch Optimisation

Your website is not finished the day it launches. It’s just starting. The best-performing websites are the ones that iterate based on real data.

In the first 30 days after launch, monitor:

• Traffic patterns: Where are users coming from? Which pages are they landing on?
• Conversion rates: Are visitors contacting you, buying, or bouncing?
• Page speed: Real-world performance with actual traffic load
• Search rankings: Are you maintaining or improving your positions?

Schedule a 30-day review with your agency. Discuss what’s working, what’s not, and what to optimise next. Then repeat quarterly.

The companies that treat their website as a living product (not a one-time project) consistently outperform those that launch and forget.

How to Choose the Right Agency

Finally, here’s what to look for when selecting a web design partner:

• Portfolio relevance: Have they built sites for businesses like yours? Do those sites actually perform, or just look pretty?
• Process clarity: Can they walk you through their process before you sign anything? If it’s vague, walk away.
• Technical depth: Do they have in-house developers, or do they outsource? You want the people who design your site to be the same people who build it.
• Communication: How do they manage projects? Weekly updates? A project management tool? If the answer is “we’ll email you,” that’s a red flag.
• Post-launch support: What happens after the site goes live? Maintenance, hosting, ongoing optimisation should be discussed upfront, not as an afterthought.