20 Questions to Ask Before Hiring a Web Designer

Hiring a web designer is a business decision, not just a creative one. The wrong designer costs you time, money and traffic. The right one becomes a long-term partner. These 20 questions are grouped into four categories. Each includes a good answer (green light) and a bad answer (red flag) so you can evaluate responses with confidence.

Experience and portfolio

Q1: Can you show me examples of work in my industry or a similar sector?
Good answer: "We have built sites for professional services, retail and hospitality. Here are three relevant examples, and here is what each achieved for the client."
Bad answer: "We can design anything. Industry experience does not matter." Industry experience is not essential, but a designer who has solved similar problems is less likely to make sector-specific mistakes.

Q2: Which sites in your portfolio are you most proud of and why?
Good answer: Mentions specific outcomes: improved traffic, better conversion rate, a complex feature delivered on time.
Bad answer: Talks only about visual design. A site that looks beautiful but does not generate business is art, not a business tool.

Q3: Have you built sites on the CMS we are considering?
Good answer: "Yes, we work with WordPress, Webflow and custom CMS platforms. Here is what each is best for."
Bad answer: "We only use X platform and that is all you need." Platform choice should fit your business, not the designer's preference. Read our CMS comparison guide to understand your options.

Q4: How do you measure the success of a site after launch?
Good answer: "We set up analytics, define KPIs before launch and review performance at 30 and 90 days."
Bad answer: "We hand over the site and you take it from there." A designer who disappears after launch leaves you without a safety net.

Q5: Can you provide client references?
Good answer: "Here are three clients you can call. I will introduce you by email."
Bad answer: "Our clients are too busy" or "we do not share client contacts." Every professional agency can provide references. If they cannot, ask why.

Process and team

Q6: What is your design and development process?
Good answer: A clear, numbered process: requirements gathering, wireframing, visual design, development, testing, launch. Each stage has a defined output and a review point.
Bad answer: "We just start designing and show you as we go." Without a defined process, scope creep and missed deadlines are almost certain.

Q7: Who will actually work on my project?
Good answer: "You will have a project manager, a designer and a developer. Here are their names and backgrounds."
Bad answer: "The team" or "the creative director will oversee it." If you do not know who is doing the work, you cannot assess whether they have the right skills. We name our six full-stack developers and one UI/UX designer on our team page.

Q8: How do you handle feedback and revisions?
Good answer: "You get two rounds of revisions per stage. Additional changes are quoted separately."
Bad answer: "Unlimited revisions until you are happy." Unlimited sounds good but usually means the scope has no discipline and the project never ends.

Q9: What do you need from me and when?
Good answer: A clear checklist: content, images, brand guidelines, domain access, third-party logins. "We send a kickoff document on day one."
Bad answer: "Just send us whatever you have." The biggest cause of project delays is the client not knowing what is expected of them. A good designer makes this explicit.

Q10: How do you handle scope changes during the project?
Good answer: "We document the change, quote it and add it to the timeline. You approve before work starts."
Bad answer: "We usually absorb small changes." Scope creep is easier to prevent than to manage. A clear change control process protects both sides.

Pricing and contracts

Q11: What is the total cost and what does it include?
Good answer: A line-item breakdown: design, development, content entry, testing, launch. "Hosting is BD 3.5 to BD 11.5 a month depending on the plan."
Bad answer: A single number with no breakdown. You need to know what is included so you can compare quotes fairly.

Q12: What is not included in the price?
Good answer: "Content writing, photography, stock images, ongoing maintenance and paid plugins are not included."
Bad answer: "Everything is included" or "we will let you know if something extra comes up." Exclusions disclosed upfront are honest. Exclusions discovered mid-project are disputes waiting to happen.

Q13: What is the payment schedule?
Good answer: Milestone-based payments tied to deliverables: 30 percent on signing, 40 percent on design approval, 30 percent on launch.
Bad answer: "100 percent upfront" or "pay as we go with no schedule." A reasonable payment schedule protects both parties.

Q14: Who owns the final design and code?
Good answer: "You own everything — the design files, the code, the content and the domain. We grant you full ownership on final payment."
Bad answer: "We retain the rights to reuse the design" or "the code is our intellectual property." You should own what you paid for.

Q15: What happens if the project goes over schedule?
Good answer: Acknowledges that both sides can cause delays. "If we cause a delay, we absorb the cost. If you cause a delay through late content or approvals, we adjust the timeline."
Bad answer: "It will be on time, guaranteed." Anyone who guarantees a creative project has not been doing this long.

Post-launch and support

Q16: What happens after the site launches?
Good answer: "We monitor for 30 days, fix any post-launch issues and hand over a maintenance guide."
Bad answer: "The site is yours. Good luck." Post-launch support separates professional agencies from project-by-project freelancers.

Q17: Can I make changes to the site myself?
Good answer: "Yes, you get a CMS control panel. We will show you how to use it."
Bad answer: "You will need us for any change." A CMS you cannot use yourself locks you into dependency. Every Almada site includes a CMS you can manage yourself.

Q18: What is your policy on bugs and issues after launch?
Good answer: "We offer a six-month bug-free warranty on custom builds. Bugs found during that period are fixed at no charge."
Bad answer: "Bugs found after launch are charged at our hourly rate." A warranty period is standard for professional work.

Q19: Do you offer ongoing maintenance?
Good answer: "Yes. We offer monthly and quarterly maintenance retainers covering updates, backups and security."
Bad answer: "Maintenance is not our focus." If they will not support the site after launch, you need a plan for who will.

Q20: How do I contact you if something breaks?
Good answer: "Phone, email and a support ticket system. We respond within four business hours, 24/7."
Bad answer: "Just email us and we will get back to you." A clear communication channel and response time SLA is essential.

These 20 questions are designed to surface the information you need to make an informed decision. For a broader view of how to choose between providers, see our how to choose a web design company guide and our honest comparison of agencies versus freelancers.

How to evaluate the answers you receive

Asking the questions is only half the process. The answers matter more than the fact that you asked them. Here is how to evaluate what you hear.

Specificity is the strongest signal. A web designer who can describe exactly how they handled a similar project, name the team members who worked on it and explain why they made specific technical decisions has real experience. Vague answers that sound good in general but lack specifics are a warning sign — they indicate the designer has not actually done what they are describing.

Look for alignment with your priorities. If your biggest concern is post-launch support and the designer keeps talking about their beautiful visual style, they are telling you that support is not where they invest their energy. Listen to what they emphasise, not just what they answer. Their priorities become your reality after you sign.

Trust your reaction to the bad answers. The bad sample answers in this guide are designed to show you red flags, but each designer will phrase their answer differently. If an answer feels evasive, press on it. If it feels too good to be true — "unlimited revisions", "guaranteed rankings", "we can do everything" — it probably is. A professional gives honest, specific answers, including honest limitations about what they can and cannot do for your project.