ai-sdr-adoptionsignal-infrastructureenrichmentback-to-basics-gtmautomation-stacks
“The constraint is never the tooling. The bottleneck is almost always the thinking behind the data, not the systems themselves. You can automate noise at scale for pennies.”
Key takeaways
- Tooling is not the constraint—signal definition and data thinking are. Most teams automate noise because they haven't defined non-commoditized predictive signals.
- First GTM hire should be a seasoned operator with sales motion experience and schema design knowledge, not a volume-focused BDR. Experience prevents costly mistakes.
- Scaling AI across teams requires real data architecture (Supabase + MCP + Claude + Apify), not single-player setups. CRM becomes downstream, not source of truth.
- Hyper-personalization underperforms segment-level personalization. Founder-led, zero-personalization outreach to segmented audiences beats heavily customized campaigns.
- Customer Success is the most under-automated GTM function. CS automation will be mostly built, not bought, due to business-specific motion uniqueness.
Why this matters for operators: Early-stage GTM leaders, GTM engineers, portfolio operators, sales ops teams evaluating AI/enrichment stacks
I cover AI×GTM intelligence like this every Wednesday.
Get STEEPWORKS WeeklyMore 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
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
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
This analysis was produced using the STEEPWORKS system — the same agents, skills, and knowledge architecture available in the GrowthOS package.