When your co-founder wants to change direction, the technical lead is often the one who has to rebuild everything — or kill the idea before it drains the runway. In this episode, Lucas and Luna break down the decision framework that one early-stage startup used to pivot from a B2B scheduling tool to a consumer wellness app without losing their core engineering team or burning cash on a rewrite. They walk through how the CTO assessed the technical cost of the pivot, why they chose to keep 60 percent of the backend unchanged, and the one question every engineering founder should ask before greenlighting a new direction. If you've ever been the person who has to tell a co-founder that their big idea means six months of rework, this episode gives you a repeatable process for evaluating whether that rework is actually worth it.

#Pivot #CoFounderConflict #TechnicalDebt #StartupStrategy #EngineeringLeadership #CTO #ProductDecisions #B2B #ConsumerWellness #Rewrite #Runway #DecisionFramework #Technology #BusinessPodcast #FexingoBusiness #TechnicalCoFounder #Engineering #Startup

Keep every episode free: buymeacoffee.com/fexingo

In this episode of The Technical Co-Founder Podcast, Lucas and Luna explore the ideal engineering team structure for early-stage startups. They break down the Spotify model, examine when to hire specialists versus generalists, and discuss how one real startup restructured from a flat team of five to a squad-based system with leads. They cover the trade-offs between functional and cross-functional teams, how to decide when it's time to reorganize, and why startup culture often kills good team structures before they take root. Specific examples include how a fintech startup scaled from 5 to 20 engineers without losing velocity, the role of the tech lead, and why you need a clear escalation path for technical decisions. If you're a founder or CTO wrestling with how to organize your engineering org in 2026, this episode gives you the concrete frameworks and real-world trade-offs to make the right call.

#EngineeringTeam #StartupStructure #TechLead #SpotifyModel #CrossFunctionalTeams #ScalingEngineering #FintechStartup #SquadModel #GeneralistVsSpecialist #EngineeringOrg #CTOAdvice #TechnicalCoFounder #BusinessAndTechnology #FexingoBusiness #BusinessPodcast #TeamScaling #CodeReview #PairProgramming

Keep every episode free: buymeacoffee.com/fexingo

In this episode, Lucas and Luna explore the art of sunsetting features — when and how to kill a product or feature that no longer serves the business. They anchor on the story of Basecamp's decision to remove their message board feature in 2024, a move that initially sparked user backlash but ultimately streamlined the product. Lucas breaks down the technical and cultural challenges: sunk cost fallacy, code cleanup, customer communication, and team morale. Luna pushes back on whether feature removal is harder for B2B vs B2C products, and they discuss a rule of thumb used at Coinbase — any feature that less than 5% of active users engage with in a month is a candidate for deprecation. This episode is essential listening for technical founders and product leaders wrestling with product bloat.

#Basecamp #FeatureSunset #ProductManagement #TechnicalDebt #SunkCostFallacy #B2B #B2C #Coinbase #ProductBloat #CodeCleanup #CustomerCommunication #TeamMorale #EngineeringLeadership #CTO #TechnicalCoFounder #BusinessPodcast #FexingoBusiness #TechStartups

Keep every episode free: buymeacoffee.com/fexingo

Episode 12 of The Technical Co-Founder Podcast tackles the hardest word in engineering leadership: no. Lucas and Luna dissect a real case from a mid-stage SaaS startup where the CTO turned down a $2 million customer’s feature request. They explore the framework behind the decision—opportunity cost, architectural debt, and team focus—and why saying no actually saved the company. Drawing on lessons from Basecamp’s long-standing policy and the 37signals playbook, they walk through how to evaluate requests, communicate trade-offs to non-technical co-founders, and protect your roadmap without burning bridges. Specific, tactical, and grounded in engineering reality.

#FeatureRequests #TechnicalDebt #ProductRoadmap #EngineeringLeadership #SayingNo #OpportunityCost #Basecamp #37signals #CTO #StartupAdvice #SaaS #CustomerManagement #Prioritization #BusinessAndTechnology #TechnicalCoFounder #FexingoBusiness #BusinessPodcast #EngineeringCulture

Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna challenge the conventional wisdom that startups should only hire senior engineers. Using the case of a fast-growing B2B SaaS company that deliberately built a team of 60% junior developers, they explore the surprising advantages: lower burn rate, stronger internal mentoring culture, and engineers who grow into the exact stack you need. They also address the risks — slower initial velocity, higher management overhead — and how to structure mentorship and code review to make it work. With specific data on ramp-up time, retention rates, and cost per hire, this episode makes a data-driven case for rethinking your hiring strategy.

#Hiring #JuniorDevelopers #StartupHiring #EngineeringManagement #TechTalent #Mentorship #CodeReview #B2BSaaS #BurnRate #Retention #RampUpTime #TechnicalCoFounder #CTO #StartupAdvice #Business #Technology #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo

In this episode, Lucas and Luna dive into a counterintuitive idea: not all technical debt is bad. They examine how companies like Etsy, Shopify, and even early Amazon deliberately carried technical debt to move faster, capture market share, and survive. Lucas explains the difference between reckless debt and strategic debt, using the example of a startup that chose to build a monolith over microservices to ship a product in six weeks instead of six months. Luna pushes back on the conventional wisdom that tech debt always needs to be repaid, and they discuss how Netflix's famous 'Chaos Monkey' approach actually created a culture of intentional debt. Along the way, they touch on a couple of dollars a month support for the show at buy me a coffee dot com slash fexingo. By the end, you'll have a framework for deciding when to pay down debt and when to let it ride.

#TechnicalDebt #StartupEngineering #StrategicDebt #Etsy #Shopify #Netflix #Amazon #MonolithVsMicroservices #ChaosMonkey #CTO #EngineeringLeadership #SoftwareArchitecture #BusinessTechnology #FexingoBusiness #BusinessPodcast #TheTechnicalCoFounderPodcast #CodeReview #PairProgramming

Keep every episode free: buymeacoffee.com/fexingo

When do you commit to a full rewrite? Most engineers know the hesitation — it's the biggest technical gamble you can take. In this episode, Lucas and Luna break down the calculus behind the rewrite decision through the lens of one engineer who actually went through it: a senior developer at a mid-stage SaaS company who inherited a tangled codebase built by five different founders over seven years. They walk through the specific signals that tipped the scales — spiralling bug-fix time, a single deploy taking two full days, and a four-hour onboarding for new hires. But the real insight? The rewrite wasn't just about cleaner code. It was about regaining team velocity and morale. They also discuss the one question you must answer honestly before you touch a single line: 'Is the existing codebase limiting your ability to ship value to customers, or is it just ugly?' If you're a technical co-founder or senior engineer wrestling with this decision, this episode gives you a framework — not a one-size-fits-all answer.

#CodebaseRewrite #SeniorEngineer #TechnicalDebt #SoftwareEngineering #EngineeringDecision #StartupScaling #CodeQuality #TeamVelocity #EngineeringLeadership #CTO #TechnicalCoFounder #RewriteVsRefactor #SaaS #BusinessAndTechnology #FexingoBusiness #BusinessPodcast #TheTechnicalCoFounderPodcast #EngineeringFounders

Keep every episode free: buymeacoffee.com/fexingo

Lucas and Luna dive into why so many early-stage startups hire junior engineers first and why that's often a mistake. They break down the trade-offs using the example of a real fintech startup that hired a senior infrastructure engineer as employee number four — and how that decision saved them six months of rewrites. The episode covers the hidden costs of mentorship, the 'learning vs. leverage' ratio, and why a single senior hire can de-risk your entire technical roadmap. If you're a technical founder deciding between two junior devs and one senior dev, this episode gives you a concrete framework to make the call.

#SeniorEngineer #StartupHiring #TechnicalCoFounder #EngineeringCulture #HiringStrategy #TechStartups #EngineeringLeadership #StartupAdvice #TeamBuilding #TechHiring #StartupGrowth #EngineeringManager #BusinessAndTechnology #FexingoBusiness #BusinessPodcast #TheTechnicalCoFounder #CodeReview #StartupLessons

Keep every episode free: buymeacoffee.com/fexingo

In this episode of The Technical Co-Founder Podcast with Fexingo, Lucas and Luna dig into the real-world story of a CTO at a mid-stage SaaS company who slashed their AWS bill by 40 percent—without sacrificing performance or developer velocity. They walk through the specific tactics: right-sizing instances, committing to reserved instances, eliminating zombie resources, and using spot instances for batch workloads. They also discuss the cultural shift required to get the engineering team on board, and why cloud cost optimization is as much about behavior as it is about architecture. A practical, no-fluff conversation for anyone building on the cloud.

#CloudCostOptimization #AWSCosts #CTOStrategies #TechnicalCoFounder #EngineeringManagement #SaaS #DevOps #FinOps #RightSizing #ReservedInstances #SpotInstances #CostReduction #CloudInfrastructure #StartupScaling #BusinessAndTechnology #FexingoBusiness #BusinessPodcast #TechLeadership

Keep every episode free: buymeacoffee.com/fexingo

In this episode of The Technical Co-Founder Podcast, Lucas and Luna dive into the engineering strategy behind scaling a product from zero to 100,000 active users with only two engineers. They break down the real-world case of a SaaS startup that hit this milestone in 18 months without VC funding, using a single PostgreSQL database, a queue-based architecture, and ruthless feature triage. Lucas explains why most early-stage teams over-engineer for scale they'll never see, and shares the specific decisions — like avoiding microservices and choosing a monolithic frontend — that kept the team's deployment cycle under 15 minutes. Luna challenges whether this approach works for every product, and they discuss the one metric that matters more than uptime when you're a two-person team: time to ship. If you're a technical founder with a small team and big ambitions, this episode will change how you think about infrastructure bottlenecks.

#Scaling #TwoPersonTeam #StartupEngineering #PostgreSQL #Monolith #QueueArchitecture #FeatureTriage #TimeToShip #SaaS #Bootstrapping #Infrastructure #TechnicalCoFounder #CTO #EngineeringStrategy #Business #Technology #FexingoBusiness #BusinessPodcast

Keep every episode free: buymeacoffee.com/fexingo