Red Flags to Watch For When Hiring Someone to Build Your Website

Almost everyone who’s had a bad experience getting a website built can point to a warning sign they noticed and talked themselves out of at the time, usually because everything else about the conversation felt fine. None of these require technical knowledge to spot either. They’re about how someone communicates and structures the work, not about code at all.

No written scope before any payment

If a developer asks for money before putting the actual scope, pages, features, price, timeline, in writing somewhere you can refer back to, that’s the single biggest red flag on this whole list. A written scope is what protects both sides from disagreements later about what was actually promised versus what someone remembers being said on a casual call weeks earlier.

Vague or shifting pricing

“It depends” is a fair answer before scope gets discussed properly. After that conversation happens, a legitimate developer should be able to give you a real number, or a clearly bounded range with the reasons for that range explained plainly in terms you understand. Pricing that stays vague even after you’ve explained exactly what you need is worth questioning directly rather than just accepting and hoping it works out.

No examples of past work anywhere

Anyone who’s built real websites for real clients should be able to show you some, ideally with a way to actually verify they built it and not just a screenshot pulled from somewhere else entirely. No portfolio, or a portfolio you can’t verify, isn’t automatically disqualifying for someone newer to the field just starting out, but it does mean you’re taking on more risk than usual going in.

Unwillingness to commit to code and domain ownership

Covered in more depth elsewhere, but worth restating as its own red flag here too. If a developer is vague or resistant about handing over full code access and domain ownership at launch, that’s worth pressing on before you commit to anything, not after the project’s already underway and you’ve already paid a deposit.

No plan for what happens after launch

If nobody can tell you who fixes something if it breaks two months from now, or what ongoing maintenance actually costs on a monthly basis, you’re finding this out for the first time exactly when you’re least prepared to negotiate, mid-crisis, with a site that’s currently down and customers who can’t reach you.

Pressure to decide immediately

A legitimate freelancer or agency wants you making an informed decision, because a client who actually understood what they were buying tends to be a better long-term client who refers others later. Heavy pressure to sign quickly, or discounts that expire within hours of a first conversation, are sales tactics more common in less reputable operations than in solid, established ones.

Payment structured entirely upfront

Some upfront payment, a deposit, is normal and reasonable practice across the industry. A hundred percent upfront, with nothing tied to actual delivery or milestones along the way, removes your only real leverage if the work doesn’t go the way you were promised it would from the start.

Communication that feels one-sided from the start

Pay attention to how quickly and clearly someone responds during the sales conversation itself, before any money has changed hands. If getting a straight answer already feels like pulling teeth at this early, low-stakes stage, that pattern rarely improves once you’re actually a paying client with less leverage than you had during the initial negotiation.

What good actually looks like, for comparison

A written proposal before any payment changes hands at all. A clear, fixed price once scope is set in stone and agreed by both sides. Real, verifiable past work you can actually check for yourself. A stated plan for ownership transfer and post-launch support laid out clearly. No pressure to decide on the spot, ever, under any circumstances. None of this is unusual to ask for, and a developer who bristles at reasonable questions like these is telling you something useful before you’ve spent a single dollar.

Trusting your own gut alongside this checklist

None of these red flags are foolproof on their own, and a developer can technically check every box above while still being a poor fit for your specific project or working style. Alongside this list, pay attention to your own comfort level during early conversations. If something feels off even when you can’t quite name why, that instinct is worth taking seriously rather than talking yourself out of it because everything on paper looked fine at first glance.

Where to look for a second opinion before committing

If you’re unsure about a developer after an initial conversation, asking to speak with a past client directly, not just viewing a portfolio, is a completely reasonable request that a confident, established freelancer or agency should have no trouble accommodating for a serious potential client. A quick five-minute call with someone who’s actually worked with them tells you more than any number of polished case studies or curated testimonials ever could on their own, since a real past client will mention the small frustrations too, not just the highlights picked for a portfolio page.

Why one red flag alone isn’t always disqualifying

A single yellow flag, a slightly thin portfolio, a first-time freelancer without years of testimonials yet, doesn’t automatically mean walk away. Everyone starts somewhere, and a newer developer with clear communication, honest pricing, and a written scope can still be a great choice, sometimes even a better value than an established name coasting on reputation. The real concern is multiple red flags stacking together, vague pricing plus pressure to decide immediately plus no written scope, which together paint a much clearer picture than any single warning sign taken entirely on its own, and that combined pattern is what’s actually worth walking away from before any money changes hands.

Every project here starts with a free scope call and a written, fixed-price proposal before anything gets charged.