Buyer Persona

A buyer persona is a structured description of a type of buyer: what their role involves, what they care about professionally, what keeps them from achieving their goals, and what success looks like from their seat. It exists to help reps and marketers adapt their approach to the specific person they’re engaging rather than delivering the same message to every stakeholder in a buying committee.

In a complex B2B deal, the buying committee includes multiple personas: a VP of Sales who cares about quota attainment, a Sales Enablement leader who cares about rep consistency, a CRO who cares about revenue efficiency, and a technical evaluator who cares about integration complexity. Each conversation is more effective when it starts from an understanding of what matters to that specific person.

The ideal customer profile and the buyer persona answer different questions and operate at different levels.

The ICP is account-level: what type of company is most likely to buy, get value, and renew? It defines the organization, not the individual.

The buyer persona is contact-level: within a company that fits the ICP, who are we selling to, and how do we adapt to them? It defines the individual, not the organization.

Both are necessary. ICP determines whether the account is worth pursuing. Persona determines how to engage the people inside it. Confusing the two leads to either pursuing the wrong accounts or delivering the same message to every stakeholder and wondering why it lands differently across the buying committee.

Personas make discovery more precise. A rep who knows they’re speaking with a VP of Sales can lead with questions about quota, pipeline quality, and rep performance rather than spending time establishing context that the persona framework already provides.

More importantly, persona-informed discovery surfaces pain more efficiently. Each persona has predictable pain points connected to their role. A Sales Enablement leader is likely concerned with training transfer and rep consistency. A CRO is likely concerned with forecast accuracy and deal velocity. Starting the discovery conversation with questions that reflect an understanding of their role demonstrates credibility and gets to the real pain faster than generic discovery.

Personas also inform how to frame the business case for each stakeholder. The same product capability means something different to a VP of Sales (“your reps stop losing deals to questions they couldn’t answer”) than to a CRO (“forecast accuracy improves when discovery is consistent across every rep”). Persona-aware framing is what separates a multi-stakeholder deal that advances from one that stalls because different stakeholders received the same message.

Useful personas come from sales conversations, not from marketing assumptions. The most valuable persona data is:

• The exact language each persona uses to describe their problem (from call recordings, not paraphrased)
• The objections each persona raises most frequently and at what stage
• What each persona cares about when the product is demonstrated (what makes them lean in versus tune out)
• What each persona needs to see in the business case to support the purchase
• What each persona fears: what would make them vote against the purchase if it came to that

A persona built from these inputs gives a rep a practical guide to the conversation before it starts. A persona built from assumptions gives a rep a marketing document.

Building personas for fictional people

Personas with names, stock photos, and made-up backstories are a marketing exercise with limited sales value. What a rep needs is not a character study. It’s a clear answer to: what does this type of person care about, what questions should I ask them, and how should I frame my product in terms they respond to?

Using the same persona for the whole buying committee

In complex deals, there is no single buyer. There are five to fifteen stakeholders, each with a different role and different priorities. A single persona approach produces messaging that works for one stakeholder and alienates the others.

Not updating personas as the market evolves

The problems a VP of Sales cared about two years ago may not be the ones they care about now. Economic conditions, product category maturity, and competitive dynamics all shift what personas prioritize. Personas built on outdated data lead to discovery conversations that miss the current pain.

Building personas but not using them in training

Personas that live in a marketing document and never reach the rep don’t change how discovery is run. The test of a useful persona is whether a rep can use it to immediately improve the first question they ask in a call. If they can’t, the persona isn’t built right.

Persona-informed discovery requires knowing which questions are most relevant for this type of stakeholder and having them available in the moment the call starts. Commit surfaces persona-specific discovery questions and framing in real-time based on who is on the call and what they’re saying, so the rep adapts to the specific stakeholder rather than defaulting to a generic discovery script.

That’s real-time sales enablement applied to persona: the right question for this specific person, surfaced at the right moment, without the rep having to remember which persona they’re talking to while simultaneously managing the conversation.