Scaling Operations: When to Hire Specialists vs Generalists
A practical guide to building operational teams as you scale, understanding when to hire specialists versus generalists.
Scaling Operations: When to Hire Specialists vs Generalists
One of the most common dilemmas in scaling organisations is: should we hire specialists or generalists? The answer depends on your stage, complexity, and strategic priorities.
The Generalist vs Specialist Spectrum
Generalists:
- Broad skillsets across multiple functions
- Adaptable to changing priorities
- Comfortable with ambiguity
- Best for: Early-stage, fast-changing, resource-constrained environments
Specialists:
- Deep expertise in specific domains
- Systematise and optimise within their function
- Drive best-in-class outcomes in their area
- Best for: Scale-stage, complex operations, mature functions
Hiring by Company Stage
Pre-Seed to Seed (0-10 people)
Hire: Generalists and "athlete" operators
Why:
- Roles are fluid and priorities change weekly
- Can't afford multiple specialists
- Need people who can wear multiple hats
Example Hire: Operations Generalist who can handle finance, operations, and people/HR.
Series A (10-50 people)
Hire: Senior generalists with specialist depth
Why:
- Functions are forming but still small
- Need people who can build processes but stay flexible
- Can't yet justify full specialist teams
Example Hires:
- Head of Finance & Operations (owns finance, ops, legal, people)
- Head of Product & Engineering (owns product and technical delivery)
Series B (50-150 people)
Hire: Functional specialists + generalist leaders
Why:
- Functions are maturing and need dedicated ownership
- Complexity requires deeper expertise
- Can afford to split generalist roles into specialist functions
Example Hires:
- CFO (finance only)
- COO (operations, process, scaling)
- CPO (product strategy and management)
- VP Engineering (technical delivery)
Series C+ (150+ people)
Hire: Deep specialists and sub-function leaders
Why:
- Operations are complex and require specialist depth
- Functions are large enough to justify sub-specialisation
- Need best-in-class capability in each area
Example Hires:
- VP Finance, Head of FP&A, Head of Treasury (finance sub-specialisation)
- VP Operations, Head of Supply Chain, Head of Business Operations
- VP Product, Head of Product Strategy, Head of Product Operations
When to Hire Specialists Early
Even at early stages, hire specialists for:
1. Regulated or High-Risk Functions
- Legal & Compliance in regulated industries
- Data Protection (GDPR, privacy)
- Information Security
2. Mission-Critical Technical Functions
- Engineering leadership if you're a product/tech company
- Data science if data is core to your value proposition
3. High-Stakes External Relationships
- Finance/CFO when fundraising or managing investors
- Legal/General Counsel when negotiating major contracts
When to Keep Generalists
Retain generalists for:
1. Cross-Functional Coordination
Generalists excel at bridging functions and driving cross-team initiatives.
2. New or Emerging Functions
Use generalists to explore new areas before committing to specialist hires.
3. Resource Constraints
If you can't afford multiple specialists, a strong generalist delivers broader impact.
The Hybrid: T-Shaped and Pi-Shaped Talent
T-Shaped:
- Broad generalist skills (horizontal bar)
- Deep specialist expertise in one area (vertical bar)
Pi-Shaped:
- Broad generalist skills
- Deep expertise in two areas
These profiles are gold dust in scaling companies: generalist enough to stay flexible, specialist enough to drive outcomes.
Red Flags: Mis-Hiring Specialists and Generalists
Hiring a Specialist Too Early:
- Symptom: Specialist struggles with ambiguity and changing priorities
- Example: Hiring a VP Finance at 15 people when you need a finance/ops generalist
Hiring a Generalist Too Late:
- Symptom: Generalist can't deliver depth; quality suffers
- Example: Keeping a Head of Finance & Ops when you're 100+ people and need a dedicated CFO
Case Study: Scaling Operations at a Series B SaaS Company
Stage: Series B, £15M ARR, 80 people, scaling to £50M ARR over 24 months
Operations Team:
-
Seed to Series A (0-40 people):
- 1x Head of Finance & Operations (generalist)
-
Series B (40-80 people):
- Split into specialists:
- CFO (finance, investor relations)
- Head of Operations (process, systems, business operations)
- Head of People (HR, talent, culture)
- Split into specialists:
-
Scaling to Series C (80-150 people):
- Further specialisation:
- CFO + Finance Director + FP&A Manager
- VP Operations + Head of Business Ops + Head of Customer Ops
- VP People + Head of Talent + Head of People Ops
- Further specialisation:
Outcome:
The company scaled operations smoothly by hiring specialists at the right stage, avoiding both premature specialisation and delayed functional depth.
Decision Framework: Specialist or Generalist?
Ask yourself:
- What's our stage? Earlier = generalist; later = specialist
- How complex is the function? Simple = generalist; complex = specialist
- Is this mission-critical? Yes = consider specialist early
- Is the role well-defined? No = generalist; yes = specialist
- Can we afford a specialist? If no, hire a strong generalist with growth potential
Conclusion
There's no universal answer. Generalists thrive in early-stage, ambiguous, fast-changing environments. Specialists drive depth, quality, and scalability in mature, complex functions. Hire the right profile for your stage, complexity, and priorities—and be willing to evolve your team as you grow.