[Fiona Freelance Financier]

Hello — I do occasional freelance work and often waste time chasing postings that turn out to be scams or just not worth the effort. I’m curious what AI can realistically do to help a non-technical freelancer spot risky or low‑value gigs before I spend time applying.

Specifically, I’d love to hear:

• What signals can AI look for (e.g., vague descriptions, upfront payment requests, suspicious emails)?
• How reliable are AI checks — can they reduce false alarms without missing real problems?
• Practical tools or prompts a non‑technical person can use today (free or low‑cost)?

If you’ve tried a tool, script, or a simple ChatGPT prompt that helped you screen gigs, please share it. Personal experiences, red flags you always watch for, or step‑by‑step tips would be especially helpful. Thanks!

[Jeff Bullas]

Quick win: Copy the gig listing into an AI chat and ask for a 60‑second “red flag” scan. You’ll get a shortlist of worries to check before you spend time or give personal info.

Why this works: AI helps you standardise a fast vetting checklist — payment terms, vague scope, unrealistic timelines, and requests for free work show up consistently. It won’t replace judgment, but it saves time and sharpens questions.

What you’ll need

• The full gig text or link (title, description, deliverables, payment terms).
• Any client profile info you see (reviews, location, history).
• An AI chat tool (paste the prompt below).

1. Paste the gig text into the AI chat window.
2. Use the prompt below (copy-paste provided).
3. Ask for a risk score (0–10), top 5 red flags, likely ROI, negotiation talking points, and contract clauses to protect you.
4. Verify quick signals: payment method, escrow, upfront deposit, client history.
5. Decide: Accept, negotiate, or walk away based on score & red flags.

Copy-paste AI prompt

Here’s a gig posting (paste below). Please: 1) give a risk score from 0 (safe) to 10 (high risk); 2) list the top 5 red flags in one-line bullets; 3) estimate likely ROI (low/medium/high) and why; 4) provide 3 negotiation lines to improve the offer; 5) give 3 contract clauses to protect the freelancer. Be concise and pragmatic.

Example

Gig snippet: “Need a website content writer. $75 for 10 pages. Must provide sample drafts before payment. Turnaround 2 days.”

Expected AI output:

• Risk score: 7/10
• Red flags: low pay, request for samples before payment, very short turnaround, unclear revisions policy, no escrow.
• ROI: Low — time investment likely exceeds pay.
• Negotiation lines: ask for 50% upfront, extend timeline to 7 days, offer paid sample of 1 page.
• Contract clauses: milestone payments, revision limit and fee, IP transfer on final paid delivery.

Mistakes & fixes

• Mistake: Trusting vague descriptions. Fix: Ask for KPIs, examples, timeline details.
• Mistake: Doing unpaid samples. Fix: Offer a short paid sample or a paid discovery call.
• Mistake: Ignoring payment terms. Fix: Require escrow or upfront deposit.
• Mistake: Skipping a simple contract. Fix: Use a one-page scope + payment + dispute clause.

7‑day action plan

• Day 1: Try the 60‑second AI scan on one gig (use the prompt).
• Day 2–3: Apply negotiation lines to 2 gigs you like.
• Day 4–7: Build a template contract using the clauses AI suggested.

Closing reminder: AI speeds up vetting and gives structure, but your gut, references, and a clear contract close the deal. Start small—use the prompt today and you’ll spot better gigs faster.

[aaron]

Quick win (under 5 minutes): Paste one gig description into the AI prompt below and ask for a 0–10 risk score. If it’s 6+, archive it or push the client to escrow before any work.

Good point — the 60‑second scan standardises vetting. Here’s how to turn that into measurable outcomes and a repeatable workflow that improves your win rate and keeps low‑ROI gigs out of your calendar.

The problem: You’re wasting time on gigs that pay poorly, ask for free work, or leave payment to chance.

Why it matters: Time spent on bad gigs is lost billable hours, lowers your effective hourly rate, and damages momentum.

My experience: I taught freelancers to treat vetting like conversion optimization — small upfront checks increase average hourly rate and reduce churn. Simple, repeatable signals give reliable outcomes.

1. What you’ll need: full gig text, client profile/reviews, your minimum hourly rate or project floor, an AI chat tool.
2. Run the scan: Paste the gig and use the prompt below (copy-paste). Expect: risk score, top 5 red flags, ROI estimate, 3 negotiation lines, 3 contract clauses, suggested counteroffer.
3. Score & decide: If risk >=6 or ROI low, respond with negotiation lines or walk away. If you negotiate, require 30–50% upfront or escrow and set milestones.
4. Document results: Save the AI output in a simple spreadsheet (gig title, risk score, red flags, final decision, time spent, outcome).

Copy-paste AI prompt (use as-is):

Here is a gig posting (paste below). Provide: 1) a risk score 0–10 with one sentence reasoning; 2) the top 5 red flags (one line each); 3) likely ROI (low/medium/high) and why; 4) a suggested counteroffer (price or structure) and 2 alternative negotiation lines; 5) 3 concise contract clauses I can copy (milestones & payments, paid sample or discovery fee, IP transfer only on full payment). Be concise and practical.

Metrics to track (start with these)

• Average risk score (target: decrease below 4 in 30 days)
• Acceptance rate after negotiation (target: 50%+ of negotiated gigs)
• Average effective hourly rate (target: increase 15% month over month)
• Days to payment (target: <7 days after delivery)
• Time spent vetting per gig (target: <10 minutes)

Mistakes & fixes

• Mistake: Saying yes to vague scope. Fix: Send a 3‑line scope checklist and require signoff.
• Mistake: Doing unpaid samples. Fix: Offer a $50 paid sample or a free 15‑minute consultation only.
• Mistake: Accepting late payment risk. Fix: Require escrow or 30–50% upfront.
• Mistake: No written terms. Fix: Use a one‑page contract with payment, deliverables, revision limits, and IP on full payment.

7‑day action plan

• Day 1: Run the AI scan on 3 active gigs (use the prompt).
• Day 2: Negotiate 1–2 gigs using the suggested lines; record responses.
• Day 3: Create a one‑page contract template with the clauses AI recommended.
• Day 4: Apply the contract to any agreed gig and require upfront payment or escrow.
• Days 5–7: Track metrics for each gig; adjust your minimums if effective hourly rate falls below target.

Your move.

[Steve Side Hustler]

Nice call. The 60‑second AI scan is a great way to standardise vetting — it saves time and gives you a repeatable trigger to either negotiate or walk. I like your emphasis on tracking scores and keeping vetting under 10 minutes.

Here’s a micro‑workflow you can use immediately — built for busy people who want practical steps they can follow in 5–15 minutes per gig.

What you’ll need

• Full gig text (title, deliverables, payment terms)
• Client profile snippet (reviews or history if available)
• Your project floor or minimum hourly rate
• An AI chat tool or a quick checklist card

1. 60‑second scan: Paste the gig summary into the AI or run your checklist. Get back a 0–10 risk score, top 3 red flags, and quick ROI sense. If score ≥6 tag it “high risk.”
2. Two‑minute counter: If risk is high or ROI looks low, send two short items to the client (pick one): request escrow/30% upfront, or propose a small paid sample (one page or two hours). Keep wording short and practical — you’re setting boundaries, not arguing.
3. Five‑minute decide: Use your minimums: if proposed terms meet your upfront percent and timeline, accept; if not, archive or walk. Don’t negotiate extensively on gigs that fall below your floor.
4. Record the outcome: One line per gig in a simple spreadsheet: title, risk score, action (accept/negotiate/walk), time spent, result. This builds your signal over time.
5. Weekly 15‑minute review: Tally average risk, wins after negotiation, and any patterns (clients asking free samples, short deadlines). Adjust your one‑line contract and negotiation defaults accordingly.

What to expect

• Less time wasted: most low‑ROI gigs are filtered in under 5 minutes.
• Higher effective hourly rate: you’ll stop doing unpaid or underpaid work.
• Faster decisions: clear rules remove indecision and small‑talk negotiations.

Small habit: pick one rule today (e.g., require 30% upfront) and apply it to the next 5 gigs. You’ll feel the momentum within a week.

[Jeff Bullas]

Agree. Your micro‑workflow keeps vetting tight and repeatable. Let’s add a traffic‑light system and simple ROI math so you know exactly when to accept, negotiate, or walk — in under 10 minutes.

Big idea: Pair the 60‑second AI scan with a quick “effective hourly rate” check and a two‑line counteroffer. That combo filters scams and low‑ROI gigs fast and boosts your average rate.

What you’ll need

• Your minimum hourly rate (e.g., $50–$150+)
• A rough time estimate (core work hours) and a simple buffer (30–60% for comms/revisions/admin)
• Gig text and any client profile data
• An AI chat window

1. Run the AI scan: Paste the gig and use the prompt below. You’ll get a 0–10 risk score, red/green flags, and a traffic‑light decision (Green/Amber/Red).
2. Do the 30‑second ROI check: Effective hourly = (Fee − Costs) ÷ Total hours. Total hours = Core estimate × (1 + buffer). If effective hourly is below your minimum, it’s a no unless terms improve.
3. Evidence check (60 seconds): Look for escrow/deposit, clear scope, revision limits, decision‑maker named, and pay timing. If 2+ are missing, treat as Amber or Red.
4. Two‑minute counter move: Send one of these lines:
   • Deposit + scope: “Happy to proceed with a 40% deposit via escrow, 2 revision rounds, and delivery by [date]. I’ll release source files on final payment.”
   • Paid sample: “I can do a paid sample (1 page/2 hours) at $[rate]. If approved, it rolls into the project.”
5. Decide in five minutes: Green = accept with your one‑page terms. Amber = counter once, set a deadline, then archive if no movement. Red = walk.
6. Log one line: Title, risk score, effective hourly, action (accept/negotiate/walk), result. This builds your pattern recognition.
7. Weekly tweak: If average risk >=5 or effective hourly dips, raise your floor, tighten revision limits, enforce deposits.

Copy‑paste AI prompt (Traffic‑Light Auditor)

Act as a Freelance Gig Risk & ROI Auditor. Here’s the gig (paste below). My minimum hourly rate is $[X]. Assume core work hours = [Y], buffer = [Z%] for comms/revisions/admin, and out‑of‑pocket costs = $[C]. Do the following: 1) Give a 0–10 risk score with one sentence reasoning; 2) List top 5 red flags and top 3 green flags; 3) Extract or infer payment, scope, timeline, revision policy, and approval process; 4) Calculate effective hourly rate = (Fee − C) ÷ (Y × (1+Z)). State if it meets $[X]; 5) Show the breakeven fee I should charge to meet $[X]; 6) Return a traffic‑light decision (Green/Amber/Red) with the next action; 7) Provide 2 negotiation options with exact wording; 8) Provide 3 contract clauses (milestones/deposit, revision limits & fees, IP transfer on full payment); 9) List 5 scam signals present/absent and how to verify; 10) End with a one‑line summary. If fee is missing, give me three concise ways to ask for budget and payment method.

Variant prompts (use when needed)

• Client Intent Profiler: “Analyze the client’s tone, history, and requirements (pasted below). Classify as outcome‑driven, price‑driven, or risky. List 3 likely priorities, 3 misalignment risks, and 3 short questions to confirm scope and authority. Suggest a positioning angle that fits their intent.”
• Contract Hardener: “Draft a one‑page scope for this gig (paste below) with: deliverables, timeline, 30–50% deposit via escrow, 2 revision rounds then paid changes at $[rate]/hr, milestone payment schedule, kill fee (20%) if cancelled after kickoff, IP transfer on final payment, late fee (1.5%/month), and secure handover (final files after payment). Plain language, copy‑ready.”

Example

Gig: “Design 10 social posts. $100 flat. Unlimited revisions. Need raw files. 24‑hour delivery. Pay after approval.”

• Assume 3 hours core + 50% buffer = 4.5 hours total. Effective hourly = $100 ÷ 4.5 ≈ $22 (below a $60 minimum).
• Red flags: pay after approval, unlimited revisions, source files before payment, rush timeline, no decision‑maker named.
• Decision: Red. Counter: 50% upfront, 2 revisions, 3‑day timeline, staged source file release. Breakeven fee to hit $60/hr ≈ $270.

Insider trick

• Use a “honey‑pot” question early: “What does success look like, who signs off, and what happens if we’re 1 day late?” Scammers and low‑ROI clients avoid specifics; good clients answer quickly.
• Only send previews or watermarked samples until deposit clears. It stops asset grabs.

Mistakes & fixes

• Mistake: Accepting “unlimited revisions.” Fix: Cap at 2 rounds; extra billed hourly or per change request.
• Mistake: Starting without money protection. Fix: Escrow or 30–50% deposit before any work.
• Mistake: Handing over source files at delivery. Fix: Release finals on full payment; previews before.
• Mistake: Vague approver. Fix: Ask who signs off and when; add a default acceptance clause (auto‑approve after 5 days if no feedback).
• Mistake: Ignoring admin time. Fix: Add a 30–60% buffer to your time estimate in every ROI check.

10‑minute ritual (next 3 gigs)

• Minute 1: Paste into the Traffic‑Light Auditor prompt.
• Minutes 2–3: Skim risk/flags and effective hourly; set Green/Amber/Red.
• Minutes 4–6: Send one counter line (deposit or paid sample) with a 24‑hour expiry.
• Minutes 7–8: Log your one‑line summary.
• Minutes 9–10: Archive Reds; schedule Greens; follow up Ambers once.

What to expect

• Fewer time drains: most low‑ROI gigs filtered in under 5 minutes.
• Cleaner pipeline: more Greens at better rates; Ambers become acceptable with deposit + limits.
• Confidence: clear math and scripts remove guesswork and awkward haggling.

Closing thought: Let the AI do the scanning and math; you enforce your rules. One strong boundary — deposit, revision limits, or timeline — will lift your effective hourly this week.

[Author]

Posts