# The AI SDR Playbook > [!question] Lingering Questions > - What defines a high-quality "signal," and how is freshness or false-positive rate measured? The whole targeting stage assumes signal quality that's never demonstrated. > - The productivity figures (15→2 minutes, 20→50 accounts) are illustrative, not measured — do they hold up under an instrumented A/B test, or are they marketing scenes? > - How transferable is the sales-signal model to community-led growth, where "buying intent" is fuzzier and consent matters more than in outbound sales? > [!tip] Article Ideas > - Port the targeting/sequencing/follow-up spine to community signals (forum posts, repo stars, docs searches) as a community-led-growth analogue to this sales playbook. > [!link] Cross Reference > - [[3. Resources/Permanent Notes/Automation Relocates Toil Into Supervision]] — a structurally opposite claim about the same move (routing work through automation); worth reading these two against each other rather than assuming they agree > - [[3. Resources/MOCs/DevRel MOC]] — the signal-based targeting model maps directly onto community-signal-driven advocate engagement > [!quote] Vocabulary > - **Signal** — a live buyer-behavior event (pricing-page visit, new VP hire, trial-activity spike) used to prioritize outreach, contrasted with static list-building > - **AEO / AI-native** — a workflow built to remove manual research and list-building work entirely, rather than bolting automation onto an existing manual process ## Author's thesis Outbound sales underperforms not because reps aren't working hard enough, but because a manual gap between "knowing who to reach" and "reaching them" swallows the day; an AI-native workflow that automates targeting, sequencing, and follow-up frees reps for the judgment and conversation work only humans can do — and exposes real skill gaps once busywork is gone. ## Key arguments (≤3) 1. **The bottleneck is manual work, not rep talent** — list-building, research, and signal-monitoring are described as mechanical tasks that "shouldn't require a human at all." 2. **Automation without a fixed foundation just scales the noise** — the piece explicitly warns that bolting AI onto a broken process produces "more noise, faster," not better outcomes. 3. **Removing busywork exposes coaching gaps a manager can no longer hide from** — once research and list-building are automated, the only remaining output is conversation quality, which is a skill problem, not a data problem. ## Claim atoms ### Outbound's real problem is manual work, not effort > [!quote] ID:rw_pending > the gap between knowing who to reach and actually reaching them is filled with manual work that shouldn't require a human at all **Context & use**: From "This is the real problem with outbound in 2026." Reframes the bottleneck from rep capability to system design — the load-bearing premise of the whole playbook. **Tags**: #xref <!-- atomicity: 1 idea ✓ --> ### Adding AI to a broken system just scales the noise > [!quote] ID:rw_pending > bolt AI onto a broken foundation and you don't fix the foundation, you just produce more noise, faster **Context & use**: Following the Monday-morning scene. The piece's strongest caution — automation amplifies whatever foundation it sits on, so fix targeting before adding volume. **Tags**: #xref #aphorisms <!-- atomicity: 1 idea ✓ --> ### AI as leverage handles mechanical work, not the human part > [!quote] ID:rw_pending > Handling the infinite, mechanical work, so the human can focus on the work that only a human can do **Context & use**: From "This is what AI as leverage actually means." Defines the human/AI division of labor — a reusable principle that transfers cleanly to DevRel and community work. **Tags**: #xref <!-- atomicity: 1 idea ✓ --> ## Permanent candidates - **Automation amplifies a foundation rather than fixing it** — the strongest candidate ([[#H2]]), and a general claim about automation that deserves its own note distinct from [[3. Resources/Permanent Notes/Automation Relocates Toil Into Supervision]] (which is about where the *toil* goes, not about whether the underlying process was sound to begin with). Promoted below, linked as a companion claim. ## Processing checklist - [ ] Cross-check the "AI as leverage" atom against the vault's existing AI-identity and effort notes for overlap - [ ] Draft a community-led-growth note porting the targeting/sequencing/follow-up spine to community signals - [x] Connect into the relevant MOC — [[3. Resources/MOCs/AI & the Future of Knowledge Work MOC]] - [x] Treated as vendor content throughout — claims about productivity gains are flagged illustrative, not evidenced ## Metadata - Source: [[3. Resources/Readwise/Articles/The AI SDR Playbook]] ## Links - [[3. Resources/MOCs/AI & the Future of Knowledge Work MOC]] — the human/AI division-of-labor framing ("AI as leverage") is directly about how AI reshapes what knowledge work looks like - [[3. Resources/MOCs/DevRel MOC]] — the signal-based targeting model is a ready-made template for community-led-growth and advocate-engagement design