Jobs to Be Done (JTBD): JTBD for Pricing Strategy

Using JTBD to design pricing that aligns with the value customers perceive from the job being done, not feature comparisons.

How to Apply

What is the economic value of getting this job done well vs poorly?

How much are customers paying for current (often imperfect) solutions?

Price based on value delivered for the job, not based on features or competitors.

Create pricing tiers that match different job frequencies or complexity levels.

Run pricing experiments to optimize conversion and revenue per customer.

Expected Outcomes

✓ Value-based pricing that customers accept
✓ Higher willingness to pay
✓ Pricing tiers that match real usage patterns

Real-World Examples

Common Pitfalls

⚠Pricing based on feature count rather than job value

⚠Underpricing because you do not understand the job value

Ehsan's Insight

JTBD-based pricing asks one question traditional pricing ignores: "what is the customer paying NOW to get this job done?" This includes money, time, frustration, and opportunity cost. Calendly priced against the JTBD cost of scheduling: the average professional spends 17 minutes per meeting in email back-and-forth scheduling. At a $75/hour salary, that is $21 per meeting. Calendly at $12/month for unlimited meetings is not competing with other scheduling tools at $8-15/month — it is competing with $21 × 20 meetings = $420/month in hidden scheduling costs. This reframing lets you charge dramatically more than feature-based pricing suggests. HubSpot CRM launched free because the JTBD cost of NOT having a CRM (lost deals, no pipeline visibility) is so high that free removes the adoption barrier, and the upgrade path captures the value once the job is being done.

Ehsan Jahandarpour

AI Growth Strategist & Fractional CMO

Forbes Top 20 Growth Hacker · TEDx Speaker · 716 Academic Citations · Ex-Microsoft · CMO at FirstWave (ASX:FCT) · Forbes Communications Council

Frequently Asked Questions

When should I use Jobs to Be Done (JTBD) for pricing strategy?

Using JTBD to design pricing that aligns with the value customers perceive from the job being done, not feature comparisons.

What are the steps in JTBD for Pricing Strategy?

There are 5 key steps: Understand the value of the job, Map willingness to pay, Price against the job, Design tiers around jobs, Test and iterate.

What results can I expect from JTBD for Pricing Strategy?

Value-based pricing that customers accept. Higher willingness to pay. Pricing tiers that match real usage patterns.

What are common mistakes with JTBD for Pricing Strategy?

Pricing based on feature count rather than job value. Underpricing because you do not understand the job value.

Can I combine Jobs to Be Done (JTBD) with other frameworks?

Yes, Jobs to Be Done (JTBD) works well with other growth frameworks. Many teams combine it with AARRR metrics and ICE scoring for a comprehensive growth system.