Dan and Ian Stokes-Rees, founder and CEO of PNI AI Studio, open by discussing the thesis of Ian's company: an opinionated stack of open-source tools wrapped in agentic AI so business analysts, managers, and finance teams can get the capabilities of a senior data scientist without learning Python, SQL, or R. Ian's primary target is financial services, where an estimated 200+ million weekly Excel users still run human-driven, tacit-knowledge processes. He frames a second opportunity, capturing the "AI exhaust" coming out of those workflows, as the seed for a follow-on product. The conversation turns to how Ian actually builds his product. Ian walks through a three-phase evolution: Cursor as a coding assistant, prompt-based Claude Code generation, and finally a full agentic team modeled on Steve Yegge's "Gas Town" post. Today he runs six to ten Claude Code agents in named roles. Xavier and Yasmin are Agile Process Managers, Anne is the Principal Architect. Now add in software engineers, QA engineers, a test engineer, and a release manager. The agents' operating manual is a roughly 5,000-line AGENTS.md tree spread across about 45 markdown files and served via MkDocs. The Kanban lives in GitHub Projects, milestones serve as sprints, story points and labels drive the workflow, and a "kaizen accumulator" task captures learnings each sprint that get translated into process changes at the start of the next one. Next up, diving into token-maxxing. Ian explains why he keeps hitting Claude Max 20x weekly limits on day three of a sprint — five software engineering agents plus two QA agents burning tokens in parallel — and the management tricks he's adopted: Caveman to enforce terse prompts, templated processes, a catalog of deterministic scripts behind self-documenting skills, pre-commit hooks, and roughly a dozen CI gates that run Claude and Codex reviews against PR templates. Still, not everything is perfect in agent-land. Ian describes his agents as "solid second quartile" engineers. They're fast, pleasant, and (currently) inexpensive, but wrong in meaningful ways on one PR in five. Vibe coding works for prototypes and small reports, but serious systems still need human-driven design thinking, separation of concerns, and testing discipline. Perhaps the current moment is an "interregnum" between 25 years of established software practice and an agent-native future. Could this one day be a software factory with human "forepersons" running follow-the-sun shifts over agents that never sleep? The episode closes with a warning about "AI brain fry" that comes from work products arriving ten times faster than humans produce them. Click here to view the episode transcript.
