Where AI fits in your GTM stack
The hard call isn't "should we use AI" — it's "which workflows are safe to fully automate, which need a human in the loop, and which still need to be human-led." The lines below are how I split it inside actual production engagements.
Comparison of GTM tasks suitable for AI-led automation, hybrid AI plus human workflows, and human-led work across content production, lead enrichment, community monitoring, sales outreach, and analytics.| Workflow | AI-led | Hybrid | Human-led |
|---|
| Content production | Repurposing one post into 6 channels; SEO drafts; transcript cleanup | Outline + first draft AI; angle, voice, opinion human | Founding-story essays, controversial POV, exec ghostwriting |
|---|
| Lead enrichment | Technographic + firmographic appending; GitHub/Stack Overflow scraping; tiering | AI tiers and drafts message; human approves before send | Champion-level account research; board-level intros |
|---|
| Community monitoring | 24/7 listening across Reddit/HN/Discord; sentiment classification; FAQ triage | AI surfaces; DevRel chooses what to engage and how | High-stakes incident response; founder-level engagement |
|---|
| Sales outreach | Sequence variant testing; deliverability monitoring; CRM sync | AI drafts personalization; AE approves and sends from their inbox | Discovery calls; champion building; pricing negotiation |
|---|
| Analytics & reporting | Anomaly detection; daily summaries; auto-generated dashboards | AI surfaces signals; PMM interprets and decides next experiment | Strategic narrative for board decks; root-cause investigation |
|---|
Split based on workflows I actually run inside the open-source DevRel Origin pipeline and the production retainer extension. Some hybrid rows move left (more AI) every quarter as model quality improves.