The pattern behind most bad jobs
Almost every "the client disappeared" or "the client wouldn't pay" story has something in common: the warning sign was visible in the job post before the proposal was ever sent. Not always obvious, but visible — if you know what to look for. This isn't about being suspicious of every client. It's about spending thirty seconds screening a post before you spend hours writing a proposal and days doing the work.
The signals worth checking
No budget, and no willingness to give one
A client who won't commit to a number — not even a range — is disproportionately likely to be the same client who disputes the price after the work is done, or ghosts when the real number lands higher than the number they had in their head but never said out loud. This isn't universal, but it's a real correlation worth weighting.
Scope that's described only in outcomes, never in specifics
"I want an app that does everything my competitor's app does" with zero detail on what that actually means is a job where the definition of "done" will keep moving, because it was never fixed in the first place. If a client can't describe their own project specifically, that's a preview of what it'll be like to get sign-off on your work later.
Urgency paired with vagueness
"Need this ASAP" combined with a post that has almost no detail is a common combination in low-quality jobs — the urgency pressures you to skip your normal scoping questions, and the vagueness means you're agreeing to something undefined under time pressure. Genuine urgency and genuine detail aren't mutually exclusive; a rushed job with a real deadline usually still comes with real specifics, because the client has actually thought about what they need.
A history of short jobs with no reviews, or reviews that mention disputes
If the client's history shows several short-lived engagements or a pattern of Smiths not sticking around, that's not proof of anything on its own — but it's a pattern worth being extra careful with, especially around getting scope and payment terms explicit before starting.
Requests to discuss "the real details" off-platform
Covered in more depth elsewhere, but worth repeating as a standalone red flag: a legitimate client has no reason to need you off Smith before you've even started. If a job post or an early message pushes toward WhatsApp, email, or a call to "figure out the real scope," treat that as a signal to slow down, not speed up.
Payment structure that skips milestones on a large job
If a client explicitly wants to pay the whole amount only at the very end of a large job, with no milestones — that's not automatically a scam, but it's the structure most likely to end in a dispute if anything goes wrong partway through. Suggesting milestones yourself, and watching how the client responds, is itself useful information.
None of these are automatic disqualifiers
A single vague post isn't proof of a bad client — plenty of good clients just aren't experienced at writing job posts, especially first-time posters. The point isn't to skip every imperfect post. It's to notice the signal and adjust accordingly: ask the clarifying questions before you apply instead of after you're hired, propose milestones explicitly rather than assuming they'll happen, and get budget and scope confirmed in writing before you start rather than treating a vague post as a green light to just start guessing.
What to actually do about it
If you spot one of these signals and you're still interested in the job, don't skip it — just close the gap yourself. Ask the missing question directly in your proposal: "What's the budget range for this?" or "Can you clarify what 'done' looks like for this feature?" A client who answers clearly is telling you the vagueness was inexperience, not evasiveness. One who doesn't answer at all is telling you something too.
The one-line version
The warning signs are visible before you apply — no budget, outcome-only scope, urgency without detail, off-platform pressure, no milestones on a big job. Screen for them, ask the missing question directly, and let the answer decide whether you proceed.