Four replies to the same email. One says $850 and can start Monday. One says $4,200 and wants a call. One is an agency at $19,000 with a discovery phase. The fourth asked six questions about how your bookings currently work and has not quoted at all. You are a florist, or a dentist, or a maker of industrial fasteners, and you cannot tell which of these people will still be answering your messages in November.

So you did what everyone does and asked the internet where to hire a reliable web developer. You got 141 answers and no decision.

Here is the uncomfortable part. Reliability is not a trait you can detect in an interview. It is a property of how you structure the engagement, and it is mostly decided in the first two weeks of work rather than in sourcing. Upwork, a referral from your accountant, a local meetup, an agency: each contains excellent developers and expensive disasters. What separates the outcomes is whether there is a written scope, a small paid piece of real work before the big commitment, and an arrangement where you can see progress without asking for it.

Remote is fine, and four hours of working-day overlap is the practical threshold, because most problems get solved by one quick exchange rather than a scheduled call. What the channels are not is interchangeable.

Five realistic places to hire a reliable web developer

Referrals from other business owners in your industry. The strongest signal available, because the person recommending saw the whole engagement, not a portfolio page. A portfolio shows the launch; a referral tells you whether the developer answered the phone in month five. Ask specifically: not “do you know a web guy” but “who built your online ordering, did they finish on time, and would you use them again for something bigger?” The weakness is supply.

The developer who already built something like yours. Underused, often the best route. List five to eight sites in your sector that do what you need, then find out who built them: a footer credit line, the About or Work page, or the domain run through BuiltWith or Wappalyzer, which shows the platform and sometimes the agency. Email them about that specific site. You start the conversation having already inspected their output in your own industry, months after launch. No proposal beats that.

Local dev communities and meetups. Meetup groups, WordCamps, city Slack and Discord servers, the nearby university’s CS job board. The value is peer visibility: someone who turns up to the same room every month has a reputation that costs something to damage. Slow, and many attendees have no interest in small business work. Worth it if you have a few weeks.

The marketplaces, which genuinely differ. Lumping Upwork, Toptal and Contra together is the mistake. They sell different things.

• Upwork is volume plus escrow. It does not vet skill; it gives you reputation signals, a work diary on hourly contracts and dispute support, and leaves judgement to you. Its own hiring pages put web developer rates at $15 to $25 an hour entry level, $30 to $50 intermediate and $50 to $200 expert, with published client fees of 5% on the Basic plan (3% for eligible US clients paying from a checking account) and 10% on Business Plus, plus a small contract initiation fee. Good for defined, testable work. Bad if you hoped the platform had screened anyone.
• Toptal sells the screening itself and publishes the funnel: 26.4% of applicants pass the language and communication stage, 7.4% survive the skill review, 3.6% the live screening, 3.2% the test project, 3% remain after ongoing performance review. A flat $79 monthly subscription applies once you proceed to matching, and engagements open with a trial of up to two weeks you are not billed for if it fails. Rates are several times Upwork’s. It fits when you cannot evaluate technical work yourself and a bad hire would cost more than the premium. For a $3,000 brochure site it is the wrong tool.
• Contra is commission-free for freelancers, charging clients a flat per-payment fee on transactions over $500 unless they take the $29 monthly tier. Because nobody is skimming 10 to 20 percent, quoted rates tend to reflect what the developer actually wants to earn. There is no vetting layer at all. A directory with payments attached.

Agencies. You are buying continuity, not a person: someone answers when your developer is away, and a project manager is paid to notice that nothing has happened for nine days. That costs two to three times an individual’s rate, and you rarely pick who touches the code. Right answer when the site carries revenue. Overkill for a booking form.

Why the cheapest and the most expensive quote are both usually wrong

The cheapest quote is rarely cheap because the person is fast. It is cheap because they understood the least. Quoting within an hour is only possible if you have not thought hard about the work, so the flat number arrives from someone who has not yet discovered that your inventory lives in a spreadsheet your office manager maintains by hand. Rate is the wrong variable anyway. A $20-an-hour developer who needs 90 hours costs more than an $80-an-hour developer who needs 20, and leaves you something you will pay a third person to unpick.

The most expensive quote is usually not insurance either. It is an agency loading overhead you have no use for onto a small job, a shop pricing in the risk your own vague brief created, or a sales-led firm charging for discovery as a product. Expensive projects fail too, and then there is less money left to fix them. Take the quote attached to a written scope and a list of exclusions, wherever it sits in the spread. “Includes X, Y and Z, does not include content writing, photography or the payment gateway’s monthly fee” tells you more than any reference call will.

Write the job post so the wrong people filter themselves out

Most small business job posts are a list of technologies copied from somewhere. “Looking for WordPress developer, PHP, MySQL, Elementor, responsive design.” That tells you nothing, because every applicant says yes to all of it. Describe the business problem instead and ask how they would approach it. That single change filters harder than anything else you can do.

Weak: “Need a developer to build a 10-page WordPress site with a booking system.” Strong: “We run three dog grooming salons. Bookings come by phone into a paper diary, so we double-book about twice a week and lose roughly six appointments a month to people who called after hours. We want customers to book online and the diary to stop being paper. Budget is $6,000 to $9,000, live before December, and our groomers are not computer people. Tell us how you would approach this and what you would want to know first.”

Keyword matchers fall away, because there is nothing to match. Experienced people reply with questions, often with a cheaper suggestion such as embedding an existing booking platform into the site you already have. You compare approaches instead of prices, which is the only comparison that means anything. State the budget range; withholding it costs you good candidates. And never ask for free mockups, because the best people decline and you are left with whoever was least busy.

The paid trial task, done properly

This is the highest-value screening you can buy, and most owners either skip it or ruin it by asking for something free.

What to pick. Something real, small, and touching your actual system. A genuine bug on a copy of your site, one small feature you want anyway, an import from the spreadsheet you really use. Four to eight hours, briefed on one page. Do not invent a puzzle, and do not hand over the hardest part of the project.

What to pay. Full rate, agreed in advance, paid on delivery whether or not you continue. Anyone who treats a paid trial as an insult expects to be judged on charm.

What to judge. Almost none of it is the code, which you cannot read.

• Did they ask questions before starting, or begin immediately?
• Did the work land inside the estimate, and if not, were you told before the deadline rather than after?
• Is there a staging URL you can click, or did they email a zip file?
• When you asked for a change at the end, was the response a conversation or a sigh?

Running this with two candidates for $600 buys better information than ten hours of interviews. Toptal formalises the same idea with its two-week trial; you are doing it at small business scale.

Screening questions that actually reveal experience

Skip “what’s your process”. Ask these, and listen to the shape of the answer rather than the content.

• “Tell me about a project that went wrong, and what you did.” Anyone with real mileage has one ready, tells it without blaming the client for everything, and can say what they changed afterwards. No story means too few projects, or no ownership of them.
• “What would you need from me for this to go well?” A good answer is uncomfortable and specific: content by a date, one decision-maker rather than a committee, registrar access, someone who replies within a day. “Nothing, just leave it with me” is a preview of how the schedule slips and whose fault it will be.
• “What in my brief would you push back on?” You want at least one thing challenged or cut. Total agreement is a sales posture you pay for later in change requests.
• “Who else touches this, and what happens if you are ill for two weeks?” No solo developer has a perfect answer. An honest one contains a name.

Reference checks that get past the highlight reel

Ask for a client from at least a year ago, not the one who launched last month. Longevity is the whole question. Then ask things with factual answers: what did the final invoice look like against the first quote, and why? When something broke, how long until you got a reply? Who holds the hosting and domain logins now? What do you wish you had put in writing at the start? Do it by phone, because the pause before “well, eventually” carries most of the information.

Red flags, roughly in order of how much they matter

• A quote with no questions asked. The most reliable predictor of a bad engagement. Nobody can price your business from a paragraph.
• A number with no written scope. Without a list of what is included and excluded, every later disagreement is your word against theirs. Same for a request for fifty percent upfront on a first engagement with no trial: a deposit is normal, that is not.
• Unwillingness to work in your repository or hosting account. “I’ll host it on my server and give you access” means they hold your business hostage by accident.
• No staging environment. Work that exists only on the live site, or only on their laptop, cannot be reviewed safely.
• Availability that sounds too good. A solo developer free immediately, full-time, for three months, at a low rate, is either between things for a reason or about to take a salaried job mid-project. “I have two other clients and can give you about 15 hours a week” is the better answer.

What to agree in writing before any money moves

A small project does not need a lawyer. It needs an email you both reply “agreed” to, covering these.

• Scope, with exclusions. What is being built, and explicitly what is not: content, photography, logo, SEO, third-party subscriptions.
• Milestones you can test yourself. “A customer completes a booking on a phone and gets a confirmation email” is a milestone. “Backend complete” is not.
• A fixed price with a change process, or hourly with a cap. Fixed price when the work is genuinely knowable and written down: a brochure site, a migration, an integration with a documented service. Hourly with an agreed cap while you are still deciding what you want, because a fixed price on a moving target converts every change into a negotiation.
• Repository and hosting in your name. Create the GitHub or GitLab account and the hosting account yourself, on your company card, then add the developer. Day one. Retrofitting it is the most common ugly conversation in small business web work.
• Third-party accounts in your company’s name: registrar, DNS, payment gateway, transactional email, analytics, plugin licences, with your address for recovery. Keep credentials in a password manager you own.
• IP assignment in present tense. Under US copyright law, “work made for hire” covers commissioned work only in nine specific categories, and the US Copyright Office’s list does not include software or website code. Without a signed written assignment, an independent contractor can retain copyright in what you paid for. One sentence fixes it: the developer “hereby assigns” all rights in the work to your company on creation.
• What happens if you stop. Name the handover deliverables (repository access, database export, deployment notes, credentials), make final payment follow them, and agree a kill fee for cancelling mid-milestone so nobody is punished for an honest ending.
• Response times. Not an enterprise SLA. Replies within one business day, and a heads-up before any silence longer than two.

The bus factor problem, and how to shrink it

One developer is one point of failure, and the failure modes are boring: a full-time job offer, illness, quiet disinterest in a client who emails once a quarter. The Bureau of Labor Statistics puts self-employment among web developers at about 18%, with a median wage of $92,650 as of May 2025, so the independent pool is real and so is the churn inside it. You cannot prevent that. You can make replacement cheap.

• Everything lives in accounts you own. That is 80% of the answer on its own.
• Insist on mainstream technology. WordPress, Laravel, Django, Rails, standard React. A framework the developer wrote themselves means only they can maintain it, which is occasionally the point.
• Buy two hours of README. How to run the site locally, how to deploy, where the database lives, what breaks when a plugin updates. Cheapest insurance available.
• Know the second name before you need it. Keep another developer on nodding terms, perhaps one who quoted and lost. The gap between “my developer vanished and I know nobody” and “I have someone to call” is weeks of revenue.

How to tell in week two that it is going wrong

By the end of week two you should have all of this: questions asked in week one, a staging URL you can click, one visible piece of work even if it is ugly, and at least one occasion where the developer told you something inconvenient before you found out yourself.

The warning signs are equally concrete. Updates made of adjectives, where “going well” replaces what was done and what is blocked. Nothing you can look at, because it all lives on their machine until the end. Silence past two business days with no warning. A request for more money before anything works. The same question deferred twice. And the quiet one: count who started the last five messages. If it was you every time, that does not improve at month three, when far more of your money is committed.

Two or more of these means one written conversation, not five worried ones. Say what you expected by now, what you need to see within three working days, and that the next milestone should be smaller. Reasonable people answer with a staging link. If nothing changes, stop at the milestone boundary and take your repository, your credentials and your loss. Stopping in week two costs a few hundred dollars and some pride. Stopping in month four costs the project, the season, and usually the deposit.

If you would rather not do the screening yourself

AB7 Solutions sits on both sides of this. We build websites, applications and APIs directly, and we do contract staffing and staff augmentation, which means placing a named developer who works inside your repository, your hosting and your definition of done rather than their own. If you want help earlier, we will write the scope and the paid trial brief with you so you can take them to market yourself, or read a quote you already have and say what is missing from it. Call +1 321 341 7733, email ab@ab7solutions.com or director@ab7solutions.com, or start at www.ab7solutions.com. If the answer is that the freelancer you already found is fine and just needs a better contract, we will say so.

Sources: Upwork client pricing and Upwork web developer hourly rates (platform’s own published figures); Toptal screening process and Toptal FAQ (company-published funnel percentages, subscription fee and trial terms); Contra pricing; U.S. Copyright Office, Circular 30: Works Made for Hire; U.S. Bureau of Labor Statistics, Occupational Outlook Handbook, Web Developers and Digital Designers (median wage $92,650, May 2025; self-employment share).