what to ask a web designer before hiring: the ten questions that sort the market

business · May 21, 2026 · 5 min read

the questions most buyers ask — how much, how long — get rehearsed answers. the questions that actually sort the market are the ones that make process, ownership and accountability visible. here are ten, with what each answer quietly tells you.

the ten questions, and what each one tests

  1. “who exactly will do the work?” tests dilution. “the team” is an answer; a name is an answer. the gap between the person who sells and the person who builds is where agency projects disappoint, as written in freelance or agency.
  2. “what do you need from me, and by when?” tests process maturity. the good ones hand you a checklist — words, photos, logins — with dates. “we’ll figure it out as we go” is where timelines die; the raw-material list is in what you need before starting a website.
  3. “how many revisions are included, and what counts as one?” tests honesty about the loop. vague here means friction later; the mechanics of why revisions multiply are in why do websites cost so much.
  4. “what platform do you build on, and why that one for my project?” tests judgment vs habit. “whatever you like” is a tell; “for your booking system, this, because x” is process.
  5. “who owns the domain, the hosting and the files when we’re done?” tests ownership defaults. the right answer is your name on the deed from day one, not at delivery; the deed rules are in what is a domain name, and the agency-bought-domain trap has its own post: do i own my domain if the agency bought it.
  6. “can i see a site you built three years ago, still running as-is?” tests what you are actually buying: not the launch, the survival. maintained sites and abandoned ones look identical on launch day.
  7. “what happens after launch, and at what cost?” tests whether the recurring half exists in their model. silence means the surprises are yours; the honest yearly bill is itemized in what recurring costs does a website have.
  8. “how will i be able to edit it myself?” tests whether the build is designed for your year-two, or for their portfolio.
  9. “what would you NOT do for my project?” tests candor. the professional answer names scope they would decline — and the no-list is where honesty lives, per is your seo agency doing anything.
  10. “what would make you fire ME as a client?” tests self-respect. the answer that names boundaries (slow content, scope creep, disrespect) predicts a project with rules — and rules protect both sides.

why these beat “how much and how long”

price and timeline get honest values only when process is visible: a two-week promise from someone with no content checklist is a guess; the same number from someone with question two answered is a plan. ask the ten questions first and the numbers become comparable — which is the whole job of how do i compare two quotes fairly.

and one meta-question costs nothing: ask for one reference from a client whose project stalled. how they talk about the messy project tells you more than three clean references.

FAQ

should i send these questions in writing before the call?

no — in the call. the written version gets polished answers; the live version gets pauses, reasoning, and the occasional “good question”, which is exactly the signal you are fishing for.

what if they get offended by the list?

a professional expects these; many will thank you. offense at process questions is itself the answer — better discovered in call three than in month two.

which is the single most important one?

number five. every horror story about “my developer disappeared with my site” reduces to a question nobody asked at the start.

the closing thought

a web project is not bought; it is joined. the ten questions are not an interrogation — they are the first design decision of the project: what kind of relationship you are entering, with what rules, whose names, on whose land. rehearsed answers to “how much” never told anyone any of that.

if you want to be on the receiving end of these questions: