How Many CTOs

Brad Hefta-Gaub & Scott Porad

Welcome to the "How Many CTOs?" Podcast, hosted by Brad and Scott, where we dive deep into the intricate world of Chief Technology Officers. Each episode features candid conversations with guest CTOs who share their real-world experiences and insights on a wide range of topics. From building and upleveling high-performing engineering teams to managing and communicating the impact of tech debt, we cover it all. Discover strategies for measuring engineering productivity, refining processes, and balancing innovation with structured methodologies. Learn from experts about decomposing monolithic systems and keeping up with the latest technology trends. Whether you're a current or aspiring CTO, our podcast offers practical solutions and valuable advice to navigate the ever-evolving landscape of technology leadership. Tune in and join the discussion on overcoming the common challenges faced by CTOs today. Don't forget to subscribe, rate, and review! #TechLeadership #CTO #techpodcast

  1. 3d ago

    Navigating the Future: Gas Town and Bespoke AI Agents

    In this episode of "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub discuss Brad's viral LinkedIn post arguing that AI has collapsed the economics that drove generalized SaaS, enabling more bespoke software for underserved SMBs and vertical niches. They debate practical examples like a plumber-specific CRM versus highly custom workflows for a regional law firm, including concerns about long-term maintenance, fragmentation, and risk. Brad contrasts "overnight magic" agent claims with what he sees in fractional CTO work: teams using AI within disciplined engineering practices and quality gates to deliver far more output, though not fully autonomous "dark factories" yet. They explore Scott's hands-on Gas Town workshop experience building a fantasy football app with multiple agents, noting orchestration value, tooling immaturity, resource constraints, and confusing nomenclature. The episode ends with why experienced operators still dismiss AI for production code and whether agent frameworks will be custom-built or marketplace-driven.   00:00 Cold Open 00:14 Show Intro and Hosts 00:58 Viral LinkedIn Post Read 03:28 "Agree... Sort Of" Nuance 04:40 Plumber CRM Example 08:36 Law Firm Workflow Doubts 11:37 Engineering Reality Check 14:29 Gas Town Workshop Demo 17:34 Factory Setup and Risks 20:28 Why Leaders Still Doubt AI 22:26 AI Naysayers 24:10 Massive PRs 27:42 Monorepo Momentum 29:07 Engineering Joy 31:10 AI Mistakes 33:19 Agent Personas 37:04 Agent Marketplace 38:54 K Shaped Future 41:15 Trust But Verify 42:30 Wrap Up Resources: How Many CTOs Pod: https://howmanyctospod.com Scott Porad: https://www.linkedin.com/in/scottporad/  Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/  #TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCTOs #Podcast #CTOs #CTOPodcast #ChiefTechnologyOfficer #Technology #Engineering #SoftwareDevelopment #SoftwareEngineering #TechLeadership #EngineeringLeadership #EngineeringCulture #TechDebates #AI #AIRevolution #AIAgents #AIAssistedCoding #AIAssisstedProgramming #BespokeSoftware #GasTown #TechInnovation #FutureTech #DigitalTransformation #TechLeadership #CTOInsights #TechTrends

    43 min

  2. May 19

    Uncovering Hidden Ambiguities: Why Product Managers Need to Adapt to AI Tooling

    In this episode of "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub discuss spec-driven development and SpecKit, starting with Brad's story of a product owner resisted SpecKit because it produced "too many words," alongside Scott's example of accepting a 60,000-line pull request by reviewing the spec instead of the code. They reflect on how product owners often can't define what they want until they see it, and how software work is usually clarified through ongoing back-and-forth dialogue. SpecKit surfaces hidden ambiguity by generating questions product owners hadn't considered, changing what used to become ad hoc decisions, bugs, or debt. They argue speed enables tighter iteration, but also pressures product to "know what they want," raising job-impact fears for engineers and possibly product managers too. Their conversation prompts ideas for training, collaborative workflows, and even self-design—tempered by the continued need for standardization and cross-functional expertise. The episode ends with the hosts reflecting on buisness ideas that never came to pass, and affirming that now value comes down to how well the problem can be described. 00:00 Cold Open 01:18 Product Is The Hard Part 02:26 Fast Teams Meet Specs 04:34 Too Many Words Pushback 05:10 Review The Spec Not Code 08:00 Coder To Reviewer Shift 10:20 Why POs Avoid Specificity 13:01 Surfacing Ambiguity Shock 17:43 Two Hour Sprint Loop 19:35 Jobs Changing Anxiety 23:39 Problem Versus Solution Trap 25:56 Vibe Tools And Self Design 26:49 Real Estate CRM Anecdote 28:28 AI Rewrites Software Economics 29:31 Self Design Simple Specs 31:00 When Standards Matter 32:23 Training Product Owners 36:05 Jobs Converge Under AI 37:49 Three Pane Spec IDE 40:40 AI Comes For PMs 44:29 Founder Moats And Copies 46:24 Missed Spotify Moment 48:19 RealNetworks Almost Made YouTube 51:36 Wrap Up And Credits Resources: How Many CTOs Pod: https://howmanyctospod.com Scott Porad: https://www.linkedin.com/in/scottporad/  Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/  #TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCTOs #Podcast #CTOs #CTOPodcast #ChiefTechnologyOfficer #Technology #Engineering #SoftwareDevelopment #SoftwareEngineering #TechLeadership #EngineeringLeadership #EngineeringCulture #TechDebates #SpecKit #SpecDrivenDevelopment #ProductManagement #AI #ProductOwners #CodeReview #QualityGates #IterativeProcess #UserStories #AIAssistedCoding #Spec

    53 min

  3. May 12

    A Fundamental Shift: Change Management, Psychological Safety, and AI's Impact on Engineering Leadership with Dr. Adam Link

    In this episode of "How Many CTOs Does It Take?" podcast, host Brad Hefta-Gaub is joined by Dr. Adam Link, former senior engineering manager at Coinbase, who shares his background leading global teams through highly technical transformations in fintech and crypto, including major infrastructure migrations. They discuss whether different kinds of change require different leadership approaches, emphasizing that change management is fundamentally about people. They discuss how fear makes change harder, so leaders must create psychological safety by providing "air cover" and managing messaging up and down. Adam notes that good managers must handle hard conversations like layoffs and performance issues with empathy while recognizing these outcomes aren't always personal decisions. He offers advice for engineers moving into management, including a tongue-in-cheek analogy that managers "test in production," and describes a challenging EC2-to-Kubernetes migration where success required strong technical credibility, hands-on help, and attention to team psychology. Adam and Brad compare blameless vs egoless retrospectives, discuss leaders defending engineers behind the scenes, and highlight the need for real remediation like error budgets or vendor changes. The conversation closes on AI as a fundamental industry shift, debate over the loss of hand-crafted coding vs enduring need for problem understanding, concerns about the junior-to-senior pipeline if entry roles disappear, decision fatigue from AI agents, and optimism about smaller teams producing better products with fewer bugs. 00:00 Cold Open 00:31 Podcast Intro Guest 02:24 Change Management Basics 03:49 Defining "Air Cover" 06:50 Hard People Decisions 10:19 Managers Test In Prod 13:38 Big Cloud Migration 17:34 Hands On Migration Help 21:04 Failure Friendly Culture 23:41 Blameless vs Egoless Retros Debate 28:56 Managing Up After Outages 30:19 Accountability And Error Budgets 31:38 Vendor Failures And Remediation 33:53 AI Adoption And Resistance 34:44 Craft Versus Assembly Line 37:52 AI As Mid Level Engineer 41:17 Business Value For Juniors 45:11 Pipeline And Decision Fatigue 47:15 Specs Waterfall Meets Agile 49:07 Summary And Closing Thoughts Resources: How Many CTOs Pod: https://howmanyctospod.com Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/  Dr. Adam Link: https://www.linkedin.com/in/adamlink/  #TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCTOs #Podcast #CTOs #CTOPodcast #ChiefTechnologyOfficer #Technology #Engineering #SoftwareDevelopment #SoftwareEngineering #TechLeadership #EngineeringLeadership #EngineeringCulture #TechDebates #AIRevolution #EngineeringCulture #ChangeManagement #LeadershipSkills #AIAssistedProgramming #AI #FinTech #Crypto #

    51 min

  4. May 5

    An Ideal Partnership: How and When to Split CTO and VP of Engineering Duties

    In this episode of "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub discuss the recurring question: when it's appropriate to hire a VP of Engineering and how to divide responsibilities so the CTO can better align product, business, and technology strategy. They define CTO vs VP of Engineering work, review Gemini's matrix (strategy/vision vs execution/people/process, external vs internal, success metrics, and typical direct reports), and add nuance about internal stakeholders within and outside the company. They discuss cases where leaders can't do both jobs and why founders shouldn't give the CTO title too early. They emphasize CTO/VPE as a yin-yang partnership with clear decision rights and KPIs. Brad shares experiences with split dev/ops teams and argues for engineers having operational skin in the game, while Scott outlines his org functions and defines ops as what's required to keep systems running. They propose carving up responsibilities by strategy vs building (and operating), debate punting corporate IT to the CFO versus keeping it tied to security, and consider using Gemini to suggest how to split roles. The episode closes on letting go of ego through clear expectations, Scott's recommendation of the book "First, Break All the Rules," how skill or interest gaps can force a split despite hierarchical titles, and a pro tip to align on expectations with your CEO so teams can measure progress and celebrate wins like uptime and cycle-time improvements. 00:00 Cold Open 00:27 Podcast Intro Banter 00:49 Small Business AI Win 02:09 Team Size Context 03:52 When to Add VPE 05:40 CTO vs VPE Roles 07:11 Gemini Comparison Matrix 10:54 Startup Hiring Patterns 13:39 Titles and Founder Pitfalls 15:18 Yin and Yang Partnership 18:09 Carving the Org Pie 20:31 Corporate IT and Security 24:20 Strategy Versus Execution 25:28 Reliability And SRE Ownership 27:24 Defining Operations Teams 30:04 On Call And Skin In Game 31:18 Using Gemini To Split Roles 33:08 Letting Go And Ego 34:33 KPIs Enable Delegation 37:28 Manager Clarity Framework 38:57 When Skill Gaps Force Split 41:55 Set Your Scorecard 44:16 Celebrate KPI Wins 45:51 Wrap Up And Credits Resources: How Many CTOs Pod: https://howmanyctospod.com Scott Porad: https://www.linkedin.com/in/scottporad/  Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/  #TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCTOs #Podcast #CTOs #CTOPodcast #ChiefTechnologyOfficer #Technology #Engineering #SoftwareDevelopment #SoftwareEngineering #TechLeadership #EngineeringLeadership #EngineeringCulture #TechDebates #VPofEngineering #Gemini #CTOvsVPE #VPE #SecurityMindset #AI #DevOps #GrowthMindset #TeamCollaboration #CorporateCulture #BusinessGrowth #AIIntegration #Operations #StrategicVision #ManagementStyles #RoleDivision #ExecutiveDecisions

    47 min

  5. Apr 28

    Where Does the Alpha Flow?: Rethinking Software Value in the Age of AI

    In this episode of "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub discuss a conversation Scott had with coworkers after discovering Confluence connected to Google Drive and Slack, raising questions about whether to rely on tools like Confluence or a generic layer like Claude to aggregate knowledge and enable agents. A colleague suggested "alpha flows to where building happens," prompting Scott to question whether he agrees, what engineers actually need from AI (clear specifications), and whether customer insights and business needs matter more than internal documents. The hosts explore different types of builders, how clean data becomes a differentiator once tooling is ubiquitous, and define "dirty" or stale data through examples of conflicting documentation and misleading dashboards. Brad argues that as the building gets easier, the value shifts to market understanding and especially to the spec, not the code, while both conclude that ultimately, advantage comes from strong guardrails for correctness and value. 00:00 Cold Open 00:26 Podcast Setup And Topic 00:52 Confluence AI Discovery 02:32 Alpha Flows To Builders 03:51 Six Big Questions 07:36 Long View On Differentiation 09:12 Specs And Translation Layer 13:15 Design Levels And Personas 17:24 Moats Disappear In AI Era 20:41 Security And Exploit Agents 21:54 Mythos And Free Code 22:33 Specifying What Matters 23:23 Agent Strip Mining Products 24:42 Dirty Data In Knowledge 28:30 Stale Docs And Deletion 30:31 Bias And Interpretation 32:08 Ready Aim Shoot Debate 34:49 Specs QA And Guardrails 37:30 Where Value Really Flows 39:29 Wrap Up And Subscribe Resources: How Many CTOs Pod: https://howmanyctospod.com Scott Porad: https://www.linkedin.com/in/scottporad/  Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/  #TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCTOs #Podcast #CTOs #CTOPodcast #ChiefTechnologyOfficer #Technology #Engineering #SoftwareDevelopment #SoftwareEngineering #TechLeadership #EngineeringLeadership #EngineeringCulture #TechDebates #AI #AITransformation #DataDriven #Innovation #Automation #DisruptiveTechnology #AIFuture #AITrends #InnovationInAI #AIForBusiness #TechRevolution #AIInsights #AIRevolution #EthicalAI #AIAssistedCoding

    41 min

  6. Apr 21

    Product-Market Fit and Pragmatic AI: Insight from RevenueCat's CTO Miguel Carranza

    In this episode of "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub" interview Miguel Carranza Spanish-born co-founder/CTO of RevenueCat, who describes discovering subscription billing pain while building the Elevate app and turning that hard, "boring" problem into a YC-backed business. He explains RevenueCat's scale (billions of API requests/day) and the resulting priorities: product-market fit, reliability/security, and sustaining culture in a fully remote team across 27 countries. Scott and Brad commiserate with Miguel about avoiding platitudes in company values by grounding them in specific principles—always be shipping, customer obsession, ownership, balance, pragmatism, and healthy paranoia—reinforced through public shout-outs and performance expectations, plus examples of choosing customer support over strict entitlement. The discussion covers AI's tailwinds, internal adoption, standardizing workflows, a rule that PR authors must understand every line, and why auto-generating PRs from bug reports still requires context and triage. 00:00 Cold Open 00:24 Meet Miguel Carranza 01:06 From Spain to Startups 02:28 Subscription Billing Pain 04:50 Building RevenueCat 09:49 Scaling and Reliability 11:16 Culture as a CTO Job 14:31 Defining Company Values 16:56 Pragmatism and Paranoia 19:16 Making Values Real 23:24 Values Over Talent 24:39 Daily Value Decisions 24:58 Slack Support Dilemma 26:28 Pragmatic Customer Fixes 28:38 Culture Fit Reality 30:02 AI Era Product Fit 35:06 Organic AI Adoption 37:28 AI Coding Guardrails 40:49 Bug To PR Debate 44:48 Engineering Identity Shift 47:30 Closing Thank Yous And Plugs   Resources: How Many CTOs Pod: https://howmanyctospod.com Scott Porad: https://www.linkedin.com/in/scottporad/  Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/  Miguel Carranza: https://www.linkedin.com/in/miguelcarranza/  RevenueCat: https://www.revenuecat.com/  #TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCTOs #Podcast #CTOs #CTOPodcast #ChiefTechnologyOfficer #Technology #Engineering #SoftwareDevelopment #SoftwareEngineering #TechLeadership #EngineeringLeadership #EngineeringCulture #TechDebates #SoftwareDevelopment #StartupSuccess #StartupCulture #TechEntrepreneurship #Innovation #AI #AIRevolution #AIAssistedProgramming #AICoding #RevenueCat

    49 min

  7. Apr 14

    The Most Optimized Blue: Differences Between UI and User Experience Design with Nick Cawthon

    In this episode of "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub talk with Nick Cawthon of gauge.io, who shares highlights from RSA 2026 and his career designing UX for InfoSec/SecOps/DevOps tools. Nick argues that modern dashboards increasingly look the same, so strategists and researchers must find the nuances by designing for the human factor. He explains how research-driven UX reduces fatigue and errors caused by behaviors like endless scrolling, swivel-chair context switching, and inconsistent layouts. The group discusses how B2B security users want speed and clarity rather than "stickiness," why UI is often confused with UX, and how product-led vs engineering-led cultures affect outcomes. They debate whether agent-led/AI companies truly understand UX, why poor UX persists (strategy, impatience, capitalism), the role of humility, what's measurable in UX, and whether cheaper engineering will shift investment toward design.   00:00 Cold Open 00:30 Podcast Intro Guest 01:09 RSA Conference Context 02:29 Design Shift Since iPhone 03:53 Human Factor in SecOps 04:40 Research First UX 04:54 Scrolling And Swivel Chair Fatigue 09:59 Consistency Notifications Workflow 11:14 B2B Speed Over Stickiness 12:56 Why We Repeat Mistakes 14:09 UX vs UI Value 18:23 Engineering Product Design Dynamics 20:25 AI Agents Deployed Engineers 22:33 Design Strategy Takes Discipline And Patience 25:47 Why Bad UX Persists 29:18 Measuring Experience 30:07 Title Suggestion 32:46 AI Chat Interfaces 36:49 Patterns and Commoditized Design 38:46 Code Gets Cheaper 41:53 Service Design Matters 43:19 Everyone Builds Now 46:02 Wrap Up and Links   Resources and hashtags to the end How Many CTOs Pod: https://howmanyctospod.com Scott Porad: https://www.linkedin.com/in/scottporad/  Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/  Nick Cawthon: https://www.linkedin.com/in/nickcawthon-ux-digital-agency-product-design-leadership/  Gauge.io: https://gauge.io/  #TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCTOs #Podcast #CTOs #CTOPodcast #ChiefTechnologyOfficer #Technology #Engineering #SoftwareDevelopment #SoftwareEngineering #TechLeadership #EngineeringLeadership #EngineeringCulture #TechDebates #InfoSec #SecOps #UX #UI #UXvsUI #UXDesign #UserExperience #DesigntoSucceed #UXStrategy #TechInnovation #AI #IndustryInsights #HumanFactor

    48 min

  8. Apr 7

    Balancing Innovation and Safety: CTOs Check-In About AI Evolution

    In this "What's on your mind?" episode of the "How Many CTOs Does It Take?" podcast, hosts Scott Porad and Brad Hefta-Gaub discuss how non-engineers using AI tools are increasing risk, with Brad concerned about security amid recent supply-chain attacks. Brad shares how an AI agent setting up a React Native scaffold generated and transmitted database passwords and API keys in clear text, raising fears that LLM logs could expose secrets if vendors are hacked. Scott describes a false alarm involving Lovable and Snowflake access, and wrestles with conflicting company values—moving fast vs. protecting customer data. They reference Robert Siciliano's ideas on fatalism and trust and debate whether SOC 2 can become simply a checkbox. Brad also shares productivity loss without automated CI/CD and ephemeral environments, and the hosts question why containers still feel hard after years of innovation. Scott worries about AI's impact on young adults and entry-level jobs, mentions a voice tool called Whisper Flow, and the episode ends with a reflection on niche trade skills, such as guitar repair.   00:59 Supply Chain LLM Exploit 03:23 Secrets Leaking via Agents 06:17 Lovable Data Scare 07:08 Move Fast vs Secure 07:57 One Way Door Security 12:59 Compliance vs Real Security 14:19 SOC 2 Box Checking 16:00 Frameworks Save the Day 16:32 Next Topic CICD Automation 18:27 Why CICD Is Hard 19:30 Startups Skip the Setup 21:05 Kids Facing AI Uncertainty 24:18 Career Pipeline Problem 25:07 Jobs Move Down Stack 27:00 Fewer Harder Tech Jobs 29:21 Punk Rock Amp Repair Storytime 31:17 Wrap Up and Credits Resources: How Many CTOs Pod: https://howmanyctospod.com Scott Porad: https://www.linkedin.com/in/scottporad/  Brad Hefta-Gaub: https://www.linkedin.com/in/bradheftagaub/  #TechPodcast #EngineeringPodcast #DevTalks #PodcastForDevs #HowManyCTOs #Podcast #CTOs #CTOPodcast #ChiefTechnologyOfficer #Technology #Engineering #SoftwareDevelopment #SoftwareEngineering #TechLeadership #EngineeringLeadership #EngineeringCulture #TechDebates #AI #AIAssisstedProgramming #AIAssisstedCoding #AIProgramming #AIRisks #Cybersecurity #DataSecurity #CyberThreats #TechSecurity #DigitalSafety #SecureTech #CyberResilience #MachineLearning

    32 min
See All (71)

Trailers

Ratings & Reviews

5
out of 5
5 Ratings

About

Welcome to the "How Many CTOs?" Podcast, hosted by Brad and Scott, where we dive deep into the intricate world of Chief Technology Officers. Each episode features candid conversations with guest CTOs who share their real-world experiences and insights on a wide range of topics. From building and upleveling high-performing engineering teams to managing and communicating the impact of tech debt, we cover it all. Discover strategies for measuring engineering productivity, refining processes, and balancing innovation with structured methodologies. Learn from experts about decomposing monolithic systems and keeping up with the latest technology trends. Whether you're a current or aspiring CTO, our podcast offers practical solutions and valuable advice to navigate the ever-evolving landscape of technology leadership. Tune in and join the discussion on overcoming the common challenges faced by CTOs today. Don't forget to subscribe, rate, and review! #TechLeadership #CTO #techpodcast

Information

  • Creator
    Brad Hefta-Gaub & Scott Porad
  • Years Active
    2025 - 2026
  • Episodes
    71
  • Rating
    Explicit
  • Copyright
    © 2025
  • Show Website
    How Many CTOs