How to Hire a Web Designer Without Getting Burned

Hiring someone to build your website feels like a gamble. You cannot see the work until it is done. And by then your money is gone.

It does not have to be a coin flip.

I build sites for local businesses for a living. Here is how to size someone up before you sign anything.

Questions to actually ask

Do not just ask if they can build a site. Anyone will say yes. Ask these instead.

Have you built sites for businesses like mine? Show me live ones.
Who owns the site when we are done? You or me?
What happens after launch if something breaks?
Do you handle Google and getting found, or just the design?
How will I know how it is going while you work?
How do you price this, and what is not included?

Write the answers down. You will compare them later, and the vague ones will stand out.

Red flags

Some answers should end the conversation. Watch for these.

"I have only done personal projects, but I can figure it out." Not on your dime.
"Deadlines are flexible." Your launch date is now a maybe.
"SEO is just a buzzword." It is not. It is how people find you.
"I only reach out when there is a problem." You will feel ignored for weeks.
"You cannot really move the site once it is built." That is a leash, not a website.

Green lights

Good signs look like this.

A real portfolio with live links you can click. See my past work for the idea.
A clear timeline and a start date they will commit to.
Straight talk about who owns the site, the domain, and the login.
They ask about your customers and your jobs, not just colors.

Designer or coder? There is a difference

This trips up a lot of owners. Two different skills hide under the same job title.

A coder builds the machine. They make the site work, load fast, and connect the pieces. That is real skill.

A designer makes it look good and guides the eye. Spacing, color, flow, the stuff that turns a visitor into a call.

Some people do both well. Many do one well and fake the other. You want both, from one person or one shop.

How to tell which you are talking to

Look at their examples. Do the sites all look the same, like one template with new logos? That leans coder. Do they show range and taste, with layouts that feel considered? That leans designer.

If the work looks solid but plain, that is often a coder without a design eye. Fixable, but ask how they handle look and feel.

If the work looks pretty but you cannot tell if it actually functions, ask flat out: does it load fast, and does it show up on Google? A soft "um, yeah" is your answer.

Why the fit matters

A website is not a one-time purchase. It is a relationship. You will work with this person for weeks, and lean on them after launch when something needs a fix.

The right one makes your business easier to find and easier to trust. The wrong one costs you the build fee, plus the months you waited, plus the do-over.

Good design and solid web development should come from someone who also cares whether you get found. If they shrug at SEO, keep looking.

The short version

Ask hard questions up front. Write down the answers.
Demand live examples, not screenshots.
Make sure you own the site, domain, and logins.
Find someone strong on both looks and function, or who is honest about which they are.

Slow down before you hire. An hour of good questions saves you a bad year.

Want a straight read on your current site, or a real quote to build the next one? See how I work, or send it over and I will tell you the truth.