Jobs to Be Done: Find the Real Reason Users Pay
People rarely set out to buy an app category. They want a life outcome — steadier finances for a home purchase, confidence speaking a language on holiday, or better sleep. Jobs to Be Done (JTBD) names that underlying outcome, so pricing, onboarding and retention work can be built around the problem instead of the product label.
Start with the outcome, not the app category
A JTBD is the goal or problem a customer wants solved, not the tool they happen to pick. Saving for a house may really mean creating a home that feels personal; learning Spanish may really mean feeling able to talk comfortably while travelling. An app is only one possible route — lessons, practice with friends, or changes to a current home could serve the same job.
That distinction matters for monetisation because willingness to pay follows the strength of the underlying drive. A trip to a large city where English is widely spoken may make language practice a nice extra. A trip to a smaller, less English-speaking place may make the same practice urgent, especially for someone anxious about being understood. The product has not changed; the job and its emotional weight have.
Painkiller or vitamin? Diagnose by behaviour
Use this as a working distinction, not a label for the whole company. The same product can be a painkiller for one job and a vitamin for another.
Vitamin pattern — nice to have, hard to prove value, first to cut when budgets tighten:
- Infrequent use
- Slow first key action
- Short sessions
- Lower lifetime value
Painkiller pattern — urgent, noticeable value, less price sensitivity:
- More frequent use
- Longer, more engaged sessions
- Higher lifetime value
Checklist: For your highest-value users, can you name the job in their words? Is that job urgent enough to sustain use without reminders? If not, which deeper motivation would make it urgent?
Run JTBD interviews before the paywall
Spend most of the conversation before the product. Ask how the problem emerged, how long it lasted, what alternatives were tried, and what was liked or disliked about each. Only then explore first impressions, important features, feelings during use, and frequency or situations of use.
Interview two groups side by side:
- High lifetime value, frequent, recent users — to learn where you already act as a painkiller
- Low lifetime value, infrequent users — to learn where you are only a vitamin
Core prompts to adapt:
- What led you to try this app?
- How long had you been struggling with this problem, and how did you realise it was a problem?
- Describe the moment you first considered solving it and what prompted that decision.
- How did you search for a solution, where did you look, and what else did you try?
- What made you choose this app, and how did you come across it?
- Which features matter most, how do you feel while using it, and when do you use it?
Map the driver before choosing the model
Functional drivers — the practical task Examples: learning a language, tracking spending, getting fit. Monetisation fit: subscription or free trial often works because ongoing use delivers the result; freemium can work when the core habit takes time to form; a one-off payment can fit a short, bounded task. Ask: What were you hoping to achieve? What challenges or inefficiencies did you face before?
Emotional drivers — the feeling the user wants Examples: peace of mind about money, confidence in conversation, a sense of accomplishment. Monetisation fit: freemium subscription can build the habit first; in-app purchases can suit small moments of satisfaction, such as continuing a game or unlocking extra play. Ask: How did you feel before? How does solving this make you feel? What fears or anxieties prompted the search? How do you feel when progress is slow?
Social drivers — status, belonging, or expectations from others Examples: sharing activity results, using a new language with colleagues, buying a home because peers have done so. Monetisation fit: often harder to sustain by subscription alone; advertising, in-app purchases, or freemium to grow a community may fit better, especially where value depends on other people. Ask: Have you shared this with friends or family, and what did you say? Do you feel pressure to achieve it? Whose opinion about your progress matters?
Most jobs mix drivers. Your task is to find which one is strongest among your best customers, then check whether your model matches it.
Turn the job into onboarding and pricing
Onboarding can capture the job directly. One meditation app asks users to pick a goal such as sleep, then shows matching sleep content and frames its free trial around better sleep. That is the pattern to copy: collect the job, tailor the next screen, and test whether that job correlates with retention, lifetime value and conversion.
Use interview language in experiments. If users say falling asleep faster rather than sleeping better, test that wording in marketing first, then in onboarding. Also check whether the home screen and early flow actually reflect the selected job, rather than only the paywall doing so.
Pricing decision: put behind premium the features that directly complete the job. Upsell to deepen success on the same job — for example, advanced sleep courses for a sleep-focused user. Cross-sell a complementary job that helps the same goal — for example, nutrition support alongside marathon training. Base both on observed JTBD patterns, not guesswork.
Reduce churn and expand by adjacent jobs
Some churn is unavoidable: for some people the product will remain a vitamin. For the rest, ask churned users what they hoped to solve, why expectations were not met, and whether they switched to another solution and why. That reveals gaps in the job you thought you served.
For growth, start with your strongest high-value job, then look for adjacent personas with the same broad job but different needs. A running app that began with first-race training, for example, can expand toward longer races and triathletes, where longer training periods and higher injury risk can support longer subscriptions and greater appreciation for guidance. The lesson is to expand by job persona and lifetime value, not by chasing every new audience.
Decision checklist
A practical sequence:
- Match the core model to the dominant driver: functional, emotional or social
- Aim acquisition messages at the job behind high lifetime value
- Write monetisation messages in the customer's job language
- Gate the features that complete that job
- Prioritise product fixes that help those customers succeed
- Look for related jobs and personas to expand into
Combine interview insight with usage and revenue data. The aim is not to assume what users want, but to prove which job makes the product indispensable enough to pay for.
| Driver | What it means | Model fit to test | Interview probe |
|---|---|---|---|
| Functional | Practical task to complete | Subscription, trial, freemium, or one-off for bounded tasks | What were you hoping to achieve? |
| Emotional | Feeling sought or avoided | Freemium subscription; in-app purchases for moments of satisfaction | How did you feel before and after? |
| Social | Status, belonging, expectations | Advertising, in-app purchases, or freemium to build community | Have you shared this? Whose opinion matters? |
Most users show a mix; identify the strongest driver among high-value customers.
Frequently asked questions
What were you hoping to achieve when you started using the app, and what challenges did you face before it? (functional-driver check)
Ask what the person hoped to achieve when they started, and which challenges or inefficiencies they faced beforehand. Those answers surface the practical problem the product must solve, separate from feelings or social pressure.