Design optimal team structures, hiring plans, compensation strategies, and equity allocation for early-stage startups from pre-seed through Series A. Use this skill when planning headcount, determining which roles to hire next, setting compensation or equity ranges, designing org structure, or building a hiring budget aligned to funding milestones.
npx skills add https://github.com/wshobson/agents --skill team-composition-analysis
Design optimal team structures, hiring plans, compensation strategies, and equity allocation for early-stage startups from pre-seed through Series A.
Build the right team at the right time with appropriate compensation and equity. Plan role-by-role hiring aligned with revenue milestones, budget constraints, and market benchmarks.
Team Size: 2-5 people
Core Roles:
Focus: Build and validate product-market fit
Team Size: 5-15 people
Key Hires:
Focus: Scale product and prove repeatable sales
Team Size: 15-50 people
Department Build-Out:
Focus: Scale revenue and build repeatable processes
Originally a 1720-byte section in this SKILL.md. Moved to references/details.md to fit Codex's 8 KB skill body cap.
Engineering:
Sales:
Product:
Marketing:
Customer Success:
Total Comp = Base Salary × 1.30 (benefits & taxes) + Equity Value
Fully-Loaded Cost:
Rule of Thumb: Multiply base salary by 1.3-1.4 for fully-loaded cost
San Francisco / New York: +20-30% above benchmarks
Seattle / Boston / Los Angeles: +10-20%
Austin / Denver / Chicago: +0-10%
Remote / Other US Cities: -10-20%
International: Varies widely by country
Founders:
Early Employees (Pre-Seed):
Seed Stage Hires:
Series A Hires:
Option Pool by Round:
Pre-Funding Dilution:
Investors often require option pool creation before investment, diluting founders.
Example:
Pre-money: $10M
Investors want 15% option pool post-money
Calculation:
Post-money: $15M ($10M + $5M investment)
Option pool: $2.25M (15% × $15M)
Founders diluted by pool creation before new money
Pre-Seed:
Founders (flat structure)
├── Contractors
└── First hires (report to founders)
Seed:
CEO
├── Engineering Lead (2-4 engineers)
├── Sales/Growth Lead (1-2 reps)
├── Product Manager
└── Operations
Series A:
CEO
├── CTO / VP Engineering (6-20 people)
│ ├── Engineering Manager(s)
│ └── Individual Contributors
├── VP Sales (5-15 people)
│ ├── Sales Manager
│ ├── Account Executives
│ └── SDRs
├── Head of Product (2-5 people)
│ ├── Product Managers
│ └── Designers
├── Head of Customer Success (2-5 people)
└── CFO / Finance Lead (2-5 people)
├── Recruiter
└── Operations
Manager Ratios:
Full-Time:
Contract:
Role Opening to Hire:
Time to Productivity:
Always add 2-3 months buffer to hiring plans.
Example:
If need engineer by July 1:
Early Stage (Seed):
Growth Stage (Series A):
Total Comp Budget = Σ (Role Count × Fully-Loaded Cost × % of Year)
Example:
3 Engineers × $202K × 100% = $606K
2 AEs × $230K × 75% (mid-year start) = $345K
1 PM × $162K × 100% = $162K
Total: $1.1M
To plan team composition:
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Take wshobson/team-composition-analysis from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.