How to tell whether a web designer understands your kind of business
What industry knowledge actually buys on a website
A laptop sits open on the counter, portfolio tab loaded, and every project on the screen is a coffee shop or a boutique. You run an HVAC company. Nothing in front of you looks anything like your business.
Industry knowledge is not vocabulary. A designer can learn what a load calculation is in an afternoon of reading. What takes longer to learn is what actually gets a homeowner with no heat at six in the morning to pick up the phone instead of clicking away.
That's the real thing on offer when you hire someone who's worked in your trade before. They already know which page a worried customer lands on first, and what has to be sitting there the moment they do. Comparing that against the wider hiring decision is worth doing before you narrow the search to specialists only, since a generalist with the right process can still handle this well.
A general-practice designer isn't automatically the wrong choice, either. Some of the strongest sites in a given trade were built by someone new to it, working closely with the owner instead of guessing from past jobs. Industry knowledge is a shortcut. It saves the guessing, not the whole project.
Asking what a customer in your trade needs to see before they call
Ask a candidate one direct question: what does a first-time customer in your trade need to see in the first few seconds on a page. A designer who's built for your kind of business before answers fast, and specifically.
They'll mention licensing, or emergency availability, or before-and-after photos, or a price range, depending on the trade. A designer without that background gives a vaguer answer instead — trust signals, clear navigation, a strong call to action — the kind of thing that's true of almost any site and specific to none of them.
Neither answer disqualifies anyone by itself. The specific one tells you they've already thought about your actual customer. The vague one tells you that thinking hasn't started yet, and you'd be doing part of it together.
Push a little further. Ask what they'd put above the fold on your homepage specifically, not in general terms. A guess dressed up as a plan sounds different from a real one once you ask it to get concrete.
Past work in a similar trade against past work that only looks similar
A site for a florist and a site for a landscaper can look alike on a screen — soft colors, big photography, a simple menu — without either designer understanding what actually drives a customer's decision in either trade.
Look past the surface style. Ask what problem each past project was actually solving. A designer who built a site for a plumber and a site for an electrician has seen two versions of the same core need: get someone in real distress to call now, not browse later.
That pattern recognition carries over even into a trade they haven't touched directly. A designer who's built for three different service trades has learned something structural about urgency and trust that a designer who's only built restaurant sites hasn't needed to learn yet.
Reading a portfolio properly means looking past the palette and asking what job each site was actually built to do. That's a different skill from admiring the photography.
Regulated trades and the details a generalist misses
Some trades carry legal weight a general-practice designer might not think to ask about. A contractor's license number, an insurance disclosure, a required disclaimer on a medical or legal page — these are not decoration. Leaving one off can be a real problem, not just a missed detail.
A designer who's worked in a regulated field before knows to raise this early, before the site is built and the missing piece has to be squeezed in later. One who hasn't may never think to ask at all, simply because it's never come up on their past projects.
That doesn't mean a generalist can't handle a regulated trade. It means you need to raise it yourself, plainly, on the first call, rather than assuming it's already been considered. Bring your own list of what has to appear, and treat it as part of the brief.
Phoning a past client in your own industry and what to ask them
If a designer has worked in your trade before, ask for a name in that same trade and actually call them. Skip the general "were you happy" question. Ask something sharper: did the site need real changes once real customers started using it, or did it work close to as planned from the start.
Ask, too, whether the designer pushed back on anything, or just built what was asked without questioning it. A designer who's worked in your trade before has often seen a mistake or two happen already, on someone else's project, and knows to flag it before it repeats on yours.
That one call can tell you more than an hour of scrolling a portfolio. A past client who's lived with the finished site for months has information no sales pitch will give you.
When a designer from outside your industry is the better hire
Sometimes the outsider is the stronger choice. If every site in your trade looks the same, a designer who's never worked in it might be the one who breaks that pattern, because they're not repeating a formula they already trust.
A designer new to your trade also has to ask more questions up front, since they can't lean on assumptions from past projects. That extra questioning can produce a sharper brief than working with someone who assumes they already know the answers.
Weigh this against your own patience for that back-and-forth. A generalist willing to learn your trade properly, and asking good questions along the way, can outperform a specialist who's coasting on habit.
The rest of the vetting process applies here regardless of which way you lean, and these industry questions fit naturally into your first real conversation with anyone you're seriously considering.
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