How to Choose a Web Designer in the UK

How to Choose a Web Designer in the UK (And Avoid Costly Mistakes)

You’ve decided it’s time to get a website for your business. Perhaps you’ve recently started working for yourself. Maybe you’ve been running your business for years, relying on recommendations and word of mouth, and now you want move your business online.

You start looking for someone to build your website. One developer quotes £400. Another wants £2,500. Then you find a company offering a website for free. All three promise a professional result.

So what’s the difference?

If you’ve never purchased a website before, how are you supposed to know whether £400 is a bargain, £2,500 is reasonable, or the free option will eventually cost you more? And you probably don’t know much about hosting, domain registration, not to mention programming languages or search engine optimisation. And why should you? You’ve got your own business to run.

The problem is that choosing a web designer involves more than looking at a few examples and comparing prices its not a choice of noodles vs noodles. You’re trusting someone to build something that will represent your business, potentially for years.

Get it right, and you’ll have a website that customers can use, that explains your services properly and that you can improve as your business develops.

Get it wrong, and you might find yourself paying for something that doesn’t meet your expectations, dealing with unexpected charges or struggling to get access to your own website.

I’ve put this guide together to explain what I’d look for when hiring a web designer in the UK, what I’d ask before paying anything and which situations would make me think twice. You don’t need to become a developer to make a sensible decision. You need however, to understand a few things that aren’t always explained when someone is trying to sell you a website.

A Good-Looking Website Isn’t Necessarily a Good Business Website

Imagine you’re looking for an emergency plumber. There’s water coming through the ceiling, you’ve got a bucket on the floor and you’re trying to find someone who can get there quickly. Brief Google search reveal the first website - There’s a beautiful animation, a video playing in the background and some impressive graphics. Endlessely scroling down, for a phone number.

Nothing that you are able to spot in an emergency situation!

That’s why I think people sometimes misunderstand what web design is supposed to achieve. There’s nothing wrong with animations, videos or creative design. I enjoy building those things myself.

But does it serve a purpose?

Beautiful website doesn’t necessarily mean a good business website. Web designer should understand who your customers are, what they’re looking for and what you want them to do when they visit. Different businesses got their own sets of priorities.

Good developer should be asking questions. Who are your customers? Where do they come from? What services are most important to you? Do you already have customers finding you through Google? What problems are you trying to solve?

Sometimes, they should simply disagree with you and explain how those decisions might affect the people using your website. You can still make the final decision. It’s your business. But you’re paying for someone’s knowledge and judgement.

Five Mistakes I’d Avoid When Hiring a Web Designer

Most website projects don’t go wrong because someone deliberately sets out to deceive a customer, sometimes the developer is inexperienced. Customer expects something that was never included. Sometimes both sides assume the other understands what’s been agreed. And occasionally, yes, someone is simply more interested in collecting payments than delivering what they promised. Whatever the reason, there are a few mistakes that can make an otherwise straightforward project unnecessarily expensive.

1. Choosing Someone Because They’re the Cheapest

If you’re running a small business, spending £2,000 or £3,000 on a website isn’t a decision you make casually. Comparing website quotations isn’t quite like comparing the price of the same television in two different shops. Developers might offer a five-page website, but that doesn’t mean you’re buying the same thing.

One might use a ready-made template, replace the photographs, add your business details and have everything online within hours. Another might spend time understanding your business, planning the structure, designing the pages individually, writing or improving content, developing the website and testing everything before launch.

The question is whether the work being offered is suitable for your business and whether you understand what you’re paying for. Also, don’t assume that a £3,000 quotation automatically means better work than a £700 quotation. - It doesn’t.

I’ve seen impressive websites built with relatively simple technology, and expensive websites that are unnecessarily complicated. What I’d want to know is exactly what each developer intends to deliver. There’s also the question of ongoing costs. Website advertised as free might come with a monthly hosting and maintenance subscription. Other might cost £2,000 upfront, followed by separate charges for hosting, updates and additional services. - You need to look beyond the initial price.

2. Not Agreeing on Exactly What’s Being Built

You agree on a price, work begins, and halfway through you discover that the quotation doesn’t include the flooring. Then you find out the electrical work is extra as well as the decorating. May be wonder why nobody explained that at the beginning - web development can create exactly the same problem.

You might assume that your quotation includes writing the website content, sourcing photographs, setting up business email addresses and making changes until you’re completely happy. The developer might have priced five pages, one contact form and two rounds of revisions.

• Before agreeing to anything, ask for a clear description of the project.

How many pages are included? Who provides the text and photographs? Are contact forms included? What about booking systems or other functionality? How many revisions can you request and what happens if you change your mind halfway through? There’s a big difference between changing a heading and deciding that your simple business website now needs an online booking system.

Additional work costs time, and time costs money.

3. Not Knowing Who Controls Your Domain and Hosting

Your domain name is your website address, your hosting on the other hand is the service that makes the website available online. The website itself consists of files, content and potentially software that runs on that hosting.

They’re different things, even though they’re often sold together.

Let’s say you hire a developer who offers to take care of everything. They register your domain, arrange hosting, build the website and manage it for you. That can be convenient, particularly if you don’t want to deal with the technical side - what happens if you decide to move to another provider?

• Do you have access to your domain registrar account?
• Is the domain registered in your business’s name?
• Can you move the website elsewhere?
• Will you receive the files needed to do that?

These aren’t questions you should leave until you’re trying to end the agreement. For a UK domain, you can find information about registration and management through Nominet. My advice would be for a business owner to register their domain in their own name and maintain control of the account.

A developer can still configure everything and manage the technical side. No need to know how DNS records work. Just need to know that you can regain control when necessary.

4. Only Thinking About What You Need Today

Perhaps you only need a homepage, a services page and a contact form - that’s fine. In fact, I’d argue that many small businesses spend money on features they don’t need. It’s worth thinking about what might happen over the next few years.

• What if you introduce another service?
• What if you want customers to book appointments online?
• What if you open another location or decide to sell products?
• Will your website allow those changes without starting again?

The answer depends on how it’s built.

Some platforms are more flexible than others. Some changes are straightforward, while others require considerable development. There’s no point paying for an enormous system today because you might need it in five years. There is a difference between keeping things simple and building something that unnecessarily limits your options.

This is something I pay attention to when developing websites at Client Flow Now.

I prefer to understand where a business is heading before deciding how its website should be structured. It doesn’t mean every website needs custom software or a complicated technical setup - quite the opposite.

5. Thinking That Having a Website Means Customers Will Find You

This deserves some special attention because there’s a lot of confusion around it. First you pay someone to build a website - they finish it, put it online and tell you everything is ready. Week later, you search Google for your services and website is nowhere to be seen.

You might start wondering: “Did the developer has done something wrong?”

Building a website and getting people to visit it are two different jobs. Developer should understand the technical foundations that help search engines access and understand your website. That includes things such as appropriate HTML structure, page titles, descriptions, mobile usability, performance and ensuring that relevant pages can be indexed.

SEO is a completely different services and it’s takes time.

Keyword research, content development, understanding competitors, local search optimisation and monitoring performance all take additional work. Even a technically excellent website isn’t guaranteed to rank highly. If someone promises that your new website will automatically appear at the top of Google, I’d ask them to explain exactly how they intend to achieve that.

At CFN, I consider technical SEO during development because fixing fundamental problems later can be more difficult and expensive, but I wouldn’t tell a client that simply launching a website guarantees traffic or enquiries - It doesn’t.

Should You Hire a Freelancer, an Agency or Someone Overseas?

This is where choosing a developer becomes interesting, you might find a local freelancer offering to build your website for £800 vs UK agency quotes £3,000. Then you find an overseas developer offering something similar for £350. Which one should you choose - website is a website right?

Working With a Freelancer

One advantage of working with a freelancer is that you often communicate directly with the person doing the work. There’s no need to explain your requirements to a salesperson, who passes them to a project manager, who then passes them to a developer - for some projects, that can work extremely well.

Of course, freelancers have limitations too - one person cannot be an expert in absolutely everything, and they can’t always be available. I’d ask how they handle support, holidays and situations where a project requires skills outside their usual work. Good freelancer should be comfortable explaining what they can do and when another specialist might be needed.

Working With an Agency

An agency may have several people involved in a project, designers, developers, copywriters, SEO specialists, salespeople and project managers. For a larger business or a complicated website, that can be useful. Don’t assume however, that hiring an agency automatically means receiving better work.

I’d want to know who’s actually responsible for the project. Who will I communicate with, who makes technical decisions and who do I speak to if something goes wrong?

Working With Overseas Developers

The first is communication - I don’t just mean whether someone speaks good English. I would consider whether they understand what you’re trying to achieve. Can they explain their recommendations? Do they ask questions? Will they tell you when something isn’t a good idea? If every suggestion receives an immediate yes, no problem, I’d want to understand whether the developer has actually considered the implications.

Your customers may expect certain information, such as service areas, qualifications, contact details or evidence of previous work. Depending on the website, UK requirements concerning privacy, accessibility and business information may also apply.

Then there’s the time difference - If you need to discuss something urgently, will you be able to reach the developer during your working day? Finally, there’s the contract - hopefully. Who are you actually paying is the business registered? What happens if there’s a dispute, which law applies to your agreement? These questions are relevant when hiring anyone, but resolving a disagreement across different jurisdictions can be more complicated - most likely you will give up.

Working with a UK-based provider can make some of these arrangements more straightforward.

What Happens If Your Web Designer Suddenly Disappears?

Imagine you’ve had your website for eighteen months, everything has been working, customers use it to find your business, send enquiries and perhaps book appointments - life is good.

Then one day, the website stops loading, you contact your developer - No reply. You send follow up email - Nothing. You try calling - still nothing. Now you need someone else to fix the problem, but you don’t know where the website is hosted. You don’t have access to the server, don’t have a backup and technical knowledge. What started as a website problem has become a business problem - this isn’t just something that could happen in theory.

In a Reddit discussion, a business owner described losing contact with the person managing their website and related services. Owner was left trying to work out how to restore access. Situation like this may happen and it show why relying entirely on someone else without understanding the arrangements can create difficulties.

How Do You Protect Yourself?

Where is your domain registered? - Usually you can find out which company your domain is registered with and contact them directly. However, recovering access can take time, especially if you don’t have the login details or the domain was registered in someone else’s name. If you didn’t register the domain yourself, things can become complicated. After all, if someone else is listed as the registered holder, proving that the domain should belong to your business isn’t always straightforward. It can be a bit like trying to claim ownership of a house that’s legally registered in someone else’s name.

Who manages the hosting?- Hosting is where your website lives. Think of it as a garage for your car. You might own a car, but you still need some secure place to keep it. Unlike a domain name, which can often be traced through registration records, finding out where your website is hosted and recovering the necessary files can be much more complicated, especially if you have no access to the hosting account, you will have to open every garage in your city to find your car - not so convinient nor legal.

Are backups being made? - Imagine arriving at your home and discovering that your home been robbed but rather than your 75” TV, your documents, customer records, photographs and years of work are gone. No copies, no way to recover anything. Ask your developer how often backups are made, where they’re stored and how long they’re kept. Ideally, backups should be stored separately from the live website.

There’s a big difference between having a problem that takes an hour to fix and discovering that your entire site needs to be rebuilt from scratch.

What happens if you want another developer to take over your website?

You’ve been working with the same web developer for three years. Everything has been going well, but now your business is growing, and you need additional features that your current developer doesn’t offer. You find someone else who can do the job, sounds simple enough, doesn’t it? - Well, not always.

If your website was custom-built, the new developer will need access to the existing code and other relevant files. But here’s something many business owners don’t realise: paying someone to build a website doesn’t automatically mean you own the code or have the right to modify it. Depending on your agreement, the original developer might retain ownership of certain parts of the website. You may have permission to use it, but not necessarily to transfer, modify or redistribute everything.

And even if you have the necessary rights, there’s another question: can the new developer actually work with what’s been built? Imagine hiring an electrician to extend the wiring in your house, only to discover that the previous electrician used an unusual system, left no documentation and made everything unnecessarily complicated. New electrician might still be able to do the job, but it could take considerably longer and cost more than expected. - Websites can have similar problems.

What if your developer stops trading, what arrangements are in place?

You pay your monthly invoice, your website works, and you’ve never had a reason to worry about the technical side. Then one day, you receive an email saying they’re closing their business or you don’t receive anything at all. Their website disappears, emails go unanswered, and their phone number no longer works. Your developer might have been paying for your hosting, domain renewals or other services through their own business accounts. If those payments stop, the services could eventually be suspended or cancelled. Your website might disappear even though you’ve been paying your developer every month. This doesn’t necessarily mean the developer has done anything dishonest, businesses close for all sorts of reasons. People retire, become seriously ill, change careers or simply decide to do something else. The question is whether your website can continue operating without them.

These are reasonable questions. A professional developer shouldn’t be offended by them.

You’ve Paid for the Website. So You Own It Right, Right? - Not necessarily.

This is something I think more business owners should understand before commissioning a website. In the UK, paying someone to create something doesn’t automatically mean you receive all the copyright in that work. The UK Intellectual Property Office explains that the creator of commissioned work is generally the first copyright owner unless different arrangements apply.

Website development can involve several different types of rights. You might own your business logo, photographs and written content. The developer might retain rights to certain code or design elements. Some software components may be provided under third-party licences. Your domain registration is a separate matter again.

None of this automatically means someone is doing anything wrong. It simply means you should understand what you’re buying. If you pay £2,000 for a website, can you take it to another developer? Can you host it somewhere else? Can someone modify the code? What happens if you stop paying for maintenance?

The answers depend on the agreement. You don’t necessarily need to own every line of code. But you should know what you’re allowed to do with the website you’ve paid for. Personally, I think these things should be explained before anyone signs a contract, not when they’re trying to leave.

Is a Portfolio Enough to Judge a Web Designer?

Most people start by looking at a designer’s previous work - that makes sense. However, screenshot doesn’t tell you how a website actually works. It might look fantastic in a portfolio, but what happens when you open it on your phone? Can you navigate properly? Does the text fit the screen? Can you find the information you’re looking for?

Try using them as if you were a potential customer. If it’s a restaurant website, try finding the menu. If it’s a builder’s website, look for previous projects and contact information. If it’s a service business, see how quickly you can understand what the company offers.

You don’t need specialist software to notice when a website is difficult to use.

What About Reviews?

Reviews can be useful, especially when customers describe specific experiences. Did the developer communicate properly? Were deadlines reasonable? Did they explain additional costs? Was support available after launch? I’d pay more attention to those details than to a collection of generic five-star reviews.

Remember, everyone has to start somewhere.

A newer developer might not have fifty completed projects or dozens of testimonials. That alone doesn’t automatically make them a poor choice. But they should still be able to demonstrate their skills, explain how they work and give you confidence that they can deliver what they’re offering.

AI, Website Builders and Why the Tools Aren’t Everything

There’s been a lot of discussion about AI replacing web developers - I understand why. Today, you can describe a website to an AI tool and receive something that looks surprisingly good within minutes.

So why pay someone to build one?

Well, think about cutting your own hair, you can buy a set of clippers and give it a go. If your goal is to be bald, you might get a perfectly acceptable result. But if you want something more complicated, or you’re preparing for an important occasion, you might prefer someone who knows exactly what they’re doing. The same applies to websites. I can guarantee that you build your own website. But having access to the tools doesn’t automatically mean you understand design, usability, performance, security or how different parts of a website work together.

AI is another tool. I don’t see anything wrong with developers using it - quite the opposite. If AI helps a developer complete repetitive tasks faster, identify problems or improve their workflow, that can reduce development time and potentially save the customer money. Think about a builder using an electric drill. Would you prefer to pay someone extra because they insist on doing everything with a manual screwdriver? - Probably not.

What matters is whether they know where to drill, what they’re fixing and whether the finished work is safe. AI doesn’t remove the need for knowledge. It changes how some of the work gets done. There’s nothing wrong with using one when it suits the project.

What I wouldn’t appreciate as a customer is paying for what I believe is a completely custom design, only to discover that someone has changed the logo and colours on a template used by hundreds of other businesses. Be clear about what you’re buying. Remember that the person or company you hire remains responsible for the work they deliver, regardless of which tools they use.

12 Questions I’d Ask Before Hiring a Web Designer

If you’re speaking to a developer about your first website, you don’t need to interrogate them for two hours. Here are some questions I’d definitely ask.

1. Are You Building My Website From Scratch or Using a Template?

There’s nothing wrong with either approach. What matters is knowing which one you’re paying for. Ask why the developer recommends that solution and whether it will meet your requirements. If you’re paying for custom development, find out what is actually being developed specifically for your business.

2. What Exactly Is Included in the Price?

Don’t settle for a quotation that simply says professional five-page website. Ask what’s included. Will the developer create the design, write the content, configure contact forms, optimise images and test the website? Are revisions included? Are there any additional charges you should expect?

3. Who Is Responsible for the Content?

Some developers expect you to provide all the text and photographs. Others can help write and organise the content. If you’re expected to supply everything, ask what guidance you’ll receive. Writing about your own business isn’t always as easy as it sounds. You know what you do, but explaining it clearly to someone who has never heard of your company is another matter.

4. Will the Website Work Properly on Phones?

At CFN, I build websites with a mobile-first approach. Why? Because nowadays, people are often more likely to visit your website on their phones than on a desktop computer. There’s another reason. Most websites can look fantastic on a desktop, where there’s plenty of screen space and generally more processing power to handle complex animations and visual effects.

Mobile devices are a different story. Smaller screens, varying processing capabilities and slower connections can make those same effects less practical or even frustrating for visitors.

That’s why I prefer to start with the mobile experience and build upwards, rather than design an impressive desktop website and then struggle to make everything fit on a smaller screen. Ask how the developer tests websites on different devices.

5. What SEO Work Is Included?

Does the developer include appropriate page titles, descriptions, headings, clean URLs and basic technical optimisation? Will search engines be able to access the pages intended for indexing? Is keyword research included? What about local SEO?

If someone says the website is fully SEO optimised, ask them what that means.

SEO isn’t a switch that gets turned on when a website launches.

6. Who Will Register My Domain?

Ideally, your business should be the registered holder of its domain. Ask whether you’ll have access to the registrar account and what happens if you decide to change providers. A developer can manage the technical configuration without needing to control the domain indefinitely.

7. What Will I Pay Every Month or Year?

Ask about hosting, maintenance, domain renewals, email services and any paid software. Some costs might be included in a monthly package. Others may be charged separately. You should understand the complete financial commitment, not just the initial development price.

8. What Happens If I Want to Leave?

This might feel like an awkward question when you’re just starting a working relationship - ask it anyway.

• Can you move the website?
• Will you receive the files?
• Are there licensing restrictions?
• Does the agreement include a minimum term or an early termination charge?

A good working relationship shouldn’t depend on you being afraid to leave.

9. Can I Add Features Later?

Maybe you don’t need online booking today, you may need next year. Ask whether the website can be expanded and what kind of changes might require additional development. You don’t need every possible feature immediately. But you should understand the limitations of the system being recommended.

10. What Happens After the Website Goes Live?

Who looks after updates? What happens if a contact form stops working? Who should you contact if something breaks? Is maintenance included? How quickly can you reasonably expect a response?

These details are easy to overlook when you’re excited about seeing the finished design. - They become much more important later.

11. How Many Changes Can I Request?

You might love the first design or you might want to adjust several things - ask how revisions work. How many rounds are included? What counts as a minor change? What happens if you decide to change the entire direction of the project?

Clear expectations make the process easier for everyone.

12. Will Everything Be Confirmed in Writing?

I’d be reluctant to begin a substantial project without a written agreement. It should explain what’s being delivered, how payments work, what each party is responsible for and what happens if circumstances change.

It should also cover relevant ownership and licensing arrangements. Again no need to understand every technical term immediately but you should feel comfortable asking someone to explain it. If you’re about to spend a significant amount of money, taking the time to understand the agreement is sensible.

Deposits, Monthly Payments and Websites Advertised as Free

Let’s return to those three quotations from the beginning. £400, £2,500 and free. Which one offers the best value? Can’t answer that without knowing what each includes. Some developers charge a deposit before starting. Others split the cost into stages. Some charge a fixed development fee and leave hosting and maintenance to the customer. Others build the website with little or no upfront charge and recover their costs through an ongoing subscription.

All of these can be legitimate business models, a deposit isn’t automatically suspicious. A monthly subscription isn’t automatically a bad deal. And a website advertised as free isn’t a scam - the details matter. If a developer asks for a deposit, what happens if the project is cancelled?

If you’re paying in stages, what needs to be completed before the next payment? If you’re paying monthly, is there a minimum contract period? Can you cancel? What happens to the website when you do?

Let’s take a simple example:

A company offers to build your website for free, with hosting and maintenance costing £49.99 per month. Over twelve months, that’s £599.88. Over three years, assuming the price doesn’t change, that’s £1,799.64. Now compare that with a website costing £1,500 upfront, plus £20 per month for hosting. Over three years, that’s £2,220.

But those numbers alone don’t tell us which offer is better. Perhaps the first includes regular updates and technical support. Perhaps the second gives you broader rights to the website and more flexibility to move providers.

Perhaps one includes services that the other charges extra for. That’s why I’d always compare the complete agreement rather than the advertised price. One more thing, when you’re purchasing a website for your business, don’t automatically assume you have the same legal protections as someone buying a product for personal use. Business contracts can operate differently; for larger projects, it may be worth getting professional advice before committing.

How We Approach Website Development at Client Flow Now?

I’ve spent most of this article explaining what I’d look for when hiring a developer. So it’s only fair to explain how I approach these things myself. Client Flow Now is an independent web design and development business based in Cambridgeshire, working with businesses across the UK.

I build websites for businesses that want a professional online presence without unnecessary complications. My approach is fairly straightforward. Before discussing colours, animations or programming languages, I want to understand the business. What do you do? Who are your customers? What do you want your website to achieve? What do you actually need right now?

Sometimes the answer is a simple landing page. Sometimes it’s a more complete business website, and sometimes a business needs functionality that goes beyond a traditional website.

I don’t see much sense in recommending an expensive solution when something simpler would do the job.

Equally, I don’t want to build something that becomes a problem as soon as the business starts growing. You Speak Directly With the Developer - when you work with CFN, you’re speaking directly with the person developing your website, that means we can discuss your ideas, work through questions and make decisions without information being passed between several departments.

If I think something could be done better, I’ll explain why and if there’s something I don’t recommend, I’ll tell you. I’d rather have that conversation before development than build something I don’t believe will work well for your business.

The Technical Side Matters Too - I develop websites with mobile usability, performance, accessibility and technical SEO foundations in mind. That doesn’t mean I promise first-page Google rankings. - It means I want the website to have a sensible technical structure from the beginning.

If you later decide to invest in SEO, content development or additional functionality, having a good foundation can make that work easier.

Understanding the Costs:

I also believe clients should know what they’re paying for. Website development, domain registration, hosting, maintenance and additional services are different things. Depending on the project, some may be included in a package and others may be charged separately, some could be charged on per hour basis. The important part is explaining those arrangements before someone commits.

For selected businesses, I can also prepare an initial website concept so the owner can see the proposed design before deciding whether to proceed. It’s much easier to discuss something you can actually see than to make decisions based entirely on promises.

If your business grows, we can discuss expanding the website rather than automatically starting from scratch.

Final Thoughts

If you’re hiring a web designer for the first time, don’t feel that you need to understand every technical detail. That’s part of what you’re paying a professional to handle. But you should understand the agreement you’re entering into.

You should know what you’re getting, what it will cost and what happens after the website goes live. You should feel comfortable asking questions and you should be able to have a proper conversation with the person or company you’re trusting with your project.

There are plenty of good web designers out there. Some work independently. Others run agencies. Some are based in the UK, while others work from different parts of the world. The challenge isn’t finding someone who can put a website online.

It’s finding someone who understands what your business needs and can explain how they’ll deliver it. Good web designer shouldn’t just build what you ask for. They should help you understand what you’re asking for.

If you’re considering your first website, or you’re unhappy with the one you already have, you’re welcome to get in touch with Client Flow Now.

Tell me a little about your business and what you’re trying to achieve. I’ll be happy to discuss what’s possible, what makes sense and what it might cost.

Let’s Discuss Your Website!