MATCH B2B INSIGHTS

BusinessEducation

Listen

All Episodes

Access Isn’t Authority: Finding the Real Decision-Maker

This episode kicks off a six-part series on smart negotiation management by showing why the person who takes the meeting is not always the person who can approve the deal. Through examples in cybersecurity, AI, medtech, fintech, manufacturing, and consulting, the hosts break down how to map economic buyers, hidden veto points, and the political power behind the org chart.

This show was created with Jellypod, the AI Podcast Studio. Create your own podcast with Jellypod today.

Is this your podcast and want to remove this banner? Click here.


Chapter 1

Access is not authority

Benny Fluman

[energetic] Welcome to the show. This is MATCH B2B Insights, I’m Benny Fluman, here with Brenda and Brian Newman. This is episode one of a six-part series on smart negotiation management. Today: finding the REAL decision-maker inside the organization. Coming next: culture, body language, internal politics, industry differences, and consensus. So let’s go straight at it -- access is NOT authority.

Brenda

[curious] And that sounds obvious until you’re in the meeting with the senior title, the nice budget language, the enthusiasm... and everybody relaxes too early.

Brian Newman

[skeptical] I’d actually push it one step further. In a lot of deals, the loudest executive isn’t just “not always” the buyer -- they’re sometimes a distraction. The person talking 60% of the time may be the least dangerous person in the room.

Benny Fluman

Exactly. People confuse visibility with control. They got the meeting, so they think they found the authority. No. They found an entry point.

Brenda

Give me a concrete one.

Benny Fluman

Cybersecurity. Vendor sells hard into the CISO. Strong pain, clear threat narrative, demos go well. The CISO says, “We need this now.” Sounds done. Then finance blocks it. Why? Because the risk, from finance’s view, is budgetary concentration. Not breach exposure -- budget exposure. Same deal, two risk models.

Brian Newman

And that “budgetary concentration” phrase matters. [short pause] I’ve seen teams hear urgency from security and assume urgency travels across the company. It doesn’t. Finance asks: is this replacing an existing tool, adding headcount, increasing annual commitment, creating vendor dependency? Different scoreboard.

Brenda

So the CISO owns the problem, but finance owns the pain of saying yes.

Brian Newman

That’s it.

Benny Fluman

Here’s another one. AI platform gets a department head excited. Pilot goes well, usage looks promising, everybody says “let’s scale.” Then procurement forces a restart because the approval chain was never mapped. Data handling, vendor review, security questionnaire, indemnity language -- suddenly the deal goes backwards.

Brenda

The word “restart” is brutal there, because it FEELS like closing and it’s actually re-qualification.

Brian Newman

Yes, and that’s where I disagree with founders who say procurement is a late-stage issue. No. In enterprise AI, procurement can be an EARLY-stage power center hiding in late-stage clothing.

Benny Fluman

[firm] I agree with the conclusion, not the framing. Procurement usually isn’t strategic authority. It’s process authority. But if process can stop the deal, then practically speaking, it behaves like authority.

Brenda

That’s a useful distinction. Strategic yes versus procedural yes.

Benny Fluman

Right. Last example: medtech. Sale looks ready, clinician is positive, technical review is fine. Then hospital administration steps in with one question: who carries implementation risk? Training, downtime, integration, liability, handoff. If nobody answered that early, the deal stalls. Not because the product failed -- because accountability was unclear.

Brian Newman

And “implementation risk” is the phrase I’d underline. In hospitals, the person who loves the outcome is often NOT the person who absorbs the disruption.

Brenda

So episode one rule is pretty simple: the person saying yes to you may not be the person allowed to say yes for the business.

Chapter 2

The real power map is political

Benny Fluman

[matter-of-fact] The next mistake is thinking the org chart tells you the truth. It doesn’t. The real company universe is political, not formal.

Brenda

[questioning tone] I’m gonna push back there. In some structured enterprises, especially regulated ones, the process IS formal. Titles and approval lanes do matter a lot.

Benny Fluman

They matter, yes. They just don’t explain enough. Formal structure tells you who is supposed to approve. Political structure tells you who can delay, redirect, or quietly kill momentum.

Brian Newman

And that’s where people need a clean map. Economic buyer. Technical buyer. Legal. Finance. Sponsor. Blocker. Hidden veto point. If you can’t name those seven, you’re not negotiating -- you’re hoping.

Brenda

Let’s slow that down. Economic buyer is who owns the money. Technical buyer is who has to believe it works. Legal and finance are obvious. Sponsor is your internal champion. Blocker is the person actively or passively resisting. And hidden veto point is the one nobody mentions until the end.

Benny Fluman

Exactly. And the hidden veto point is where deals die politely.

Brian Newman

Public fintech is the clean example. On paper, commercial leadership looks powerful. In reality, legal and compliance often have more power than their titles suggest. Not because they want the deal less -- because regulatory exposure outweighs enthusiasm.

Brenda

“Regulatory exposure outweighs enthusiasm” -- that’s the whole sector in one line. [chuckles] A VP can love your platform, but one compliance objection can freeze everything.

Benny Fluman

Private manufacturing looks different. Founder appears decisive. Everyone says, “If the founder likes it, we’re in.” Maybe. But the operations lead may still be the real gatekeeper because implementation lands on that team. If ops says this disrupts throughput, the founder suddenly becomes very cautious.

Brian Newman

I’ve seen that exact thing. Founder says yes in the room. Operations says, “Not this quarter.” And guess what? “Yes” becomes “circle back in six months.”

Brenda

And consulting is another trap. The partner who introduced the opportunity feels senior, sounds senior, probably is senior. But they may not control budget, scope approval, or final signature. They control ACCESS, not commitment.

Benny Fluman

Which brings us back to the thesis. Access is not authority. And Brenda, your pushback was fair -- formal structure matters. But negotiation management fails when people stop at the formal layer and never map the political one underneath.

Chapter 3

How to spot the true authority early

Brian Newman

[focused] The first clue is not title. It’s who controls next steps. Who sets the second meeting? Who decides who joins? Who changes the agenda without asking? That person matters.

Brenda

And I’d add three softer signals: silence, calendar control, and follow-up behavior. Sometimes the most important person says almost nothing. Sometimes they never touch the deck, but everybody waits for their note afterward.

Benny Fluman

Defense sector is perfect here. You’ll get a buyer who speaks maybe twice in a 45-minute call. Very little reaction, almost no warmth. Then the meeting ends and nobody moves until that person sends the summary note. If the room waits for one email, that email holder has gravity.

Brian Newman

That “one email” clue is gold. [short pause] People overread charisma and underread workflow. Workflow tells the truth.

Brenda

Medical device is similar. The clinician can be the loudest by far -- use case, outcomes, urgency, all of it. But the final decision often tracks with operations or finance because they’re measuring staffing, rollout burden, reimbursement pressure, whatever the internal constraint is.

Benny Fluman

Yes, and this is where teams misdiagnose support. They say, “The doctor loves us.” Fine. Does the business love the change required to adopt you?

Brian Newman

AI infrastructure gives another strong clue. The person arranging the second meeting is often more important than the one speaking most in the first. If someone quietly pulls in security, data, architecture, procurement -- that person is shaping the decision architecture.

Brenda

Decision architecture is a great phrase, because that’s what’s happening. They’re not just attending. They’re constructing the path to yes... or to no.

Benny Fluman

[sharply] And let’s be honest: if you still don’t know who owns the final risk after meeting two, that’s not ambiguity. That’s bad qualification.

Brian Newman

I mostly agree. I’d soften one part. In some enterprise deals, you won’t get the full map by meeting two. But you SHOULD know where authority is likely clustering -- budget, implementation, compliance, or executive sponsorship.

Brenda

So maybe the practical test is this: not “who likes us?” but “who can change the process tomorrow?” If one person can add stakeholders, pause legal, or pull budget review forward, that’s your signal.

Benny Fluman

[reflective] Exactly. Negotiation starts long before pricing. It starts the moment you decide who actually matters. And if you get that wrong, every strong meeting after that is built on borrowed confidence.

Brenda

That’s a good place to leave it.

Brian Newman

Next one gets interesting.

Benny Fluman

See you in episode two.