S11 E18: Theodore Bergqvist, Turbotic

Episode Summary

Executive Summary: The episode follows Theo Berquist, founder/CEO of Turbotic, as he explains how the company evolved from enterprise orchestration into a leaner AI-powered "vibe automation" platform for non-engineers. He emphasizes rapid pivots, focused feature scope, team reshaping, and the need to prioritize product-market fit over premature scaling. The conversation frames Turbotic’s future as the unification of its orchestration, assistant, and automation products.

Main Topics: Turbotic’s origin and enterprise automation roots (Priority: 5/5): Theo describes launching Turbotic after seeing how hard it was for enterprises to scale IT operations and automation, especially during his time working on transformation at Ericsson. Multiple pivots toward generative AI and lightweight automation (Priority: 5/5): The company shifted away from enterprise orchestration and then further toward generative AI/LLM-assisted process discovery for mid-size companies, culminating in a new automation product. Product strategy: narrow scope and usability (Priority: 5/5): Instead of trying to automate everything, Turbotic focused on two to three core features and made them work well for a specific ICP of lighter, no-code automation users. Tooling and MVP development approach (Priority: 4/5): Theo explains the team uses Cursor for coding, skilled builders for rapid MVPs, and Lovable for prototype UI/front-end work, with brainstorming centered on how to add value on top of LLMs. Team building, retention, and constant reconfiguration (Priority: 4/5): He argues that successful execution required repeatedly pivoting the team, preserving a few core people while replacing much of the org to match evolving product needs. Scaling only after product-market fit (Priority: 5/5): Theo says early focus on scale led to wasted effort and money; now he prioritizes product-market fit first, even if that means rebuilding the application later. Future roadmap and market positioning (Priority: 4/5): The goal is to merge orchestration, assistant, and vibe automation into one platform and push harder into the U.S. market while continuing to leverage India-based talent.

Key Arguments: Enterprises struggled to scale AI and automation operationally, which created the initial opportunity for Turbotic. AI products should not be built broadly at first; a narrow, usable product for a specific ICP is more likely to succeed. The best way to build is to reuse prior investments where possible, but only if they fit the new product direction. Product-market fit matters more than scalability early on; if the app is wrong, rebuilding is preferable to over-optimizing. Teams must also be pivoted, not just products; execution requires people whose skills match the current phase. The speed of the AI market means products can become obsolete within months, so founders need to stay ahead of the curve. A future unified platform can capitalize on prior orchestration and assistant work rather than treating prior pivots as sunk costs.

Data Points: Years since company founding: 5 years - Theo says Turbotic started about five years ago as an orchestration platform. Major pivot timing: 1.5 years ago - He says the company made a big pivot roughly a year and a half before the interview. Recent product upgrade work: 6 months - The team spent the past six months building the upgraded product released that week in San Francisco. Team turnover during pivots: 80-85% - Theo estimates most of the team was replaced across three pivots over four and a half years. Operational support from Microsoft: Microsoft startup program support - He says Microsoft invested heavily and supported the company’s cloud scalability. Company/customer focus: mid-size companies - After pivoting away from enterprise, Turbotic targeted lighter-weight users and mid-sized businesses. Core feature count: 2-3 features - The team deliberately narrowed the product to a few features and made them work very well. Potential product misuse avoided: supply chain workflow complexity - Theo uses this as an example of what they chose not to target in favor of simpler automations. Career start year: 1999 - Theo says his first venture began in the gaming industry in 1999. Tokyo/Japan practice intensity: 5-6 times a week; 10 hours/day in Japan - He describes his deep commitment to Japanese martial arts as a major part of his life. Product intelligence advisory opportunity: closed beta - The episode also promotes SEMA’s closed beta and advisory board sign-up.

Pivotal Quotes: "if you don't pivot, you die, basically" — Theo Berquist: His core advice to founders on adapting products, teams, marketing, and strategy. "we said, let's just make two, three features and make them work really well" — Theo Berquist: Explaining the deliberate choice to narrow scope rather than build a broad automation platform. "I think scaling for me, I'm not worried about scaling. I'm more worried about getting the product market fit" — Theo Berquist: His current philosophy on what matters most before investing in growth.

Implications: For founders and operators, the episode reinforces that AI startups win by narrowing scope, moving quickly, and reshaping teams around the current product phase. It suggests the next wave of automation will be no-code, AI-assisted, and unified across workflows.