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
What happened at Nvidia GTC: NemoClaw, Robot Olaf, and a $1 trillion bet | Equity Podcast
The podcast dissects Y Combinator CEO Gary Tan's controversial 'cyber psychosis' AI hype at SXSW, Travis Kalanick's return to autonomy through his newly rebranded Adams Inc. and acquisition of Pronto, and Uber's potentially $1.25 billion partnership with Rivian to co-develop autonomous R2 SUVs.
The $32B acquisition that one VC is calling the 'Deal of the Decade' | Equity Podcast
TechCrunch reporters discuss a whistleblower's allegation that a DOGE employee stole Social Security databases, the launch of AI notetaking wearables Taya and Sandbar, Palmer Luckey's retro gaming startup Mod Retro seeking a $1 billion valuation, and Meta's acquisition of AI agent startup MultiOn.
When startups become a family business
Married co-founders Hala Jawwan and Alessio Tresanti of Rivio reveal how their spousal partnership strengthens their AI procurement startup through deep trust and complementary expertise, while their third co-founder provides crucial balance and investors prioritize founder-market fit over traditional concerns about family businesses.
Anthropic's Pentagon deal is a cautionary tale for startups chasing contracts | Equity Podcast
TechCrunch editors analyze Paramount's acquisition of Warner Bros as part of ongoing streaming consolidation, discuss My Fitness Pal's purchase of teen-founded Cal AI and Pinterest's $1 billion activist investment, while raising skepticism about defense contractor Anduril's multi-billion dollar valuation amid questions over product effectiveness.