Red Flags to Watch for When Hiring a Web Developer

Most Bad Web Development Experiences Were Predictable

Almost every business owner who's been burned by a web developer can point to a moment, in hindsight, where something felt off before they signed. The site that never got finished, the invoice that kept growing, the developer who went silent for weeks — these rarely come out of nowhere. There are usually warning signs during the sales conversation, if you know what to look for.

No Written Contract or Scope Document

If a developer is willing to start work based on a verbal agreement or a one-line email, that should stop you immediately. A legitimate contract should spell out:

• Exactly what's being delivered (number of pages, specific features, integrations)
• The payment schedule and what triggers each payment
• The timeline, broken into milestones, not just a single final date
• Who owns the code, domain, and content once the project is complete
• What counts as a revision versus a new request that costs extra

Without this in writing, every disagreement later becomes a "he said, she said" problem, and you're the one who already paid.

Asking for Full Payment Before Any Work Begins

Deposits are normal — many agencies ask for a portion upfront to secure the project and cover initial costs. But a developer who wants full payment before starting has no financial incentive to finish, and if the relationship goes wrong, you have no leverage left. A staged payment schedule tied to milestones — design approval, development complete, launch — protects both sides.

A Vague Timeline That Never Gets More Specific

"A few weeks" isn't a timeline. Watch for developers who can't break a project into phases with rough dates attached: discovery, design, development, review, launch. A realistic project has a plan behind it. A vague one is often a sign the developer hasn't actually thought through the scope, or is telling you what you want to hear to close the deal.

If the timeline keeps sliding without explanation once work starts, that's the same red flag showing up after the contract is signed.

No Questions About Your Business

A developer who quotes you a price within minutes of hearing "I need a website" hasn't done any discovery. Good web development starts with questions: who are your customers, what do competitors' sites look like, what's currently working or not working, what should the site actually accomplish. If nobody asks, nobody's really planning — they're assembling a template and hoping it fits.

Guarantees That Don't Make Sense

Be skeptical of any developer who guarantees specific Google rankings, a set number of leads, or a fixed increase in sales as part of a website contract. Nobody controls Google's ranking algorithm, and search visibility depends on many variables outside a single developer's control. A guarantee like this is either a misunderstanding of how rankings actually work, or a sales tactic — neither is a good sign.

Can't Explain Hosting or Ownership Clearly

Ask directly: if you stop working with this developer, do you keep the website, the domain, and the hosting account? A trustworthy answer is specific and immediate. A vague answer, or one that dodges the question, often means the agency plans to keep control of your site as leverage — sometimes described as being held hostage by a developer who owns your domain registration or hosting login and won't hand it over without extra fees.

This is one of the most common and most damaging problems small businesses run into. You should always know exactly who holds the keys to your own website.

Portfolio Examples That Don't Hold Up

If every "recent project" link is broken, redirects somewhere unrelated, or looks nothing like what's described, that portfolio isn't trustworthy. Click through every example a developer shows you. If they can't produce live, working examples of past projects, ask why — sometimes there's a legitimate reason, like an old client taking the site down, but it shouldn't be the norm across the whole portfolio.

Pressure to Sign Immediately

"This price is only good today" is a sales tactic, not a business reality. Web development pricing doesn't expire overnight. A developer pushing you to sign before you've had time to compare options, read the contract carefully, or ask follow-up questions is prioritizing closing the deal over getting the project right.

Silence Once the Deposit Clears

Pay attention to how communication feels during the sales process, because it's usually a preview of what happens after payment. If a developer is highly responsive before you pay and slow afterward, that pattern tends to continue through the whole project — and gets worse as launch approaches and problems inevitably come up.

No Mention of What Happens After Launch

A website isn't finished the day it goes live — it needs monitoring, security updates, and occasional fixes. If post-launch support never comes up in conversation, ask about it directly. A developer with no plan for what happens after launch is often planning to disappear once they're paid.

What to Do If You Spot One of These

One yellow flag isn't necessarily disqualifying — everyone has an off day, and a rushed answer isn't always a sign of dishonesty. But if you notice two or three of these patterns together, treat it as real information. Trust what you observe during the sales process over what's promised in it.

For a positive framework covering what to actually look for instead, see how to choose a web development agency.