Each episode of Tech Leadership with Fexingo is a structured dialogue between Lucas and Luna, dissecting the decisions that define engineering organizations. Lucas, with a journalist's precision, and Luna, probing from the practitioner's chair, examine real CTO playbooks — from Netflix's architecture team restructuring to how Stripe scaled its engineering manager track. They walk through the trade-offs in code review velocity vs. quality, the economics of platform teams, and the talent signals that predict a VP of Engineering hire. The show is built for people who actually run technical organizations: engineering managers deciding whether to centralize infrastructure, CTOs weighing a monorepo migration, and tech leads who need to justify architectural choices to a board. Every conversation is grounded in specific metrics — deployment frequency, on-call load, and hiring leaky-funnel data — and each episode ends with a concrete tension that the listener can adapt to their own stack. What
Pitch Analysis
Required Pod Score for this show. PitchCentric checks your profile against host openness, topical fit, and audience signals before you generate a pitch.
Contact path
Verified email
Booking probability
35%
Guest openness
Selective
Verified email on file
80/100
Required Score
Sign up to generate a grounded pitch for Tech Leadership with Fexingo: Engineering Managers, CTOs, and Technical Leadership Conversations.
What is Tech Leadership with Fexingo: Engineering Managers, CTOs, and Technical Leadership Conversations?
Tech Leadership with Fexingo: Engineering Managers, CTOs, and Technical Leadership Conversations is a business podcast hosted by Fexingo, with 154 episodes on record and a Required Pod Score of 80. PitchCentric scores this show on Booking Probability, Listen Score, and live audience signals refreshed every 24 hours.
About the host
Fexingo hosts Tech Leadership with Fexingo: Engineering Managers, CTOs, and Technical Leadership Conversations, a business show with 154 episodes published.
Our AI reads these to draft pitches. Use them as grounding for a pitch that cites a real guest and a specific topic.
Episode #160
How CTOs Use Ops Reviews to Prevent Incident Fatigue
Aug 20, 20269 minS4
In episode 160 of Tech Leadership with Fexingo, Lucas and Luna explore how CTOs and engineering leaders can prevent incident fatigue by restructuring their operations reviews. Using the example of a payments platform that reduced its weekly incident review from two hours to twenty minutes, they discuss the shift from blame-oriented post-mortems to forward-looking action tracking, the role of blameless culture, and how to measure the effectiveness of ops reviews. They also touch on the balance between learning and action, and how to keep reviews from becoming bureaucratic rituals. For leaders who feel their teams are drowning in retrospectives, this episode offers practical advice on how to make ops reviews a tool for improvement rather than a drain on energy. #TechLeadership #CTO #OpsReviews #IncidentManagement #BlamelessCulture #EngineeringManagement #IncidentFatigue #SRE #PostMortem #ActionItems #ReliabilityEngineering #Leadership #TechPodcast #FexingoBusiness #BusinessPodcast #EngineeringLeadership #OperationalExcellence #IncidentReview Keep every episode free: buymeacoffee.com/fexingo
How CTOs Use the Incremental Commitment Model to Manage Risk
Aug 19, 20269 minS4
Episode 159 of Fexingo Tech Leadership dives into the Incremental Commitment Model (ICM) with hosts Lucas and Luna. They explore how CTOs can use this risk-driven framework to steer complex technology projects, contrasting it with traditional waterfall and pure agile methods. The conversation anchors on a real-world case: a fintech company migrating a core payments platform to microservices. Lucas and Luna break down the ICM's four phases — definition, design, implementation, and operations — and explain how each phase uses 'anchor points' to validate assumptions before heavy investment. They discuss how ICM helps avoid the 'big bang' failure mode, using examples like the Denver Airport baggage system and compare it with modern practices like continuous delivery. The episode is practical for engineering leaders facing high-stakes, ambiguous initiatives, offering a structured yet flexible approach to risk management. Listeners will learn how to apply ICM's principles, such as concurrent engineering and staged commitment, to improve decision-making and increase project success rates. #IncrementalCommitmentModel #ICM #CTO #EngineeringManagement #RiskManagement #TechnologyLeadership #TechLeadership #ProjectManagement #SoftwareArchitecture #Fintech #Microservices #Agile #Waterfall #ContinuousDelivery #FexingoBusiness #BusinessPodcast #TechPodcast #Leadership Keep every episode free: buymeacoffee.com/fexingo
How CTOs Use Versioned APIs to Retire Legacy Systems
Aug 18, 20269 minS4
In this episode of Tech Leadership with Fexingo, Lucas and Luna explore how CTOs use versioned APIs as a strategic tool for retiring legacy systems without the chaos of a big-bang rewrite. They break down the real-world case of a major bank that successfully migrated from a decades-old mainframe system by exposing a modern API layer, incrementally moving consumers over, and shutting down the old system piece by piece. Along the way, they discuss the difference between breaking and non-breaking changes, how to communicate deprecation timelines to internal and external developers, and why versioning is as much about organizational change management as it is about technology. The conversation also touches on the practical challenge of running two systems in parallel, the cost implications, and how to keep stakeholders aligned during a multi-year migration. If you're a CTO or engineering leader facing a legacy modernization project, this episode gives you a concrete framework to think about it—plus a reminder that the hardest part is often people, not code. #TechLeadership #FexingoBusiness #BusinessPodcast #CTO #LegacySystems #APIVersioning #TechnicalDebt #SoftwareMigration #MainframeModernization #EngineeringManagement #DeveloperExperience #TechStrategy #DigitalTransformation #SystemArchitecture #Technology #Innovation #Leadership #Podcast Keep every episode free: buymeacoffee.com/fexingo
In this episode of Tech Leadership, Lucas and Luna explore how CTOs apply the Spotify Model to scale agile practices across growing engineering organizations. They break down the model's core components—squads, tribes, chapters, and guilds—and discuss real-world adaptations beyond music streaming. The conversation digs into the trade-offs of autonomous squads versus alignment, how to avoid the 'copy-paste' trap, and why the model isn't a one-size-fits-all blueprint. They also share practical advice for leaders considering this approach, including how to balance autonomy with shared technical direction. Plus, they touch on the importance of cognitive load, which was the focus of a previous episode, and how the Spotify Model can either alleviate or exacerbate it depending on implementation. Listeners will walk away with a clear understanding of the model's strengths and pitfalls, and actionable insights for tailoring it to their own teams. #SpotifyModel #AgileScaling #CTO #TechLeadership #EngineeringManagement #SquadModel #ChapterAndGuild #AutonomyAndAlignment #ScalingAgile #AgileTransformation #TeamStructure #TechLeadershipPodcast #FexingoBusiness #BusinessPodcast #Technology #SpotifyModelMisconceptions #CognitiveLoad #EngineeringCulture Keep every episode free: buymeacoffee.com/fexingo
How CTOs Use the Concept of Cognitive Load to Structure Teams
Aug 16, 202612 minS4
In this episode, Lucas and Luna explore how CTOs use cognitive load theory to design engineering teams and systems. They start with a concrete example: a team at a mid-sized SaaS company that was drowning in context-switching because they owned a sprawling monolith. The discussion covers the difference between intrinsic, extraneous, and germane load, and how a CTO might measure team overload. They cite research on the limits of working memory and contrast it with team-level capacity. The episode also touches on how the concept pairs with platform teams, the inverse Conway maneuver, and the danger of adding too many tools. Lucas shares a practical exercise for mapping team cognitive load, and Luna asks about the risk of underloading highly skilled engineers. The show closes with a forward-looking question about how AI assistants might shift the cognitive load landscape. #CognitiveLoad #TeamDesign #CTO #TechLeadership #EngineeringManagement #WorkingMemory #IntrinsicLoad #ExtraneousLoad #GermaneLoad #PlatformTeams #InverseConway #ContextSwitching #TeamCapacity #SoftwareArchitecture #TechTeamStructure #Business #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo
Every question we get asked before someone starts their trial.
If you have a concern about deliverability, AI quality, data privacy, or whether this will actually work for your specific situation, it's probably answered below.
What is the difference between Founder Solo and Founder Pro?
Founder Solo gives you 50 AI pitches per month using the credit model (Standard pitches cost 1 credit, Enriched pitches cost 2). Founder Pro raises that to 200 credits per month and adds full Booking Probability access, unlimited Magic Match, Apollo enrichment credits, and data export capabilities. Both plans use the same credit system, so you can stretch your monthly budget further by using Standard-mode drafting.
How do agency tiers work?
Agency tiers have no base fee. You pay per managed client and per talent profile. Agency Standard is $199 per client per month; Agency Pro is $399 per client per month. Both add $39 per talent profile per month. Your own team's user seats are always free.
What is a talent profile?
A talent profile represents one person (founder, executive, or spokesperson) you are booking onto podcasts. It includes their bio, topics, headshots, and outreach history. Team plans include 5 profiles; agency plans are pay-as-you-go.
Can I switch plans later?
Yes, at any time. Upgrades take effect immediately; downgrades apply at the end of the current billing period. Contact support if you need help migrating between plan families.
Do you offer a free trial?
Every paid plan includes a 15-day free trial. Your card is saved at signup but you will not be charged until day 16. Cancel any time from your dashboard.
What happens if I cancel?
You keep access until the end of your current billing period. No charges after that. Your data is retained for 30 days in case you reactivate.
Is the 20% annual discount automatic?
Yes. Select Annual on the pricing toggle and the discounted price is applied automatically at checkout. The annual price shown is the full year cost.
What if I have more than 50 profiles or 20 clients?
That is our Enterprise tier. Contact our sales team and we will build a custom plan with volume pricing, a dedicated account manager, and SLA guarantees.