Founding Team Design And Agreements

---
name: founding-team-design-and-agreements
description: "Build a balanced founding team and agree the rules of engagement (Founders' Agreement) before disagreements arise."
---

# Founding Team Design & Agreements

## Purpose

Build a balanced founding team and agree the rules of engagement (Founders'
Agreement) before disagreements arise.

## Based on

the owner's published commercialisation guide (owner, 2025). Chapter
"Building the Right Team" (pp. 53-56).

- Colombo & Grilli (2005) — founders' human capital (technical + management
  experience) correlates with growth
- Choi et al. (2019, 21,000+ startups) — multi-member teams outperform solo
  founders in revenue growth and survival
- Denoo et al. (2024) — diversity of skills in the founding team and advisors
  accelerates "application readiness"

## Method

1. Identify the team's current skill mix: technical, commercial,
   operational — fill gaps with co-founders, early hires, or advisors.
2. Remember the research evidence: multi-member, complementary teams survive
   and grow better than solo founders. If you are alone, compensate with a
   strong advisor and support network.
3. Draft a Founders' Agreement early — even before incorporation: roles,
   decision rights, individual IP contributions, equity shares.
4. Document each founder's contribution (idea/IP, time invested, seed
   capital) — these later justify uneven equity splits.
5. Use vesting or a dynamic equity model (e.g. "Slicing Pie") to tie
   ownership to ongoing contribution and keep the split fair over time.
6. Distinguish this from the later, broader Shareholders' Agreement (SHA),
   which also covers new investors and partners — not the same document as
   the Founders' Agreement.
7. Ensure transparency and trust: when everyone understands how contribution
   converts into ownership, the team withstands uncertainty and conflict
   better.

## Gotchas

- The Founders' Agreement and the later Shareholders' Agreement are
  explicitly different documents (step 6) covering different scopes —
  drafting only the Founders' Agreement and assuming it also governs
  future investors/partners leaves a real gap once outside capital enters.
- Equity splits agreed on "gut feel" instead of the documented
  contribution log from step 4 (idea/IP, time invested, seed capital) are
  hard to defend later — the documentation exists specifically so an
  uneven split can be justified after the fact, not just accepted at
  signing.
- Skipping vesting or a dynamic equity model (e.g. Slicing Pie, step 5)
  because "we trust each other" removes the exact mechanism the Method
  relies on to keep the split fair if a founder's contribution changes or
  drops over time.
- For a solo founder, the Method's mitigation is specifically "a strong
  advisor and support network" (step 2) — treating "find a co-founder
  eventually" as the fix, rather than compensating now, skips the
  near-term action the skill actually recommends.
- This skill does not produce a legally binding agreement (see "What this
  skill does NOT do") — treating its output (roles, decision rights,
  contribution log) as sufficient without routing to actual contract/
  corporate-law expertise risks an agreement that isn't enforceable when
  it's tested.

## What this skill does NOT do

- Does not draft a legally binding Founders' or Shareholders' Agreement — it
  structures what the agreement should cover. For legal drafting see
  `sopimukset:sopimuksen-laatiminen` and `yhtiooikeus:osakassopimus`.
- Does not resolve an equity dispute for you.

## Continue from here

- Next in this pack: `../industry-partner-engagement/SKILL.md` — Bring
  industry partners into commercialisation early so the product and business
  logic stay grounded in reality.
- Drafting agreements and shareholders' agreement terms require separate
  contract and corporate law expertise (not included in this skills pack).
- Pack's shared guardrails: `../../CLAUDE.md`
- Overview of the full journey: `../commercialisation-journey-roadmap/SKILL.md`

## References

- `../../references/case-studies.md` — 7 spin-out examples from different
  industries and regions
- `../../references/terminology.md` — the handbook's glossary
- `../../references/sources.md` — the handbook's own source references
- `../../CLAUDE.md` — the pack's shared guardrails