How to choose a web developer for your small business

Hiring someone to build your website is a trust purchase you can't inspect up front. You won't truly know whether you chose well for months. So the decision comes down to two things you can judge now: how someone answers questions before any money changes hands, and whether the setup leaves you free to walk away later.

What should you ask before hiring anyone?

These six questions do most of the work. Send them in an email — to everyone you're considering, us included:

• What's the total price, and what exactly does it cover?
• What's explicitly not included?
• Who owns the domain, the code, and the accounts after launch?
• How many revision rounds, and what does a change cost after that?
• Is there support after launch, and what does it cost?
• What are you guaranteeing, and what's honestly up to my market?

We wrote a companion piece on the document they hand back — how to read a web-design proposal — because how those answers show up in writing matters as much as the answers themselves.

What ownership traps should you watch for?

The big one is lock-in. Some builders make a site you can never move: a proprietary platform with no way to export, a domain sitting in the developer's account, no access to your own code. It feels fine right up until you want to leave — and then you find you're starting from zero, because you never actually held the keys.

Before you sign, make sure the answer to each of these is “you”:

• The domain nameis registered in your account, in your name — not the developer's.
• The code and design files are yours to take, not something you rent access to.
• The accounts — hosting, analytics, your Google Business Profile — are in your name with you as the owner.

A fair developer sets all of this up in your name from day one and hands it over cleanly if you ever part ways. A proprietary page-builder you can't export from is the trap to avoid. Ask the question before you sign, not after.

How do you compare quotes that look nothing alike?

The smallest number is not the comparison. Two quotes can differ by thousands and be selling completely different things. Line them up on the same terms:

• Is content writing included, or are you providing the words?
• Are photos included?
• How many pages, exactly?
• How many revision rounds?
• Is there support after launch, and for how long?

A $900 quote that excludes content and a $2,500 quote that includes writing, photos, and a support window aren't the same product — and the gap usually is the difference. If you want the market context behind those numbers, we broke it down in how much a small business website costs.

What are the warning signs?

• No price in writing — only “let's hop on a call.”
• A guaranteed number-one spot on Google. Nobody controls Google's ranking system, so nobody can honestly promise that.
• Can't or won't show you past work.
• Vague or evasive about who owns what after launch.
• Dodges the “what's not included” question.
• Manufactured urgency — a discount that evaporates if you don't sign today.

What matters more than the portfolio?

A good-looking portfolio is table stakes — nearly everyone has one. What actually separates a developer worth hiring is communication: straight answers, honesty about tradeoffs, and a willingness to tell you when you don'tneed something. Someone who talks you out of a feature you won't use is worth more than someone who happily adds it to the bill. The whole point of the questions above is to surface that person.

Solo developer or agency — does it matter?

Both are legitimate, with honest tradeoffs. A solo developer or small shop usually means a direct line to the person doing the work and often a lower price, but less redundancy if they get busy or step away. An agency brings more people and more process, at a higher cost. Neither wins by default — it depends on your scope and how much hand-holding you want. We're a solo-plus-AI shop ourselves, and that same tradeoff applies to us: you get a direct line and honest pricing, and we'll be straight with you about capacity rather than overpromise.