An example of a customer segmentation framework for a SaaS product combines three segmentation types — behavioral, firmographic, and needs-based — to answer the question that matters most for product decisions: which customer segments should drive the roadmap, and which segments represent a distraction from the core product's potential.
Most SaaS companies segment customers by company size (SMB, mid-market, enterprise) and call it done. This is firmographic segmentation and it is useful — but it does not tell you why different customers use your product differently, what they need next, or which segments have the highest expansion potential.
A complete segmentation framework uses all three dimensions and maps each segment to concrete product and prioritization decisions.
The Three Segmentation Dimensions
H3: Dimension 1 — Firmographic Segmentation
Company-level attributes: size, industry, geography, revenue, growth stage.
Use for: Pricing tiers, sales motion design, compliance and security requirements, customer success allocation.
Not useful for: Feature prioritization, UX decisions, or understanding why customers churn.
Example firmographic segments for a B2B SaaS project management tool:
- Segment A: 1–20 employees, seed/Series A, technology sector
- Segment B: 20–200 employees, Series B–C, professional services
- Segment C: 200+ employees, enterprise, financial services
H3: Dimension 2 — Behavioral Segmentation
How customers actually use your product: which features they use, how frequently, what workflows they've built, and where they drop off.
Use for: Feature prioritization, onboarding optimization, identifying power users vs. at-risk accounts, product-led growth motions.
Example behavioral segments for the same project management tool:
- Power users: High DAU, use templates, create recurring tasks, invite external collaborators. Most likely to expand and refer.
- Casual adopters: Log in 2–3x per week, use basic task creation only, rarely collaborate. High churn risk.
- Integration-dependent users: Low direct app usage but high API activity — product is embedded in their workflow via integrations. Sticky but invisible to standard usage metrics.
According to Lenny Rachitsky's writing on product-led growth, behavioral segmentation is the most underutilized segmentation dimension in SaaS — most PMs know their firmographic segments perfectly but could not describe the behavioral difference between their highest-retention and lowest-retention customers.
H3: Dimension 3 — Needs-Based Segmentation
What jobs customers are hiring your product to do. This requires qualitative research — you cannot derive it from usage data alone.
Use for: Roadmap prioritization, positioning, feature development, identifying unmet needs that new products could address.
Example needs-based segments for the same project management tool:
- Coordination-focused: Hiring the product to keep distributed teams synchronized. Primary need: visibility and async communication.
- Delivery-focused: Hiring the product to ship projects on time. Primary need: milestone tracking and dependency management.
- Client-reporting-focused: Hiring the product to communicate project status to external clients. Primary need: clean external-facing views and reporting.
These three needs-based segments may have identical firmographic profiles (same company size, same industry) but require completely different feature investments to retain.
According to Shreyas Doshi on Lenny's Podcast, the reason most product roadmaps feel incoherent to users is that the PM is building features for three different needs-based segments simultaneously without acknowledging the trade-offs — a feature that serves the delivery-focused segment perfectly may actively frustrate the coordination-focused segment.
Building the Segmentation Framework
H3: Step 1 — Identify Your Segments
Combine all three dimensions to create a matrix. For each cell, estimate:
- Number of accounts in this segment
- ARR contribution
- Churn rate
- NPS score
- Expansion potential (estimated)
H3: Step 2 — Identify Your Core Segment
The core segment is the one your product is most designed for and where you have the highest retention and expansion rates. This is your primary roadmap audience.
Every product decision should be evaluated against the question: "Does this serve our core segment, or are we diluting for a different segment?"
H3: Step 3 — Map Segments to Product Decisions
For each segment, identify:
- Top 3 features they rely on (protect these — any degradation here causes churn)
- Top 3 unmet needs (based on qualitative research — these are your highest-leverage roadmap items for this segment)
- Features they don't use (candidates for simplification or removal)
H3: The Segmentation-to-Roadmap Connection
Use the segment analysis to structure roadmap discussions:
"Our core segment is [X]. They rely on [Y] and have unmet needs around [Z]. This quarter's roadmap should invest primarily in [Z] because it has the highest impact on retention and expansion for our core segment. We are explicitly not investing in [W] because it primarily serves [non-core segment] and would dilute focus."
According to Gibson Biddle on Lenny's Podcast, the clearest signal that a SaaS product has a segmentation problem is when the roadmap is a compromise — every feature serves someone but no feature deeply serves anyone. The solution is not better features; it is a clearer decision about which segment to serve and willingness to explicitly not serve the others.
FAQ
Q: What is customer segmentation in SaaS product management? A: The process of grouping customers into distinct categories based on shared firmographic attributes, behavioral usage patterns, or jobs-to-be-done to inform product priorities, pricing, and roadmap decisions.
Q: What are the three main types of customer segmentation for a SaaS product? A: Firmographic segmentation by company size and industry, behavioral segmentation by product usage patterns, and needs-based segmentation by the jobs customers are hiring the product to do.
Q: How does customer segmentation affect SaaS product roadmap decisions? A: Segments allow PMs to identify which customer group drives the highest retention and expansion, then prioritize roadmap investments that deepen value for that core segment rather than spreading investment across incompatible needs.
Q: How do you identify needs-based customer segments? A: Through qualitative research — customer interviews, jobs-to-be-done analysis, and thematic analysis of support tickets and NPS verbatims. Needs-based segments cannot be derived from usage data alone.
Q: What is the most common customer segmentation mistake in SaaS? A: Over-relying on firmographic segmentation (company size, industry) without understanding behavioral or needs-based differences between customers — which leads to roadmaps that serve the average of all segments and deeply serve none of them.
HowTo: Build a Customer Segmentation Framework for a SaaS Product
- Build firmographic segments by company size, industry, and growth stage to inform pricing tiers and sales motion design
- Analyze behavioral data to identify usage patterns and create behavioral segments such as power users, casual adopters, and integration-dependent users
- Conduct qualitative research through customer interviews to identify the jobs customers are hiring your product to do and create 3 to 5 needs-based segments
- Map each segment to ARR contribution, churn rate, NPS, and expansion potential to identify your core segment — the one your product is most designed for
- For your core segment, identify the top 3 features they rely on to protect and the top 3 unmet needs that represent your highest-leverage roadmap investments
- Use the segmentation framework to structure every roadmap discussion by explicitly stating which segment each investment serves and which segments are being explicitly not served