The Role of CTO in AI Companies (Mohit Aron)

Why Your API Is Your Moat (Mohit Aron)

Mohit Aron has spent nearly 20 years watching technology shifts play out, and his read on AI moats is blunt: the fundamentals of competitive advantage haven't changed, the tools just have. Most founders are asking the wrong question entirely. With AI agents increasingly acting as the primary interface between users and software, Mohit breaks down exactly where durable value lives, why the "SaaS is dead" crowd is conflating two very different things, and why most AI-native ERP and CRM startups are walking into a market positioning trap they don't see coming. Topics discussed: * API depth as the primary moat for AI agents, not data or model fine-tuning * Why "SaaS is dead" confuses the UI layer with the underlying service value * Ecosystem interoperability as a moat that wipe-coded clones cannot replicate * Why early-stage startups should use vanilla LLMs before touching fine-tuning * The SMB gravity trap pulling AI-native enterprise challengers permanently down-market * Working backwards from go-to-market motion before designing the product * The insertion point strategy for breaking into enterprise without trying to replace incumbents directly

The Role of CTO in AI Companies (Mohit Aron)

Most CTOs talk about AI productivity gains in the abstract. Mohit Aron, Founder of Cohesity and Nutanix, has a concrete system — one he built by taking his pre-AI coding methodology and mapping AI directly onto every phase of it. He still writes unit tests, runs two coding agents in parallel for different tasks, and has a firm view on why hiring for AI fluency before engineering fundamentals is a trap that will cost you. In this conversation with Ashish, Mohit shares his full AI-assisted development methodology — natural language spec first, then API boundaries, intermediate state, skeleton functions, implementation, and only then unit tests — and why skipping that order is exactly how teams end up owning code they don't understand. He also pushes back on blanket productivity claims: 20x gains are real for unit tests and pattern-heavy work, but design-heavy work with humans in the loop will see far less. And on the prediction that 90% of engineering jobs disappear in 18 months, he's not buying it — his company is still actively hiring, and good engineers remain hard to find. Topics discussed: * Early-stage CTO as player-coach: when to build alongside the team vs. step back * The 5-step AI coding methodology: spec, API, intermediate state, skeleton functions, implementation * Why open-ended AI prompting produces bad output and who is accountable when it does * Applying a looser review standard to AI-written unit tests vs. production code and why * Interviewing engineers without AI to test fundamentals — fluency is a bonus, not a baseline * Why high token usage means nothing if the output quality is poor * Running multiple coding agents in parallel and switching between them by task type * Why AI as a pattern matcher still requires strong engineers to catch what it gets wrong

Your First Sales Hire Is Wrong (Mohit Aron)

Mohit Aron has built two companies past $10B+ valuations and is now on his third. In this episode, he walks through the exact go-to-market playbook he has run each time, starting with why the founder has to be the primary seller early on, a practical necessity before messaging has been proven in the field. He also shares the three-scorecard hiring framework he uses across every go-to-market role, and a blind reference technique where you use a candidate's own provided references to find people they never intended to give you access to. Topics discussed: * Founder as primary seller until messaging is proven in the field * Product-market fit defined as: average rep sells to average customer without pulling in HQ * Why giving a CRO title early attracts mediocre candidates and sets them up to fail * Building geography-based pods first, then creating internal competition before hiring a leader * Three-scorecard hiring system: pre-interview resume screen, structured interview, and reference check * Using a candidate's own references to surface second-order contacts they never meant to share * Why pattern-matching leaders plateau and what first-principles thinking actually looks like in a sales org * Reassessing every leader at the two-year mark as the company's growth rate changes the job entirely

Culture as Competitive Advantage (Marcus Ryu)

Most founders delay culture work until later. Marcus Ryu made it foundational at Guidewire when they had no customers—because no one would talk to them about a non-existent product. That decision became their survival mechanism through a product failure, an existential lawsuit, and multiple breaking points. In this episode, Marcus distinguishes between moral values that matter under pressure and operational preferences that don't, explains why adversity binds teams more powerfully than success, and shares the specific practices—from value-citing in decisions to the quarterly "granite award"—that made culture a competitive advantage worth billions. What founders will learn: * Defining moral vs. operational values * The integrity, rationality, collegiality framework * Leading through product failures and lawsuits * Why shared sacrifice binds more than shared success * Creating reciprocal accountability with leadership * Making values dispositive, not debatable * Ritualizing difficult, unglamorous work * Why radical transparency is non-negotiable for startups

The Power of Agenda: Managing Your Board (Marcus Ryu)

Most founders approach board meetings like performance reviews: exhausting themselves trying to look good while board members gradually encroach into operational decisions. Marcus Ryu reveals this is a failure mode. In this episode, he reframes the board relationship from governance to advisory, explains why you have more power than you realize through "the power of agenda," and shares the specific practices that kept his board focused on cadence and accountability rather than marketing software decisions. From choosing who's in the room (worth far more than valuation points) to knowing when to escalate to a "code red" discussion, Marcus provides the framework for maintaining founder authority while leveraging board wisdom. What founders will learn: * Reframing boards as advisory, not governance * Using "the power of agenda" to control discussions * Why boards add little thrust but tons of drag * Selecting investors beyond valuation optimization * Keeping boards at 5-6 people maximum * Candor vs. radical candor with your board * When directors cross sacred CEO lines (team selection, culture) * Managing forecasting failures without losing authority * The 80% templated deck approach * Why two weeks of board prep is a failure mode