How to vet a web designer before you hire them
What to look for beyond the portfolio itself
A portfolio full of polished screenshots proves someone can make an image look good. It doesn't prove they actually built the sites shown, that those sites still exist, or that they still function the way the screenshot suggests.
Click through to a handful of the actual live sites, not just the static images on the portfolio page. Open them on a phone, too. A site that only looks good in a screenshot is telling you something worth noting.
Look for a range of different projects, not five versions of the same layout with different logos dropped in. Range says more about actual skill than polish alone does.
Notice the dates on the portfolio too. A page that hasn't added a new project in a long stretch of time might mean a slow year, or it might mean something else worth asking about directly.
None of these checks take long individually. Together, they take less time than a single design revision, and they happen before you've spent anything at all.
Knowing what to look for once you're there turns a quick scroll into a real check you can trust.
The wider set of options this decision sits inside is worth reviewing too, since vetting looks slightly different depending on whether you're evaluating a freelancer, an agency, or something in between.
Confirming they're an actual, findable business
A legitimate designer or agency usually has a presence that predates the moment you found them: a business registration, a history of posts or reviews, a website that's been live for more than a few months already. None of that is hard to look up.
Search their business name plus the word "review" or "complaint" and see what comes back. A total absence of any digital footprint outside a single ad or a brand-new profile is worth noticing.
That absence isn't proof of anything on its own. It's a reason to ask more questions before you send any money. A new business isn't automatically a risky one, but it deserves a slower first step.
Check whether the name on the ad matches the name on the invoice you'd eventually receive. A mismatch there is a small thing to notice now and a hard thing to untangle later.
Asking about their process before asking about price
Leading with price tells you almost nothing except a single number. Leading with process tells you how a project actually runs day to day: how revisions work, how feedback gets handled, what happens if something needs to change after the first draft is delivered.
Someone with a real process can walk through it clearly, in order, without hesitating over any part of it. Someone without one tends to answer with generalities and steer the conversation straight back to cost.
A real process also has an end point that isn't just "launch." Ask what happens in the first week after the site goes live, specifically, and see whether the answer sounds rehearsed or lived-in.
Ask what the third step of their process is, specifically. A person who has actually run this before answers instantly, without needing to think about it.
Ask, too, what they need from you at each stage. A real process has a clear answer for your role in it, not just theirs, down to specific deadlines for content and feedback.
Red flags that show up in the first conversation
Pay attention to what happens before you've committed to anything at all. Pressure to decide immediately, reluctance to share a written scope, or vague answers about who will actually be doing the work are all worth pausing on.
Specific sales phrases worth doubting tend to show up right here, in this very first conversation, before any contract exists to hold anyone to anything they've said.
Once you know the pattern, it becomes easier to hear as it happens. Trust that instinct. It's usually right, even when it's hard to name exactly why.
Write down anything that felt off in the moment, even if you can't explain it yet. A pattern across three small things is easier to spot on paper than it is to remember after the fact.
None of this means treating every conversation with suspicion from the first word. It means giving equal weight to the small signals alongside the big, obvious ones, instead of only noticing a problem once it's already expensive.
Checking whether they'll still be reachable after launch
Ask directly what happens once the site is live and the invoice is paid in full. Who fixes something if it breaks down the road? Is ongoing support already part of the arrangement, or a separate conversation you'll need to have later?
What that ongoing relationship is actually supposed to look like is worth reading before you ask this question, so you can tell a real answer from a vague one when you hear it.
Calling a past client in your own trade and asking what the process was actually like can confirm whether that answer holds up once you talk to someone who's actually lived through it. A designer who gets uncomfortable discussing what happens after payment clears is telling you something worth hearing now, not after launch day.
Ask this question early, before you've mentally committed to anyone. It's much harder to hear the honest answer once you already want them to be the right choice.
None of these checks take a long conversation to run. Together they take less time than picking out a font, and they happen before a single deposit changes hands.
Skipping them to save an afternoon rarely saves anything at all. It just moves the cost of finding out later, when the project is further along and it's harder and more expensive to fix properly.
More from the blog
- Will a professionally built website actually get you more customers
- When a booking system is worth adding to your site
- What has to be on your website before a stranger will choose you
- What to ask before a monthly retainer adds a new tool to your site
- Where your website's contact form submissions actually go