How to fight with your co-founder
TL;DR
Ian Schmidt of Trimmergence explains that co-founder conflict is inevitable and healthy when navigated correctly, advocating for early 'relationship synchronizing' through personal operating system mapping and explicit agreements to prevent relational debt and startup failure.
💥 Reframing Conflict 3 insights
Conflict is healthy and necessary
Healthy conflict is critical for navigating tension points; the goal is managing disagreement constructively, not avoiding it entirely.
Unresolved issues create relational debt
Like technical debt, avoiding conflict accumulates 'relational debt' that compounds over time and damages the partnership.
Delayed confrontation leads to explosive blowups
Waiting too long can result in public confrontations, such as founders yelling at each other during team offsites, causing collateral damage to company culture.
🛠️ Personal & Relational Tools 3 insights
Map your personal operating system first
Founders must understand their own triggers, gifts, and blind spots—including separating identity from company outcomes—before fixing the relationship dynamic.
Create relationship synchronizing agreements
Co-founders should memorialize explicit one-page agreements covering decision ownership, individual needs, and protocols for navigating triggering moments.
Establish an ongoing upgrade cadence
Treat team dynamics like software requiring continuous OS upgrades through regular individual deep work and joint relational maintenance sessions.
⚠️ Structural Flashpoints 3 insights
CEO designation and role evolution
Major conflicts arise over who takes the CEO seat and whether founders can evolve from zero-to-one operators to one-to-one-hundred leaders as the company scales.
Similar backgrounds risk groupthink
Founders with identical skills may finish each other's sentences but risk missing critical perspectives without explicitly inviting diverse viewpoints.
Diverse backgrounds require trust to prevent projection
Different working styles create exponential value but require deep trust and accurate interpretation to avoid misreading motivations and second-guessing decisions.
Bottom Line
Founders should map their personal operating systems and establish explicit one-page relationship agreements early to build the trust infrastructure necessary for healthy conflict and long-term partnership survival.
More from TechCrunch
View all
Everyone wants a piece of the enterprise AI pie | Equity Podcast
The podcast explores XAI's pivot from AI lab to GPU landlord through a major compute deal with Anthropic, a resurgence in crypto venture funding driven by regulatory shifts, and the viral crowdfunding attempt to save bankrupt Spirit Airlines.
The long road to driverless with Aurora's Chris Urmson (Live at HumanX) | Equity Podcast
Aurora CEO Chris Urmson explains why autonomous trucking has reached an inflection point, moving from pilot programs to commercial scale operations across the Sun Belt with over 250,000 driverless miles completed. With next-generation hardware unlocking production of thousands of vehicles and California regulations expected to ease, Aurora is betting that freight economics and 24/7 utilization advantages will drive adoption faster than robotaxis.
Musk v. Altman is just getting started | Equity Podcast
This episode examines the legal fallout when Sallie Mae allegedly monetized Scoly's student data post-acquisition despite founder promises, BMW i Ventures' $300 million strategic bet on industrial AI automation, and how Scout AI's $100 million raise signals defense tech's mainstream acceptance.
Keeping Your Team Motivated When FDA Approval Isn’t Guaranteed l Build Mode
Biotics AI CEO Robbie Bustami shares strategies for navigating FDA clearance for their AI ultrasound co-pilot, emphasizing early regulatory engagement, integrating clinical studies with go-to-market plans, and maintaining team motivation through multi-year approval timelines.