# AI OSINT Operator's Playbook ($39) — Gumroad Page Copy
# 3 title + first-paragraph variants for A/B testing

---

## Variant A — leads with the keyword (AI OSINT Playbook)

**Title:** AI OSINT Operator's Playbook — A Step-by-Step Investigation Guide for Claude and ChatGPT

**First paragraph:**
AI OSINT investigations fail not because of the tools, but because of the process. Analysts jump straight to running queries, get back unstructured output, lose the thread, and produce reports that can't be defended. The AI OSINT Operator's Playbook gives you the end-to-end process: how to scope a target, which tools to use in which order, how to chain findings, how to verify before documenting, and how to write a report that stands up.

---

## Variant B — leads with the audience (operators)

**Title:** AI OSINT Operator's Playbook — How Practitioners Use Claude and ChatGPT for Real Investigations

**First paragraph:**
Pentesters, investigators, and analysts who use AI for OSINT all hit the same wall: the model is capable, but there's no systematic way to drive it. This playbook closes that gap. It's a practitioner guide — not a primer on what OSINT is, but how to actually run an AI-assisted investigation from first contact to final report, with decision trees, pitfalls, and worked examples.

---

## Variant C — leads with the problem (unstructured output)

**Title:** AI OSINT Operator's Playbook — Turn Unstructured AI Output Into Defensible Intelligence

**First paragraph:**
The problem with AI-assisted OSINT isn't generating output — it's trusting it. Without a verification step, you can't tell what's real. Without a documentation step, you can't share your work. The AI OSINT Operator's Playbook gives you the full investigation workflow: scope, collect, pivot, verify, document, and report — with explicit checkpoints so you know when to move forward and when to stop.

---

## Full body copy (use with any title variant)

### The pain

Most AI OSINT workflows collapse at the verification stage. You get a hit, assume it's real, build on it, and end up with a report full of confidently stated nonsense. Or you never structure the investigation at all — you ask the model questions, it answers, you move on, and at the end you have a chat transcript instead of intelligence.

### Who this is for

- Pentesters who need a repeatable recon methodology they can document
- Bug bounty hunters building a structured pre-engagement workflow
- OSINT analysts running long-form investigations on people, companies, or infrastructure
- Threat intelligence practitioners adding AI to an existing workflow

Not for complete beginners who have never run a manual OSINT investigation. This assumes you know what WHOIS, email enumeration, and Shodan are.

### What's inside

- **The investigation framework** — the 5-stage loop (scope, collect, pivot, verify, document) with decision points and exit criteria at each stage
- **Target-type playbooks** — specific workflows for email, username, domain, IP, phone, and company investigations
- **AI driver guide** — how to give Claude/ChatGPT instructions that produce structured, auditable output rather than prose summaries
- **Verification matrix** — tool-by-tool breakdown of what each source proves, what it can't prove, and minimum corroboration requirements
- **Report templates** — tactical format (pentest reports) and analytical format (intelligence products)
- **Ethics and legal checklist** — jurisdiction-level breakdown of what you can and can't do with public data

### The concrete result

You run an investigation using the playbook's stage-by-stage structure, verify every finding against the corroboration threshold, and produce a report that is source-documented, confidence-rated, and defensible. The whole workflow takes less time than your current ad-hoc approach, and the output is better.

---

## CTA / button label

**Get the playbook — $39**
