Co-Founder Synergy Prover

Co-Founder Synergy Prover MCP Connector for Claude

A+

Two founders shook hands on 'we trust each other' — with no vesting cliff. It approved a 50/50 equity split out of politeness. It said 'we always agree' as conflict resolution. That is not synergy — that is a lawsuit. This tool forces five YC-level partnership axes: vesting protection, skill separation, deadlock resolution, equity justification, and execution velocity.

1 tools Official Updated Jun 28, 2026 Official Vinkius Partner

The Problem

Every LLM commits five partnership reasoning failures:

  1. Cliff Blindness — accepts handshakes without 4-year vesting and 1-year cliff.
  2. Skill Overlap — approves two 'CEOs' with no builder.
  3. Deadlock Design — accepts 50/50 without tie-breaker.
  4. Equity Politeness — defaults to 50/50 out of fairness.
  5. Velocity Absence — lets founders plan forever.

The 5 Partnership Axes

Axis Pivot Rule
Vesting Cliff Mandated 4-year, 1-year cliff, forfeiture terms.
Skills Separated Builder vs Seller — mutually exclusive.
Conflict Deadlock Broken Named CEO with tie-breaker authority.
Equity Justified Time, risk, capital, IP — not politeness.
Execution Velocity Proven Shipping dates, user counts, deploys.

Verdict Matrix

Axis 1 fails → CLIFF_ABSENT
Axis 2 fails → SKILL_OVERLAP
Axis 3 fails → DEADLOCK_RISK
Axis 4 fails → EQUITY_NAIVE
Axis 5 fails → VELOCITY_ABSENT
All pass     → SYNERGY_PROVEN
co-founderequityvestingstartuppartnershipyccap-table

1 tools expose this connector's capabilities to your AI agent.

validate_co_founder_synergy

Think like a YC partner evaluating a founding team — the #1 cause of startup death is co-founder conflict, and it is always structural. You must: (1) secure the CAP TABLE — 4-year vesting, 1-year cliff, monthly vesting after cliff, forfeiture terms, acceleration clauses. "We trust each other" is not a cap table strategy. Trust is necessary AND insufficient — legal structure protects both parties WHEN trust is tested, not IF, (2) separate SKILLS with MUTUALLY EXCLUSIVE ACCOUNTABILITY — who builds, who sells. Not "we complement each other" — specific daily activities. CTO writes code daily. CEO runs customer calls daily. If both "manage," nobody is accountable for output, (3) break DEADLOCKS — name the CEO with strategic tie-breaker authority. Define domain authority: CEO decides strategy/hiring/fundraising, CTO decides architecture/tech-stack/engineering-process. Escalation protocol: if disagreement persists after 48h, CEO decides. "We always agree" is a fantasy — disagreement is inevitable and healthy IF there is a resolution mechanism, (4) justify EQUITY — calculate based on measurable contributions: time invested (full-time from when?), risk absorbed (salary foregone, savings invested), capital contributed ($X), IP brought (prototype, patents, domain expertise, network). "50/50 to be fair" is politeness, not a rationale — it creates resentment when one founder contributes more, (5) prove VELOCITY — show shipping evidence. MVP launched by week X. First Y paying users by week Z. Weekly deploys. Customer interviews per week. Pivots based on data. "Stealth mode" is death — you learn nothing without shipping. "Perfecting the plan" is procrastination. If rejected, the partnership has a fatal structural flaw. Structured reflection tool for YC-partner-level co-founder dynamics evaluation. Forces the agent to validate partnership structure with legal protections, mutually exclusive accountability, conflict resolution mechanisms, contribution-based equity, and shipping velocity. Catches Cliff Blindness (no vesting cliff — trusting handshakes instead of 4-year/1-year-cliff equity protection with forfeiture terms), Skill Overlap (two CEOs, no builder — "we both manage" means nobody is accountable), Deadlock Design (50/50 equity without tie-breaker authority — "we always agree" is a fantasy that kills startups), Equity Politeness (splitting 50/50 "to be fair" instead of calculating based on time, risk, capital, and IP contribution), and Velocity Absence ("stealth mode," perfecting the plan — no shipped product, no users, no data). Call once per founder team evaluation or partnership structure decision

See how to talk to your AI agent using Co-Founder Synergy Prover.

We trust each other, 50/50, we both manage, we always agree, still in stealth mode.

CLIFF_ABSENT — Five fatal gaps: no vesting, skill overlap, deadlock, equity politeness, zero velocity.

4y vesting, 1y cliff. CTO builds, CEO sells. CEO decides after 48h. 60/40 by contribution. MVP week 4, 10 users week 8, weekly deploys.

SYNERGY_PROVEN — Partnership validated. All axes pass. Execute.

Technical co-founder wants to rebuild the entire backend (6 months). Business co-founder wants to launch in 3 markets simultaneously (needs current backend). Both have valid points. Equity is 50/50.

Classic build-vs-ship tension. Neither is wrong — the conflict reveals missing decision framework. Define: what is the technical debt cost of NOT rebuilding? What is the market cost of NOT launching? Make the tradeoff quantitative, not emotional. Set a 90-day compromise: launch 1 market on current backend while scoping modular rebuild.

Trust is not a cap table strategy. Without vesting, a co-founder can leave in month 2 with half the company. Mandate 4-year vesting, 1-year cliff.

Related Connectors