Skip to content
web1o
Blog

Red flags when hiring a web developer (and the questions to ask)

The warning signs of a bad web developer — no contract, they own your domain, vague pricing, no maintenance — plus the exact questions to ask before you sign.

  • web development
  • hiring
  • agencies
  • small business
  • buyer guide

Hiring the wrong web developer is expensive twice: once when you pay them, and again when you pay someone else to undo the damage. The good news is that bad developers and agencies tend to show the same warning signs early — usually before you've signed anything. This guide covers the red flags to watch for and the exact questions to ask so you can walk away before it costs you.

Red flag 1: No written contract or scope

If a developer proposes to start on a handshake, a one-page email, or "we'll figure out the details as we go," stop there. A proper agreement should spell out what you're getting: how many pages, which features, how many rounds of revisions, the timeline, the price, and what happens if either side wants out.

A contract that just says "website design and development" with no breakdown is not much better than nothing — it's the setup for a dispute where "that wasn't included" becomes the answer to every request. Vague scope is where projects quietly balloon in cost and time.

Ask: Can I see a written proposal with the page list, features, revision rounds, and total price before we start?

Red flag 2: They own your domain, code, or accounts

This is the single most damaging trap, because you often don't discover it until you try to leave. You should own your domain name, your hosting, your website code and design files, and any third-party accounts (analytics, email, ads) set up on your behalf. The industry consensus is unambiguous: the domain should be registered in your name — not the agency's — and if a developer registers it for you, you must be listed as the legal owner, with them as a technical contact at most.

When a developer holds the domain or hosts everything on a proprietary platform you can't export, they can hold your site hostage in a dispute, point it elsewhere, or simply let it expire. Under copyright law the creator of a design is the default owner, so your contract needs to explicitly transfer ownership of the code and design to you once you've paid.

Ask: When the project is done and paid for, exactly what do I own — domain, code, design files, and admin access? Put it in writing. And: Is my domain registered in my name on my own registrar account?

If you're weighing platforms and lock-in, our sibling guide on how to choose a web design agency goes deeper on vetting the shortlist.

Red flag 3: No visible process

A weak developer jumps straight to colours, fonts, and trendy animations without asking a single question about your business, your customers, or what the site is meant to achieve. Design without a goal is decoration.

Good developers have a process they can describe in plain language: discovery, structure and content, design, build, review, launch, and handover. You don't need to understand every technical step — you need to hear that a repeatable process exists and know where your input and sign-offs happen.

Ask: Walk me through your process from kickoff to launch. Where do I review and approve things?

Red flag 4: Vague pricing and no clarity on "extra"

"It depends" is a fair answer to a rough enquiry, but by the time you're signing, the number should be concrete. Watch for quotes with no breakdown, prices that seem far below everyone else (someone always pays the difference later), and no definition of what counts as an out-of-scope change versus an included revision.

You want to know the total, what's included, the hourly or fixed rate for work beyond scope, and whether hosting, maintenance, or licences are extra monthly costs. If you're still calibrating what a project like yours should cost, run the numbers with our website cost calculator and read the full breakdown in how much a website costs in 2026.

Ask: What's the all-in price, what's a billable change versus an included revision, and what will I pay monthly after launch?

Red flag 5: No maintenance or handover plan

A website is not a one-off purchase; it needs updates, security patches, and backups. If a developer has no answer for what happens after launch — no maintenance option, no documentation, no handover of accounts and passwords — you're being handed a car with no service manual and no keys to the boot.

Even if you decide to maintain the site yourself, you need a clean handover: admin logins, hosting access, a list of plugins or services in use, and where backups live.

Ask: After launch, who handles updates, security, and backups — and what happens if I want to take it in-house or move to another provider?

Red flag 6: Poor communication from day one

How a developer communicates while they're trying to win your business is the best version of the communication you'll ever get. If they're slow to reply, dodge direct questions, over-promise, or can't explain things without jargon during the sales stage, that behaviour rarely improves once the invoice is paid.

Clear, prompt, plain-language answers early are one of the most reliable signals of a project that will actually finish on time.

Ask: Who is my point of contact, how do we communicate, and what's your typical response time?

Red flag 7: No proof of past work

Anyone can claim experience. Ask for a portfolio of live sites you can visit, and ideally a reference or two you can contact. Be wary of a portfolio full of designs that were never launched, or an agency that can't point to a single client who'll speak to you. Real results and real clients are easy to produce when they exist.

Ask: Can I see three live sites you've built and speak to a recent client?

The short list to bring to every call

  • Can I see a written proposal with scope, revisions, timeline, and total price?
  • When it's paid off, what do I own — domain, code, files, and admin access?
  • Is my domain registered in my name, on my account?
  • What's your process, and where do I approve things?
  • What counts as an extra charge, and what will I pay monthly?
  • Who handles maintenance, and how does handover work if I leave?
  • Can I see live work and talk to a past client?

If a developer answers these clearly and puts the important ones in writing, that's a strong signal. If they get defensive, vague, or evasive, believe them — that's the relationship you'd be signing up for.

Working with a partner who does this by default

At web1o we build websites for European SMBs with all of this handled up front: clear scope, ownership in your name, a documented process, and a plan for what happens after launch. If that's the kind of working relationship you want, see web development or book a free consultation and we'll walk through your project with no obligation.