How to Hire a Web Designer: A 2026 UK SMB Guide

If you're hiring a web designer right now, you're probably in one of two situations. Your current site feels dated and isn't helping the business, or you don't have a proper site at all and need one that looks credible, works on mobile, and brings in enquiries.

Most small business owners start by searching for someone who can "make a nice website". That sounds sensible, but it's where projects go wrong. A website isn't a paint job. It's closer to fitting out a shop. Layout affects how people move, signage affects what they understand, and small technical mistakes can leave the front door half shut.

The good news is that learning how to hire a web designer doesn't require you to become a designer yourself. You just need a better filter. The right process helps you avoid weak portfolios, vague pricing, poor contracts, and expensive rebuilds later.

Table of Contents

• Preparing for Your Web Design Project - Start with the business outcome - Build a usable project pack - Write down what success looks like

• Where to Find the Right Web Design Talent - Freelance marketplaces - Portfolio platforms - Specialist agencies - A simple way to choose the channel

• How to Evaluate Portfolios and Technical Skills - Use a seven-point portfolio check - Look under the bonnet - What to check for Wix work

• The Interview Process and Insightful Questions to Ask - Start with delivery, not design taste - Test technical judgment in plain English - Ask about pressure, mistakes, and boundaries - A practical scorecard for shortlist interviews

• Decoding Pricing Models Contracts and Project Scope - What pricing model fits your project - UK cost and legal traps - A simple project brief template

• Onboarding Your Designer and Ensuring Long-Term Success - Set the working rhythm early - Think beyond launch day

Preparing for Your Web Design Project

Most bad website projects are damaged before a designer is even hired. The problem usually isn't talent. It's unclear goals, missing content, scattered feedback, and a business owner trying to answer strategic questions halfway through design.

Treat preparation as the foundation, not admin. If you skip it, you'll pay for it in revisions, delays, and a site that looks polished but doesn't move the business forward.

Start with the business outcome

A designer can't make good decisions if your brief is only "I want something modern". Modern is a style preference. It isn't a business objective.

Write down what the site needs to do in practical terms:

• Generate leads: phone calls, contact form submissions, consultation requests, quote requests.

• Support sales: product purchases, basket completion, fewer drop-offs.

• Build trust: stronger first impression, clearer service pages, better proof.

• Reduce friction: fewer repetitive questions, easier booking, cleaner navigation.

• Help marketing: pages built to support SEO, email capture, paid traffic landing pages.

That clarity affects everything. Navigation, homepage structure, call-to-action placement, page count, and copy all flow from the outcome.

Practical rule: If you can't explain what the website is supposed to change in the business, no designer can scope it properly.

Build a usable project pack

Designers work faster and better when the client is organised. That doesn't mean producing a glossy brand manual. It means gathering the materials they need.

Your project pack should include:

• Brand assets: logo files, fonts, brand colours, usage notes.

• Existing content: service descriptions, about copy, FAQs, testimonials, pricing notes.

• Imagery: team photos, product images, workplace shots, brand photography.

• Competitor references: not to copy, but to show market expectations.

• Website examples you like: useful for tone and structure, not just visual taste.

If you need help shaping the brief itself, this clear actionable guide to writing a website brief is a practical starting point.

For business owners who also want to understand how web design and search visibility fit together, this overview of F1Group web design and SEO is useful because it frames the site as both a design and marketing asset.

Write down what success looks like

This doesn't need to be complicated. It needs to be explicit.

A short checklist works well:

Area	What to define before hiring
Audience	Who the site is for, what they care about, what makes them hesitate
Offer	Your main services or products and the order they should appear
Primary action	Call, book, buy, enquire, download, subscribe
Must-have pages	Home, about, services, contact, shop, booking, case studies
Nice-to-haves	Blog, resource hub, gated downloads, members area
Decision makers	Who gives feedback and who has final approval

One more point matters. Decide who inside your business will respond to content questions, image requests, and design approvals. When three people give conflicting feedback, the project slows and the quality drops.

Good clients don't need all the answers. They need enough structure for the designer to solve the right problem.

Where to Find the Right Web Design Talent

A common small-business mistake in London goes like this. You post a quick job, get 25 replies by tomorrow, pick the cheapest decent-looking option, and only later realise the person has never built a Wix booking flow, cannot explain handover, and works in a way that creates headaches for a UK client.

Where you look affects what kind of risk you take on.

The US Bureau of Labor Statistics expects continued growth in web development and digital design roles, with 7 percent growth from 2024 to 2034 and around 14,500 openings a year on average (BLS occupational outlook). That does not tell you what a London small business should pay, but it does explain why experienced designers with clear process rarely compete on bargain pricing.

Freelance marketplaces

Freelance platforms are fast. You can post a brief, collect proposals, and get a rough sense of pricing within a day or two.

That speed comes with admin. You have to sort through templated pitches, inflated review scores, and portfolios that may not reflect who will do the work. For a UK business, there is another layer. Contractor status, statements of work, and handover terms matter more than many first-time buyers expect. IR35 will not apply to every small web design engagement, but it is still sensible to structure the relationship clearly and avoid casual arrangements that blur freelancer and employee status.

I have seen this play out many times. The cheap quote looks fine until content delays trigger extra fees, revisions drag on because nothing was defined properly, and the designer disappears once the site is live.

Freelance marketplaces suit owners who can manage tightly, write a sharp brief, and spot weak process before paying a deposit.

Portfolio platforms

Behance and Dribbble are useful for finding visual style. They help you answer a narrow question. Do I like how this person thinks on the page?

They do not tell you much about delivery. A polished homepage mock-up says very little about page speed, mobile behaviour, Wix editor competence, accessibility, or whether the designer can build a service site that your staff can update without calling for help every month.

Use these platforms as a shortlist tool. Save work you like, then leave the platform and inspect the designer's own website, live client URLs, and service pages. If someone only shows static shots and cannot point to real projects, treat that as a warning. If you're also building in-house confidence around digital projects, these online education platforms for UK learners can help a team member get more comfortable assessing briefs, design terminology, and platform basics.

Portfolio sites help with taste. Due diligence starts after you click away.

Specialist agencies

Agencies usually cost more than a solo freelancer. In return, you are paying for structure, not just design hours.

For many London SMBs, that trade-off is sensible. Website projects often go wrong in the middle of the job, not at the first concept stage. Copy arrives late. Feedback comes from four people with different opinions. SEO is assumed rather than specified. Nobody is sure what happens after launch. A good agency reduces that friction because process, sign-off points, and responsibilities are defined earlier.

Platform depth matters too. If you want a Wix site, ask whether the team has real Wix experience, not just general web design experience. Wix can be a strong fit for a small business, but only in the right hands. A designer needs to know when a template is enough, when a custom layout is justified, how Wix apps affect performance, and what should be handled inside Wix versus through external tools.

One option some London businesses consider is Baslon Digital, which focuses on Wix websites for small businesses and individuals. If you are comparing agency models more broadly, this guide on how to choose a web design agency gives a practical framework for comparing fit, process, and support.

A simple way to choose the channel

Use this quick filter:

If you need...	Better route
Lower upfront cost and you're comfortable managing the project closely	Freelance marketplace
Visual inspiration before contacting anyone	Portfolio platform
Strategy, process, support, and clearer accountability	Specialist agency

The right option depends on how much uncertainty your business can afford. If a delayed launch, weak handover, or poor Wix build would cost you leads, time, or credibility, paying more for stronger process is often the cheaper decision in the end.

How to Evaluate Portfolios and Technical Skills

A good-looking portfolio can still hide poor structure, weak SEO, and sloppy build quality. That's why surface-level review isn't enough. You need to inspect live work, not just static images.

A rigorous 7-step portfolio evaluation methodology can produce a 42% higher project success rate, and the same guidance highlights checks like public portfolio availability, SEMrush-based review of canonical tags and schema markup, and mobile optimisation against Core Web Vitals. It also notes that Core Web Vitals compliance is required for 75% of top UK Google rankings (SquareRoot guide to hiring website designers).

Use a seven-point portfolio check

When reviewing any designer, go through these seven checks.

1. Check that the work is public and live Ask for live URLs, not only PDF mock-ups or cropped screenshots. A real site lets you inspect navigation, responsiveness, calls to action, and technical details.

2. Look for relevant project type A designer may be talented and still wrong for your job. A restaurant site, a personal brand site, and a service-led B2B site solve different problems.

3. Test mobile properly Open the site on your phone. Then use Chrome DevTools on desktop to check different screen widths. Menus, headings, forms, and buttons should remain usable without awkward spacing or broken layouts.

4. Review user flow Ask yourself one blunt question. Can a first-time visitor understand what the business does and what to do next? Clear hierarchy beats visual flair every time.

5. Inspect polish Read the pages. Look for typos, inconsistent spacing, stretched images, odd hover states, or clumsy button labels. Small mistakes are often signs of rushed QA.

6. Check performance and technical basics A designer doesn't need to be a deep technical SEO consultant, but they should build clean, indexable pages and understand the basics of speed and structure.

7. Ask them to explain decisions A strong designer can tell you why they used a layout, a call-to-action pattern, or a page structure. If they can only talk about colours and trends, that's a warning sign.

If you want examples of what stronger portfolio presentation looks like, these good portfolio website examples and builders are worth reviewing.

Look under the bonnet

A portfolio review gets serious when you stop asking "Does this look nice?" and start asking "Does this work well?"

Use a simple live-site checklist:

• Navigation: Can you reach key pages quickly?

• Calls to action: Is the next step obvious?

• Forms: Do they feel short, clear, and easy to complete?

• Page speed: Does the page load promptly on mobile data?

• SEO basics: Are page titles sensible? Are URLs clean? Is there visible structure?

• Credibility: Are testimonials, trust signals, or proof elements present where needed?

SEMrush can help you inspect some technical signals on a domain, especially if you want a quick view of site health and visibility patterns. You don't need to become an SEO auditor, but you do want to spot obvious neglect.

A pretty homepage can hide weak foundations. If the live site is slow, confusing, or technically careless, the design hasn't done its job.

What to check for Wix work

Wix is often underestimated. In the right hands, it's a practical platform for many small businesses. In the wrong hands, it turns into a stack of overlapping elements, bloated pages, and awkward mobile behaviour.

When hiring for Wix, ask specifically about:

Area	What a capable Wix designer should discuss
Responsive setup	How they handle breakpoints and mobile layout review
Custom features	Whether they use Velo when standard components aren't enough
CMS and collections	How they manage repeatable content such as services, blog posts, or team profiles
SEO settings	Control of titles, descriptions, indexing, redirects, schema-related setup where relevant
Client handover	How they make routine edits manageable for non-technical owners

A strong Wix designer also knows when not to overbuild. Many weak projects suffer because the designer tries to force complex interactions into places where a simpler solution would be easier to maintain.

When a candidate presents results, ask to see what changed and how they verified it. Good designers don't get defensive about that. They welcome the question.

The Interview Process and Insightful Questions to Ask

A short interview can save you from a long, expensive mess.

I have seen plenty of small UK businesses in London hire a designer on the strength of a polished portfolio, only to find out two weeks later that replies are slow, feedback gets lost, and nobody agreed who was writing the copy or approving the pages. The interview is your chance to test how the person works before money changes hands. For a small business, that matters as much as the visual style.

Treat the conversation like a project rehearsal. You are not trying to catch them out. You are checking whether they can run a smooth job with your team, your timeline, and your platform. If the site is being built on Wix, ask Wix questions. If you are hiring a freelancer rather than an agency, ask who handles revisions, SEO setup, and post-launch fixes. In the UK, also be clear on working arrangements early if the role starts to look like ongoing contracted work. That can have IR35 implications if the relationship begins to resemble employment.

Start with delivery, not design taste

Good interviews begin with process. A designer can have a strong eye and still be painful to work with if they cannot plan, gather requirements, or manage approvals.

Ask questions like these:

• How do you run discovery at the start of a project?

• What do you need from us before design starts?

• Who usually supplies the content, and what happens if it's late?

• How do you structure revisions and sign-off?

• How do you decide page hierarchy, calls to action, and user flow?

• If we're a London small business with limited internal time, what do you do to keep the project moving?

Useful answers are concrete. They should mention a brief, sitemap, content plan, timeline, review stages, and who signs off what. If they talk as if every project is improvised, expect delays and rework.

One practical question I like is: What usually causes web projects to drift, and how do you prevent that? Experienced designers rarely blame bad luck. They talk about missing content, too many decision-makers, slow feedback, and fuzzy scope.

Test technical judgment in plain English

You do not need to interview them like a developer. You do need enough to tell the difference between someone who can build a business tool and someone who can only make a mock-up look nice.

Use questions that reveal how they think:

• What do you do to keep page speed under control on mobile?

• How do you handle redirects during a redesign?

• Which SEO settings do you usually check before launch?

• If you're building on Wix, when would you use Velo, and when would you avoid it?

• How do you build a Wix site so a small business owner can update it without breaking the layout?

The best answers are clear, specific, and calm. A capable designer can explain speed, indexing, redirects, CMS collections, and mobile layout choices without hiding behind jargon.

That matters with Wix in particular. Plenty of freelancers say they "work with Wix" when what they mean is they can drag blocks onto a page. A real Wix specialist should be able to explain breakpoints, collections, repeatable content, app limitations, and when custom code creates future maintenance problems.

Ask about pressure, mistakes, and boundaries

Projects rarely fail because the homepage draft was slightly off. They fail because communication broke down, the brief changed halfway through, or no one wanted to own a difficult decision.

Ask this directly: Tell me about a project that went off-track and how you handled it.

Listen for four things:

• Ownership. They can explain their part in the problem.

• Communication. They kept the client informed rather than going quiet.

• Decision-making. They proposed options instead of waiting passively.

• Learning. They changed their process afterwards.

Then ask: What would you need from us to make this project run well?

Strong candidates usually mention one point of contact, timely feedback, realistic deadlines, and clarity on content. That answer tells you they understand delivery, not just design.

A useful UK-specific follow-up is: Do you work as a freelancer, limited company, or through an agency, and who is responsible for the work day to day? That helps you understand accountability. It also helps if you are comparing quotes from a solo freelancer in Manchester, a London studio, and an overseas contractor using UK-friendly language on their site.

A practical scorecard for shortlist interviews

Do not rely on gut feel alone. Keep a simple scorecard and fill it in straight after each call while the details are fresh.

Category	What to look for
Process	Clear stages, deadlines, approvals, and handover steps
Technical judgment	Sensible answers on speed, redirects, SEO, and platform limits
Wix capability	Knows CMS collections, mobile behaviour, editor limitations, and when custom code is worth it
Communication	Listens well, answers directly, asks smart questions, explains trade-offs clearly
Commercial fit	Scope, revisions, support, and responsibilities are easy to understand
UK practicalities	Can work in your time zone, invoices properly, and is clear on freelancer or agency setup

That last row gets overlooked. It should not. A cheaper quote can stop looking cheap once you factor in VAT, delayed communication, unclear support, or a contractor setup that causes admin headaches.

A strong interview feels like the start of a working relationship. You should come away with clearer expectations, a better sense of risk, and confidence that the designer can build something your business can use.

Decoding Pricing Models Contracts and Project Scope

A small business owner gets three quotes for a Wix site. One comes in at £1,200, one at £3,800, and one at £6,500. All three say "five-page website". On paper, they look comparable. In practice, they may be pricing three completely different jobs.

That is why the headline price is only the starting point. The key question is what you are buying, what has been left out, and who carries the risk if the brief changes halfway through.

What pricing model fits your project

Most web design work for UK small businesses falls into three models. None is universally right. Each shifts cost certainty and project risk in a different direction.

Hourly pricing

Hourly pricing suits smaller jobs, unclear scopes, and work that is easier to do in phases. That might mean tidying up a Wix site, building a landing page, fixing layout issues on mobile, or adding a booking tool after launch.

The upside is flexibility. The downside is that a vague brief can turn into a long invoice. If you agree to hourly, set a cap, ask for a task list, and require approval before any extra hours are spent.

For a London business hiring a freelancer, this matters even more. Local rates can vary sharply by experience, and the same "small job" can run very differently depending on whether the designer is correcting existing problems or starting from clean foundations.

Fixed project pricing

Fixed pricing is usually the cleaner option for a new brochure site, a standard Wix build, or a redesign with known pages and features. It gives you a clearer budget and forces both sides to define the work before the build starts.

It only works well when the scope is specific. "A modern website for our business" is not a scope. "Six pages, Wix CMS for case studies, one enquiry form, mobile optimisation, basic SEO settings, and redirects from the old site" is a scope.

I generally see fixed pricing work best for owner-managed businesses because it reduces surprise. It also exposes weak proposals quickly. If a quote is fixed but the deliverables are fuzzy, expect friction later.

Retainer pricing

A retainer is usually better after launch than before it. It suits businesses that need regular updates, campaign landing pages, ongoing design input, or someone to keep the site current without raising a new quote every month.

It is less useful as the main buying model for your first website unless the project is planned for staged releases. Otherwise, a retainer can blur what is included and what is still being decided.

UK cost and legal traps

The most expensive quote is not always overpriced. The cheapest quote is often missing work.

I have seen low-cost proposals exclude copy formatting, mobile tidy-up, redirects, image sourcing, cookie banner setup, analytics, training, and post-launch fixes. Once those items are added back in, the "cheap" option stops being cheap.

For a London-based SMB, compare quotes line by line. Check whether VAT is included. Check whether hosting, domain work, stock imagery, and app subscriptions are extra. Check whether content entry is included or whether you are expected to upload everything yourself.

Wix projects need another layer of scrutiny. Some designers can produce a nice homepage mockup but struggle with the practical parts that affect day-to-day use. If your site needs CMS collections, dynamic pages, booking flows, member areas, or custom forms, make sure those items appear in the scope and not just in a sales call.

There is also the contractor point. If you are hiring a freelancer directly in the UK, especially for a longer engagement or one that starts to resemble an embedded role, ask for clarity on their trading setup, invoicing, VAT status, and whether IR35 is relevant to the arrangement. Many small businesses skip this because it feels like admin. It becomes a problem later if the relationship was documented badly from the start.

Commercial warning: A low quote can win approval fast and still cost more once revisions, delays, and omitted tasks start stacking up.

A contract should spell out the job in plain English. If a designer needs to "clarify later" what basic deliverables include, the contract is too loose.

Cover these points:

• Scope of work: pages, features, integrations, forms, blog, shop, booking tools, migration work

• Deliverables: sitemap, wireframes if included, design concepts, final build, mobile setup, launch support

• Platform details: Wix Editor or Wix Studio, CMS setup, app configuration, custom code if any

• Timeline: start date, milestone dates, review windows, launch target, what pauses the timeline

• Revisions: number of rounds, what counts as a revision, and what becomes extra work

• Content responsibilities: who writes copy, who supplies images, who uploads products, posts, or case studies

• Payment schedule: deposit, stage payments, final invoice, late payment terms

• Ownership and access: admin access, transfer of accounts, ownership of content and design assets

• Post-launch support: bug-fix period, training session, maintenance options, response times

• Legal and tax points: VAT treatment, invoicing terms, contractor status, IR35 position where relevant

A short explainer can also help if you're reviewing common contract and scope issues before signing.

https://www.youtube.com/watch?v=ZLn2GX476Lg

A simple project brief template

A good brief saves money because it removes guesswork. It also makes quotes easier to compare, which is half the battle.

Use this structure:

Brief item	What to include
Business overview	What you do, who you serve, where you operate
Primary goal	Leads, bookings, enquiries, sales, credibility
Target audience	Ideal customer, objections, priorities
Website pages	Core pages required at launch
Key functionality	Forms, bookings, payments, CMS, blog, memberships
Brand inputs	Logo, colours, tone, existing guidelines
Content status	Ready, partly ready, needs support
Examples	Sites you like and why
Technical needs	SEO setup, redirects, analytics, integrations
Approval process	Who signs off and how feedback is collected

If you want a simple rule, use this one. If a feature matters to the business, put it in writing. Do not assume "basic SEO", "mobile-friendly", or "training" means the same thing to every designer.

Clear scope produces cleaner quotes, fewer arguments, and a site that matches what you thought you were buying.

Onboarding Your Designer and Ensuring Long-Term Success

Signing the contract doesn't create momentum on its own. Good onboarding does. This is the point where a promising hire either becomes a productive partnership or slides into missed emails, delayed content, and fuzzy accountability.

The strongest working relationships are usually built with professionals who treat their service like a real business. That's one reason training and business maturity matter. Survey data from 771 web designers shows that designers who invest more in professional development are more likely to command higher fees, and over 65% of those who enrolled in formal online courses or coaching programmes operate full-time businesses, compared with about 61% of self-taught designers who hadn't yet reached that milestone (Paige Brunton salary and pricing survey).

Set the working rhythm early

Your kickoff should answer four practical questions:

• Who communicates with whom

• Where feedback lives

• How quickly each side replies

• What can delay the project

Email is fine if it's organised. Shared docs are fine if one person consolidates comments. The exact tool matters less than consistency.

A healthy kickoff also settles file access, content deadlines, and review windows. If feedback drips in from different people over several days, the build slows and the designer starts redesigning by committee.

Good onboarding protects both sides. It helps the client stay informed and helps the designer keep the project moving.

Think beyond launch day

A website launch is not the end of the work. It's the point where the website starts doing its real job in public.

Before launch, clarify:

• Who handles routine content edits

• Who monitors forms and lead notifications

• Who updates software or connected tools where relevant

• Who checks for broken pages, outdated offers, or old team details

• What support looks like if something needs changing next month

Many small businesses often get caught out. They buy the build but not the operating model. Then nobody owns updates, the site gets stale, and the investment loses value.

The best outcomes usually come from treating the designer as a partner for a period after launch, not just a supplier of files. That doesn't always mean a long retainer. It means having a defined support path and a shared expectation about what happens next.

If you want a team that can help scope, design, and support a Wix site for your business, Baslon Digital offers consultations around project scope, budget, and timelines so you can decide whether the fit is right before committing.