Disappearance almost never happens suddenly — it has a run-up of about two to four weeks, and the first reliable signal is that reply times lengthen while nothing viewable appears. Read the sequence below; the useful action is to stop paying, not to chase harder.
The reassuring part first
You’re watching for something that gives notice. Complaint accounts describe a consistent arc: replies within minutes during the sale, then hours, then only after two follow-ups, then nothing. Nobody in those accounts describes a vendor who was fully engaged on Tuesday and gone on Wednesday.
Which means the fear is manageable. You’re not waiting for a coin flip; you’re watching for a pattern with a beginning.
The seven signals, in order
1. Reply times lengthen. Minutes become hours, then a day. This is the earliest signal and the most reliable, because it appears before any deadline is missed.
2. Updates become descriptions instead of links. “Working on it” replaces “here’s the page.” A build in progress can always be shown, so this substitution is informative.
3. A staging link is promised and doesn’t arrive. Once, fine. Twice, that’s the signal.
4. Reasons arrive without new dates. Festival, exam, another client’s urgent work. Each may be true. What matters is whether a revised date comes attached — a reason without one is a stall.
5. A second revised date slips. A first slip is normal. When the revised date also moves, the estimate was never real.
6. More money is requested before anything viewable exists. This one is serious enough to stop payments over on its own.
7. Replies only come after two follow-ups. By this point you’re managing the relationship rather than receiving a service, and the trajectory is set.
| Signals present | Where you are |
|---|---|
| 1 only | Possibly just a busy week. Ask for a link |
| 1–3 | Drifting. Ask for a date and a link, in writing |
| 1–5 | The estimate was wrong. Stop further payments |
| 6 or 7 present | Escalate in writing and plan an exit |
What to do at each stage, briefly
Early (1–3): send one message that accepts the situation and asks for the consequence. “Understood. What’s the new date for [deliverable], and can you send the staging link so I can see where it is?” Polite, unarguable, and it produces either an answer or a pattern on record.
Middle (1–5): stop paying. Any instalment still outstanding stays outstanding until something viewable exists. Put the request in writing with a date.
Late (6–7): written escalation with a deadline, and a decision about whether to continue. Don’t send more money to unlock progress — that’s the specific pattern complaint records document.
The log that makes this concrete
Open a note and record four columns: date, what was promised, what arrived, reason given. Two minutes a week.
Three things come of it. You stop wondering whether you’re being unreasonable — the list either shows a pattern or it doesn’t. You can quote specifics rather than complain generally, which changes the conversation. And if this ends in a refund request or a claim, a dated log of promises against deliveries is the strongest document you’ll have.
Why this fear should be smaller than it is
Because the four structural terms make disappearance survivable rather than catastrophic:
- Domain registered in your own account before hiring — so their exit doesn’t take your business name.
- Advance of 20–30% — so the loss is bounded.
- Payments against stages you can open — so you stop at the first signal rather than the last.
- Written scope — so you know exactly what wasn’t delivered.
With those in place, a developer disappearing at signal five costs you 30% of a modest project and three weeks. Without them it costs everything, which is why the fear feels disproportionate — it’s tracking the exposure, not the probability.
The fair caveat
Some genuinely capable developers are badly organised rather than dishonest. They’ll finish, late, and the work will be good.
The distinction is progress you can see. Excuses attached to a visible, advancing staging link are inconvenient. Excuses attached to nothing are the pattern on this page. If real progress exists, extending the timeline in writing usually beats switching — switching mid-build has its own cost and delay.
What to do this week
- Note where your project sits on the seven-signal list.
- Start the four-column log, backdated from memory.
- Ask for the staging link in one plain message.
- Hold any outstanding payment until something viewable exists.
- Confirm the domain is already in your own account.
If you want it done the certain way
You get a staging link from the first build day and twice-weekly updates with a link attached, so drift is visible in week two rather than week eight. Domain in your name, 30% advance, stage-linked balance. WhatsApp us; we reply in about five minutes between 9am and 7pm.
Related reading
- When replies go from minutes to days
- The excuse playbook of late developers
- Your developer is ignoring you: the escalation ladder
- How to spot a developer who might disappear
FAQ
What are the warning signs a web developer is about to disappear?
Lengthening reply times, updates that describe work instead of linking to it, a staging link promised twice and never sent, reasons given without revised dates, a second slipped deadline, and a request for more money before anything is viewable.
What should I do when my developer starts going quiet?
Accept the reason and ask for the consequence — a new date for a named deliverable plus the staging link. Stop any further payment until something viewable exists, and start logging promises against deliveries.
How do I make a developer disappearing less damaging?
Register the domain in your own account before hiring, keep the advance to 20–30%, tie payments to stages you can open on your phone, and get scope in writing. Those four turn a catastrophe into a bounded loss.
