Best for
- 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.
wshobson/agents/plugins/startup-business-analyst/skills/team-composition-analysis/SKILL.md
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.
Decision brief
Design optimal team structures, hiring plans, compensation strategies, and equity allocation for early-stage startups from pre-seed through Series A.
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/wshobson/agents --skill "plugins/startup-business-analyst/skills/team-composition-analysis"Inspect the Agent Skill "team-composition-analysis" from https://github.com/wshobson/agents/blob/d82998e7df393c671ede2387a8435075f0b633f5/plugins/startup-business-analyst/skills/team-composition-analysis/SKILL.md at commit d82998e7df393c671ede2387a8435075f0b633f5. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
Focus: Build and validate product-market fit
Early Employees (Pre-Seed):
To plan team composition:
Focus: Build and validate product-market fit
Focus: Scale product and prove repeatable sales
Permission review
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 81/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 39,130 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
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:
Frequently asked questions
Design optimal team structures, hiring plans, compensation strategies, and equity allocation for early-stage startups from pre-seed through Series A.
The source record exposes this install command: npx skills add https://github.com/wshobson/agents --skill "plugins/startup-business-analyst/skills/team-composition-analysis". Inspect the command and pinned source before running it.
Alternatives
coreyhaines31/marketingskills
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
coreyhaines31/marketingskills
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o
prowler-cloud/prowler
PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing index usage statistics, reindexing, dropping indexes, or working with partitioned table indexes. Also trigger when discussing index strategies, partial indexes, or index maintenance
narrative-io/narrative-skills-marketplace
Translate a fuzzy analytical question into a rigorous investigation plan. Interrogates the ask, grounds the plan in the available data dictionary, applies analytical best practices, and produces a structured brief of query specifications for a downstream query-writing skill. Plans, does not write SQL. Use when: "why did X drop", "is there a relationship between A and B", "who are our highest-value customers", "what's driving the change in Y", "investigate this trend", "design an analysis for", "