Article
Startup Guide

Co-Founder Risk × OpenSeed — A Pre-Dispute Diagnostic Workflow

2026.05.28·8 min·OPENSEED

Co-founder disputes are one of the most common reasons startups die. But they don't erupt randomly — they start with structure: how equity is split, how roles are defined, vesting, and board voting rights. OpenSeed's business plan analysis catches these team-structure signals in advance. This article is a practical guide to how OpenSeed's 15 reviewers diagnose the 4 dimensions of co-founder risk.

Intro.

#The 4 Dimensions of Co-Founder Risk

The patterns behind co-founder disputes typically start in 4 dimensions. Each dimension tends to signal independently rather than reinforcing the others. Even a single weak dimension can develop into a dispute within 1–3 years.

DimensionWhat It CoversWhen the Dispute Signal Appears
Equity split50/50 or even N-way splits, mismatches between seed capital and effortFirst VC meeting (seed)
Role divisionOverlapping C-level roles, no dedicated CTO, etc.MVP stage (year 1)
Vesting and departure clausesEquity granted without vesting → dead equity if someone leavesWhen a C-level exec departs
Decision-making structureTied voting rights → deadlock, no boardRight before Series A

Of the 4 dimensions, equity split shows the earliest signal. When a VC looks at your cap table in the first meeting and sees a 50/50 or even N-way split, they cut you on the spot. The other 3 dimensions accumulate over time.

02

#Mapping OpenSeed's 15 Reviewers to the 4 Co-Founder Dimensions

Here are the reviewers that catch co-founder risk during an OpenSeed business plan analysis, and what each one looks at.

ReviewerDimensionDetection Signal
Team-fit reviewerEquity / role50/50 split, no dedicated CTO, heavy reliance on outsourcing
Deal-structure reviewerEquity / vestingCap table, option pool size, whether vesting is specified
Legal/governance reviewerVesting / decision-making4-year vesting with a 1-year cliff, right of first refusal, tied voting rights
Business-model reviewerRole divisionA pattern where BD, finance, and technical roles all fall on one person
IC ChairAll 4 dimensions combinedA dispute-likelihood verdict plus a priority order for reinforcement

When you get an OpenSeed business plan analysis, the 'Team' section shows comments from these 5 reviewers together. If your business plan has no cap table or vesting details, a 'missing cap table' red flag gets raised immediately.

03

#When a 50/50 Split Gets Caught — OpenSeed's Signals

The most common dispute pattern is two co-founders starting at a 50/50 split. OpenSeed catches it through these signals:

  • If your business plan's 'Team' section describes both co-founders identically → the team reviewer flags 'weak CEO/CTO distinction'
  • If the cap table shows a 50/50 equity split → the deal reviewer raises a 'voting deadlock risk' red flag
  • If there's no vesting section, or every member is on the identical schedule → the legal reviewer flags 'missing vesting' or 'missing cliff'
  • If there's no role-division table → the business-model reviewer notes 'BD/finance roles unassigned'

If all 4 of these signals show up together, OpenSeed's verdict drops to 'high team-structure risk.' Getting the same verdict before a VC meeting means you can still fix it in advance.

04

#The Reinforcement Workflow — How to Fix a Caught Dispute Signal

Here's the standard sequence for reinforcing the 4-dimension signals OpenSeed catches, directly in your body text.

SignalDirection to FixBusiness Plan Text Change
50/50 splitA slight differential like CEO 51% / CTO 49%Update the cap table + name the tie-breaking decision-maker
Missing vestingAdd 4-year vesting with a 1-year cliffOne line: 'Vesting: 4 years / 1-year cliff' + attach the agreement
Overlapping rolesA one-page C-level responsibility matrixName one person each for BD, finance, technology, and operations
Tied voting rightsA 3-person board (2 founders + 1 outside member)Specify the board composition and voting rules
Undefined option poolSet aside a 10–15% option pool in advanceState the option pool percentage on a post-money basis

After you make these fixes, running OpenSeed Round 2 clears red flags like 'missing cap table' and 'missing vesting,' and the verdict rises to 'team structure reinforced.' That puts you in meeting-ready shape for VCs.

05

#The 5 Patterns of C-Level Disputes — Timing and OpenSeed Detection

Here's when C-level disputes most often erupt, and the signal OpenSeed catches for each in advance.

TimingMain PatternOpenSeed Signal
6–12 months (right before MVP)Vision misalignment (product vs. business model)Business-model reviewer: 'contradictory BM direction'
12–18 months (right after seed)Role encroachment (CTO doing BD)Team reviewer: 'overlapping roles'
18–24 months (prepping for Series A)Recognizing contribution gapsDeal reviewer: 'vesting not applied'
24–36 months (post-Series A)Conflict over re-splitting equityLegal reviewer: 'no re-split procedure defined'
36+ months (growth stage)Misalignment on exit strategyIC Chair: 'no exit scenario defined'

Of these 5 stages, OpenSeed can catch 1 through 4. The 5th (exit-related conflict) isn't something business-plan data can catch — it needs outside advisory input.

06

#What OpenSeed Can't Catch — an Honest Limitation

Here's what OpenSeed can't catch in a co-founder risk diagnosis.

  • The trust in a personal relationship — this doesn't show up in business plan data
  • How deep a vision gap actually runs — hard to tell surface agreement from genuine agreement
  • A co-founder's personal values — this needs outside advisory input
  • The intensity of a conflict that's already started — this is family- and legal-advisory territory
  • Whether agreement is possible during an M&A or exit — this requires real negotiation data

OpenSeed can't catch any of these 5. This territory needs to be reinforced through regular 1:1 meetings between co-founders, outside mentor advice, and specialized legal counsel. OpenSeed can only diagnose 'structural signals' — the 'relational signals' are human territory.

Summary.

#Summary — A Dispute-Prevention Workflow

Here's the OpenSeed usage cycle for preventing co-founder disputes proactively.

  • Early stage (0–6 months) → OpenSeed Round 1: catch missing cap table/vesting signals
  • Right before MVP (6–12 months) → Round 2: validate the role-division matrix
  • Right before seed (12–18 months) → Round 3: check voting rights and board structure
  • Prepping for Series A (18–24 months) → Round 4: specify the option pool and re-split procedure
  • After that — once every 6 months (optional)
CTA
Once a dispute has erupted, it's already too late. Add a page on your cap table, vesting, and role matrix to your business plan, and get a pre-check from OpenSeed's 15 AI reviewers. A 4-dimension diagnosis is free during the current beta period.
광고

Check Your 4-Dimension Structure Before a Dispute Erupts

OpenSeed's 15 AI reviewers, mapped to equity, roles, vesting, and decision-making, diagnose dispute signals in advance.

🔒 Free during beta · your submission isn't saved

Start Free AI Feedback →

관련 AI 피드백 서비스.

AI 피드백
사업계획서 AI 추천
AI 피드백
사업계획서 피드백
AI 피드백
IR 자료 검토
RELATED · Same categoryStartup Guide
Business Plans With No Unit Economics at All — Why Reviewers Dock Points Immediately2026.07.12 · 8 minBusiness Plan 'Competitive Advantage' — Why an Unsupported Comparison Table Costs You Points in Review2026.07.11 · 8 minBusiness Plan Mistake Log: When You Have a 'Problem Definition' But No Customer Validation2026.07.09 · 7 minThe Business Plan Mistake Log Series — 4 Point-Losing Patterns AI Review Keeps Finding2026.07.09 · 8 min3 Patterns Where the 'Problem → Solution' Logic Breaks Down in Korean Startup Grant Business Plans2026.07.09 · 8 min
← Back to Discovery