Key Takeaways
- Ask designers for evidence of how they work, as well as examples of what the finished website looks like.
- Use the same nine questions with each shortlisted supplier so the comparison stays fair.
- Let the person who will update your website try an ordinary editing task before you commit to the proposed system.
- Discuss testing, account control, reporting and ongoing help in plain language. You should not need technical vocabulary to understand the arrangement.
- Choose a supplier whose answers fit your business, then turn those answers into a written scope and agreement.
Finding website designers for a small business is easy. Choosing one can feel much harder, especially when three proposals describe themselves as bespoke, mobile-friendly and SEO-ready.
The first conversation should help you understand what those phrases mean in practice. You are hiring people to make decisions with you, build something your customers can use and leave you able to run it. Attractive screenshots cover only part of that job.
Use these nine questions as a meeting guide. They are not a technical exam or a demand for unpaid strategy. Ask for a short explanation and a relevant example. A good supplier can also say, “We would need to investigate that before promising an answer.”
1. Who Will Do the Work, and Who Will I Speak To?
Ask who is responsible for design, development, content, testing and project decisions. In a small team, one person may cover several jobs. In a larger agency, specialists may work together. Either arrangement can work if responsibility is clear.
Find out who attends reviews and who receives your feedback. If the person selling the project will disappear after the deposit, you should know how the delivery team will understand what was discussed.
Ask what happens during holidays or illness. A freelancer does not need to pretend to be a large agency, and an agency does not need to promise instant access to every specialist. You need a realistic contact and continuity arrangement.
Useful evidence is a simple project contact list with responsibilities. Be cautious if nobody can tell you who will answer an ordinary question or approve a change. Record any subcontracting or access arrangements that matter to your business before sharing private material.
2. Can You Explain a Relevant Project Beyond the Screenshots?
Choose one portfolio example and ask the designer to explain the original problem, the constraints and a decision they made. You might ask why the navigation changed or why a particular enquiry route appears on the homepage.
Look for reasoning that relates to customers and business needs. A credible answer can include something the team decided not to build. It does not have to include impressive growth figures.
If results are quoted, ask what was measured, over which period and whether other marketing activity changed. Traffic growth is different from qualified enquiries. A supplier should not imply that they caused every improvement simply because their launch happened first.
Ask which parts of the example they personally delivered and whether the current site still reflects their work. Websites change after handover. A clear explanation is more useful than claiming responsibility for an entire brand because they built one landing page.
3. What Would You Need to Understand Before Recommending a Build?
Describe your business, the customers you want and what the current website struggles to do. Then ask which information the designer would need before recommending a platform or detailed solution.
Useful questions from them might concern your common enquiries, existing content, search traffic, product data, approval process and who will maintain the website. Their answer should reveal how they investigate a problem.
Use the professional website audit checklist to check what that initial investigation should examine.
Sometimes a paid discovery stage is appropriate. Ask what it produces, what decision it helps you make and whether you can use the findings if you choose another supplier. That protects both sides from pretending a complex integration can be specified in a short sales call.
A website audit and consultation can be a sensible first purchase when the scope is uncertain. If a supplier recommends a full rebuild without examining a functioning existing site, ask what evidence supports replacing it rather than improving it.
4. Can My Team Try the Editing Tasks We Will Do Every Month?
Ask for a demonstration using realistic content, then let the future editor take over. Changing a service description, replacing a photograph and adding an article are good starting tasks. Include any awkward job your current system makes difficult.
Watch how many instructions the editor needs. Can they tell which changes are saved as drafts and which are live? Can they preview on a small screen? If a layout breaks, do they know how to recover it?
Discuss account permissions. In WordPress, the official roles and capabilities documentation explains that different users can have different powers. Your team should not all need unrestricted administration access to correct a paragraph.
Ask what remains a developer task and how that work is charged. There is nothing wrong with a defined technical boundary. Problems arise when “fully editable” means something very different to the owner and the person who built it.
For an AI-generated build, also check whether your team can run an AI-built website before accepting the handover.
5. How Will You Check That Customers Can Use the Site?
Choose a customer task: find the correct service, read a specification, book an appointment or send an enquiry. Ask the designer how they will test that journey on mobile and with a keyboard.
The W3C preliminary accessibility checks offer examples including page titles, image text alternatives and keyboard focus. W3C is clear that these are an initial review, not proof of comprehensive accessibility. A supplier should make that distinction too.
Ask what manual checks complement automated tools, which devices are covered and how faults will be recorded. A perfect score from one automated test cannot establish that every customer can complete your booking form.
Our guide to choosing a mobile-first web developer goes deeper on mobile evidence. During an interview, you mainly want to hear a repeatable process and see a sample test record with private information removed.
6. How Will You Protect What Already Works?
For a replacement website, ask how the team will identify existing pages, links, enquiries and integrations worth keeping. A designer should not assume that everything old has no value.
Ask who checks existing search landing pages before URLs change. Find out how live forms, payment services, booking tools and email settings are protected during testing. A preview should not accidentally send a real customer a test message.
For a new business, use the same question about other assets. Your domain, brand files, product information and analytics accounts need an owner and a place in the plan.
Listen for the difference between what the supplier can verify now and what they still need access to inspect. “We will check the current URL inventory before proposing changes” is a clearer commitment than “SEO will be fine.” Google's SEO starter guide explains useful foundations without promising first place for following a checklist.
7. What Will Happen on Launch Day if Something Fails?
Ask who authorises launch, what checks happen immediately afterwards and who can decide to delay or reverse a change. The answer should suit the risk of your website. A busy shop needs a different plan from a small brochure site.
Use a concrete example: the contact form displays a success message, but the sales inbox receives nothing. Who investigates, where do they look and how will you know enquiries are being handled while the fault is fixed?
The supplier does not need to describe every technical command. They should explain the support route and the evidence used to confirm recovery. “We are available” is less useful than knowing where to report the problem and who owns it.
Ask about launch timing as well. Avoid a release just before everyone leaves for the weekend unless there is a genuine business reason and agreed cover. The first normal trading day is part of the test, even when the public pages looked good at launch.
8. How Will We Know the Website Is Helping the Business?
Pick outcomes you can actually observe. These might include relevant enquiries reaching the right person, bookings being completed or customers finding product information without phoning for a PDF.
Ask what data will be collected, who reviews it and how consent or other measurement limits affect the report. A useful answer separates search clicks, website visits, form submissions and qualified leads.
The designer may work with a marketing partner or offer an analytics and reporting service. Clarify where the website project ends and ongoing marketing begins. Launching pages does not automatically create a programme of content, paid traffic or sales follow-up.
Be wary of guaranteed rankings or a promised revenue figure without a credible basis. Ask instead for the baseline, the changes within the supplier's control and the review schedule. A transparent limitation is easier to work with than a promise nobody can test fairly.
9. What Will I Pay for, Control and Maintain After Handover?
Ask for the normal recurring costs after any introductory period. Include hosting, licences, platform subscriptions, support and work outside the agreed allowance. Confirm whether prices include VAT.
When discussing how much a website costs in the UK, separate the build price from those renewals.
Find out who controls the domain, CMS, hosting and relevant source files. Ask what you receive if you change supplier. Ownership, licences and access are related questions, but they are not interchangeable.
Discuss the difference between a defect, an ordinary content update and a new feature. Then ask how each is reported and priced. Our website redesign proposal checklist helps turn the interview answers into a complete written scope.
Finish by asking the supplier what they would need from you each week. Delayed content and unclear decisions affect delivery. A fair arrangement makes your responsibilities as visible as theirs.
Compare the Answers Before Comparing the Presentation
After each meeting, record what was demonstrated, what was promised in writing and what remains unknown. Use the same headings for every supplier. Avoid giving extra weight to a glossy proposal when another team has answered the difficult questions more clearly.
Whether you are comparing web design in Reading or suppliers farther afield, choose the designer whose process matches the job and whose costs you understand. If you want to discuss a custom website design, send us your current site and the task your customers need to complete. That is enough to begin a useful conversation without asking you to arrive with a finished technical brief.
Frequently Asked Questions
How many website designers should a small business speak to?
A manageable shortlist is more useful than collecting many vague quotes. Speak to enough suitable suppliers to understand the options, ask each the same questions and compare their evidence, communication and scope rather than price alone.
Should a website designer have experience in my exact industry?
Relevant experience can help, but ask what they learned and how they will investigate your customers' needs. A supplier with a clear process and comparable functional experience may be a better fit than one offering an unchanged industry template.
Can I ask to test the website editor before hiring someone?
Yes. Request a demonstration of the proposed editing approach using representative tasks. A supplier may use a sample environment rather than build your website for free. Let the future editor try the controls and record any limitations.
Should I choose the cheapest website quote?
Compare the same scope and ongoing responsibilities first. A lower quote may exclude content, migration, testing or support that another includes. Equally, a more expensive proposal is not automatically better. Ask what each difference delivers.
What is a warning sign during a website designer interview?
Warning signs include unclear responsibility, unexplained recurring charges, reluctance to discuss account control and guaranteed search rankings. Ask a follow-up before judging; the supplier should be willing to turn important answers into written commitments.
