1. 🧭 Why the Team Question Comes Before the Product Question
Part 2's legal structure protects and formalizes a team — it doesn't tell you who should be on it. That's a harder, more consequential decision, and the data on startup failure backs this up repeatedly: co-founder conflict and team dysfunction are among the most commonly cited reasons early companies collapse, ahead of running out of money or building the wrong product. In an AI-specific company, this gets sharper: the skill sets you need (ML research, infrastructure engineering, product, distribution) are unevenly distributed, expensive, and — for the research-heavy roles — genuinely scarce relative to demand. Getting the team question right, lane by lane, is this article's entire job.
2. 🤝 Choosing Co-Founders
You need co-founders whose combined credibility can unlock nine-figure capital before any product exists — in practice, this usually means at least one founder with a genuine track record at a frontier lab (research leadership, not just an engineering role), because investors writing checks this large are underwriting the team's ability to compete for scarce research talent as much as the idea itself. A common, realistic pattern is a research-credible co-founder paired with an operations/fundraising-focused co-founder — splitting "can this team actually build a frontier model" from "can this team actually run a company at this capital scale," since very few individuals are genuinely strong at both.
Most Lane 2 companies are genuinely fine starting with one or two founders — a technical founder who can build the initial product and a founder (sometimes the same person) who can talk to customers and sell. The classic complementary pairing here is technical-plus-commercial, but the more important test isn't skill complementarity on paper, it's whether you've actually worked together before under real pressure. A co-founder relationship formed purely from a pitch-competition introduction carries meaningfully more risk than one built on a prior working relationship, regardless of how well the resumes match on paper.
Here the co-founder question is almost entirely about research credibility and shared technical conviction in a specific, currently-unproven thesis — investors in this lane are betting on the founding researchers' judgment about an open problem, so a founding team without deep, personally-held conviction in the specific research direction (not just general AI enthusiasm) is a weak pitch regardless of individual pedigree. A non-research co-founder handling operations and fundraising is still valuable, but the research conviction has to be genuinely shared among the technical founders, not delegated to one person while others go along.
3. 🎯 Early Hires — Who You Actually Need First
3b. 🗂️ What the Team Actually Looks Like, Role by Role
Putting Sections 2 and 3 into a single reference: here's a realistic team structure at roughly the seed stage (first 12-18 months) for each lane — not a hiring plan to execute mechanically, but a sense of scale, seniority mix, and where headcount actually concentrates.
| Role | 🔴 Lane 1: Scale-First | 🔵 Lane 2: Applied Layer | ⚪ Lane 3: Research Bet |
|---|---|---|---|
| CEO / Fundraising Lead | Founder, usually with prior frontier-lab or exec credibility | Founder, often the commercial/product co-founder | Founder, usually a senior researcher who also carries the pitch |
| Research / Technical Lead | Founder or very early hire with published research track record | Often the same person as CEO, or a technical co-founder | One or more founders — the entire pitch rests on this credibility |
| Engineering (headcount) | Heavy — infrastructure/training engineers dominate early hiring | Light — 1-3 generalist engineers total pre-Series A | Light — engineering only supports the research, doesn't lead it |
| Research staff (headcount) | Growing fast, often 10+ within a year if capital allows | Usually none — no dedicated research function | Small, senior, deliberately slow-growing (Section 3) |
| Product / Design | Minimal or absent pre-launch | Critical — often a founder wears this hat directly | Absent — no product exists yet by design |
| Sales / Customer Success | Not needed pre-revenue | First non-engineering hire, arrives early | Not applicable — no customers yet |
| Operations / Finance | Dedicated hire fairly early — capital deployment at this scale needs real financial control | Founder-handled or outsourced (bookkeeper/fractional CFO) until Series A | Founder-handled or outsourced, similar to Lane 2 |
| Total headcount at $2-5M raised | Often still under 15 — capital goes to compute, not headcount, at this stage | 3-8 people | Under 10, senior-weighted |
Illustrative structure for the simulation's assumptions (Part 1, Section 6) — actual team shape varies by specific idea and founder background.
4. 💰 Equity Splits — How They Actually Get Decided
The default advice — "split equity based on contribution" — is true and almost useless in practice, because contribution is nearly impossible to measure fairly at the moment a company is founded, before anyone knows what the real work will turn out to be. Two structurally different approaches show up repeatedly in real companies:
Regardless of which split you choose, vesting is non-negotiable — standard four-year vesting with a one-year cliff protects the company (and remaining co-founders) if someone leaves early, and its absence is one of the most common, most regretted early-stage mistakes across every lane.
5. 🏛️ Case Study: Anthropic's Seven-Founder Equal Split
5b. 🧭 Do You Need a Board, Advisors, or Mentors This Early?
Founders often assume a formal board is either irrelevant at seed stage or mandatory from day one — neither is quite right, and the honest answer differs by lane and by what stage of capital you're at.
A real, active board arrives early and matters immediately, because the capital amounts involved mean investors will require board seats as a condition of funding, not a courtesy. Beyond formal governance, this lane benefits most from senior technical advisors — ideally people with direct frontier-lab research leadership experience — who can pressure-test research direction and compute-allocation decisions the founding team may not have faced before at this scale. A board that includes at least one member with genuine hands-on experience scaling a research organization (not just a generalist VC board seat) is a real, practical asset here, not a formality.
A formal board is usually unnecessary before an institutional seed or Series A round — most Lane 2 founders operate with no board at all in the earliest months, just founders making decisions directly. What's genuinely useful this early is a small, informal group of 2-4 advisors: ideally someone who has built and sold a similar product, and someone with domain expertise in your specific customer vertical. This can be structured with small advisor equity grants (commonly 0.1-0.5% each, vested over one to two years) rather than a formal board seat — lower commitment, easier to adjust if the relationship isn't adding value. A formal board typically forms once an institutional investor's term sheet requires one, discussed further in Part 4.
Similar to Lane 1 in that investor-required board seats arrive early given the capital scale, but the more valuable addition here is often a small scientific advisory group distinct from the governing board — respected researchers in the specific subfield who can vouch for the thesis publicly and sanity-check research direction privately, without holding formal governance authority. This matters more in Lane 3 than either other lane because the company's entire credibility rests on a technical bet outsiders (investors, future hires, eventually the public) have to trust before any product exists to prove it.
6. 📋 Side-by-Side: Team Building by Lane
| Factor | 🔴 Lane 1: Scale-First | 🔵 Lane 2: Applied Layer | ⚪ Lane 3: Research Bet |
|---|---|---|---|
| Ideal founding team size | 3-7, mixing research and operational credibility | 1-2, technical + commercial | 2-5, senior research-heavy |
| First non-founder hires | Research infrastructure engineers | Second engineer, then sales | Additional senior researchers |
| Equity split tendency | Weighted by seniority and fundraising role | Weighted, sometimes equal for close peers | Often near-equal among research founders |
| Biggest hiring constraint | Competing with incumbent labs' compensation | Cash-constrained hiring before revenue | Narrow pool of researchers who share the thesis |
| Team size at $2-5M raised | Still pre-revenue, team may already be 20+ | Typically 3-8 people | Often still under 10, senior-weighted |
7. ⚠️ Risk Flags
8. 🧪 Team-Building Checklist (All Three Lanes)
9. 🧭 What's Next in the Series
Part 4 covers Seed Capital — pitching, valuation, and term sheets, again across all three lanes: what investors in each lane actually want to see, how valuation gets set differently for a pre-revenue product company versus a research-thesis company, and what a realistic term sheet looks like at each capital tier.