Chapter 28: Team Structure and Roles

The right team structure at the wrong stage is worse than the wrong structure at the right stage — org design must evolve with your company.

Why This Matters

Role	Why You Should Care
🏢 Owner	Organizational structure determines speed, quality, and culture. Get it wrong and you'll ship slowly or burn cash.
💻 Dev	Your team topology directly affects what you can build, how fast you ship, and how much on-call pain you feel.
📋 PM	Cross-functional alignment depends on structure. You need to know who owns what and how decisions get made.
🎨 Designer	Where design sits in the org (embedded vs. centralized) shapes your influence and the quality of output.

The Concept (Simple)

Think of team structure like building a house. At first, one person does everything — framing, plumbing, electrical, painting. That works for a shed. For a house, you need specialists. For a skyscraper, you need specialized teams with a general contractor coordinating everything.

SaaS companies go through the same evolution:

5 people: Everyone does everything
50 people: Functional teams with clear roles
500 people: Cross-functional squads, platform teams, and support functions

The mistake most founders make is either structuring too early (bureaucracy kills small teams) or too late (chaos kills growing teams).

How It Works (Detailed)

ASCII Org Chart Evolution

Stage 1: Founding Team (2-5 people)

                 ┌─────────────┐
                 │   Founder/  │
                 │     CEO     │
                 └──────┬──────┘
                        │
         ┌──────────────┼──────────────┐
         │              │              │
  ┌──────▼──────┐ ┌─────▼─────┐ ┌─────▼──────┐
  │  Co-founder │ │ Engineer  │ │ Engineer   │
  │  (Product / │ │ #1        │ │ #2         │
  │   Design)   │ │ (Full-    │ │ (Full-     │
  │             │ │  stack)   │ │  stack)    │
  └─────────────┘ └───────────┘ └────────────┘

  Everyone does everything. No formal titles needed.
  Communication: constant, informal, in the same room.

Stage 2: Early Growth (10-25 people)

                      ┌──────────────┐
                      │     CEO      │
                      └──────┬───────┘
                             │
          ┌──────────────────┼──────────────────┐
          │                  │                  │
  ┌───────▼───────┐  ┌──────▼───────┐  ┌───────▼───────┐
  │  VP / Head of │  │  VP / Head of│  │  VP / Head of │
  │  Engineering  │  │  Product     │  │  Sales / GTM  │
  │               │  │              │  │               │
  │  - 3-5 devs   │  │  - 1-2 PMs   │  │  - 2-3 AEs    │
  │  - 1 DevOps   │  │  - 1 designer│  │  - 1 SDR      │
  │               │  │              │  │  - 1 CS / Supp │
  └───────────────┘  └──────────────┘  └───────────────┘

  Functional teams emerge. Weekly cross-team syncs.
  Danger: silos start forming if you don't actively fight them.

Stage 3: Scale-Up (50-100 people)

                           ┌───────────┐
                           │    CEO    │
                           └─────┬─────┘
                                 │
       ┌─────────┬──────────┬────┴────┬──────────┬─────────┐
       │         │          │         │          │         │
  ┌────▼───┐ ┌──▼────┐ ┌───▼───┐ ┌───▼───┐ ┌───▼───┐ ┌──▼─────┐
  │  CTO / │ │ VP    │ │ VP    │ │ VP CS │ │ VP    │ │ CFO /  │
  │  VP Eng│ │Product│ │ Sales │ │& Supp │ │Mktg  │ │ VP Ops │
  └───┬────┘ └──┬────┘ └──┬────┘ └──┬────┘ └──┬────┘ └──┬─────┘
      │         │         │         │         │         │
  ┌───▼────┐    │    ┌────▼───┐ ┌───▼────┐    │    ┌────▼───┐
  │Eng Team│  PMs    │ AEs    │ │ CSMs   │  Mktg  │ Finance│
  │  Leads │  + UX   │ SDRs   │ │ Support│  team  │ HR     │
  │(3-5    │  Design │ RevOps │ │ agents │        │ Legal  │
  │ squads)│  team   │        │ │        │        │        │
  └────────┘         └────────┘ └────────┘        └────────┘

  Cross-functional squads form. Design embedded in product teams.
  Need: RACI matrices, defined escalation paths, OKR alignment.

Stage 4: Growth (200-500+ people)

                              ┌───────────┐
                              │    CEO    │
                              └─────┬─────┘
                                    │
    ┌────────┬────────┬─────────┬───┴───┬────────┬────────┐
    │        │        │         │       │        │        │
  ┌─▼──┐  ┌─▼──┐  ┌──▼──┐  ┌──▼──┐ ┌──▼──┐  ┌──▼──┐ ┌──▼──┐
  │CTO │  │CPO │  │CRO │  │CCO │ │CMO │  │CFO │ │COO │
  └─┬──┘  └─┬──┘  └──┬──┘  └──┬──┘ └──┬──┘  └──┬──┘ └──┬──┘
    │        │        │        │       │        │       │
  Eng      Prod     Sales     CS    Mktg     Fin    People
  Dirs     Dirs     Dirs     Dir    Dir      Dir    Dir
    │        │        │        │       │        │       │
  Squad   Squad    Region   Segment Region   FP&A    HR
  Leads   Leads    Leads    Leads   Leads    Legal   Ops
    │        │                                        │
  ┌─┴──────────┐                                     IT
  │ Platform   │
  │ + Feature  │
  │   Squads   │
  └────────────┘

  Multiple layers. Platform teams enable feature squads.
  Need: formal operating rhythms, clear DRIs, thorough documentation.

Key Role Definitions

Role Responsibility Table

Role	Core Responsibility	Key Metrics	Reports To	Typical Hire Stage
CEO	Vision, strategy, fundraising, culture	Revenue, growth rate, cash runway	Board	Co-founder
CTO	Technical vision, architecture, eng culture	System uptime, eng velocity, tech debt	CEO	Co-founder or $1-5M
VP Engineering	Eng execution, hiring, delivery	Sprint velocity, release cadence, retention	CTO/CEO	$2-10M
VP Product	Product strategy, roadmap, prioritization	Feature adoption, NPS, time-to-value	CEO	$2-10M
Product Manager	Feature discovery, specs, delivery coordination	Feature metrics, customer satisfaction	VP Product	$1-5M
UX Designer	User research, interaction design, prototyping	Usability scores, task completion rate	VP Product/Design	$500K-2M
Engineering Lead	Squad delivery, code quality, mentoring	Team velocity, code review time, quality	VP Eng	$2-5M per squad
DevOps / SRE	Infrastructure, CI/CD, reliability	Uptime, deploy frequency, MTTR	VP Eng / CTO	$1-3M
CRO	Revenue strategy (sales + CS + marketing alignment)	ARR, NRR, CAC payback	CEO	$10-20M
VP Sales	Sales execution, pipeline, team	Quota attainment, win rate, cycle time	CRO/CEO	$2-5M
VP Customer Success	Retention, expansion, customer health	NRR, gross retention, health scores	CRO/CEO	$3-10M
VP Marketing	Demand gen, brand, positioning	MQLs, pipeline contribution, CAC	CRO/CEO	$3-10M
Head of Support	Ticket ops, SLAs, self-serve	CSAT, response time, deflection rate	VP CS	$2-5M

Cross-Functional Team Models

Model A: Functional Teams (Traditional)

  ┌─────────────┐  ┌─────────────┐  ┌─────────────┐
  │ Engineering  │  │   Product   │  │   Design    │
  │             │  │             │  │             │
  │ All devs    │  │ All PMs     │  │ All         │
  │ report to   │  │ report to   │  │ designers   │
  │ Eng Lead    │  │ Product Lead│  │ report to   │
  │             │  │             │  │ Design Lead │
  └─────────────┘  └─────────────┘  └─────────────┘

  PROS: Deep expertise, consistent standards, clear career paths
  CONS: Handoffs, slow communication, siloed thinking
  BEST FOR: Teams < 15 people

Model B: Cross-Functional Squads (Spotify-inspired)

  ┌──────────────────────────────────────────────┐
  │              PRODUCT AREA: GROWTH            │
  │                                              │
  │  Squad: Onboarding    Squad: Activation      │
  │  ┌────────────────┐   ┌────────────────┐    │
  │  │ PM             │   │ PM             │    │
  │  │ 2 Engineers    │   │ 3 Engineers    │    │
  │  │ 1 Designer     │   │ 1 Designer     │    │
  │  │ 1 Data Analyst │   │                │    │
  │  └────────────────┘   └────────────────┘    │
  └──────────────────────────────────────────────┘

  ┌──────────────────────────────────────────────┐
  │           PRODUCT AREA: PLATFORM             │
  │                                              │
  │  Squad: API          Squad: Infrastructure   │
  │  ┌────────────────┐   ┌────────────────┐    │
  │  │ PM             │   │ Eng Lead       │    │
  │  │ 3 Engineers    │   │ 2 SREs         │    │
  │  │               │   │ 1 Engineer     │    │
  │  └────────────────┘   └────────────────┘    │
  └──────────────────────────────────────────────┘

  PROS: Fast decisions, high ownership, customer-aligned
  CONS: Duplication, inconsistency, harder to maintain standards
  BEST FOR: Teams 25-200 people

Model C: Matrix (Large Scale)

  Functional Managers (career, skills, standards)
           │
           │     Project / Product Teams (delivery)
           │              │
           ▼              ▼
  ┌──────────────────────────────┐
  │  Engineer A                  │
  │  Reports to: Eng Manager     │
  │  Works on: Growth Squad      │
  │                              │
  │  Engineer B                  │
  │  Reports to: Eng Manager     │
  │  Works on: Platform Squad    │
  └──────────────────────────────┘

  PROS: Balance of expertise + delivery focus
  CONS: Two bosses, political, slow decisions
  BEST FOR: 200+ people (use sparingly)

RACI Matrix for Common Decisions

R = Responsible (does the work) | A = Accountable (final decision) | C = Consulted | I = Informed

Decision	CEO	CTO/VP Eng	VP Product	PM	Eng Lead	Designer	Sales	CS
Product roadmap priorities	I	C	A	R	C	C	C	C
Technical architecture	I	A	C	I	R	I	-	-
Feature spec & design	-	I	C	A	C	R	C	C
Sprint planning	-	I	C	A	R	C	-	-
Pricing changes	A	C	R	C	-	-	C	C
Hiring a new engineer	I	A	C	-	R	-	-	-
Customer escalation (P0)	I	R	I	I	R	-	I	A
New market entry	A	C	R	C	-	C	R	C
Design system updates	-	C	C	I	I	A	-	-
SLA tier definitions	A	C	C	R	-	-	C	R
Annual budget allocation	A	C	C	I	-	-	C	I

Team Structure by Stage

Stage	Headcount	Key Hires	Org Model	Communication
Pre-Seed	2-3	Co-founders only	Flat, everyone does everything	Constant, same room
Seed ($500K-$2M)	4-10	First PM, first designer, 3-5 engineers	Functional leads emerge	Daily standup, weekly all-hands
Series A ($2M-$10M)	15-40	VP Eng, VP Product, first CSM, first AE	Functional teams	Team standups, bi-weekly all-hands
Series B ($10M-$30M)	40-100	CTO, VP Sales, VP CS, VP Marketing	Cross-functional squads	OKR cadence, monthly all-hands
Series C+ ($30M+)	100-500+	CRO, CFO, COO, Directors	Squads + platform teams	Quarterly planning, written comms

When to Hire: Sequencing Guide

  Revenue ──────────────────────────────────────────►

  $0        $500K      $2M       $5M       $10M      $30M+
  │          │          │         │          │         │
  │ Founders │ Eng #3-5 │ VP Eng  │ VP Sales │ CRO     │
  │ Eng #1-2 │ PM #1    │ VP Prod │ VP CS    │ CFO     │
  │          │ Design#1 │ AE #1-2 │ VP Mktg  │ COO     │
  │          │ CS/Supp#1│ SDR #1  │ Eng Mgrs │ VP People│
  │          │          │ DevOps  │ Data/Ana │ Directors│
  │          │          │         │ Supp Lead│         │
  │          │          │         │ RevOps   │         │
  │          │          │         │          │         │
  ▼──────────▼──────────▼─────────▼──────────▼─────────▼
  2-3        5-10       15-30     30-60      60-150    150+
  people     people     people    people     people    people

In Practice

Real-World Example: "DataPipe" Scaling from 8 to 80

DataPipe, a B2B analytics SaaS, grew from $1M to $12M ARR over 18 months. Here's how their org evolved:

At $1M ARR (8 people):

Flat structure, CEO made all decisions
5 engineers, 1 PM/designer hybrid, 1 salesperson, CEO
Worked fine — everyone knew everything

At $5M ARR (30 people):

Hired VP Eng and VP Product
Formed 3 engineering squads (Growth, Core Product, Platform)
Hired first 2 CSMs, 3 AEs, 1 SDR
Problem: No clear decision-making framework. VP Eng and VP Product clashed on priorities.
Fix: Implemented RACI matrix. VP Product owns roadmap priorities; CTO owns architecture decisions.

At $12M ARR (80 people):

Added VP Sales, VP CS, Head of Marketing
5 cross-functional squads, each with PM + engineers + designer
Design team centralized with designers embedded in squads
Introduced OKR cadence (quarterly planning, monthly check-ins)
Problem: Communication broke down between squads.
Fix: Weekly cross-squad demo, shared Slack channels, written RFCs for cross-cutting decisions.

Common Mistakes

[ ] Hiring managers before ICs — you need people who do the work before people who manage the work
[ ] Title inflation — giving VP titles at 10 people means you'll have to re-level at 50 (painful)
[ ] No decision-making framework — "everyone decides" means nobody decides. Use RACI.
[ ] Copying big-company org charts — a 20-person startup doesn't need a Head of People or a PMO
[ ] Siloed CS and Support — these teams share context and should collaborate closely (see Chapter 26 and Chapter 27)
[ ] Ignoring the "glue work" — documentation, onboarding new hires, cross-team coordination. Reward it or it won't happen.
[ ] Scaling headcount before process — hiring more people into chaos just creates more chaos

Team Health Checklist

Use this quarterly to assess your org:

[ ] Every team member can articulate the company's top 3 priorities
[ ] Every project has a single DRI (Directly Responsible Individual)
[ ] Cross-team dependencies are identified and tracked
[ ] There's a clear escalation path for blocked decisions
[ ] New hires can ship their first meaningful contribution within 2 weeks
[ ] No single person is a critical bottleneck for any core function
[ ] Team satisfaction / eNPS is measured and trending positively
[ ] Career growth paths exist for both IC and management tracks

Key Takeaways

Structure follows strategy, and strategy follows stage. Don't copy Spotify's model at 10 people.
Hire ICs before managers, specialists before generalists (except at the very earliest stage where generalists are king).
Use RACI to make decisions explicit. Ambiguity about who decides is the #1 source of organizational friction.
Cross-functional squads work best from 25-200 people. Below that, functional teams are fine. Above that, you need platform teams too.
Every hire should either build the product, sell the product, or support the people who do. Challenge any role that doesn't map to one of those three.
Communication costs grow with n-squared complexity. As you grow, shift from meetings to written artifacts (RFCs, design docs, ADRs).

Action Items

Role	Next Step
🏢 Owner	Map your current org against the stage-appropriate chart above. Identify the next 3 hires you need. Build a RACI for your top 5 recurring decisions.
💻 Dev	Propose a squad structure if your eng team is 8+. Document your architecture decision-making process.
📋 PM	Ensure every feature in the roadmap has a clear DRI. Set up a cross-functional weekly sync if one doesn't exist.
🎨 Designer	Advocate for embedded design (in squads) over centralized if the team is growing. Build a design system to maintain consistency across squads.

Previous: Chapter 27 — Support Operations | This chapter is part of the Operations section of the SaaS Playbook.

Chapter 28: Team Structure and Roles ​

Why This Matters ​

The Concept (Simple) ​

How It Works (Detailed) ​

ASCII Org Chart Evolution ​

Stage 1: Founding Team (2-5 people) ​

Stage 2: Early Growth (10-25 people) ​

Stage 3: Scale-Up (50-100 people) ​

Stage 4: Growth (200-500+ people) ​

Key Role Definitions ​

Role Responsibility Table ​

Cross-Functional Team Models ​

Model A: Functional Teams (Traditional) ​

Model B: Cross-Functional Squads (Spotify-inspired) ​

Model C: Matrix (Large Scale) ​

RACI Matrix for Common Decisions ​

Team Structure by Stage ​

When to Hire: Sequencing Guide ​

In Practice ​

Real-World Example: "DataPipe" Scaling from 8 to 80 ​

Common Mistakes ​

Team Health Checklist ​

Key Takeaways ​

Action Items ​