Personal Productivity & AI-Augmented WorkLenny's Newsletter
I gave Claude Code our entire codebase. Our customers noticed. | Al Chen (Galileo)
Why I picked this
So risky, but the grounding and ROI makes sense
ai-coding-toolscursor-vs-copilotautomation-stackspkm-workflowssecond-brain
“Despite never having held an engineering role, Al has built a system using Claude Code to query 15 separate repositories and deliver hyper-personalized answers that would otherwise require constant engineering support”
Key takeaways
- Non-technical field engineer eliminated engineering support bottleneck by giving Claude Code access to entire 15-repo codebase, creating self-service technical answers
- Code as source of truth beats documentation - current codebase provides more accurate answers than static docs, especially for complex multi-repo architectures
- Customer quirks system creates hyper-personalization at scale - combining repo context with Confluence, Slack, and customer-specific deployment patterns turns single questions into reusable knowledge
- Information organization matters less in AI era - ability to query unstructured codebases directly reduces need for meticulous documentation and knowledge management
- Simple 16-line Claude-written script keeps all repos updated automatically, maintaining fresh context for accurate answers
- Virtuous loop effect: customer-facing teams querying codebase directly reduces engineering interruptions to near-zero while improving answer quality and speed
Why this matters for operators: B2B companies with technical products struggling with customer support scalability and engineering team interruptions
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.