Most SaaS companies describe what their product does, not what job it's hired to do. Two companies sell "project management software." One positions around features: Gantt charts, time tracking, resource allocation. The other positions around the job: help remote teams feel coordinated without micromanaging.
The second one wins every time.
Because people don't buy products. They hire them to get a job done. When you understand the job your customers hire you to do, positioning becomes obvious. When you focus on features, you sound like everyone else.
Jobs to Be Done (JTBD) is a framework that helps you understand what customers hire your product to accomplish in their lives, leading to positioning that connects with real buyer motivation. It shifts focus from who your customers are (demographics) to what progress they're trying to make (motivation).
87% of companies struggle with differentiated positioning, according to the Product Marketing Alliance 2023 Report. The reason isn't lack of creativity. It's lack of understanding about what job customers actually need done.
Jobs to Be Done focuses on understanding the progress customers are trying to make in their lives, rather than who they are demographically.
Traditional personas tell you that Sarah is a 35-year-old marketing director at a 200-person SaaS company who likes yoga and reads Harvard Business Review. JTBD tells you that Sarah hires your product when she's stressed about team alignment and needs to feel confident that nothing is falling through the cracks without becoming a micromanager.
One describes a person. The other describes a situation and desired outcome.
Clayton Christensen's famous milkshake example illustrates this perfectly. A fast-food chain wanted to improve milkshake sales, so they researched who bought milkshakes. Demographics showed busy commuters bought them in the morning. But that didn't explain why they hired milkshakes for that job.
The real insight came from understanding the job. Morning commuters had a long, boring drive ahead and needed something that would keep them full until lunch while being easy to consume with one hand. Competitors weren't other milkshakes. They were bagels, coffee, bananas, and even doing nothing.
This matters for positioning because when you understand the job, you can position against the real competition. Your project management software isn't competing with other PM tools. It's competing with Slack chaos, email threads, and the anxiety of not knowing what's happening.
Only 23% of B2B buyers can clearly articulate how solutions differ from competitors, according to Gartner's B2B Buying Journey Report. When everyone positions around features, differentiation becomes impossible.
Every product gets hired to do three types of jobs: functional, emotional, and social.
Functional jobs are the practical tasks customers need accomplished. Emotional jobs are about how they want to feel. Social jobs are about how they want to be perceived by others.
Most SaaS companies only address the functional job, which is why their positioning feels generic.
Take Slack. The functional job is team communication. Send messages, share files, organize conversations in channels. Every competitor can claim the same functional job with minor variations.
The emotional job is reducing information anxiety. Teams hire Slack when they're tired of wondering if they missed something important or if their message got lost in an email thread. They want to feel connected and informed without being overwhelmed.
The social job is appearing modern and efficient. Teams that use Slack signal they're forward-thinking and collaborative. Email feels dated. Slack feels progressive.
Understanding all three jobs transforms your messaging. Instead of "team communication platform," Slack positions as "where work happens." The functional job is implied. The emotional and social jobs are explicit.
[NATHAN: Share a specific example of how JTBD research changed your understanding of what customers actually hired Copy.ai or another product to do - include the surprising job you discovered vs. what you initially thought]
JTBD interviews focus on switching moments rather than satisfaction surveys.
The key question is: "Tell me about the last time you switched from [old solution] to [new solution]." Then follow the timeline from trigger to outcome.
Start with the situation that triggered their search. What wasn't working? What was the breaking point? Don't accept generic answers like "we needed better collaboration." Drill down: "What happened that day that made you realize your current solution wasn't working?"
Explore what they considered. This reveals the real competitive set. Often it includes non-consumption (doing nothing) and workarounds (spreadsheets, email, manual processes) that you'd never identify through competitor research.
Understand the decision criteria. What made them choose your solution? What concerns did they have? What alternatives did they almost pick instead?
Most importantly, probe the desired outcome. "What were you hoping would be different?" This uncovers the emotional job. Customers rarely say they wanted "better project management." They say they wanted to stop worrying about dropped balls or feel confident their team was aligned.
Here are the specific questions that work:
Trigger questions:
- What prompted you to look for a solution like ours?
- What was happening in your work that made the status quo unacceptable?
- Can you remember a specific moment when you thought "there has to be a better way"?
Consideration questions:
- What did you consider before choosing us?
- What were you doing before you had any solution at all?
- What almost stopped you from switching at all?
Outcome questions:
- What would have to happen for you to consider this a success?
- How would your day be different if this worked perfectly?
- What are you hoping to avoid or eliminate completely?
For more detailed interview methodology, check out our guide on customer interview questions that reveal what buyers actually want.
The timeline approach works because it grounds responses in actual behavior rather than hypothetical preferences. People are terrible at predicting what they'll do, but they're accurate at describing what they did.
The best-positioned SaaS companies understand all three jobs their customers hire them to do.
Notion isn't positioned as "productivity software" or "knowledge management." They position around the job: helping knowledge workers feel organized without being constrained by rigid structure.
Functional job: Organize information and workflows. Emotional job: Feel creative control over your workspace. Social job: Appear thoughtful and intentional about how you work.
Their messaging reflects this understanding: "Write, plan, share. With AI at your side." The functional elements are there, but the focus is on creative control and flexibility.
Figma could position as "design software" but instead focuses on the collaboration job: help designers collaborate without losing creative control.
Functional job: Create and iterate on designs. Emotional job: Maintain creative integrity while incorporating feedback. Social job: Demonstrate modern, collaborative design practices.
"Nothing great is made alone" speaks directly to the social and emotional jobs, not the functional ones.
Calendly avoids "scheduling software" positioning and focuses on the anxiety-reduction job: help busy professionals schedule meetings without the back-and-forth email dance.
Functional job: Coordinate calendars and book meetings. Emotional job: Eliminate scheduling stress and friction. Social job: Appear respectful of others' time and professionally organized.
"Scheduling infrastructure for absolutely everyone" positions Calendly as essential infrastructure rather than optional software.
[NATHAN: Describe a time when you realized you were competing against the wrong alternatives because you didn't understand the real job - what was the actual competition?]
Each of these examples shows how understanding the complete job creates positioning that differentiates through context rather than features.
Translating JTBD research into positioning requires identifying your primary job and mapping the real competitive landscape.
Start by identifying your primary job from the research. Look for patterns in the switching stories. What job comes up repeatedly? What outcome do customers consistently describe?
Most products serve multiple jobs, but one usually dominates. Focus your positioning around that primary job while acknowledging the secondary ones in your messaging architecture.
Next, map the real competition. JTBD reveals competitors you'd never identify through feature analysis. If customers hire you to "feel confident nothing is falling through the cracks," you're competing against manual tracking, anxiety-driven micromanagement, and the status quo of hoping everything works out.
This expanded competitive view opens new positioning angles. Instead of comparing features with similar software, you position against the pain of the current state.
Use this positioning template: "When [situation], [target customer] hires [product] to [functional job] so they can [emotional outcome] without [constraint/anxiety]."
Example: "When remote teams feel disconnected and information gets lost, marketing leaders hire Notion to organize their team's knowledge so they can feel confident everyone has access to what they need without creating rigid processes that slow people down."
This template forces you to include the situational context (when), the emotional outcome (so they can feel), and the constraint you help avoid (without).
For more guidance on crafting these statements, see our complete guide to writing a positioning statement that differentiates.
The key insight is that great positioning starts with the job, not the product. When you lead with the situation and desired outcome, differentiation becomes natural because you're positioning in the customer's context, not the vendor landscape.
Building a comprehensive voice of customer program ensures you continuously understand how customer jobs evolve and your positioning stays relevant.
What is Systems-Led Growth?
JTBD research becomes powerful input for SLG systems. Customer interview transcripts flow through AI workflows that automatically extract job stories, generate positioning variations, and create messaging frameworks based on the specific language customers use to describe their needs. One interview becomes multiple positioning assets without starting from a blank page. Learn more about the SLG approach.
Companies using JTBD frameworks see 85% higher innovation success rates according to Jobs-to-be-Done Institute research, because they build solutions around real customer progress rather than assumed needs.
What's the difference between Jobs to Be Done and user personas?
Personas describe who your customers are demographically, while JTBD explains what progress they're trying to make. A persona tells you Sarah is 35 and works in marketing. JTBD tells you Sarah hires solutions when she needs to feel confident her team is aligned without micromanaging.
How many customer interviews do I need for reliable JTBD insights?
Start with five interviews per customer segment. You'll begin seeing patterns after three to four interviews, but five gives you confidence in the insights. Quality matters more than quantity, so focus on customers who recently switched to your solution.
Can JTBD work for technical products with complex buyer journeys?
Yes, especially for technical products. JTBD reveals that technical buyers often hire solutions for emotional jobs like reducing implementation risk or appearing innovative to leadership, not just functional capabilities.
How often should I update my JTBD research?
Conduct fresh JTBD interviews quarterly, especially after major product launches or market shifts. Customer jobs evolve as markets mature and new alternatives emerge. What worked six months ago might miss current motivations.
What if customers can't articulate why they switched?
Focus on timeline questions rather than asking directly about motivation. "What happened the week before you started looking?" and "Walk me through your decision process" reveal motivations customers might not consciously recognize.
According to Harvard Business Review's innovation research, companies that master JTBD see 2.5x higher success rates in new product development because they build around customer progress rather than competitor features.
Great positioning starts with understanding the job your customers hire you to do, not describing what your product does.
Most teams skip the research phase and jump straight to messaging, which is why their positioning sounds like everyone else's. They optimize for clarity about features instead of connection to motivation.
The companies that break through the noise understand that customers don't buy project management software. They hire solutions to help them feel organized, confident, and in control of complex work without becoming bottlenecks.
Run three JTBD interviews this month. Ask about switching moments, not satisfaction levels. Focus on the timeline from trigger to outcome. Listen for the functional, emotional, and social jobs your product gets hired to do.
When you truly understand why customers hire you, positioning stops being a creative exercise and becomes a documentation process. You're not inventing differentiation. You're describing the unique value you already create in your customers' lives.
The job was always there. Most companies just never asked about it.