Questions to Ask Before Hiring a Web Developer: A Practitioner's Guide

The most expensive question is the one you never asked

I have sat on both sides of this table, building websites for small businesses, and reading the contracts other developers send. The projects that go wrong almost never fail on the code.

They fail on questions nobody asked before the money moved: an owner finds a developer, loves the portfolio, pays the deposit, then learns the domain is registered in someone else's name and updates stopped coming.

These are the questions to ask before hiring a web developer: the six that separate a smooth project from an expensive lesson, the red flags that should make you walk away, and one pre-payment ritual nobody talks about.

Questions to ask before hiring a web developer: get the frame right first

First, know which kind of help you are buying. The price bands are different products:

1. Freelancer's basic site: $500-$5,000 (Clutch's bands). 2. Agency project: ~$66,000 average, $25-$150/hr. 3. Freelance web developer rates on marketplaces: ~$25/hr median, most of the market $13-$60 (6,014 real Upwork job posts). 4. The U.S. Bureau of Labor Statistics: median pay for web developers and digital designers was $99,520 in 2025.

The mistake is comparing a $1,200 quote against a $12,000 quote as if they were the same product. My 2026 website cost guide breaks down what each band buys, and my build-or-buy guide covers the SaaS-versus-custom decision.

Question 1: Show me live work, and tell me what you did on it

Screenshots prove nothing. Ask for three live websites and open each on your phone. If the portfolio shines but the live sites are broken or abandoned, you are watching a highlight reel.

Then: “What did you personally build on this one?” Someone who did the work can say what went wrong; someone selling screenshots cannot.

Good: named roles, trade-offs, one honest regret. Bad: “my team handled that”, with no details.

Question 2: Why this technology for MY project?

“We always use WordPress” is not an answer; “we always write custom code” isn't either. A developer should explain, in plain language, why this stack fits your business, its costs, its limits, what gets harder later.

Then: “What would make you choose differently?” A prepared developer names the alternatives and why they lost. One who hasn't gets defensive, and defensiveness is data.

It also guards against lock-in: a site built on tools you cannot staff, update, or move is a hostage situation with a login screen.

Question 3: Who owns the domain, the code, and every account on day one?

The most-skipped question, and the costliest to skip. Before you pay a dollar, demand a written inventory: domain, hosting, code repo, payment processor, analytics, business email, email marketing, paid plugins, every account in YOUR name, with you holding the logins.

Then the ritual nobody talks about: log in yourself before releasing the final payment. Not screenshots, your own session, your own password. A developer who registered your domain “for convenience” built himself a ransom position, and no escrow fixes that afterward.

Good answer: “Everything lives in your accounts from day one. Here is the list.” Anything vaguer is a negotiation you will lose later.

Question 4: What happens when the scope changes, and what does it cost me to leave?

Scope changes on every real project. What matters is a grown-up process: how changes are priced, who approves them, and whether they land in writing first.

Then the question almost nobody asks: “If I cancel in week three, what do I owe and what do I keep?” The exit-fee trap is the ugliest pattern, you own the site, but it costs a fee to receive it. Put termination terms, handover deliverables, and deposit rules in the contract, not a chat message.

Honest norms, not laws, are roughly: 25-50% deposit, ownership transfers on full payment, two revision rounds per deliverable with extras billed hourly. Where a contract deviates, that deviation should be the part they explain best.

Question 5: What does my site cost after it goes live?

The build price is the down payment on the real cost. Ask for the annual number, hosting, domain renewals, plugin licenses, SSL, backups, maintenance, itemized in writing before you sign.

Then the Friday-night question: “When something breaks at 10pm on a Friday, who do I call and how fast do you respond?” Many developers vanish after launch. Pin down the bug-fix window, the support plan, and the monitoring now, not during an outage.

Also: “Can I update content myself without breaking the design?” A site needing its builder for every text change is a subscription you never agreed to.

Question 6: Who writes the words and feeds the site?

Content stalls more website projects than anything else, and almost no hiring guide makes it a contract question. Who writes the copy? Who picks and resizes the images, uploads the products, migrates old pages with proper redirects?

Then: “What happens to the deadline if my content is two weeks late?” A shrug means your launch date is fiction. Content work should start the day you sign, and the contract should say who waits for whom.

Ask what “SEO included” means exactly: titles and descriptions, sitemap submission, speed work, or just a plugin someone installed.

The red flags worth walking away over

No single red flag proves a bad developer. But they cluster:

1. No written contract, ever. Walk away, whatever the portfolio. 2. Full payment upfront. Where escrow exists, there is no honest reason for this. 3. No estimate breakdown. “$8,000” with no parts is a number, not a quote. 4. Defensiveness about “why this technology.” 5. No answer for the Friday-night question. 6. The exit-fee trap: vague handover, one-sided liability caps, auto-renewal with the cancellation window buried in paragraph fourteen. 7. A fantasy timeline: “two weeks” for a custom build means it isn't scoped, or it's a template.

Trust the pattern, not the charm. Good developers answer specifically; evasive ones answer everything with confidence, which is what this list pierces.

Quick answers to the questions owners actually ask

Freelancer or agency? A freelancer fits a straightforward site; an agency fits complex builds with ongoing needs. A 2025 survey of 406 US small-business owners found 45% used agencies versus 9% freelancers, but your project decides, not the average.

How long should it take? Three to six weeks for a basic site with content ready; eight to sixteen for a custom build. Days for custom work means a template.

Already paid a deposit and it feels wrong? Stop the bleeding: get everything in writing, secure your logins and domain, then negotiate handover of paid work before funding more. A bad fit gets more expensive the longer you fund it.

Questions to ask before hiring a web developer, then decide like an owner

The questions to ask before hiring a web developer are business questions, not technical ones. You don't need to understand the code. You need to understand the deal: who owns what, what changes cost, what happens when things break, and how you walk away.

Twenty minutes of hard questions before you pay saves twenty weeks of regret after. Good developers respect the questions. The rest were never going to respect your project.