Most bad-developer stories go the same way: the money is sent, the deadline passes, there is no website, and the developer stops replying. Here are 12 red flags that help you avoid web developer scams and spot this scenario before you pay, and a plan for what to do if it has already happened.

Why website scams are so common

The client usually knows little about development and cannot check what the work really costs or how long it takes. The result shows up weeks later, and until then you have to take someone at their word. Scammers use this, and so do developers who took on more than they can deliver.

The good news is that nearly every problem is visible in advance. If a developer passes the checks below without fuss, your risk drops sharply. If not, it is better to lose a week finding someone else than to lose your money and half a year.

12 red flags

1. They want 100% upfront

Once the developer has the full amount, they have no reason to hurry and you have no leverage. Even an honest developer may drift toward a project where the money is still ahead.

What to do instead: pay in stages, each ending with a clear result such as a prototype, finished design, or a working version on a test address. Payment schemes are covered in detail in “Prepayment and staged payments”.

2. They register the domain and hosting in their own name

It is framed as “for convenience”. In practice, whoever the domain is registered to owns it. In a dispute, the site can be switched off or redirected, and you lose the address already printed on your cards and signs.

What to do instead: register the domain, hosting, and every paid service to yourself or your company. The developer only needs access.

3. They work without a contract

“We agreed in the chat” sounds friendly until there is a dispute. Without a contract, it is unclear what exactly is included, when it is due, and who owns the result.

What to do instead: sign a contract with the brief attached, plus stages, deadlines, and an acceptance procedure. The essential clauses are listed in “A website development contract”.

4. “A website in three days for pennies”

A proper business website cannot be built in three days. Someone has to understand the task, agree on the structure, design the screens, add content, and test it. A price that is too low means a template with your logo swapped in, extra charges later, or a developer who never plans to finish.

What to do instead: compare quotes by scope of work, not just the total. Ask what is included in the price and what is not.

5. The portfolio cannot be verified

Nice pictures with no links, sites that “have since closed”, projects “under NDA”. Sometimes that is true, but if nothing at all can be checked, be careful.

What to do instead: open live projects, ask what exactly the developer did, and ask for at least one client contact. How to do this is covered in “How to check a developer’s portfolio and reviews”.

6. They pressure you to pay now

“The discount ends today.” “Someone else will take your slot if you don’t pay tonight.” Urgency is there so you don’t have time to think and compare.

What to do instead: take a pause. An honest developer will wait a couple of days while you read the contract and compare offers.

7. The estimate is vague

“Turnkey website: $2,000” with no breakdown. A month later it turns out the contact form, the mobile layout, or the admin panel “were not included” and cost extra.

What to do instead: ask for an itemized estimate: which pages, which features, how many rounds of revisions. Discuss anything not on the list up front.

8. They refuse to show work in progress

“We’ll show you everything at the end, it’s more impressive.” For months you see nothing, and at the end you get something you didn’t expect, or nothing at all.

What to do instead: agree on regular demos: prototype, design, a working version on a test address you can open yourself. At NOVO, for example, we start every project with a prototype so the client sees the main screens before development begins.

9. Hidden recurring payments

The build price is low, but after launch a bill arrives for “platform maintenance”, a “license”, or overpriced hosting. You can’t say no, because the site only runs on that developer’s setup.

What to do instead: before signing, ask which payments come after launch, how much they cost, and whether you can move the site to another provider without losing anything.

10. A template sold as custom work

You pay for a “unique design” at custom prices and get a ready-made theme that costs very little. A template is not bad in itself. It is bad when you are charged as if it was built from scratch.

What to do instead: ask directly whether the design will be made for you or taken from a template. Both are fine if they are named and priced honestly.

11. Access is held hostage

Passwords for the admin panel, hosting, and email are promised “after full payment”, then “after the next stage”. While the developer holds the access, you can’t switch providers or even get your own materials back.

What to do instead: write into the contract which accounts and files you receive, and when. A full list of what the owner should have is in “Who owns your website”.

12. Only a personal messenger and no paperwork

No company or registered business, no invoices or acceptance acts, payment to a personal card, one single contact. If that account disappears, so does the developer.

What to do instead: find out who you are dealing with: name, business status, payment details. Pay against invoices and sign an acceptance act for each stage.

How to vet a web developer in one evening

Before you pay, take a few simple steps:

  • search the studio or developer name together with words like “reviews” and “scam”;
  • open two or three portfolio projects on your phone and try to submit a request;
  • ask to see a draft contract and an itemized estimate;
  • ask whose name the domain, hosting, and, for an app, the App Store and Google Play accounts will be in;
  • ask a few questions about their process and notice how specific the answers are.

The main rule: at every stage you should have something that stays with you even if the developer disappears tomorrow. Access, files, a signed act, a working version.

What to do if a developer took your money or disappeared

The developer vanished, deadlines slipped by months, or access is withheld. Act calmly and step by step.

Collect evidence

Save the full conversation, with screenshots showing dates and the other person’s name. Messengers let you export chat history: do it before the developer’s account is deleted. Separately gather all payment confirmations, the contract, invoices, acts, mockups, and any files they sent you.

Check who owns the domain and hosting

Any domain lookup service will show when the domain was registered and when it expires. If it is not in your name, contact the registrar: they have a transfer procedure, which usually requires confirmation from the owner or supporting documents. Also check whose hosting account it is and who pays for it.

Request access in writing

Send the developer a calm email or message with a list: domain, hosting, admin panel, source code, design files, email, analytics. Set a reasonable deadline for a reply. A written request is useful if things go as far as a formal claim.

Save whatever still works

If the site still loads, make a copy and save the texts and images. Change passwords wherever you have access, and remove the developer’s access to your email, ad accounts, and payment services.

Decide on next steps

If the amount is significant, show the contract and correspondence to a lawyer, who can tell you whether a claim makes sense and what your options are. If you paid by card, ask your bank whether the payment can be disputed. Meanwhile, ask another developer to assess what can be saved and what is easier to rebuild.

In short

  • Pay in stages, not everything upfront, and get a result you can open and check for each stage.
  • Register the domain, hosting, and all accounts in your own name from day one.
  • Sign a contract with a brief and an itemized estimate.
  • Don’t give in to pressure, and don’t trust prices that look too good.
  • If you have already been deceived, first collect the correspondence and payments, then request access in writing, and for a large sum talk to a lawyer.