how to find a good web designer: the search that starts before google

business · May 22, 2026 · 4 min read

searching for a good web designer mostly produces portfolio roulette: everyone’s work looks finished because portfolios are finished. the real signal lives elsewhere — in process, questions, and the way someone behaves before they are hired.

where the real signal is

  • referrals with the reason attached. the best source: — not “they made our site” but “they asked us questions nobody had asked, and the site finally says what we do”. the reason is the signal; the name is just the pointer. network of your clients, of other owners, of the local business groups — and collect the why, not just the who.
  • their own site, as a specimen. a designer’s site is the one reference that cannot be faked by client budgets: their words, their speed, their maintenance. if their site is slow, amateur or stale — treated honestly in why does my website look amateur — believe it over any pitch.
  • the questions they ask you. the single strongest predictor. a good designer interviews about clients, services, money, seasonality before talking visuals. a bad one pitches. the list of what a real discovery covers is written in what should i ask a web designer before hiring — read it and invert it.
  • case studies with the boring parts. anyone can show the launch. the honest case study includes the conflict: the scope that grew, the content that arrived late, what changed, who decided. finished-only portfolios are silent about the half of the job that actually tests people.

the five-minute call that predicts everything

before quotes, before portfolios: a short call where you ask three questions and listen.

  1. “what would you ask me that i haven’t thought of?” — the good ones have an answer ready.
  2. “how do you handle it when a client is slow with content?” — the real answer involves dates and responsibility, not optimism.
  3. “what happens after launch?” — silence here is the whole review, written in advance.

how someone reasons through unfamiliar questions predicts the project better than any mockup, because projects are months of unfamiliar questions.

the red flags, honestly ranked

  • quotes before questions — they are pricing a template, not your project.
  • guaranteed rankings or guaranteed timelines — nobody owns the search engine or the calendar; the honest timeline is in how long does it take to build a website.
  • “we’ll handle everything, you just approve” — the version of you that approves without being asked anything is the version that gets a generic site.
  • a portfolio of only yours-industry clones — competence in one niche is fine; a monoculture suggests templates doing the thinking.

FAQ

is upwork/fiverr viable for a business site?

for small, well-specified jobs, yes — the platform’s escrow and reviews do some vetting for you. for the project with judgment in it, the discovery call matters more than the marketplace tier; wherever you find them, run the same three questions.

should the designer be local?

not required, and useful: local means they know your market’s references, and the site can mention places honestly — the parma pages on my own site, ux designer in Parma and web development in Parma, exist for exactly that reason. remote works when communication is disciplined; the timezone math is in the checklist.

how many should i talk to before choosing?

three, with the same three questions. three is enough to see the range of process quality — and the comparison itself is written up in how do i compare two quotes fairly.

the closing thought

finding a good designer is not about finding the best portfolio. it is about finding the person whose questions are better than yours, whose process survives slowness, and whose post-launch answer has a name attached. run the five-minute call with three candidates and the market sorts itself.

if you want to see the process this describes applied to real projects: