Claim
For SaaS, the most reliable segmentation comes from the switch interview applied to recently-converted, actively-paying customers (so they still remember life before the product). The four questions are: What struggle pushed you to look for a solution? How did you find us? What was the moment you knew this product was right? What can you do now that you couldn't before? Distinct customer segments emerge from shared jobs, not from demographic data.
Mechanism
Recent converters have intact memory of the switch event; long-time customers have rationalized it. Survey 100-200 of them (25-50 minimum responses for pattern recognition), then run 10-12 deep interviews with the most articulate, kept open-ended ("Would you ask this at a bar?"). Cardinal sin: asking about specific features. Output is a job-story template ("When [situation], I want to [motivation], so I can [outcome]") and verbatim language that flows directly into onboarding emails, copy, and feature priorities. Calendly example: salespeople and professors emerged as distinct jobs, enabling segment-specific onboarding.
Conditions
Holds when:
- Product has enough recent converters to populate the survey/interview pool.
- Marketing has authority to act on the segments (not just document them).
Fails when:
- Pre-PMF products where the converters themselves are atypical edge cases.
- Markets where the buyer and user are different and the user can't articulate the buyer's job.
Evidence
"Identify 100-200 'high-value' customers — people who are actively paying and recently converted, so they still remember life before the product."
"The cardinal sin is asking about specific features rather than letting customers describe their own journey."
— Claire Suellentrop (synthesized from operator's published work)
Signals
- Onboarding emails branch by detected job, not by signup form fields.
- Pricing page copy uses verbatim phrases from interview transcripts.
- New-feature priorities map to named jobs, not internal roadmap themes.
Counter-evidence
Behavioral-segmentation school (Sarah Levinger, BJ Fogg) argues observed in-product behavior beats self-reported job stories — what users do reveals what they actually need, regardless of how they describe it.
Cross-references
- (none in current corpus)