AI Engineering, Small Teams, and Public Demo Days at Omni

<p>What happens when AI changes more than coding speed?</p><p><br></p><p>Chris Merrick, Co Founder and CTO at Omni, explains how his engineering team is adapting around AI, autonomy, product ownership, and a lighter operating model.</p><p><br></p><p>Omni has about 25 engineers working in groups as small as one to three people. Engineers are expected to make product decisions, move without waiting for detailed specifications, and show unfinished work during a weekly company demo day.</p><p><br></p><p>Those demos are also posted publicly. Customers watch them, join betas, and see features often move into production soon after.</p><p><br></p><p>Chris also shares how Claude Code changed development across the team. Commits to main increased roughly two to three times without comparable team growth, but the added output created another constraint: code review.</p><p><br></p><p>Takeaways</p><p><br></p><p>• Small teams can operate with less process when engineers have real ownership.</p><p>• Public demos create feedback loops between engineers, customers, and the rest of the company.</p><p>• AI can increase engineering output while moving the bottleneck somewhere else.</p><p>• Token costs still matter when AI usage scales across products and engineering teams.</p><p><br></p><p>Key Moments</p><p><br></p><p>01:15 Building AI into the engineering workflow</p><p>03:38 Why Omni works in teams of one to three engineers</p><p>06:48 The weekly demo day that replaces heavier process</p><p>10:29 Why Omni publishes unfinished product demos publicly</p><p>17:14 Measuring AI engineering productivity through commits to main</p><p>19:52 When token economics start affecting engineering decisions</p><p><br></p><p>One Line That Stuck</p><p><br></p><p>“I’m not married to the process. I’m married to the outcomes.”</p><p><br></p><p>Follow The Tech Trek for more conversations about how modern engineering and product teams are changing.</p>