How to Choose a Web Designer for Your Small Business: 11 Questions Before You Pay

Choosing a web designer is difficult because you may only hire one every few years.

The safest way to choose is not to ask, “Whose portfolio looks nicest?” Ask whether this person can turn your business problem into a website you can still understand, measure and control after launch.

A website should leave your business with more control than it had before the project started. That means clear ownership, working conversion paths, measurable results and an exit path if you ever change designers.

Here are the questions I would ask before paying a deposit.

1. Who will own the domain name?

Your domain is the address people search, save and link to. It should not become hostage to a freelancer’s personal account.

A strong answer sounds like: “The domain will be registered in your business-controlled account, or transferred to you with documented access.”

Be cautious if the answer is vague, if the designer refuses to share registrar information, or if ownership is tied permanently to an unrelated account.

This is not just paperwork. ICANN explains that the registrant holds the right to use, renew and transfer a registered domain. Your business should know which account holds those rights and how to access it. See ICANN’s guidance on domain-name rights and lost domains.

2. Can I see live websites, not just screenshots?

Open the work on your phone.

Test the navigation, forms, speed, typography and basic usability. A static screenshot hides the parts of web design that customers actually experience.

Also ask what problem each site was solving. Good design work should have reasoning behind it.

I would pay particular attention to the boring parts: does the form actually submit, does the mobile menu behave properly, are important buttons obvious, and does the site still feel coherent after you leave the homepage? Those details tell you more about build quality than a polished mockup.

3. What exactly is included in this quote?

“Website design” can mean almost anything.

Ask for a written scope covering:

• pages or templates;
• copywriting responsibilities;
• image sourcing;
• forms and booking;
• ecommerce if relevant;
• mobile design;
• analytics;
• basic SEO setup;
• integrations;
• revisions;
• hosting and deployment;
• post-launch support.

Two quotes are not comparable until their scopes are comparable.

Also ask what is not included. A clear exclusion is often more useful than a vague promise to “handle everything.”

4. Who is responsible for the content?

Many projects stall because the client thought the designer would write everything and the designer thought the client would supply finished copy.

Clarify who creates:

• homepage messaging;
• service descriptions;
• calls to action;
• team bios;
• FAQs;
• case studies;
• photos;
• legal pages.

A website with weak content will still feel weak even if the visual design is excellent.

5. How will you decide what goes on the homepage?

This question exposes whether the designer starts with a template or with the business.

A useful homepage normally needs to help a visitor understand:

What do you do? Who is it for? Why should I trust you? What should I do next?

If the process begins with “pick a template you like,” ask what happens to strategy, customer questions and conversion structure.

For service businesses, I also want to know where the enquiry journey begins. For a clinic that may be an appointment. For a consultant it may be a call. For a hotel it may be a direct booking. The page structure should reflect the actual business outcome rather than copy a generic layout.

6. What happens to my existing SEO if this is a redesign?

If your current site already ranks, receives traffic or has backlinks, a redesign can damage that value when URLs are changed casually.

Ask whether the designer will preserve important URLs, map redirects when paths must change, keep metadata intentional and check indexing after launch.

Google’s own site-migration guidance recommends mapping old URLs to their new destinations, implementing redirects, checking canonicals and monitoring traffic after a move. A designer rebuilding an established website should have a deliberate answer for that process, not discover it after launch. See Google Search Central’s site-move guidance.

This matters even more when a business has been online for years.

7. How will the site work on mobile?

Do not accept “responsive” as the whole answer.

Ask how they test mobile navigation, forms, buttons, long titles, tables, images and booking flows. Your customer may first meet your business on a small screen while distracted, on a slow connection or in a hurry.

The important action should still be obvious.

8. What will I be able to edit myself?

Some clients want a hands-off managed website. Others need to change prices, team members, services, articles or photos every week.

Both models can work. The problem is discovering the limitation after launch.

Ask exactly what you can edit, what requires developer help and whether training is included.

A useful test is to name three changes you expect to make during a normal month and ask the designer to show how each would be handled. “You can edit the site” is too vague if changing a service description still requires opening code.

9. What analytics and measurement will be installed?

A website should not become a black box.

At minimum, you should know how the site can measure important outcomes such as contact submissions, calls, bookings, purchases or other relevant actions.

Do not obsess over vanity traffic. Decide what a meaningful conversion means for your business and make sure the site can observe it.

For example, a hotel may care more about completed direct-booking journeys than page views. A law firm may care about qualified consultation requests. An ecommerce business may need purchase and checkout data. The measurement plan should follow the business goal.

10. What happens after launch?

Ask who handles:

• software updates;
• backups;
• security issues;
• content changes;
• broken forms;
• domain and hosting renewals;
• performance problems;
• new pages.

Then ask what is included versus billed separately.

If ongoing maintenance is confusing, read Website Maintenance Packages for Small Businesses: 2026 Cost Guide.

11. What happens if we stop working together?

This may be the most important question.

A healthy project should have an exit path.

You should know whether you receive or retain access to the domain, hosting, repository/source code where relevant, CMS, analytics, images, content and other accounts used for the site.

The goal is not distrust. It is operational clarity.

Ask for an ownership and handoff list before the project starts

I increasingly treat this as part of the build itself, not an afterthought. Before launch, there should be a simple record of which accounts exist, who owns them and where the business has administrative access.

For a typical small-business site, that may include:

• domain registrar;
• DNS or CDN account;
• hosting or deployment platform;
• CMS administrator account;
• source-code repository when applicable;
• analytics and Search Console;
• business email used for recovery;
• forms, booking or ecommerce accounts;
• image and content assets;
• renewal responsibilities.

You do not need every password written into a document. You need to know that the business controls the accounts and recovery paths that matter.

Red flags that deserve another question

Pause when you hear things like:

• “Don’t worry about the domain; I handle everything.”
• “SEO is guaranteed.”
• “You don’t need access to that account.”
• “We can decide the price as we go” with no boundaries.
• “Mobile will sort itself out automatically.”
• “I cannot show you any live work.”
• “You must stay on my hosting forever.”

A red flag is not always proof of bad intent. It is a reason to clarify the arrangement before money changes hands.

How to compare the final shortlist

Score each option from 1–5 on:

Do not automatically choose the highest score or the lowest price. Use the exercise to expose trade-offs you would otherwise discover later.

If you are still deciding between DIY and professional help, read Website Builder vs Web Designer: When Should a Small Business Stop Doing It Yourself?.

What a good designer should be able to explain

By the end of the first serious conversation, you should understand not only what the website might look like, but why it is being structured that way.

That is the standard I use in my own work: plan the business and product logic first, then design and build around it. I also want the client to understand what they own, what they can edit, how enquiries are measured and what happens after launch.

If you want me to review what you are trying to build, see my web design service or send the project details.