A Step‑by‑Step Web Design Process: From Discovery to Launch to More Enquiries

Practical checklist to plan, design and launch a website that generates enquiries: discovery, UX, conversion, SEO, QA and post-launch optimisation and testing.

Step‑by‑Step Web Design Process

Get clear: discovery, goals & scope (aka “stop the ‘one more thing’ spiral”)

If you want a website that brings in enquiries (not just “oo nice site mate”), you need brutal clarity up front: what it needs to do, who it’s for, and what you’re actually willing to spend. Skip this bit and your project will slowly wander off into the woods shouting “can we just add…” until your timeline and budget collapse in a heap.

You don’t need a 40-page strategy deck. A simple discovery output is plenty. Ideally you finish this stage with:

  • a one-page brief (plain English, not corporate poetry)
  • a prioritised scope list (must / should / could)
  • a draft sitemap
  • a short risk log (because reality exists)
  • stakeholder sign-off before anyone opens Figma

For keeping scope sane, use MoSCoW prioritisation. It’s what GOV.UK recommend for discovery work, and it stops the “nice-to-haves” eating the essentials [Source: GOV.UK]. The trick that actually works: slap rough costs against each tier so the budget follows the priorities — not the other way round.

Get the sitemap down early too. It forces navigation decisions while changes are cheap, and it helps you spot SEO gaps before you design yourself into a corner. Nielsen Norman Group explain why sitemaps matter for UX and findability [Source: Nielsen Norman Group].

And yes, keep a risk log. Nothing fancy. Content delays, integrations, approvals, scope creep — the usual suspects. Give each risk an owner so problems don’t just float around the project like bad vibes. Atlassian’s risk register template is a decent starting point [Source: Atlassian].

Once stakeholders sign the brief, tie that approval to your design handover (Figma is perfect for this) so the designer isn’t guessing what matters. If you want a feel for how we run that handoff, see our Figma approach. And if your “must” list doesn’t clearly connect to lead drivers, fix that now — not after launch. Here’s the blunt version: why most business websites don’t generate leads.

Make it usable: UX, structure & journeys (build routes, not mazes)

Good UX isn’t a vibe. It’s making it easy for the right person to do the right thing: call, book, request a quote, or buy. The fastest way there is simple: turn each business goal into one clear user journey, then build the site around that.

Before anyone starts arguing about gradients and animations, do these five practical things:

  • Finalise the sitemap. Map one clear route per goal and keep important actions within two or three taps. If you keep thinking “what else can we add?”, congratulations — you’re building a maze, not a sales tool. [Internal: why most business websites don’t generate leads]
  • Sketch low-fidelity wireframes for key pages. You’re testing hierarchy and flow, not trying to win a design award. Figma is great, pen and paper still counts. [Internal: Figma & our process] · [Source: Nielsen Norman Group]
  • Go mobile-first. People browse on phones. Google indexes the mobile version first, so if mobile is clunky you’re starting with one hand tied behind your back [Source: Google Developers]. Ofcom’s research shows just how welded adults are to smartphones in the UK [Source: Ofcom]. For practical checks, see our fast, mobile-friendly guide.
  • Set unmistakable CTAs and simple forms. Clear verbs. Strong contrast. Short, single-column forms. Complexity kills conversions [Source: HubSpot]. Baymard’s research is a useful reminder of how often users abandon when it starts feeling like effort [Source: Baymard Institute].
  • Test the journey fast. Watch one colleague (or better, a real customer) try to complete the task. You don’t need a huge research programme — five testers typically uncover most usability issues [Source: Nielsen Norman Group].

The point: you’re not designing pages. You’re designing routes. When the route is clear, the site becomes easier to navigate, easier to optimise for SEO, and much easier to convert.

Make it sell: design & content that actually gets enquiries

“Looks good” is lovely. “Gets enquiries” is the job. Conversion-focused design is mostly about clarity: strong hierarchy, one primary action per screen, and copy that answers “what’s in it for me?” in plain English.

Start with your calls to action. Benefit-led beats vague every time. HubSpot’s CTA examples are a decent reference, and Nielsen Norman Group go deeper on CTA button usability [Source: HubSpot], [Source: Nielsen Norman Group].

  • Hierarchy: headline → benefit → single CTA. Keep the CTA visually dominant and close to the supporting copy so users don’t have to go hunting [Source: Nielsen Norman Group].
  • Images: use next-gen formats, responsive srcset, and lazy loading so visuals don’t wreck performance. web.dev has clear guidance on image delivery and Core Web Vitals [Source: web.dev] · [Source: web.dev (Core Web Vitals)].
  • Trust signals: real testimonials, recognisable client logos, and review structured data where it makes sense so search engines can surface ratings [Source: Google Developers].
  • Content first (yes, seriously): don’t launch with placeholder copy or dummy images. It creates a mismatch between design and reality, and it usually means SEO gets shoved to “later”, which often means “never”. Smashing Magazine make the case against lorem ipsum well [Source: Smashing Magazine]. Build high-fidelity templates in Figma with real headings, benefits, and section lengths so content fits the layout — and the layout supports conversion. If you’re using Figma as your source of truth, see how we use it.

Quick next steps that actually move the needle: pick one primary CTA for each key page, replace lorem ipsum with final headings and benefits, compress your images, then run Lighthouse to see what’s slowing the page down. If you’re building on WordPress, this is the practical version: WordPress for small businesses. And if you want the blunt truth on why pretty sites still don’t convert, read this: why sites fail to generate leads.

Make it work: development, SEO & QA (the unsexy stuff that makes it win)

Now you make it real. Build for people first, search engines second — but don’t ignore either. A site can be beautiful and still fail if it’s slow, insecure, hard to crawl, or full of broken forms.

Here’s a launch-ready checklist covering the foundations:

  • CMS & security: keep core, themes and plugins updated, lock down admin access, and use HTTPS. WordPress’s hardening guidance is a solid baseline [Source: WordPress.org]. For the small-business version, see our WordPress guide.
  • Responsive build: mobile-first CSS, test common breakpoints and real devices, and keep build decisions aligned with your Figma prototypes [Internal: Figma designs].
  • On-page SEO & redirects: unique titles and meta descriptions, clean heading structure, schema where it genuinely helps, and a proper 301 redirect map if you’re replacing an old site [Source: Google Search Central].
  • Performance: optimise images (WebP/AVIF), enable caching, and tune for Core Web Vitals (LCP/CLS/INP). Measure with Lighthouse and treat speed as a conversion feature, not a technical detail [Source: Google Web Vitals]. More practical steps here: fast & mobile.
  • Privacy & accessibility: GDPR basics (clear notices and cookie policy) and WCAG AA checks like alt text, keyboard navigation and colour contrast [Source: ICO] · [Source: W3C WCAG].
  • Full QA pass: forms, analytics, redirect map, cross-browser checks, and a staging-to-production checklist. Most “my website doesn’t get leads” problems are tracking gaps, broken CTAs, or clunky forms — all catchable before launch [Internal: lead problems].

Fix issues by impact: lead capture and crawlability first, cosmetic tweaks later. And always have a rollback plan. Small wins here often create the biggest jump in enquiries.

Launch & grow: checklist, monitoring & ongoing optimisation

Launching isn’t the finish line. It’s the start of the bit that actually pays: measurement, iteration, and steady improvement.

  • DNS & SSL: plan the cutover, set short TTLs beforehand, expect propagation delays, and confirm HTTPS (and HSTS, if you’re using it) are working [Source: Cloudflare] · [Source: Google Developers].
  • Final checks: test redirects, robots.txt, canonical tags, and key pages on mobile and desktop. Moz’s launch checklist is a useful prompt list [Source: Moz]. Also run through speed and mobile checks: [Internal: mobile-friendly sites].
  • Indexing & telemetry: submit your sitemap to Search Console and make sure GA4 and Search Console are actually collecting data [Source: Google Developers] · [Source: Google Analytics].
  • Announce and monitor: do the email/social launch, then watch impressions, clicks, crawl errors and 404s daily for the first week, then weekly.
  • Ongoing optimisation: run small CRO tests (forms, CTAs, page structure), track properly, and keep a 90-day plan logging rankings, conversions and errors [Source: CXL] · [Internal: fixing poor lead flow].

Practical next step: document access details, set a reporting rhythm (weekly to start, then monthly), and choose your first two CRO tests based on where people drop off. Want a real-world example of enquiry growth from smarter site decisions? This case-style write-up is worth a look: how Dartford businesses boosted enquiries with smarter websites.

Sources

Auburn Blogs

Welcome to The Auburn Webs blog. Where we share everything and anything about improving your digital footprint!

More Posts

Hey there! I’m Aubie 👋 Need a hand?