Red Flags When Hiring a Web Developer

The biggest red flags when hiring a web developer show up before you pay anything: a proposal with no itemised scope, no answer about who owns the domain and hosting once you pay, and a payment structure that asks for most of the money upfront with nothing tied to delivery. If a proposal cannot answer those three questions in writing, that is worth pausing on before a deposit changes hands.

I build custom WordPress sites for a living, so I read a lot of other people’s proposals when a client asks me to compare quotes or rescue a stalled project. The patterns repeat. Here is what I actually check, in the order I check it.

What should a proposal actually itemise?

A proposal should list the pages or content types being built, what platform the site runs on, what is included in the price, and what counts as a revision versus new scope. If it reads like a one-paragraph quote with a total at the bottom and nothing else, you do not really know what you are buying.

I itemise every quote I send: number of pages, whether custom post types are involved, whether the client needs forms, integrations, or copywriting, and what happens if the brief changes mid-build. Real price bands and what drives them is a good reference if you want to know why one quote is a few hundred dollars and another is several thousand for what sounds like the same website. Usually the gap is exactly this itemisation, or the lack of it.

A vague scope is not always dishonest. Sometimes a developer genuinely has not thought it through yet. An unwillingness to itemise when you ask directly is the actual red flag, not the vagueness on its own.

Who should own the domain and hosting after you pay?

You should own the domain and hosting, registered in your name or your business’s name, with the login details in your hands before or immediately after the deposit clears. If a developer wants to register the domain under their own account “to make things easier,” that is the clearest red flag on this whole list.

I have taken on rescue jobs where the previous developer held the domain over an unpaid invoice, and the business owner had no way to move the site or even fix their email in the meantime. Website ownership: what you actually own walks through the four things to check, domain, hosting, code, and content, and how to verify each one in about ten minutes. Do that check before you sign, not after something goes wrong.

A developer who hands over full access without hesitation is telling you something about how they operate. One who gets defensive about the question is telling you something too.

Why does a vague timeline matter more than it seems?

A vague timeline usually means the scope underneath it is vague as well. “A few weeks” with no milestones is not a timeline, it is a hope.

Ask for a start date, a rough midpoint check-in, and a target launch date, even with the usual caveat that content delays push things back. If a developer cannot give you that structure before you pay, they likely do not have a real plan for your project yet, only a queue they will fit you into eventually.

What payment structure actually protects you?

A fair structure ties payment to delivery: a deposit to start, a milestone payment partway through, and a final payment at or near launch. Full payment upfront, with nothing due at completion, leaves you with no way to push back if the work stalls or the quality slips.

I ask for a deposit to start, because turning down other work to begin your project is a real cost on my side too. The rest is tied to progress you can actually see. If a developer asks for the full amount upfront on a project with no track record you can verify, that is a real risk, not just an inconvenience.

This cuts both ways. If you are haggling a developer down to a token deposit with the rest due whenever it suits you, you are creating the same instability from the other direction. A fair structure protects both sides, and a developer who will not discuss it at all is worth a second look.

Is a rock-bottom price ever the real red flag?

Sometimes, but not always. A low price on its own is not proof of anything. Billy’s salon site was built on Wix at a modest budget, and that was the right call for the business at that stage, not a corner cut.

The actual red flag is a low price paired with vague scope and no ownership answers. That combination usually means the build will be templated, undocumented, and hard to hand off later, even if it looks fine on launch day. A cheap build you fully own and understand beats an expensive one you do not.

What I would not trust is a price that seems too good for the stated scope, from someone who cannot explain where the time is actually going. Either the scope shrinks quietly later, or corners get cut somewhere you cannot see yet.

What should you ask before you say yes?

Ask five questions before any deposit: what exactly is included, who owns the domain and hosting once I pay, what the payment schedule is, what happens if I want changes after launch, and can I see finished work I can actually visit.

JustHyb is one of mine, a custom WordPress build for a battery specialist that loads in under a second and started taking B2B calls in its first week. I point prospects to it and to my other work because a developer confident in the work will send you live links, not vague testimonials with no URL attached. If a developer cannot or will not show you a site with their name on it, ask why.

None of this means every developer without a perfect answer is trying to take you for a ride. Some are freelancers still building their process. A pattern of dodged questions across scope, ownership, and payment together is the real signal. One vague answer is a conversation. Three vague answers is a pattern.

If you want a second opinion on a proposal before you pay a deposit, send it to me on WhatsApp and I will tell you plainly what looks fine and what does not. Message me on WhatsApp, or read more about custom WordPress development and see pricing for a sense of where honest quotes land.

Quick answers

Is a 50 percent deposit normal?

Yes, a deposit around half the project cost is standard for custom web work, especially from a developer with limited capacity who is turning down other jobs to start yours. The concern is not the size of the deposit, it is whether the rest is tied to visible progress.

Should I always pick the cheapest quote?

No. Compare quotes on what is itemised and who owns what afterward, not just the total. A cheap quote with vague scope and no ownership answers usually costs more later, either in a rebuild or in a standoff over the domain.

What if I already paid a deposit and I am seeing red flags now?

Ask the three questions directly in writing: exact scope, who owns the domain and hosting, and the payment schedule for what remains. A clear answer means you can likely proceed carefully. Silence or defensiveness means it is worth getting a second opinion before you pay anything else.