Jobs-to-Be-Done Interviews for SaaS

Jobs-to-be-done, usually shortened to JTBD, is a framework for understanding why customers buy products. Instead of starting with demographics or feature lists, it asks what progress a customer is trying to make in a specific situation. A jobs to be done interview for a SaaS product reconstructs the story of a real purchase: what was happening in the customer's world, what made the old way of working intolerable, what they considered, and what nearly stopped them.

Those stories reveal the circumstances, motivations and anxieties that lead people to switch to your product. For a small SaaS team, the insights feed directly into positioning, messaging, onboarding and product decisions. This guide explains the core idea, who to interview, how to run the conversation, how to analyze what you hear and how to put it to use.

The core idea

The central idea of JTBD is that customers "hire" products to make progress in their lives or work. A marketing manager might hire an analytics tool not simply to see data, but to explain results to leadership with confidence. The job is the progress, and the product is one possible way of achieving it.

Thinking this way changes three things. First, it helps you describe value in the customer's terms. "Confidently explain results to leadership" speaks to the marketing manager far more directly than "advanced attribution modeling." Second, it helps you identify your real competitors. If the job is explaining results to leadership, you are competing not only with other analytics tools but with spreadsheets, an analyst's time, a consultant and the option of not reporting at all. Third, it helps you prioritize features that support the job, rather than features that sound impressive but do not help anyone make progress.

Many teams discover through JTBD interviews that their main competitor is the spreadsheet, the manual process or the decision to put the problem off for another quarter.

Who to interview

The best interviewees are customers who recently switched to your product, ideally within the last few months. Their memory of the decision is still fresh. They can remember what triggered the search, which options they looked at and what worried them. Customers who bought years ago tend to tell a tidied-up story shaped by everything that has happened since.

Two other groups are worth including when you can reach them. Customers who switched away from your product can tell you what job you failed to do, or what changed in their situation that made a different solution a better fit. Prospects who evaluated you and chose a competitor can tell you what tipped the decision. Both are harder to recruit, and both often provide the most uncomfortable and useful insights.

For a small team, a practical starting point is to look at customers who signed up in the last three months, pick those who are actively using the product, and send a short, personal invitation from a founder or product lead. Explain that you want to learn about their decision and that there is nothing to buy.

Preparing for the interview

Plan for a 30 to 60 minute conversation. Shorter calls rarely leave enough room to reconstruct the full timeline, and longer ones tire both sides. Tell the interviewee at the start that you want to understand their decision. You are not selling anything and you are not collecting feature requests. Setting that expectation keeps the conversation from turning into a product feedback session, which is useful in its own way but answers different questions.

Ask permission to record. A recording lets you listen fully during the conversation and return to exact phrasing later, which matters because the customer's own words are among the most valuable outputs of the interview. If you can, bring a second person to take notes, so the interviewer can focus entirely on the conversation.

The timeline approach

JTBD interviews typically reconstruct the buying journey as a timeline, moving from the first moment the customer felt something was wrong to their experience after starting with your product. Working through it chronologically helps people remember details they would not recall if asked directly.

First thought

Start at the beginning, before any searching happened.

When did you first realize you needed something different?

People often name a vague period at first. Push gently for a specific moment, such as a meeting that went badly or a task that took far too long.

Passive looking

Next, explore the period when the customer was aware of the problem but not yet acting on it.

What were you doing at that time? Did you notice any solutions?

This phase can last months. Customers may have seen ads, heard colleagues mention tools or bookmarked articles without doing anything about it.

The event

Something usually turns passive awareness into active searching.

What happened that made you start actively looking?

Triggering events are among the most valuable findings. A new boss, a failed audit, a funding round or a lost customer can all push someone from tolerating a problem to solving it.

Active looking

Then explore the search itself.

What options did you consider? How did you evaluate them?

Listen for the full set of alternatives, including doing nothing, hiring someone or building something in-house.

Deciding

Next comes the decision.

What made you choose this product? What almost stopped you?

The second question often produces the most useful answer of the whole interview, because it reveals the anxiety you need to address for future buyers.

Using

Finally, ask about life after the purchase.

What happened after you started? Did it meet expectations?

This shows whether the job is actually being done and where onboarding helped or hurt.

Uncovering the four forces

JTBD describes four forces that shape every switching decision. Two push toward change and two hold people back.

Push

The push is the set of problems with the current situation. It is the frustration that makes the status quo uncomfortable.

What was frustrating about how you did things before?

Pull

The pull is the attraction of the new solution, the picture of a better way of working.

What made this product appealing?

Anxiety

Anxiety covers the concerns about switching: cost, risk, effort, the chance of choosing wrong.

What worried you about changing?

Habit

Habit is attachment to the current way of doing things, even when it is flawed. Familiar processes are comfortable, and changing them takes energy.

What made it hard to move away from the old approach?

A switch happens when push and pull outweigh anxiety and habit. That framing is practical. Your marketing can strengthen the push by naming the frustration clearly and strengthen the pull by showing the better outcome. Your sales process, onboarding and guarantees can reduce anxiety. Migration help, templates and imports can weaken habit by making the change less effortful.

Interview technique

Ask about specific moments rather than general opinions. "Tell me about the last time you prepared that report" produces far richer detail than "How do you feel about reporting?" Use follow-up prompts such as "Tell me more about that" or "What happened next?" to dig deeper whenever an answer touches something interesting.

Avoid leading questions. "Was the main reason our integrations?" plants an answer. "What made you choose us?" lets the customer tell you. Let silence work as well. After an answer, pausing for a few seconds often prompts the interviewee to add the detail that matters most.

Focus on behavior rather than hypothetical preferences. What people actually did is reliable evidence. What they say they would do in a hypothetical situation is much less reliable, so steer back to real events whenever the conversation drifts into "I would probably."

Analyzing interviews

After several interviews, review the recordings and notes together and look for patterns. Group findings by triggering event, shared frustration, alternatives considered, decision criteria and anxieties or objections. A simple document or spreadsheet with a row per interview and a column for each category is enough for a small team.

Then summarize the patterns as job statements, using a consistent structure:

When [situation], I want to [motivation], so I can [expected outcome].

For example:

When our board asks about marketing performance, I want to quickly show which channels drive revenue, so I can defend our budget confidently.

A good job statement describes a situation and a desired outcome without mentioning your product. If you find several distinct job statements, you may be serving different segments with different needs, which is useful to know when deciding where to focus.

Using the insights

Positioning and messaging

Use the customer's language and the jobs you identified in homepage copy, ads and sales materials. A headline built from a real job statement tends to resonate more than one built from internal feature names.

Content

Create content that addresses the triggering events and anxieties you uncovered. If many customers started looking after a difficult board meeting, a guide to preparing board-level marketing reports reaches people at the exact moment the job becomes urgent.

Sales

Share common objections and decision criteria with whoever runs sales conversations. Knowing what nearly stopped past buyers helps the team address those concerns early rather than discovering them late.

Onboarding

Design onboarding around the job customers hired the product to do. If the job is reporting to leadership, the first success moment should be a report the user could show their boss.

Product

Prioritize features that support the core job, and be skeptical of requests that do not connect to it. JTBD gives you a principled way to say no.

How many interviews

Patterns often emerge after a modest number of interviews, especially within a single segment. Keep going until new interviews add little you have not heard before. If each new conversation still surprises you, you either need more interviews or you are speaking with customers from several different segments, and should analyze them separately.

Common mistakes

The most common mistake is asking about features instead of situations, which turns the interview into a feedback session. Interviewing customers who bought long ago produces reconstructed stories rather than real ones. Leading questions produce the answers you expected instead of the truth. And failing to analyze the interviews systematically leaves the team remembering only the most vivid anecdote.

The takeaway

JTBD interviews reveal why customers really buy, and the answer is often different from what the product team assumes. Interview recent switchers, walk through their timeline, listen for the four forces, and summarize what you learn as job statements. Then use those statements to shape your messaging, content, sales conversations, onboarding and roadmap.