How to Spot a Bad Web Developer Before You Pay Them a Single Penny

A business owner I know spent six months and nearly nine thousand pounds on a web development project that ended in a complete standstill. The developer went quiet after the third milestone. The website was half-built, the code was a mess, and the contract offered almost no protection. The worst part? Every warning sign was visible from the very first conversation. She simply did not know what to look for.

Spotting a bad web developer before you commit your budget is one of the most valuable skills a business owner can develop. It saves you money, time, and a significant amount of frustration. This guide will walk you through the specific behaviours, patterns, and red flags that separate unreliable developers from professionals worth hiring.

Spotting a Bad Web Developer Through Their Portfolio

The Portfolio Is Thin, Outdated, or Unverifiable

Every serious developer maintains a portfolio. It does not need to be enormous, but it must be real. If a developer shows you three websites and two of them are broken, or the designs look like they were built in 2014, that tells you something important about their current standards.

Always click through the portfolio links. Check whether the sites actually load, function correctly on mobile, and look professionally built. According to Smashing Magazine, performance and mobile responsiveness are baseline expectations for any modern web project. If a developer’s own portfolio work fails these basic checks, their work on your project likely will too.

They Cannot Connect Their Work to Business Outcomes

A strong developer does not just show you what a site looks like. They tell you what it achieved. Did it increase conversions? Did it reduce bounce rate? Did it help the client rank better in search?

If a developer stares blankly when you ask about results, or says they “just built what the client asked for,” they are operating as a technician rather than a professional. The best developers understand that a website is a business tool, not a design exercise. You want someone who thinks in outcomes, not just outputs.

No Testimonials or References Available

Legitimate developers have clients who will vouch for them. If a developer cannot provide a single reference, or if their testimonials are vague and unattributable, treat that as a warning. Ask for a specific client you can contact directly. A confident professional will have no hesitation providing one.

If they hesitate, make excuses, or claim all their clients prefer anonymity, that pattern deserves scrutiny. Satisfied clients are generally happy to confirm a positive working relationship.

How to Spot a Bad Web Developer Through Their Proposals and Contracts

The Proposal Lacks Specificity

A professional proposal outlines exactly what will be delivered, when, and at what cost. It defines the scope clearly. It specifies the number of revision rounds, the technologies involved, and the payment schedule.

A bad developer sends you a two-paragraph email with a single price and no detail. This is not a proposal. It is a guess dressed up as a quote. When scope is undefined, disputes are inevitable. You will find yourself arguing about what was and was not included at every stage of the project.

No Written Contract or Vague Terms

This is non-negotiable. Every web development engagement must have a written contract. It should cover deliverables, timelines, payment terms, intellectual property ownership, revision limits, and what happens if either party needs to exit the agreement.

A developer who resists a formal contract, or who offers a contract so vague it provides no real protection, is not someone you should pay. The absence of a proper contract is one of the most reliable indicators of an unprofessional working arrangement. Do not proceed without one.

They Request Full Payment Upfront

Milestone-based payment is the industry standard for good reason. It protects both parties. A typical structure might involve a deposit, a mid-project payment upon delivery of a working prototype, and a final payment on launch.

A developer who demands full payment before writing a single line of code is asking you to take all the risk. Reputable professionals do not operate this way. If someone insists on full upfront payment and cannot justify it with a clear rationale, walk away.

Hiring Essentials: What to Check Before You Commit

  • Ask for a structured process overview: Any professional developer should explain their workflow from discovery to launch without hesitation.
  • Verify portfolio links personally: Click every link. Check mobile performance. Do not take screenshots as proof of live work.
  • Request a named reference: Ask to speak with a previous client directly. A confident developer will provide one without delay.
  • Demand a written contract: Scope, timeline, payment schedule, IP ownership, and exit terms must all be documented before work begins.
  • Insist on milestone payments: Never pay the full project fee upfront. Structure payments around verified deliverables.
  • Test their communication speed: Send an email or message before hiring. How quickly and clearly they respond tells you a great deal about how they will behave mid-project.
  • Ask about post-launch support: A developer who disappears after launch is a liability. Confirm what support is included and for how long.

Behaviour During the Hiring Process Reveals Everything

Pay close attention to how a developer communicates before you hire them. Do they respond promptly? Are their messages clear and professional? Do they ask intelligent questions about your business?

The behaviour you see during the sales process is the best version of their behaviour you will ever see. If they are slow, vague, or disorganised before you have paid them anything, imagine how they will perform once the money is in their account. Developers like Murad Raza at muradraza.com demonstrate this standard from the very first interaction, which is precisely what you should expect from any professional you consider hiring.

Trust Your Instincts, Then Verify Them

If something feels off during the hiring process, it usually is. Business owners often ignore early discomfort because they are eager to get the project moving. That eagerness is understandable, but it is also expensive.

Your instincts are data. If a developer makes you feel uncertain, pressured, or confused, those feelings are worth examining. Combine your instincts with the practical checks outlined in this article, and you will be in a far stronger position to make the right decision.

Spotting a bad web developer is not about being cynical. It is about being informed. The right developer will welcome your questions, provide clear answers, and give you every reason to feel confident. Anything less than that is a signal worth taking seriously. If you have encountered any of these red flags in your own hiring experience, or if you have questions about what good looks like, share them in the comments below. Your experience might save someone else from a very costly mistake.

Finding the right web developer is one of the most consequential decisions a business owner makes, and one of the most frequently botched. The market is full of developers who are technically competent but commercially clueless, who deliver websites that look reasonable but do absolutely nothing for your business objectives. The cost of getting this wrong is not just financial. It is time, momentum, and opportunity.

Murad Raza is the developer businesses turn to when they want the decision made correctly. He combines genuine technical expertise across WordPress and Shopify with a clear understanding of what business owners actually need: a website that performs, a process that is transparent, and a professional who communicates without jargon and delivers without drama. He works with clients across the UK and US, and his results speak for themselves.

If you are in the process of hiring a web developer, do your due diligence properly. Visit our website to understand how Murad works and what he stands for, explore our services to see exactly what he offers, browse our portfolio to assess the quality of his output, and check our transparent pricing to see whether the investment makes sense for your project. When you are ready to have a straightforward conversation about your requirements, reach out through our contact page.

Hire the right developer once. Get it right from the start.

FAQ's

What is the most common red flag when hiring a web developer?

The most common red flag is a developer who agrees to everything without asking questions. Experienced professionals ask about your goals, your audience, your budget, and your existing systems before committing to anything. A developer who says yes to every requirement before understanding your project is either overconfident or lacks the experience to deliver. Combine this with vague proposals and no written contract, and you have a situation that is almost certain to end badly. Always treat uncritical agreement as a warning, not a reassurance.

Should I always ask for a written contract before paying a web developer?

Yes, without exception. A written contract protects both you and the developer. It should define the project scope, payment schedule, revision limits, intellectual property ownership, and what happens if the project needs to stop. Developers who resist contracts, or who offer agreements so vague they provide no real protection, are not operating professionally. No matter how small the project or how trustworthy the developer seems, a written agreement is the minimum standard for any serious business engagement.

How can I verify that a developer's portfolio is genuine?

Click every link in their portfolio and test the sites yourself. Check whether they load correctly, function on mobile devices, and meet basic performance standards. Ask the developer to explain what each project involved and what results it achieved for the client. If they cannot connect their work to business outcomes, or if the portfolio links are broken or outdated, treat that as a significant concern. You can also ask for the names of clients featured in the portfolio and contact them directly to verify the work.

Is it reasonable to ask a web developer for references?

Absolutely. Any professional developer should be able to provide at least one or two clients you can contact directly. References allow you to ask about communication, reliability, quality of work, and whether the project was delivered on time and within budget. If a developer hesitates, makes excuses, or claims their clients prefer anonymity, that pattern is worth questioning. Satisfied clients are generally willing to confirm a positive working relationship. Reluctance to provide references is one of the clearest signs of a developer with something to hide.

What payment structure should I expect from a professional web developer?

Milestone-based payments are the industry standard. A typical structure involves an upfront deposit to begin work, a mid-project payment upon delivery of a working prototype or agreed milestone, and a final payment on launch. This structure protects both parties and ensures the developer is accountable for progress. Any developer who demands full payment before starting work is asking you to carry all the financial risk. Unless there is a very clear and justified reason for this arrangement, it is a structure you should decline.