Skip to main content

VSaaS Players

Who does the work?


The Core Insight

Hire from industry. Customer-facing roles need domain scars.

Generic SaaS experience isn't enough. Your sellers, CS leaders, and solutions engineers need to have LIVED the pain your customers face.


The Hybrid Team Model

Pair SaaS expertise with industry expertise:

Role TypeSaaS SkillsIndustry SkillsHire For
Industry EngineerBasicDeepCredibility, discovery
SaaS SellerDeepBasicProcess, closing
SolutionsMediumMediumBridge, implementation
CS LeaderDeepDeepRetention, expansion

The pairing: Industry Engineer + SaaS Seller on every significant deal.


Role Profiles by Stage

Founding Team (0-10 customers)

RoleWhoFocus
Founder/CEODomain expertSales, product direction
Technical Co-founderBuilderMVP, iterate fast
First hireIndustry operatorCustomer success, feedback

Anti-pattern: Hiring SaaS generalists before PMF.

Growth Team (10-100 customers)

FunctionHireWhy
SalesIndustry AECredibility in room
SolutionsTechnical + domainImplementation success
CSIndustry operatorRetention, expansion
ProductSaaS PM + domain advisorBalance velocity with depth

Scale Team (100+ customers)

FunctionStructureNotes
SalesIndustry verticalsSub-segment by size or geo
CSPooled + namedNamed for enterprise
SolutionsPre-sales + post-salesSpecialize
ProductPlatform + vertical podsShared infra, domain teams

Don't Hire "SaaS" CS Leaders

From the Linear playbook—vertical CS is different:

SaaS CS LeaderVertical CS Leader
Optimizes for scaleOptimizes for depth
Playbook-drivenRelationship-driven
Metrics firstOutcomes first
Industry agnosticIndustry native

The risk: SaaS CS leaders bring horizontal playbooks that don't fit vertical relationships.

The fix: Hire operators who became CS, not CS who learned operations.


AI + Human Split

Where AI handles work vs. where humans are essential:

FunctionAI RoleHuman RoleAI % Today
Lead genIdentification, enrichmentQualification, outreach60%
SalesPrep, follow-up, adminDiscovery, negotiation, close30%
SolutionsDocumentation, configArchitecture, trust-building40%
CSHealth monitoring, alertsRelationship, expansion35%
SupportL1 resolution, triageComplex issues, escalation70%

The trend: AI percentage increasing 10-20% per year in each function.

See Work Charts for the full framework.


Hiring Profile: Industry Engineer

The role that makes or breaks vertical sales:

Background:

  • 5-10 years operating in the vertical
  • Managed the workflow you're replacing
  • Known and respected in the industry
  • NOT a career salesperson

Responsibilities:

  • Lead discovery conversations
  • Translate product to industry language
  • Build trust with operators
  • Inform product roadmap

Compensation:

  • Lower base than traditional AE
  • Higher variable tied to outcomes
  • Equity for key hires

Team Audit

Score your current team composition:

QuestionScore 1-5
Do customer-facing roles have domain scars?
Can you speak customer language, not SaaS language?
Is your CS focused on outcomes, not metrics?
Do you hire operators who learned sales, not salespeople who learned operations?
Are you pairing industry expertise with SaaS process?

Threshold: If any score is below 3, you have a hiring problem.


Context

Questions

Which vSaaS player type — bootstrapped specialist, venture-backed category creator, or horizontal player going vertical — is most likely to capture the majority of value in a consolidating vertical?

  • At what market share threshold does a vSaaS leader become attractive enough for acquisition by a horizontal SaaS player or PE firm?
  • How does the introduction of AI-native competitors change the competitive dynamics for established vSaaS players with large customer bases but legacy codebases?
  • Which vertical SaaS player (from the landscape) has the most durable moat against AI disruption — and what makes that moat defensible?