How to Choose a Web Designer for Your Small Business

I have been building websites for more than 15 years. Client sites, media sites, niche projects, experiments. Today that work lives under Built by Knup, and the question I hear most from small business owners is not "Can you build me a site?" It is some version of "How do I know who to trust with this?"

Fair question. Hiring a web designer is weird. You are paying for something you cannot fully see until it is done, from someone who usually speaks a different language than you do. Plenty of business owners have a story about a site that took twice as long as promised, a designer who disappeared, or a login they never got back.

So here is how I would choose a web designer if I were on the other side of the table. Even if you never hire me, this will help you hire well.

Start with what the site needs to do

Before you look at a single portfolio, write down what the website is supposed to accomplish for your business.

Not "look modern." That is a preference, not a goal. A goal sounds like this:

• Get more calls or form leads from people in my area.
• Book appointments without the back-and-forth.
• Sell products or take payments online.
• Build trust so referrals check us out and reach out.
• Answer the same questions so my team stops repeating themselves.

This one step changes the whole hiring conversation. A designer who hears "I need more booked appointments" should start asking about your booking process, your follow-up, and your offers. A designer who only asks about colors and fonts is telling you what they think the job is.

I learned this the long way. Built by Knup is not supposed to be "we install a website and good luck." The site is one piece. The page flow, lead capture, follow-up, and reporting behind it are what actually move the business. I wrote about that gap in Why Your Blog Gets Traffic but No Leads, and the same thing applies to a brand-new website.

Know the difference between a designer, a developer, and an agency

These words get mixed up all the time, so it helps to know what you are shopping for.

• Web designer. Focuses on how the site looks and feels: layout, colors, type, and the user experience. Some also build. Some only design.
• Web developer. Focuses on how the site works: code, hosting, speed, forms, integrations, and payments.
• Freelancer who does both. Common for small business sites. Can be a great fit if their skills match your project.
• Agency. A team with a designer, developer, project manager, and sometimes marketing. More hands, more process, usually more cost.

For most small businesses, you want one person or a small team who can handle design and build, then stick around after launch. Ask directly: "Who actually designs it, who builds it, and who do I call when something breaks?"

Look at their work like a customer, not a judge

Every designer's portfolio looks good. That is the point of a portfolio. So do not just look at the screenshots. Go visit the live sites.

When you click through a few of them, pay attention to:

• Your phone first. Pull the sites up on your phone, because that is how most people will find you. Does it load fast? Can you tap the buttons without zooming?
• Speed. Run a couple of their live sites through Google's PageSpeed Insights. You do not need to understand every number. You are looking for whether their sites are generally fast or generally sluggish.
• The path to action. Can you tell what the business does and how to contact them within a few seconds?
• Variety. Do the sites all look like the same template with a new logo? That is not always bad, but you should know what you are buying.
• Live and maintained. Are the sites still up, still working, and still looking like the portfolio? A portfolio full of dead links is a signal.

Then ask the designer to walk you through one project: what the client needed, what they built, and what happened after launch. Good designers can tell that story clearly.

Make sure you will own everything

This is the part that burns small business owners the most, so I am going to be blunt about it.

You should own your domain, your website content, and your accounts. Not your designer. You.

Before you hire anyone, get clear answers on:

• Domain name. It should be registered in your name, in an account you control. ICANN publishes a plain-English list of registrant rights and responsibilities that is worth a skim. You can check who a domain is currently registered to with ICANN Lookup.
• Hosting. Who is the account holder? What happens if you part ways?
• Logins. Will you get admin access to the site, hosting, and any tools connected to it?
• Files and code. If you leave, can you take the site with you?

If you have not picked a domain yet, start there. I wrote a whole guide on how to pick a domain name for a new business.

A designer who gets cagey about ownership is a designer to skip. A good one will want you to own your stuff, because it makes the relationship cleaner for everyone.

Ask how they build, not just what they build

You do not need to become technical. But you should know what your site will be built on and why.

After more than 15 years building on WordPress, I moved Built by Knup away from it as the center of how we build. I explain why in I'm Done With WordPress. That does not mean WordPress is wrong for you. It means the platform should fit your goals, not the designer's habits.

Good questions to ask:

• What platform will you use, and why is it right for my business?
• Can I update basic content myself? Hours, prices, photos, a new blog post.
• How many plugins or add-ons does it depend on? More moving parts usually means more maintenance.
• How will you handle speed, security, and backups?
• Is it accessible? Accessibility helps real people use your site. The W3C's WCAG overview is the standard most designers work from, and a good designer should know what it is.

Listen to how they answer. You want clear, plain-English reasons. If every answer is jargon, imagine trying to get help from this person six months from now.

Ask about SEO without falling for SEO promises

Your new site should be built so search engines can find and understand it. That part is basic and every good designer should cover it: clean page titles, descriptions, headings, fast pages, and a site structure that makes sense. Google's own SEO Starter Guide is a great baseline for what "SEO-friendly" actually means.

What you should be careful about is anyone who guarantees rankings. Nobody controls Google. A designer can build a solid foundation. Ongoing rankings come from content, reviews, links, and time.

So ask: "What SEO basics are included in the build, and what is ongoing work after launch?" That answer tells you whether they understand the difference.

Get the scope, timeline, and price in writing

Most web design horror stories are really scope stories. The owner thought one thing was included. The designer thought something else.

Before you sign, get a written proposal that covers:

• Pages included. Home, about, services, contact, and anything else, by name.
• Features included. Forms, booking, payments, email signup, blog, and integrations.
• Who provides what. Text, photos, logo, and branding. If you are responsible for content, know that up front, because waiting on content is one of the most common reasons projects stall.
• Rounds of revisions. How many, and what happens after that.
• Timeline. With milestones, not just a launch date.
• Payment schedule. What you pay up front, at milestones, and at launch.
• What happens after launch. Hosting, updates, fixes, and support.

When we scope projects at Built by Knup, we talk through what actually needs to be built first, then build that, instead of forcing someone into a predetermined package. Whoever you hire, the principle is the same: the proposal should describe your project, not a generic one.

Plan for after launch, not just launch day

A website is not a one-and-done purchase. Things need updating. Plugins and tools change. Something eventually breaks. You will want a new page or a new offer.

Ask every designer you talk to:

• Who handles hosting, updates, and backups after launch?
• What does ongoing support cost, and what does it include?
• How fast do you respond when something is broken?
• Can I make small changes myself, and will you show me how?

This is why Built by Knup pairs builds with Knup Site Care, so what we build stays working and keeps improving. Whatever you choose, make sure "after launch" is a real plan, not a shrug.

Red flags to watch for

A quick list of things that should make you slow down:

• No live sites to show. Only mockups or screenshots.
• They want to own your domain or hosting and will not explain why.
• Guaranteed first-page Google rankings.
• No written proposal, or a vague one.
• Slow, unclear communication during the sales process. It rarely gets better after you pay.
• Everything is a template but priced like custom work.
• No answer to "what happens after launch?"

Questions to ask before you hire a web designer

If you want a short version to bring to every call:

1. What do you think my website needs to accomplish?
2. Can I see three live sites you built and talk to one of those clients?
3. Who designs it, who builds it, and who supports it after launch?
4. What platform will you use, and why?
5. Will I own my domain, hosting, content, and logins?
6. What exactly is included, and what costs extra?
7. What is the timeline, and what do you need from me to hit it?
8. What happens after launch?

The designer who answers these clearly, honestly, and without pressure is usually the right hire.

Final thoughts

Choosing a web designer is not about finding the flashiest portfolio. It is about fit and trust. Know what the site needs to do. Look at real live work. Own your domain, content, and logins. Understand how it will be built and supported. Get the scope in writing. Then hire the person who explains things clearly and plans to stick around.

If you would rather skip the guesswork, that is what Built by Knup is for. You can do it yourself with the same process and tools I use, have me build it for you, or build it together so you understand how it all works. Tell me what you are trying to accomplish. You do not need to know the technical answer before we talk.

FAQ

How do I choose a good web designer for my small business?

Start with what you need the website to do, like generating leads, booking appointments, or selling online. Then review live sites the designer has built on your phone, confirm you will own your domain and accounts, ask how they build and support sites, and get the scope, timeline, and price in writing before you start.

What questions should I ask a web designer before hiring?

Ask what they think your site needs to accomplish, to see live examples and talk to a past client, who designs and supports the site, what platform they use and why, whether you will own your domain and logins, what is included versus extra, what the timeline is, and what happens after launch.

Should I hire a freelancer or an agency to build my website?

Either can work. Many small businesses do well with one person or a small team who can design, build, and support the site. Agencies bring more people and process, which helps for larger projects. Pick based on your project's size and who will actually support you after launch.

Who should own my website domain and hosting?

You should. Your domain should be registered in your name in an account you control, and you should have admin access to your hosting and website. A good web designer will set it up that way and help you keep it organized.

Can a web designer guarantee my site will rank on Google?

No. No one controls Google's rankings. A good designer builds a fast, well-structured site with solid SEO basics. Rankings over time come from ongoing work like content, reviews, and links.