GTM OpsOutbound Kitchenby Elric Legloire - Outbound Chef

How Florin Tatulea Scales SDR Teams

Read original
back-to-basics-gtmhuman-first-salesai-sdr-adoptionsignal-infrastructure

“Of the 30,000 accounts that looked addressable, only about 6,000 were real”

Key takeaways

  • TAM vs SAM gap causes systematic over-hiring: 30K addressable accounts collapsed to 6K real targets, meaning most outbound teams are 5x oversized based on fantasy pipeline math
  • Don't hire SDRs before $1M ARR or PMF - contrarian stance against conventional 'hire sales early' wisdom, with specific threshold and reasoning about process vs person validation
  • AI companies (Anthropic, OpenAI, Clay) still hiring human SDRs despite building AI tools - signals that even AI-native companies see limits to full automation and value human-in-loop for complex sales
  • Hire 2 SDRs simultaneously to separate person from process - tactical framework to avoid false negatives when testing outbound motion, ensures you're testing the playbook not just individual performance
  • Build SDR teams like sports teams with complementary skills rather than cloning top performers - shift from 'hire 10 of your best rep' to intentional skill diversity and role specialization

Why this matters for operators: Founders/RevOps leaders sizing outbound teams and evaluating when to hire first SDR

I cover AI×GTM intelligence like this every Wednesday.

Get STEEPWORKS Weekly

More picks

AI DevelopmentLenny's Podcast

Humans will keep inventing new reasons why we must stay in the loop with agents

  • Human resistance to full AI autonomy is not purely technical—it's psychological and organizational; companies will rationalize keeping humans in decision loops even when agents are capable
  • The 'human-in-the-loop' requirement may become a self-perpetuating narrative rather than a genuine necessity, driven by organizational risk aversion and change resistance
  • Product leaders at scale (Notion) are observing this pattern, suggesting it's a widespread phenomenon across enterprise AI adoption, not isolated to specific use cases
ai-agent-adoptionhuman-in-the-loopai-governance
Read original Full analysis →
GTM Ops**RevOps Impact (Jeff Ignacio)

Comp plans for consumption pricing

  • Consumption pricing fundamentally breaks traditional SaaS comp models—requires rethinking sales incentive structures around usage vs. contract value
  • Four distinct contract structures exist (pay-as-you-go, uncommitted, committed, hybrid), each requiring different compensation mechanics and sales behaviors
  • Enterprise consumption-based deals create tension: customers want flexibility, sales teams need predictability for quota attainment—comp design must bridge this gap
revenue-platform-consolidationconsumption-pricing-modelssales-comp-design
Read original Full analysis →
AI×GTMGTM OS: The Future GTM Operator

3 revenue motions your AI is only half wired into

  • Model parity has arrived: OpenAI/Claude now trade evenly on core tasks, making 'better AI' a non-differentiator—the edge shifts to integration depth into existing revenue motions
  • Waste is quantified: teams paying $17K-$37K/month for AI seats that never touch pipeline generation; real cost is opportunity cost of unused capacity, not subscription fees
  • Lean teams have a structural advantage: cannot out-buy larger competitors on model access, but can out-embed them by wiring AI 1 revenue motion deep (pipeline → content → deals) with proprietary deal context competitors haven't seen
ai-sdr-adoptionrevenue-platform-consolidationback-to-basics-gtm
Read original Full analysis →

This analysis was produced using the STEEPWORKS system — the same agents, skills, and knowledge architecture available in the GrowthOS package.