---
name: economic-buyer-identification
slug: economic-buyer-identification
description: This skill should be used when the user asks to "identify the economic buyer", "find who controls the budget", "determine who approves the purchase", "identify the EB in a deal", "find the budget holder", "identify who signs the check", "determine purchasing authority", "find the real buyer", "identify the economic decision maker", or any variation of identifying the person with budget authority in a B2B SaaS deal.
category: general
---

# Economic Buyer Identification

The economic buyer (EB) is the person who can say yes to spending the money. Not the person who evaluates the tool. Not the person who uses it daily. The person with the authority and the budget to approve the purchase. In MEDDPICC, this is the "E." It's also the most commonly misidentified role in B2B sales. Reps think they've found the EB because the person on the call has a VP title. But "VP" at a 30-person startup is different from "VP" at a 3,000-person company. Authority comes from budget control, not from the org chart.

The principle: the EB is identified by what they can DO (approve spend), not by who they ARE (their title). A Director with discretionary budget is a more real EB than a VP who needs C-suite sign-off. Test authority by asking about the approval process, not by reading the title.

## How to Identify the Economic Buyer

### The 3 identification methods

**Method 1: Ask the champion directly**

| Question | What it reveals |
|----------|----------------|
| "If your team decided to move forward, who would sign off on the budget?" | The person with final approval authority |
| "Who approved the last tool purchase in this price range?" | The actual EB from a real precedent (most reliable) |
| "Is there a spending threshold above which someone else needs to approve?" | Whether your deal exceeds the contact's authority |
| "Does this come from your team's budget, or does it need separate allocation?" | Whether budget exists or needs to be created |

**Method 2: Infer from org structure and deal size**

| Your deal size | Company size | Likely EB |
|---------------|-------------|----------|
| < $10K/year | Any | The person on the call (Manager+). May self-approve |
| $10-30K/year | < 200 employees | Director or VP of the buying function |
| $10-30K/year | 200-1000 employees | VP of the buying function |
| $30-100K/year | < 500 employees | VP or C-level |
| $30-100K/year | 500+ employees | VP with budget authority. May need CFO alignment |
| $100K+/year | Any | C-level or SVP. Often requires board/finance committee |

**Method 3: Test with a commitment request**

The most reliable EB test: ask for something that requires authority.

| Test | EB response | Non-EB response |
|------|------------|----------------|
| "Can you commit to a timeline for decision?" | "Yes, we'll decide by [date]" | "I'd need to check with my VP" |
| "If we align on pricing, can you approve this quarter?" | "Yes, if the numbers work" | "I can recommend it but [name] approves" |
| "Should I send the contract to you?" | "Yes, send it to me" | "Send it to [name] / procurement" |

### Identification rules

- **The champion is rarely the EB.** Champions feel the pain and drive the evaluation. EBs approve the spend. They're usually one level above the champion. Exceptions: small companies where the champion IS the budget holder
- **"I make the decision" often means "I make the recommendation."** Test with a commitment question. If they defer to someone else, they're the recommender, not the EB
- **The EB changes by deal size.** The same person may be the EB for a $5K tool but not for a $50K tool. Ask about thresholds: "Is there a dollar amount above which you'd need additional approval?"
- **There may be multiple EBs.** A $100K+ deal may need VP approval AND CFO sign-off AND board awareness. Map all approval gates, not just the first one

---

## EB Profiles by Company Stage

### How EB authority works at different company stages

| Company stage | EB for $10-30K | EB for $30-100K | EB for $100K+ |
|--------------|---------------|----------------|---------------|
| Seed / Pre-Series A (< 20 employees) | Founder / CEO | Founder / CEO | Founder + investors |
| Series A (20-80 employees) | VP or Director | VP or CEO | CEO + board awareness |
| Series B (80-300 employees) | VP (usually self-approves to $30K) | VP + CFO alignment | C-suite + board approval |
| Series C+ (300-1000 employees) | VP (may have $50K discretionary) | VP + CFO or SVP | C-suite + finance committee |
| Enterprise (1000+ employees) | Director or VP (with allocated budget) | VP + procurement + finance | SVP/C-suite + procurement + legal + finance |

### Stage-specific rules

- **At Seed/Series A: the CEO is the EB for everything.** If the CEO doesn't know about the deal, it's not real. Get in front of the CEO early. Don't over-formalize the process at this stage
- **At Series B: VPs typically have discretionary budget up to $30-50K.** Above that, they need CFO or CEO alignment. Know the threshold
- **At Enterprise: the EB may not be the person who approves the spend.** The VP may approve the business case, but procurement approves the terms, and a separate finance team releases the budget. Map all three

---

## Engaging the Economic Buyer

### When to engage the EB

| Deal stage | EB engagement goal |
|-----------|-------------------|
| Discovery | Identify who the EB is. Don't engage directly yet |
| Demo / Evaluation | EB should know the evaluation is happening. Champion should have briefed them |
| Proposal | EB should have seen the business case and agreed directionally before the proposal is sent |
| Negotiation | EB should be actively engaged on terms, timeline, and final approval |

### How to get in front of the EB

| Method | How it works | Success rate |
|--------|-------------|-------------|
| Champion introduction | Champion sets up a meeting: "My VP wants to hear about this" | Highest. Internal credibility. EB is pre-sold |
| Peer-to-peer outreach | Your VP/CEO emails their VP: "Our teams are evaluating a partnership" | High. Title parity creates respect |
| Business case document | Champion shares the ROI doc with the EB. EB requests a meeting | Medium-high. EB is curious based on the numbers |
| Direct outreach (last resort) | You email the EB directly without champion introduction | Low. Risks bypassing the champion |

### EB engagement rules

- **Champion introduction is always the preferred path.** The EB meeting that comes from "my Director recommended I meet with you" starts from a position of internal credibility
- **Prepare the champion before the EB meeting.** "What does your VP care about? What questions will they ask? What would make them say no?" Use the champion's intel to tailor the EB conversation
- **EB meetings are 15-20 minutes, not 45.** EBs give you less time. Lead with the business outcome, not the product. ROI, competitive risk, strategic alignment. Then: "Want to see a quick view of the product?" If yes, show the dashboard/reporting view only. Not a feature tour
- **Never go around the champion to the EB without a reason.** If the champion can't get you the EB meeting, that's a signal: either the champion lacks influence, or the deal isn't a priority for the EB. Address the root cause, don't just bypass the champion

### EB meeting talk track

```
"[EB name], thanks for taking a few minutes.
[Champion name] has been evaluating [product] to solve
[specific problem].

The business case: your team currently [quantified pain:
"spends $75K/year on manual research" or "is missing $500K
in pipeline per quarter"]. Based on what [peer company] saw,
[product] could [specific outcome with number].

I wanted to make sure this aligns with your priorities before
we move to the next step. Does [problem] rank as something
worth addressing this quarter?"
```

**EB talk track rules:**
- Lead with the business outcome, not the product. "Your team spends $75K/year on manual research" not "Our product automates prospecting"
- Reference the champion by name. "Sarah has been evaluating this." This signals that the initiative is bottom-up, not a vendor cold call
- Use peer proof. "Based on what [peer company] saw" is more credible to an EB than "our product can do X"
- End with a priority question, not a pitch. "Does this rank as something worth addressing?" lets the EB confirm or redirect. If they redirect, you've saved weeks of pursuing a deal that won't close

---

## EB Red Flags

### Signs you haven't found the real EB

| Red flag | What it means | What to do |
|---------|-------------|-----------|
| "I approve this" but then nothing happens for 3 weeks | They don't have the authority they claimed. Someone above them is the real blocker | Ask: "Is there an additional step I should know about? Sometimes these decisions need a second sign-off" |
| "Let me run it by my boss" repeatedly | Your contact is the recommender, not the EB. Their boss is the EB | Ask: "Can I join that conversation with your boss? I can answer any questions directly" |
| "We need to wait for budget cycle" | Budget isn't allocated. The EB hasn't prioritized this. No discretionary spend available | Ask: "When is the next budget cycle? Can we get this into the plan?" |
| "Procurement will handle it from here" after proposal | The EB approved the concept but procurement has independent authority to negotiate or block | Engage procurement directly. Don't assume approval = done |
| EB meeting keeps getting rescheduled | The deal isn't a priority for the EB. The champion can't secure their attention | Coach the champion: "What would help get [EB] to commit 15 minutes?" Or escalate via peer-to-peer outreach |
| "Approved!" verbally, but no follow-through | Verbal approval without process initiation (no contract sent, no procurement engaged) | Ask: "Great. What's the next step to turn this into a signed contract? Should I send the MSA to procurement?" |

---

## Hidden EBs

### Non-obvious people who control the budget

| Hidden EB | When they appear | Why they matter |
|-----------|-----------------|----------------|
| CFO / Finance | Deals above a certain threshold. New budget line items | Can override the VP's approval. "Finance said no" kills deals that the VP approved |
| Board of Directors | Large deals at smaller companies. $100K+ at Series A-B | Board may need to approve or be aware. CEO checks with the board before signing |
| Chief of Staff | Large companies. Gatekeepers for the C-suite | Influences the C-suite's priorities and calendar. Can accelerate or delay |
| IT Security (with veto power) | Any company with a security review process | Can block a deal on security grounds regardless of business approval |
| VP of a different department | When budget comes from a shared pool | Two VPs competing for the same budget. Your VP championing the deal may lose to the other VP's priority |
| The predecessor's choice | When the current VP inherited the incumbent tool | The VP who chose the current tool may have left, but the decision lingers. The new VP may be reluctant to change something that's "working" |

### Hidden EB rules

- **Always ask: "Is there anyone else who needs to approve or could block this?"** This catches hidden EBs that the champion didn't mention because they don't think of them as part of the buying process
- **Finance is a hidden EB on any new budget line item.** If your product is replacing an existing tool, the budget exists. If it's a new category with no prior spend, Finance may need to approve the line item, not just the amount
- **Board awareness ≠ board approval.** At Series A-B companies, the CEO may say "I need to mention this to the board." This is usually awareness, not a formal vote. But it can delay by 2-4 weeks until the next board meeting

---

## CRM Implementation

### EB tracking fields

| Field | Type | Object | Values |
|-------|------|--------|--------|
| `economic_buyer_identified` | Checkbox | Opportunity | Yes / No |
| `economic_buyer_name` | Lookup to Contact | Opportunity | The EB contact record |
| `economic_buyer_engaged` | Picklist | Opportunity | Not yet / Identified / Meeting scheduled / Met / Aligned / Approved |
| `spending_authority_threshold` | Number | Account | The dollar amount above which additional approval is needed |
| `approval_chain_documented` | Checkbox | Opportunity | Yes / No |

### CRM rules

- **`economic_buyer_identified` should be a stage-gate.** Don't advance a deal past Evaluation without identifying the EB. Make it a required field at the Proposal stage
- **`economic_buyer_engaged` tracks progression.** "Identified" is different from "Met" is different from "Approved." Track the EB relationship stage, not just their name

---

## Measurement

| Metric | Definition | Target | Frequency |
|--------|-----------|--------|-----------|
| EB identified by Demo stage | % of deals where EB is named before Proposal | > 80% | Monthly |
| EB engaged by Proposal stage | % of deals where EB has been met before proposal sends | > 60% | Monthly |
| Win rate with EB engaged vs not | Close rate comparison | EB-engaged should win at 2x+ | Quarterly |
| Deals lost to "no decision" with EB unengaged | Deals that died because the EB never approved | Track. Should inform process changes | Quarterly |
| Average deal stage when EB is first identified | At which stage does the EB typically get named | Should be Discovery or Demo. If Negotiation = too late | Quarterly |

---

## Anti-Pattern Check

- Assuming the person on the call is the EB because they have a VP title. Title ≠ authority. A VP at a 30-person company may approve everything. A VP at a 3,000-person company may need CFO sign-off for anything above $20K. Test authority, don't assume it
- Never asking about the approval process. "Who approves this?" is a simple question that 40% of reps never ask. Without asking, you discover the real EB when the deal stalls at procurement
- Accepting "I make the decision" without testing. Champions often believe they're the EB because they make the recommendation. Test with a commitment question: "Can you approve this quarter?" If they defer, they're not the EB
- Sending the proposal without the EB knowing about the deal. A proposal that arrives at procurement without the EB's knowledge or approval gets stuck. The EB should have seen the business case and agreed directionally before the proposal is sent
- Going directly to the EB without the champion's knowledge. Bypassing the champion to email the VP directly undermines the champion's role and trust. If you need EB access, work through the champion. "Can you set up a 15-minute meeting with your VP?" is the correct path
- Treating the EB meeting like a demo. The EB gets 15-20 minutes. They don't want a feature walkthrough. They want the business case: what's the problem, what's the cost, what's the ROI, who else has done this. Lead with numbers, not screens
- Not mapping hidden EBs. The VP approved. But Finance rejected the new budget line item. Or IT blocked on security. Or the board wanted to discuss first. Ask about EVERY approval gate, not just the most obvious one