Red flags

Avoiding low-quality clients before they cost you a week.

Bad clients rarely announce themselves. They arrive as exciting opportunities with flexible budgets and huge futures — and cost the average freelancer twelve to twenty hours in revision loops, ghosted samples, and chased invoices. The defense is a checklist applied before enthusiasm does your thinking.

The red flags, ranked by how much they've cost editors

Exposure compensation — “great for your portfolio” is rent-free only for the client. Pass unless the audience is provably massive and exactly your niche.
Revenue share instead of rates — unverifiable numbers, indefinite timelines. Rarely worth it without transparent analytics access AND a guaranteed floor.
Vague scope — “make it pop,” no length, no revision count. Undefined work expands into your nights.
Unlimited revisions requested upfront — a billing dispute scheduled for later. Standard is two rounds; say it early.
Urgency without budget — needed yesterday, price discussed after delivery. Inverted priorities predict inverted payment.
Editor churn stories — “our last three editors didn't work out.” Interview the pattern: it's usually the constant, not the variables.
Test-round mills — collecting free edits from several candidates for a project that may not exist. One scoped sample maximum, ever.
Payment strictly after delivery — for first projects, split it: half upfront via invoice, remainder on delivery. Professionals expect this.

Green flags worth prioritizing

Sponsorships already running — proven budgets, professional expectations, deadlines that mean something.
Consistent cadence — creators who post five times a week understand output and value editors accordingly.
Process fluency — they mention briefs, references, or feedback rounds unprompted.
Named ranges when asked — a straight answer to “what's the budget?” predicts a straight relationship.
Respects turnaround questions — how they treat your calendar pre-hire forecasts post-hire.

Two scripts for walking away cleanly

Editors stay polite because communities are small. Both scripts thank, decline, and exit — no lecture, no door-slamming.

Declining exposure-based work

Thanks for thinking of me! I keep paid and portfolio work separate —
this one sounds like the latter, so I'm not the right fit.
If a paid project comes up, I'd love to be first in line.

Declining unlimited revisions / vague scope

Happy to help — I quote fixed-scope: [format, length, two revision rounds]
at [rate]. If that structure works, I'll send the invoice and timeline.
If you need something more open-ended, another editor will suit you better.

Systemize the filter so saying no stays easy

Red-flag resistance is a full-pipeline phenomenon: you decline bad offers precisely when good leads exist elsewhere. That's why the filter lives inside the scoring routine — sub-4 scores never become pitches, red-flag combos override any number, and Weekly Goals keep fresh qualified leads arriving so no single “opportunity” feels load-bearing.

Frequently asked questions

Should I ever take revenue-share deals?

Rarely, and only with both guards up: direct access to the analytics that compute the share, plus a guaranteed minimum per deliverable. Without transparency, you're lending your craft to someone else's spreadsheet.

How do I decline without burning bridges?

Thank, name the structural mismatch (not their character), leave the paid door open. The scripts above do it in three sentences — communities remember grace longer than gigs.

What's a safe free-sample size?

Thirty seconds, watermarked, one round, delivered once — stated upfront in the pitch itself. If a prospect needs more than that to decide, the decision they're avoiding is hiring anyone at all.