# Role Definitions for Early-Stage Teams

**Purpose:** Role definition guidance for early-stage team building.

**Related References:**
- See `hiring-checklist.md` for hiring workflow
- See `co-founder-assessment.md` for co-founder compatibility
- See `first-hire-framework.md` for prioritization decisions

**Integration:** Used by `building-team` skill for role-planning topic.

---

## Core vs. Optional Roles

### Core Roles (Early Stage)

**Technical Lead**
- Product development and technical architecture
- Code quality and technical decisions
- Team technical coordination

**Business/Operations Lead**
- Day-to-day operations
- Customer and partner relationships
- Administrative and financial oversight

**Growth/Marketing Lead**
- Customer acquisition
- Market positioning
- Revenue growth strategies

### Optional Roles (Later Stage)

- Customer Support
- Sales Lead
- HR/People Operations
- Data Analyst

## Role Responsibility Boundaries

Clear role boundaries prevent overlap and accountability gaps:

1. **Decision Authority** - Who has final say in each domain
2. **Collaboration Points** - Where roles must coordinate
3. **Escalation Paths** - How disagreements get resolved

## Hiring Sequence

Typical role addition sequence for funded startups:

| Phase | Timeline | Roles |
|-------|----------|-------|
| Founding team | 0-6 months | Co-founders, early advisors |
| First functional hires | 6-12 months | First dedicated role per function |
| Specialist roles | 12-24 months | Domain experts (sales, marketing, data) |
| Management layer | 24+ months | Team leads, middle management |
