AI DevelopmentSaaStr — Jason Lemkin

Amjad Masad and Me at SaaStr AI 2026: The Agents We Actually Built, and What Replit’s Founder Thinks Comes Next

Read original

Why I picked this

Especially the overall idea of reporting to agents

ai-coding-toolsautomation-stacksai-sdr-adoptionself-improving-agentsmono-repo-architecture

“The context window is now effectively infinite, and that changes everything. We run 10K perpetually. We never reboot it. The agent holds more context than any human ever could.”

Key takeaways

  • Context windows expanding from 16K to 1M+ tokens enables perpetually-running agents that never need rebooting, fundamentally changing agent architecture from ephemeral to persistent
  • Mono repo architecture (10 apps in one codebase) beats separate apps for AI agents because global context compounds - agent remembers how it built previous apps when building new ones
  • Self-improving agents are production-ready: Replit's internal agent autonomously reads traces nightly, generates PRs with prompt improvements, ships A/B tests, and loops back without human intervention
  • AI outreach quality has crossed human parity for B2B: Jason's agent drafted personalized VC emails with specific context (25 Replit attendees) that outperformed human-written versions
  • The '$257 employee' framing suggests dramatic cost reduction for knowledge work, though specific ROI calculation not disclosed in excerpt

Why this matters for operators: Companies building AI agents, evaluating Replit vs Cursor, designing agent architectures

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.