B2B Customer Segmentation

B2B SaaS companies use three primary segmentation approaches, each surfacing different strategic insights. Firmographic segmentation: dividing by company size, industry, revenue, geography, or technology stack. This is the most common approach and the easiest to implement from CRM data. It produces segments like "Series B-D SaaS companies with 50–500 support agents" — useful for ICP definition and sales targeting. Behavioral segmentation: grouping customers by how they use the product — which features they adopt, their usage frequency, their support interaction patterns. This surfaces segments invisible to firmographic analysis: "power users who have adopted 8+ features" vs. "limited users who primarily use 2 core features." Most predictive of retention and expansion outcomes. Needs-based (psychographic) segmentation: dividing by the customer's primary motivation for using the product — "efficiency-focused buyers who want to do more with fewer resources" vs. "insight-focused buyers who want data to make better decisions." This segmentation is hardest to derive from data (requires qualitative research) but produces the most differentiated messaging and product strategy insights.

Enterprise vs. SMB is the most consequential segmentation decision a SaaS company makes because it drives fundamentally different operating models. Enterprise (typically $50k+ ACV): requires named CSMs with low account ratios (1:7 to 1:20 accounts); complex, consultative sales cycles (6–18 months); custom contract and SLA negotiation; dedicated technical account management; procurement and security review requirements; and product capabilities like SSO, advanced RBAC, audit logs, and data residency that are enterprise-table-stakes. Support model: differentiated SLAs, named support contacts, dedicated Slack channels. SMB (typically under $5k ACV): served at high efficiency ratios (a CSM may manage 200+ accounts); self-serve onboarding and success programs supplemented by digital-touch CS; standardized contracts. Support model: primarily self-service with email support SLAs measured in business hours. A company serving both segments simultaneously must run essentially two parallel operating models — and the tension between the high-touch enterprise model and the efficient SMB model is one of the primary challenges of "mixed" SaaS businesses.

Segmentation is only operationally valuable when it drives different decisions and experiences for different segments. Product Ops uses segmentation in: roadmap prioritization (features requested exclusively by enterprise accounts are evaluated differently than features benefiting the full base — their lower frequency of request may be offset by higher ARR impact); A/B testing program design (experiments should be segmented in results analysis — an onboarding change that improves SMB conversion by 30% but harms enterprise conversion by 15% should not be rolled out globally without an enterprise-specific variant); and analytics reporting (retention curves, feature adoption rates, and health score distributions reported separately by segment reveal patterns obscured in blended analysis). CS Ops uses segmentation in: coverage model design (CSM-to-account ratios differ dramatically by segment tier); compensation structure (CSMs managing enterprise accounts earn different OTE than digital-touch SMB CSMs); and success plan templates (enterprise success plans are custom and detailed; SMB success plans are lightweight digital-touch or automated).