A RevOps Guide to the Jobs to Be Done Framework

The Jobs to be Done (JTBD) framework offers a transformative lens for understanding why customers buy. It’s a powerful strategic shift: you stop focusing on who the customer is and start analyzing why they’re “hiring” your product to make progress.

Moving Beyond Personas with Jobs to Be Done

For years, B2B teams have built go-to-market (GTM) strategies on detailed buyer personas. We’ve crafted profiles based on demographics and job titles, attempting to paint a picture of our ideal customer. But if you’re in RevOps, you’ve likely felt the gap between a persona-based plan and the real-world triggers that drive a purchase.

This is where Jobs to be Done provides critical clarity. The core principle is that customers don’t buy products; they hire them to do a specific job. This “job” is not a task, but the progress they are trying to make in a given situation.

Let’s make this tangible. A marketing operations manager doesn’t just buy HubSpot because they fit a certain persona. They “hire” HubSpot to solve a problem, such as “establish a single, reliable view of our marketing attribution to prove ROI to the executive team.” That’s the job.

Why JTBD Matters for RevOps

Grasping this core job provides a much richer, more actionable insight than any persona. For professionals managing complex Salesforce or HubSpot instances, this perspective is a game-changer for several key reasons:

• Precision Targeting: Segment your audience based on the actual job they need to get done, which is far more precise than a job title.
• Resonant Messaging: Your content and sales pitches can speak directly to the customer’s real-world struggle and the outcome they need to achieve.
• Intelligent System Design: It provides a blueprint for configuring your CRM and marketing automation platforms to track and support the customer’s journey toward completing their job.

The central idea of Jobs to Be Done is that by understanding the “job,” you can design better products, services, and experiences. For RevOps, this means engineering a GTM engine that aligns perfectly with customer motivation, not internal assumptions.

Persona vs. Jobs to Be Done: A Quick Comparison

To fully appreciate the difference, it helps to compare the two approaches. Personas provide a snapshot of a person, but JTBD reveals the story behind their motivation.

Aspect	Traditional Persona	Jobs To Be Done (JTBD)
Primary Focus	Who the customer is (demographics, title, role)	Why the customer acts (their goal, struggle, desired outcome)
Core Question	“What are the characteristics of our target user?”	“What progress is the customer trying to make?”
Key Insight	Correlation: “People with this job title tend to buy our product.”	Causation: “When this situation occurs, people hire our product to resolve it.”
Application	Guides high-level segmentation and ad targeting.	Informs product development, messaging, and the entire revenue process.

This table makes it clear: while personas have a role, JTBD provides the “why” that is essential for building a truly effective revenue engine.

From Demographics to Motivation

A persona might tell you who your customer is, but JTBD tells you why they act. For instance, a persona could be “Sales Ops Sarah,” a manager at a mid-sized SaaS company. But the Jobs to be Done framework uncovers that Sarah’s primary job is to “eliminate manual data entry for my sales team so they can spend more time selling and less time on administrative tasks.”

That single insight is infinitely more powerful for revenue optimization than a dozen demographic data points. It informs how you structure lead scoring in Marketing Cloud Account Engagement, what content will capture her attention, and which features to emphasize in a sales demo within Salesforce.

By focusing on the job, you move from correlation (people with this title often buy our solution) to causation (people with this specific struggle hire our solution to fix it). Personas are still useful, and you can learn more about how to create buyer personas in our detailed guide to use alongside your JTBD analysis. However, the JTBD lens is the key to diagnosing system gaps, improving data quality, and driving measurable revenue growth.

Understanding the Core Principles of JTBD

To apply the Jobs to be Done framework effectively, you must understand its core components. JTBD is not an abstract business theory; it provides a practical language to diagnose why customers buy—and, just as importantly, what stops them. It’s about analyzing the context and motivation behind a purchase, moving beyond a simple feature list.

The framework boils down to three key concepts that offer a new way to analyze customer behavior. Once you grasp these, you can map your operations in tools like Salesforce or HubSpot directly to what your customers are trying to accomplish.

The Job, the Struggle, and the Outcome

At its heart, every purchase decision is driven by these three elements. Let’s break them down with a B2B scenario familiar to any marketing or sales ops leader.

• The Job: This is the progress a person is trying to make in a specific situation. For a RevOps leader, the job isn’t to “buy a CRM.” Their real job is something more specific, like “establish a single source of truth for revenue attribution” to prove marketing’s impact and secure budget.
• The Struggle: These are the roadblocks preventing progress. For our RevOps leader, the struggle is a daily battle with siloed data across HubSpot and Salesforce, painful manual reporting in spreadsheets, and constant debates over conflicting metrics from different teams.
• The Desired Outcome: This is the future state they envision once the job is done. It’s not just functional; it’s social and emotional. Our leader wants to walk into a board meeting and confidently present an automated dashboard that shows the C-suite the precise ROI of every campaign.

Understanding this progression—from struggle to desired outcome—is the key to unlocking customer motivation. Your product or service is simply the vehicle they hire to make that journey.

The Four Forces of Progress

Every buying decision can be viewed as a tug-of-war. JTBD breaks this down into four forces that constantly push and pull on a customer, determining whether they will switch to a new solution or maintain the status quo.

1. Push of the Situation: The current frustrations compelling the customer to seek change. Perhaps our RevOps leader is under pressure from the CEO, who is demanding better attribution data now. That’s a powerful push.
2. Pull of the New Solution: The allure of your product. The promise of a unified dashboard in Salesforce and automated reporting through a tool like Marketing Cloud Account Engagement (Pardot) starts to pull them toward your solution.
3. Anxiety of the New Solution: The “what ifs” that create hesitation. “Will the data migration be a nightmare? What if my team resists the new process?”
4. Habit of the Present: The powerful inertia of their current workflow. It’s the voice that says, “Our messy spreadsheets are a pain, but at least we know how they work. It’s good enough for now.”

For a sale to occur, the push and pull must be stronger than the habit and anxiety. Your role in marketing and sales is to amplify the push and pull while mitigating the anxiety.

This provides a clear roadmap for your messaging, demos, and implementation plans. It also highlights why fine-tuning your GTM operations is so vital, especially in a challenging market. In California’s job market, for instance, weak private sector growth means B2B firms need every operational edge. When professional and technical services jobs are on the decline, the “job” of streamlining RevOps becomes a survival mechanism. This is how the jobs to be done framework transitions from theory to an indispensable operational tool. You can find more insights about recent trends in California’s job growth on Hoover.org.

How to Uncover Your Customer’s Real Job

Let’s move from theory to practical application. This is where the Jobs to be Done framework truly demonstrates its value. Identifying the job your customer is actually trying to accomplish isn’t guesswork; it’s about learning to listen in a specific way. The goal is to move past surface-level feature requests and uncover the fundamental progress someone is trying to make.

The single most powerful tool for this is the “switch” interview. This is a conversation focused entirely on the moment a customer decided to “fire” their old solution—a competitor’s product or a collection of spreadsheets—and “hire” yours. By replaying the timeline of their struggle, you can pinpoint the exact triggers and outcomes that drove their decision.

Conducting Effective Switch Interviews

The key to a great switch interview is to stop asking leading questions about your product. You are not a salesperson; you are a journalist trying to uncover the story behind their purchase.

Instead of asking, “Why did you choose our reporting feature?” try, “Take me back to the day you realized your old way of reporting wasn’t working. What was going on?”

Your primary objective is to understand the full context surrounding their decision. This is where tools like a people enrichment API can provide a significant advantage. It helps you build a complete professional profile, giving you a richer understanding of their world before the conversation begins.

A solid switch interview always uncovers three critical layers of the job:

• Functional: What is the practical, tactical outcome they need? (e.g., “I need to consolidate lead data from three systems into Salesforce without manual intervention.”)
• Social: How does this job impact their professional standing or reputation? (e.g., “I need to appear competent and in control when I present our data to the executive team.”)
• Emotional: How do they want to feel once the job is done? (e.g., “I want to feel confident and relieved, not stressed about data accuracy.”)

By capturing these three dimensions, you move beyond a simple use case. You gain a complete picture of the customer’s motivation, which is invaluable for your marketing, sales, and RevOps teams.

Non-Leading Interview Questions to Ask

To get to the heart of their story, you need questions that encourage them to talk about their experience, not just your product. The aim is to reconstruct their entire journey.

Here are a few sample questions to get the conversation flowing:

1. To understand the initial struggle:

• “When did you first start thinking there might be a better way to handle [the problem area]?”
• “What was the most frustrating part of your old process?”

2. To explore their search for a solution:

• “What other tools or methods did you try before you found us?”
• “What were the most important criteria you were looking for in a new solution?”

3. To pinpoint the decision trigger:

• “Was there a specific event or a ‘last straw’ moment that made you decide to actively look for something new?”
• “Who else was involved in making the final decision, and what were their primary concerns?”

These types of questions are designed to let the customer tell their story. The insights you gather will directly inform everything from your lead scoring models in your marketing automation platform to your pipeline stages in Salesforce and the copy on your website.

Introducing the Job Map

After conducting several interviews, you will start to see patterns. This is where the Job Map becomes a powerful tool for visually organizing these insights. It breaks down the customer’s core job into a sequence of distinct, logical steps.

A typical Job Map follows a universal structure:

1. Define: The customer clarifies their goals and plans resources.
2. Locate: They gather the necessary information and inputs.
3. Prepare: They set up the environment to execute the job.
4. Confirm: They verify that they are ready to proceed.
5. Execute: They perform the core functional job.
6. Monitor: They track progress and measure success.
7. Modify: They make adjustments to improve the outcome.
8. Conclude: They complete the job and assess its success.

When you map your customer’s journey against these steps, you will see exactly where they struggle most. These friction points are your opportunities for innovation—a new product feature, a better onboarding process, or more targeted content. For a RevOps team, this map shows you precisely where your Salesforce or HubSpot configuration can be optimized to help customers make progress at every stage.

Putting JTBD Insights to Work in Your MarTech Stack

Understanding your customer’s Job to be Done is a critical strategic insight. The real value, however, is realized when you integrate that insight into your daily operations. This is where we bridge the gap between JTBD theory and hands-on MarTech execution. By embedding job-centric data into your CRM and marketing automation platforms, you transform them from simple databases into intelligent engines for your entire GTM strategy.

The goal is to make a customer’s ‘Job’ and ‘Struggle’ as clear and actionable as their job title or company size. This requires a deliberate shift in how you configure systems like Salesforce Sales Cloud, Marketing Cloud Account Engagement (Pardot), and HubSpot.

Capturing JTBD Data in Your CRM

First, you need to create a dedicated space for this richer data. Instead of relying solely on standard fields, build a structure that captures why a customer is engaging with you. This single change dramatically improves data hygiene and provides your teams with the context needed for more meaningful conversations.

Here’s a practical way to get started in Salesforce or HubSpot:

• Create Custom Fields: Add key fields to your Lead and Contact objects. A picklist for the primary ‘Job to be Done’ (e.g., “Prove Marketing ROI,” “Improve Sales Forecasting Accuracy”) is a great start. Also, add a text area for the ‘Struggle’ or ‘Trigger Event’ (e.g., “CEO questioned Q3 ad spend,” “Manual reporting took 10 hours last week”).
• Update Your Forms: On high-intent forms, add an optional, open-ended question like, “What’s the primary challenge you’re hoping to solve?” This is an excellent way to capture the customer’s struggle in their own words.
• Train Your Sales Team: Onboard your sales development and account executive teams. Teach them to ask JTBD-focused discovery questions and provide a clear process for logging those insights directly in the CRM.

When you operationalize JTBD insights, you move beyond demographic-based qualification. A lead’s “struggle” becomes a far better indicator of intent than their title, leading to improved pipeline visibility and more accurate forecasting.

Redesigning Lead Scoring Models

Many traditional lead scoring models are overly reliant on demographics (like title or company size) and simple actions (like an ebook download). A JTBD-informed model is more intelligent, prioritizing actions that signal a real struggle and an active search for a solution.

This requires rethinking which behaviors truly matter. For example, a prospect who visits your pricing page, watches a case study on ROI reporting, and uses live chat to ask about your Salesforce integration is clearly communicating their Job to be Done. Their score should reflect that high-intent context.

Consider these adjustments:

• Score Based on Context: Assign higher scores for consuming content that maps directly to a known ‘Job’. If someone downloads a guide on “Advanced Attribution Models,” they are signaling their specific struggle.
• Weight High-Intent Actions: Give more weight to behaviors like viewing integration documentation or starting a free trial. These are more valuable signals than passive actions like opening a newsletter.
• Incorporate Job Data: If a lead’s ‘Struggle’ field is populated in Salesforce, use that data to automatically boost their score in Account Engagement or HubSpot. You can find more practical advice in our guide to CRM and marketing automation integration.

Enriching Lead Data with GTM Engineering

To elevate this approach, use GTM engineering tools to automatically enrich lead data with job-centric information. Platforms like Clay can pull data from multiple sources to create a more complete picture of a prospect, often uncovering clues about their potential ‘Job to be Done’ before the first conversation.

This is especially critical in competitive markets. In the tech-heavy Bay Area, there is an incredible demand for data-focused roles, pointing to a massive, pressing ‘job’ for businesses: turning data into better pipeline visibility and attribution. A recent report revealed that data scientist roles in the San Francisco metro area increased by 572% between 2019 and 2024. For RevOps leaders, this data boom highlights the urgent need to turn raw information into measurable ROI—a core ‘job’ MarTech Do excels at solving. You can dig deeper into these trends in the latest analysis of California’s job market on ppic.org.

By connecting JTBD theory to your MarTech stack, you build a smarter, more targeted RevOps engine. This alignment ensures that every piece of data you collect and every automation you build serves one primary purpose: helping your customer make progress.

Aligning Sales and Marketing Teams With JTBD

One of the most persistent challenges for any RevOps leader is the friction between sales and marketing. Marketing focuses on hitting MQL targets with persona-based campaigns, while sales conducts feature-first demos. The result is often a disjointed and inefficient GTM motion.

The most effective way to bridge this gap is to anchor both teams to a shared understanding of the customer’s Jobs to be Done. The conversation shifts from internal metrics to a common, customer-centric goal. JTBD provides a shared language and a unified purpose, transforming siloed departments into a cohesive revenue engine.

When both teams focus on the why behind a customer’s decision, their daily activities naturally align. This has a direct, practical impact on how your teams operate within your Salesforce and HubSpot ecosystems.

Crafting a Unified GTM Motion

When you build your go-to-market strategy on a JTBD foundation, the roles of sales and marketing organically redefine themselves to better support the customer’s journey. Daily tasks become strategic, synchronized actions.

For the marketing team, this means moving beyond broad, generic content aimed at a vague persona. Instead, they create assets that speak directly to a customer’s specific struggle. Blog posts, webinars, and case studies become tools that help a prospect understand their problem and see a clear path to their desired outcome.

For the sales team, discovery calls are no longer a checklist of features. They become collaborative sessions focused on diagnosing the customer’s ‘Job’. Reps learn to ask questions that uncover the functional, social, and emotional drivers behind the struggle, positioning them as trusted advisors. You can go deeper on this in our guide to achieving B2B sales and marketing alignment.

A shared Job Story—a simple narrative outlining the customer’s situation, motivation, and desired outcome—becomes the North Star for everyone. It is the central artifact that guides both campaign briefs and sales playbooks, ensuring a consistent message across the entire customer journey.

To illustrate how this shared focus changes operations, let’s compare the traditional approach to a JTBD-aligned one.

JTBD-Driven Sales vs. Marketing Alignment

Team Activity	Traditional Approach	JTBD-Aligned Approach
Content Creation	Focuses on buyer personas and firmographics. Content is often feature-heavy.	Focuses on the customer’s struggle and desired progress. Content educates on solving the ‘Job’.
Lead Qualification	Based on demographic/firmographic fit (e.g., company size, title). MQLs are the key metric.	Based on identifying the ‘struggling moment’. Is the prospect actively trying to make progress?
Sales Discovery	A checklist of qualifying questions about budget, authority, and timeline.	A diagnostic conversation to uncover the context, forces of progress, and desired outcomes of the ‘Job’.
Product Demos	A tour of product features, showcasing what the product can do.	A walkthrough showing how the product helps the customer achieve their outcome and overcome their struggle.
Success Metrics	Siloed KPIs: Marketing tracks MQLs and CPL; Sales tracks demos booked and deals closed.	Shared KPIs: Both teams are measured on pipeline velocity, customer success milestones, and revenue.

This table makes it clear: when you align around the customer’s Job, you are not just using the same terminology—you are working toward the same outcome. The entire revenue motion becomes smoother and more effective.

Practical Templates for Alignment

To put this into action, your teams can build their core operational assets around a central Job Story. This guarantees consistency from the first ad a prospect sees to the final proposal they sign.

1. The JTBD-Informed Marketing Brief
A campaign brief built on JTBD looks completely different from a traditional one. It shifts the focus from “who are we targeting?” to “what struggle are we solving?”

• Core Job to be Done: What progress is the customer trying to make?
• The Struggle: What specific pains, anxieties, or roadblocks are in their way?
• Key ‘Aha!’ Moment: What core insight must this campaign deliver for it to resonate and make them feel understood?
• Call to Action: What is the next logical step for someone trying to get this job done?

2. The JTBD-Powered Sales Playbook
Similarly, your sales playbook can be structured to help a customer complete their job, with stages that mirror their journey toward progress.

• Discovery Questions: A curated list of open-ended questions designed to uncover the ‘push’ and ‘pull’ forces driving their decision.
• Objection Handling: Reframe common objections (like “implementation sounds complicated”) within the context of their desired outcome and the cost of inaction.
• Success Metrics: Define what “success” means for the customer—not by the features delivered, but by their ability to complete their job effectively.

This unified approach is critical for navigating changing market conditions. For example, recent data on California’s varied regional job markets shows a clear ‘job to be done’ for B2B companies: adapt your GTM to local economic realities. While Sacramento’s job market grew by 3.1%, fueled by health care and government jobs, the Bay Area and LA saw their information sectors decline. As a RevOps leader, this means tailoring your Salesforce and HubSpot strategies to these specific regional contexts is essential for survival. You can see more about how each California region tells a different job story at ppic.org.

By grounding every sales and marketing effort in the customer’s real-world context, you create a powerful, unified machine that drives predictable, scalable growth.

Common Questions About the Jobs to Be Done Framework

Even after grasping the core concept, implementing a new framework into your operations will raise questions. The Jobs to Be Done theory is compelling, but how does it hold up in a fast-paced RevOps environment?

To provide clarity, here are answers to the most common questions from marketing, sales, and revenue ops leaders. The goal is to give you the confidence to start applying these ideas within your company and MarTech stack.

How Is Jobs to Be Done Different from Building Customer Personas?

This is the most common question. The distinction is critical. While both tools are about understanding the customer, they focus on entirely different dimensions.

A persona describes who your buyer is, while JTBD defines why they are buying. A persona might tell you, “Our ideal customer is a Marketing Manager at a mid-sized tech company.” This is useful for high-level targeting, but it reveals nothing about their motivation.

JTBD, on the other hand, zeroes in on the progress that manager is trying to make. Their job isn’t to “be a Marketing Manager”; their real job is to “prove every marketing dollar is tied to pipeline so I can justify my budget.” JTBD is about context, not characteristics, making it a far better predictor of buying behavior and more actionable for optimizing your RevOps strategy in Salesforce or HubSpot.

Can We Implement JTBD Without a Huge Research Budget?

Absolutely. You do not need a massive budget to generate powerful insights. While formal research projects are valuable, you can begin weaving JTBD principles into your work today using lean, practical methods.

The key is to build the discovery process into your existing conversations. Start by training your sales and customer success teams to conduct informal “switch” interviews during their regular calls. You can uncover a wealth of information with just a handful of open-ended questions.

For instance, ask a new customer:

• “What was happening in your business that first led you to look for a new solution?”
• “Before you came on board, what were you using to get this done?”
• “What was the most frustrating part of that old process?”

These simple questions help you reconstruct their struggle and pinpoint the trigger behind their decision. You can then use these qualitative insights to immediately tweak messaging and adjust workflows in Account Engagement (Pardot) or HubSpot without spending a dime on research.

How Does JTBD Apply Specifically to B2B RevOps?

In the B2B space, the Jobs to be Done framework is especially powerful for revenue operations because it provides a single, unifying logic that connects all the moving parts of your GTM engine.

For marketing operations, it’s about moving away from MQLs based on static data like job titles. Instead, you can qualify leads based on behaviors that signal they are actively struggling with a job your solution solves—like repeatedly visiting a specific integration page or downloading a case study on improving data accuracy.

For sales operations, it means you can structure your CRM pipeline stages around the customer’s buying journey, not just your internal sales process. This makes your forecasting more accurate because a deal only moves forward when the customer has made real progress. It also helps reps focus on what matters: helping the customer make that progress.

Ultimately, JTBD aligns your entire GTM engine—from the first marketing touchpoint in HubSpot to the final deal stage in Salesforce—around the customer’s core motivation. This is the foundation of scalable, predictable revenue growth.

What Are the First Steps to Apply JTBD in Salesforce or HubSpot?

Getting started does not require a massive overhaul. A great, manageable first step is to audit your current system through a JTBD lens.

1. Identify and Interview: Select 5-10 of your best recent customers. Conduct brief conversations to identify the core ‘Job’ they hired your product to do.
2. Map Their Journey: Sketch out the key steps and struggles they described on their path to buying.
3. Compare to Your System: Now, open Salesforce or HubSpot. Do your lifecycle stages match their real journey? Do you have custom fields to capture their ‘struggle’ or ‘desired outcome’?

You will likely spot gaps immediately. Start small by creating a few custom fields on the Lead or Contact object to begin capturing this data. Then, build a simple report or dashboard to track it. This initial effort provides a data-driven starting point for optimizing your entire RevOps machine.

---

At MarTech Do, we help B2B companies translate powerful strategic frameworks into practical execution within your MarTech stack. If you’re ready to align your systems with your customer’s true motivations, let’s talk about how we can optimize your operations for measurable growth. Learn more and get in touch at https://martechdo.com.