If you're looking for a website developer, you've probably already discovered the problem: the search doesn't surface developers. It surfaces directories ranked by who paid, agencies whose developers you'll never meet, marketplaces optimizing for whoever answers fastest, and a wall of portfolios that all look professionally identical — because portfolios are the easiest credential to manufacture. The person who will actually write your code is the single most important variable in the project, and the market is structured so you meet that person last, if at all.
This guide inverts that. Here's where the search actually goes wrong, the three vendor shapes behind every result, how to vet the developer in one conversation, and the ownership checklist that decides whether you hired a developer or acquired a dependency.
Where the search goes wrong
Most buyers start in one of three places, and each has a structural bias worth knowing before you trust it:
- Directories and “top 10” lists. Rankings on most agency directories are influenced by paid placement and review-gathering effort, not build quality. They're a phone book with sponsorships, useful for generating a long list and nothing after that.
- Freelance marketplaces. Genuine talent exists there, buried in an interface that rewards fast replies and low bids. The marketplace's incentive is transaction volume; complicated projects — the kind where you most need the right developer — are exactly the ones the format serves worst.
- Referrals. The best starting point by far, with one caveat: a referral tells you the developer was right for that project. A friend's five-page brochure site and your quoting-system integration are different purchases wearing the same word.
None of these is disqualifying. The mistake is treating any of them as the evaluation rather than the long list. The evaluation happens in conversation with the person who writes the code — everything before that is advertising.
The three shapes behind every search result
Strip away the branding and every candidate is one of three shapes. We map them fully in how to choose a custom web development company, but the short version decides most hires:
Match the shape to the job before comparing prices. A freelancer and an agency quoting the same brief aren't competing bids — they're different products, and the spread between them is information about what each one thinks your project is. If the site's job is genuinely complicated — the kind of work we define in what custom web development actually means — the shape question narrows fast, because two of the three shapes handle complicated jobs by handing them to someone you haven't met.
The talk-to-the-coder rule
One rule outperforms every other vetting technique: before you sign anything, have a real technical conversation with the specific person who will write your code. Not a salesperson who “speaks developer,” not a project manager relaying answers — the developer.
The rule works because it's a test the wrong vendors structurally can't pass. An agency that subcontracts can't produce the developer, because the developer hasn't been chosen yet and will be whoever's cheapest when your contract lands. A shop whose “custom” work is theme configuration can't survive twenty minutes of questions about how they'd build your specific hard requirement. And a genuine developer, asked about the complicated part of your project, does something imitators can't fake: gets specific, names trade-offs, and tells you which part is risky. In our experience, hesitation at this request predicts the entire engagement — if you can't reach the developer before you've paid, you won't reach them after.
What to ask in that conversation:
- “Here's the hardest part of my project — how would you build it?” You're not grading the architecture; you're listening for specificity, trade-offs, and honest uncertainty versus a smooth “we do that all the time.”
- “What's the most complicated thing you've built, and what broke?” Real experience includes failure and maintenance stories. Marketing doesn't.
- “What would you cut from my brief?” Developers descope; salespeople upsell. The direction of the answer tells you who's talking.
- “What happens in month thirteen?” Updates, small fixes, response time when something breaks. A good answer is specific and boring.
The ownership checklist
More projects are ruined at the account level than the code level. The pattern is always the same: the developer “handled all that” at launch, and two years later the business discovers it doesn't control its own website. Before any work starts, get each of these in your name, in writing:
- Domain — registered in your registrar account, not the developer's. This one alone can hold your business hostage.
- Hosting — your account, your billing, developer added as a collaborator. Agency-owned hosting is a retention strategy with a monthly fee.
- Source code — you own what was written for you, and you can take it elsewhere. Custom code you can't take with you is a subscription with extra steps.
- Analytics and tracking — your accounts, so the measurement history survives any vendor change.
- Content and data — exportable, in a usable format, demonstrated rather than promised.
A developer who agrees to all five without friction has nothing to lose by your independence — which is exactly the vendor you want. One who resists is telling you their business model, and you should believe them. Our 42-point evaluation criteria covers the technical version of this same test.
What hiring a developer costs
Ranges, not quotes — the published market research we cite in our packages guide puts standard small-business builds at roughly $1,000–$5,000 with freelancers and $6,000–$12,000 with small agencies, with genuinely custom engineering starting where those bands end. The honest cost warning is different, though: the expensive failure mode isn't overpaying for a good build. It's paying twice — once for the vendor who couldn't do the complicated part, then again for the developer who could. Buyers who apply the talk-to-the-coder rule almost never pay twice, because the vendors who would have failed can't pass it.
The honest verdict
Looking for a website developer is really looking for one person: the one who will write the code, who you can talk to directly, and who treats the complicated part of your project as the point rather than the problem. Everything in this guide — the shapes, the rule, the checklist — is machinery for finding that person and confirming they exist before money moves.
We're built so that person is who answers. You describe the job to the developer who does it — the same model behind the platform Mercy House Ministry runs on (secure case management, an AI phone assistant, online giving — and the nonprofit half our profits fund) and the inspection report technology A.C. Moate's entire field team works on daily. Get a scoped proposal and run every question on this page against us — that's what the questions are for.
Frequently Asked Questions
How do I find a good website developer?
Use directories, marketplaces, and referrals only to build a long list, then evaluate by conversation: insist on speaking directly with the person who would write your code, describe your hardest requirement, and listen for specificity, named trade-offs, and honesty about risk. Confirm in writing that domain, hosting, source code, analytics, and content will live in your accounts. Vendors who pass both tests — the conversation and the ownership terms — are rare, and reliably better than whatever any ranking told you.
How much does it cost to hire a website developer?
Published market research puts standard small-business sites around $1,000–$5,000 with freelancers and $6,000–$12,000 with small agencies; genuinely custom development — integrations, calculators, portals, structured data — starts where those ranges end because you're buying engineering time rather than configuration. Price is driven by integration depth, logic, and data, not page count. The costliest outcome isn't overpaying once; it's paying a second developer to rebuild what the first one couldn't finish.
What should I ask a website developer before hiring them?
Four questions do most of the work: how would you build the hardest part of my project; what's the most complicated thing you've built and what broke; what would you cut from my brief; and what does month thirteen look like — maintenance, small changes, response time. You're evaluating behavior more than answers: specificity, willingness to descope, and comfort discussing risk are what separate a developer from a sales process with technical vocabulary.
What's the difference between a website developer and a web designer?
A designer's product is how the site looks and communicates: layout, typography, brand, content structure. A developer's product is what the site can do: code, data, integrations, performance. Small projects often get both skills in one person; complicated projects rarely do. If your requirements include quoting, booking, logins, or talking to your CRM, you're hiring a developer whatever the job title says — and the vetting in this guide is how you confirm the development skill actually exists.