Detect Client Red Flags
Paste a client message and get an honest assessment of red flags, risks, and whether to take the job.
When to use
Use before replying to any job post, client inquiry, or project brief. Takes 30 seconds and can save you weeks of pain.
Recommended LLMs
When to use
Every time a new client or job post lands in your inbox. I run this before replying to anything. It's saved me from at least a dozen nightmare projects.
The things this catches: scope creep setups, "we have a small budget but big vision" clients, unrealistic timelines, projects where the client clearly doesn't know what they want, and the classic "we just need some small changes" on a legacy codebase.
Tips for best results
- Paste the full original message, not a summary — nuance matters
- Include any follow-up messages if you've already had a back-and-forth
- If the risk score is above 6, seriously reconsider. 8+ = walk away.
- Use the "If I Proceed" section as a checklist before signing anything
Expected output
Red flags listed with explanations, a risk score 1-10, a clear verdict, and a protection checklist if you decide to move forward despite the risks.
The Prompt
Copy it, paste it, use it.
You are a battle-hardened freelance developer who has worked with over 100 clients and seen every pattern — the good, the bad, and the catastrophic. Analyse the following client message or job post for red flags.
[CLIENT MESSAGE / JOB POST]:
{paste the full message or listing here}
Provide:
1. **Red Flags Found** — list each one with a brief explanation of why it's a problem. Be specific about what in the text triggered this flag.
2. **Green Flags** — anything that suggests this is a legitimate, well-scoped, reasonable client
3. **Risk Score**: 1-10 (1 = take it immediately, 5 = proceed with caution, 8+ = run)
4. **Verdict** — should I pursue this project? Give me a direct yes/no and the main reason
5. **If I Proceed** — 3-5 specific things I need to get in writing (contract clauses, clarifications, deposits) before starting
Be blunt. Don't sugarcoat it. I'd rather know upfront than deal with scope creep, payment disputes, or an endless revision loop 3 months in.