Uncovering B2B Buyer Motivations: Beyond the Stated Need

Hello! Welcome to the final lesson in our "Voice of Customer Research" module.

In our last two lessons, you did an excellent job of gathering raw customer language. You started by mining public forums and review sites, then moved on to analyzing internal company resources like support tickets and sales calls. You now have a collection of the exact words B2B buyers use to describe their needs, questions, and frustrations.

Today, we're going to add the final, crucial layer to that research. We'll learn to look beneath the surface of what buyers say to understand what truly drives them. This lesson directly addresses our learning outcome: to distinguish between stated needs and underlying motivations in B2B buyer language.

A buyer might say they need a specific feature, but what they often mean is that they need to reduce personal risk, look good to their boss, or eliminate a source of daily frustration. Your most powerful copy won't just speak to the feature request; it will connect with the deeper human motivation behind it.

1. The "Faster Horse" Problem

One of the most famous quotes in business (apocryphally attributed to Henry Ford) is, "If I had asked people what they wanted, they would have said faster horses." People asked for a better version of what they already knew, not the revolutionary solution they truly needed.

This is the core challenge we're tackling today. Your buyers will often state their needs in the form of solutions or features. It's your job as a copywriter to understand the fundamental problem or "job" they are trying to get done.

In B2B, a "faster horse" might sound like:

• "I need a dashboard with more reporting widgets."
• "I need a tool that integrates with Slack."
• "I need a project management tool that lets me assign tasks to multiple people."

These are stated needs. Our goal is to uncover the underlying motivations behind them.

2. A Framework for Motivation: Jobs to be Done (JTBD)

To get past the "faster horse" problem, we can use a framework called Jobs to be Done (JTBD). The core idea is that customers don't "buy" products; they "hire" them to get a job done. This "job" is the real motivation.

The JTBD framework helps us categorize these motivations into different dimensions.

As the video explains, every purchase has layers:

• Practical Job: This is the most obvious, functional task. It's the "what" the person is trying to do. (e.g., "Commute safely and reliably from home to the office.") This often aligns with the stated need.
• Social Job: This relates to how the person wants to be perceived by others. (e.g., "Show my friends I am on the cutting edge of technology.")
• Emotional Job: This relates to how the person wants to feel. (e.g., "Feel special and comfortable during my commute" or "Feel secure that I am contributing positively to the environment.")

The social and emotional jobs are the home of underlying motivations. They are rarely stated but are often the most powerful drivers of a decision.

This way of thinking is so powerful that many marketers now prefer it over traditional buyer personas, which can be superficial.

3. Layers of Need in a B2B Context

In a B2B sale, these "jobs" exist at multiple levels within the organization. A purchase isn't just about one person's needs; it's about the needs of their team and the company as a whole.

This image provides a simple but effective model for thinking about these layers.

• Company Needs (Often Stated): These are the high-level business goals: "Increase revenue," "reduce costs," "improve efficiency."
• Department Needs (Stated/Underlying): These are the team-level goals: "Our sales team needs to close deals faster," "Our support team needs to reduce ticket response time."
• Individual Needs (Almost Always Underlying): These are the personal, human motivations of the buyer: "I need to hit my quota to get my bonus," "I need to look competent to my new boss," "I need to reduce the stress of my workload."

Your copy is strongest when it can connect a product feature all the way from the company need down to the individual's emotional "job."

This chart provides a helpful cheat sheet for thinking about the difference between the functional (stated) and emotional (underlying) benefits.

4. Your Turn: From Stated Need to Underlying Motivation

Let's apply this. We'll use the "internal memo" about the Momentum project management tool from our last lesson. For each scenario, I've listed the Stated Need that the customer expressed.

Your Task (10 minutes):

For each of the three scenarios below, analyze the stated need and write down the potential Underlying Motivations. Think about the practical, social, and emotional jobs the buyer is trying to get done.

---

1. Support Ticket #A-451:

• Stated Need: "I need to assign a task to more than one person."
• What are the underlying motivations? (Think about the frustration of workarounds, the desire for team harmony, the fear of a tool disrupting a creative process.)

2. Support Ticket #B-103:

• Stated Need: "I need to know the price for 25 users without buying an enterprise plan."
• What are the underlying motivations? (Think about the need for fairness, budget predictability, and the fear of being overcharged or "tricked.")

3. Excerpt from a Sales Call:

• Stated Need: "I'm concerned about the switching cost and the disruption of migrating projects and retraining the team."
• What are the underlying motivations? (Think about the personal risk involved. What happens to the buyer's reputation if the switch goes badly? How do they want to feel during and after this process?)

---

Take a few minutes to jot down your thoughts for each. There are no single right answers; the goal is to practice looking for the human story behind the business request.

Conclusion

Fantastic work. This is one of the most important conceptual leaps in copywriting. Once you start seeing the "job" behind the feature request, you can write copy that resonates on a much deeper, more persuasive level.

Key Takeaways:

• Stated vs. Underlying: Buyers often state what they think they want (a faster horse), not the underlying problem they need to solve (a way to get to town faster and more reliably).
• Jobs to be Done (JTBD): People "hire" products to do a job. These jobs have practical, social, and emotional dimensions.
• The Power of 'Why': The most powerful motivations are often emotional and social—the desire for security, status, control, or the fear of risk, stress, and failure.
• B2B is Human: Behind every B2B purchase is a person (or group of people) making a decision, and they are driven by the same kinds of motivations as any other consumer.

In this module, we've gone from finding raw customer language to understanding the deep motivations behind it. In our next lesson, we'll begin a new module, "Crafting the Core Message & Value Proposition," where you'll learn how to translate product features into tangible business outcomes that speak directly to these motivations.