Resources · Buyer personas
Sales buyer personas.
The six people you sell to on a B2B deal, economic buyer, technical evaluator, champion, procurement, end user, skeptical exec. What each cares about, how each objects, and how to sell to them.
In short
- A real B2B deal isn't one buyer, it's a committee, usually six distinct personas, each with different priorities and a different way of pushing back.
- Sell to the economic buyer on outcomes, the technical evaluator on proof, the champion on internal wins, procurement on terms, the end user on daily life, the skeptical exec on risk.
- The same product needs a different pitch per persona. Knowing who you're talking to is what tells you which pitch to run.
You're not selling to one person
The biggest mistake in B2B selling is treating a deal like a one-on-one. It's a committee. A typical deal runs through six personas, and each one cares about a different thing, objects in a different way, and needs a different pitch. Run your economic-buyer pitch at a technical evaluator and you'll lose; run your end-user pitch at a skeptical exec and you'll never get budget.
Below are the six, what each cares about, how each tends to object, and how to sell to them. The skill isn't memorizing the table, it's recognizing which persona you're on the phone with in the first sixty seconds, so you run the right pitch instead of a generic one.
The six buyer personas
Same deal, six different people. Match your pitch to who you're actually talking to, their priority, their objection, and the move that works on them.
| Persona | What they care about | How they object | How to sell to them |
|---|---|---|---|
| Economic buyer | Outcomes and ROI. Will this hit the number I'm accountable for, and is it worth the spend? | "What's the actual return?" "Why now instead of next year?" Objects on business case, not features. | Lead with outcomes and impact, not capabilities. Quantify the cost of the status quo. Tie the buy to a goal they're measured on this quarter. |
| Technical evaluator | Whether it actually works, integrations, security, performance, fit with the existing stack. | "How does this handle [edge case]?" "Does it integrate with X?" Objects on proof and detail. | Be precise and honest. Show, don't claim. Offer docs, a sandbox, a security review. Admit limits, they respect candor and punish hand-waving. |
| Champion | Looking good internally. They want this to work and want credit for bringing it in. | Rarely objects to you, instead asks "how do I sell this to my boss?" Their risk is internal, not external. | Arm them. Give them the business case, the slides, the answers to questions they'll face. Make it easy to be the hero. Coach them through the internal sell. |
| Procurement / legal | Terms, risk, and process, pricing, contract language, compliance, vendor risk. Not whether to buy, but on what terms. | "These terms won't work." "We need this clause." "What's your security posture?" Objects on contract and process. | Be responsive and organized. Know your terms cold, have your security docs ready, and don't take the friction personally. Their yes is procedural, make the process easy. |
| End user | Their daily life. Will this make my job easier or add another tool to fight with? | "This looks complicated." "We already have too many tools." Objects on usability and change cost. | Sell the day-to-day win. Show the before-and-after of their actual workflow. Address adoption and the learning curve. Their buy-in protects the deal post-sale. |
| Skeptical exec | Risk and credibility. They've been pitched a thousand times and assume hype until proven otherwise. | "Everyone says that." "What happens if it doesn't work?" Objects on trust and downside. | Drop the pitch voice. Be direct, concede the limits, and lead with proof, peers, numbers, references. Lowering the risk matters more than raising the upside. |
Persona
What they care about
- Economic buyer
- Outcomes and ROI. Will this hit the number I'm accountable for, and is it worth the spend?
- Technical evaluator
- Whether it actually works, integrations, security, performance, fit with the existing stack.
- Champion
- Looking good internally. They want this to work and want credit for bringing it in.
- Procurement / legal
- Terms, risk, and process, pricing, contract language, compliance, vendor risk. Not whether to buy, but on what terms.
- End user
- Their daily life. Will this make my job easier or add another tool to fight with?
- Skeptical exec
- Risk and credibility. They've been pitched a thousand times and assume hype until proven otherwise.
Persona
How they object
- Economic buyer
- "What's the actual return?" "Why now instead of next year?" Objects on business case, not features.
- Technical evaluator
- "How does this handle [edge case]?" "Does it integrate with X?" Objects on proof and detail.
- Champion
- Rarely objects to you, instead asks "how do I sell this to my boss?" Their risk is internal, not external.
- Procurement / legal
- "These terms won't work." "We need this clause." "What's your security posture?" Objects on contract and process.
- End user
- "This looks complicated." "We already have too many tools." Objects on usability and change cost.
- Skeptical exec
- "Everyone says that." "What happens if it doesn't work?" Objects on trust and downside.
Persona
How to sell to them
- Economic buyer
- Lead with outcomes and impact, not capabilities. Quantify the cost of the status quo. Tie the buy to a goal they're measured on this quarter.
- Technical evaluator
- Be precise and honest. Show, don't claim. Offer docs, a sandbox, a security review. Admit limits, they respect candor and punish hand-waving.
- Champion
- Arm them. Give them the business case, the slides, the answers to questions they'll face. Make it easy to be the hero. Coach them through the internal sell.
- Procurement / legal
- Be responsive and organized. Know your terms cold, have your security docs ready, and don't take the friction personally. Their yes is procedural, make the process easy.
- End user
- Sell the day-to-day win. Show the before-and-after of their actual workflow. Address adoption and the learning curve. Their buy-in protects the deal post-sale.
- Skeptical exec
- Drop the pitch voice. Be direct, concede the limits, and lead with proof, peers, numbers, references. Lowering the risk matters more than raising the upside.
The same product needs six different pitches. The skill is knowing in the first minute which person you're actually talking to, then running that pitch, not the generic one.
How to tell who you're talking to
You can usually spot the persona fast by what they ask about. Questions about ROI and timing? Economic buyer. Questions about integrations and edge cases? Technical evaluator. Asking how to position it to their boss? Champion. Pushing on contract clauses? Procurement. Worried about their day-to-day? End user. Skeptical and asking what happens when it fails? Skeptical exec.
One person can wear more than one hat, a founder might be economic buyer and skeptical exec at once. Read the questions, not the title. The title tells you their job; the questions tell you which pitch to run right now.
Working the whole committee
Winning a deal means more than nailing one persona, it means moving each one in the right direction. The economic buyer needs the business case. The technical evaluator needs proof. The champion needs ammunition for the internal fight. Procurement needs clean terms. The end user needs to want it. The skeptical exec needs the risk lowered.
Your champion can't carry all of that alone, so map the committee early in discovery, who's involved, what each one cares about, who can kill the deal. Then make sure each persona's concern gets addressed by someone, ideally before it becomes the objection that stalls everything.
Frequently asked
What are the main buyer personas in a B2B sale?
- Six show up on most committee deals: the economic buyer (owns the budget and the outcome), the technical evaluator (judges whether it works), the champion (wants it and sells it internally), procurement or legal (owns terms and risk), the end user (lives with it daily), and the skeptical exec (assumes hype until proven). Each cares about something different and objects in its own way.
How do I sell to an economic buyer?
- Lead with outcomes and ROI, not features. The economic buyer is accountable for a number, so frame the buy against a goal they're measured on and quantify what the status quo is costing. Answer "why now", they need a reason this is a this-year decision, not a someday one. Save the feature detail for the technical evaluator; the economic buyer wants the business case.
What's the difference between a champion and an economic buyer?
- The champion wants your product and pushes for it internally, but usually doesn't own the budget, their risk is looking bad in front of their boss. The economic buyer owns the spend and the outcome. You arm the champion to sell up; you sell the economic buyer directly on ROI. Confusing the two means pitching the wrong thing to each.
How do I handle a skeptical executive?
- Drop the pitch voice entirely. A skeptical exec has been sold to a thousand times and treats enthusiasm as a red flag. Be direct, concede your product's real limits, and lead with proof, peer references, hard numbers, names they trust. With this persona, lowering the perceived risk matters more than raising the upside, because their default assumption is that it won't work.