Latest / MATCH B2B INSIGHTS / Access Isn’t Authority: Finding the Real Decision-Maker

Transcript

Access Isn’t Authority: Finding the Real Decision-Maker · MATCH B2B INSIGHTS

• 0:09
  Welcome to the show.
• 0:10
  This is MATCH B2B Insights, I'm בני פלומן,
• 0:13
  here with Brenda and Brian Newman.
• 0:15
  This is episode one of a six-part series on smart negotiation management.
• 0:20
  Today: finding the REAL decision-maker inside the organization.
• 0:25
  Coming next: culture, body language,
• 0:28
  internal politics, industry differences,
• 0:30
  and consensus.
• 0:31
  So let's go straight at it -- access is NOT authority.And that
• 0:36
  sounds obvious until you're in the meeting with the senior title,
• 0:40
  the nice budget language, the enthusiasm...
• 0:43
  and everybody relaxes too early.I'd actually push it one
• 0:47
  step further.
• 0:48
  In a lot of deals, the loudest executive isn't just "not always" the
• 0:52
  buyer -- they're sometimes a distraction.
• 0:54
  The person talking 60% of the time may be the least dangerous person
• 0:58
  in the room.
• 0:58
  Exactly.
• 1:00
  People confuse visibility with control.
• 1:02
  They got the meeting, so they think they found the authority.
• 1:05
  No.
• 1:07
  They found an entry point.
• 1:07
  Give me a concrete one.
• 1:07
  Cybersecurity.
• 1:12
  Vendor sells hard into the CISO.
• 1:14
  Strong pain, clear threat narrative,
• 1:17
  demos go well.
• 1:18
  The CISO says, "We need this now." Sounds done.
• 1:22
  Then finance blocks it.
• 1:24
  Why?
• 1:25
  Because the risk, from finance's view,
• 1:27
  is budgetary concentration.
• 1:29
  Not breach exposure -- budget exposure.
• 1:31
  Same deal, two risk models.
• 1:31
  And that "budgetary concentration" phrase
• 1:37
  matters.
• 1:38
  I've seen teams hear urgency from security and assume urgency
• 1:43
  travels across the company.
• 1:44
  It doesn't.
• 1:45
  Finance asks: is this replacing an existing tool,
• 1:49
  adding headcount, increasing annual commitment,
• 1:52
  creating vendor dependency?
• 1:53
  Different scoreboard.
• 1:53
  So the CISO owns the problem,
• 1:58
  but finance owns the pain of saying yes.
• 1:58
  Here's another one.
• 2:04
  AI platform gets a department head excited.
• 2:07
  Pilot goes well, usage looks promising,
• 2:10
  everybody says "let's scale." Then procurement forces a restart because
• 2:15
  the approval chain was never mapped.
• 2:16
  Data handling, vendor review, security questionnaire,
• 2:20
  indemnity language -- suddenly the deal goes backwards.
• 2:20
  The word "restart"
• 2:25
  is brutal there, because it FEELS like closing and it's actually
• 2:25
  re-qualification.
• 2:25
  Yes,
• 2:32
  and that's where I disagree with founders who say procurement is a late-stage
• 2:35
  issue.
• 2:36
  No.
• 2:37
  In enterprise AI, procurement can be an EARLY-stage power center hiding
• 2:41
  in late-stage clothing.I agree with the conclusion,
• 2:44
  not the framing.
• 2:46
  Procurement usually isn't strategic authority.
• 2:49
  It's process authority.
• 2:50
  But if process can stop the deal,
• 2:53
  then practically speaking, it behaves like authority.
• 2:53
  That's a useful
• 2:57
  distinction.
• 2:58
  Strategic yes versus procedural yes.
• 2:58
  Right.
• 3:02
  Last example: medtech.
• 3:03
  Sale looks ready, clinician is positive,
• 3:06
  technical review is fine.
• 3:08
  Then hospital administration steps in with one question: who carries
• 3:13
  implementation risk?
• 3:15
  Training, downtime, integration,
• 3:18
  liability, handoff.
• 3:20
  If nobody answered that early,
• 3:22
  the deal stalls.
• 3:23
  Not because the product failed -- because accountability was unclear.
• 3:23
  And
• 3:28
  "implementation risk" is the phrase I'd underline.
• 3:31
  In hospitals, the person who loves the outcome is often NOT the person
• 3:35
  who absorbs the disruption.
• 3:35
  So episode one rule is pretty simple: the person
• 3:40
  saying yes to you may not be the person allowed to say yes for the
• 3:40
  business.
• 3:46
  The next mistake is thinking the org chart tells you the truth.
• 3:49
  It doesn't.
• 3:50
  The real company universe is political,
• 3:53
  not formal.I'm gonna push back there.
• 3:56
  In some structured enterprises,
• 3:58
  especially regulated ones, the process IS formal.
• 4:02
  Titles and approval lanes do matter a lot.
• 4:02
  They matter,
• 4:06
  yes.
• 4:07
  They just don't explain enough.
• 4:09
  Formal structure tells you who is supposed to approve.
• 4:12
  Political structure tells you who can delay,
• 4:15
  redirect, or quietly kill momentum.
• 4:15
  And that's where people need a clean
• 4:19
  map.
• 4:20
  Economic buyer.
• 4:22
  Technical buyer.
• 4:22
  Legal.
• 4:23
  Finance.
• 4:24
  Sponsor.
• 4:24
  Blocker.
• 4:25
  Hidden veto point.
• 4:26
  If you can't name those seven,
• 4:28
  you're not negotiating -- you're hoping.
• 4:28
  Let's slow that down.
• 4:33
  Economic buyer is who owns the money.
• 4:35
  Technical buyer is who has to believe it works.
• 4:38
  Legal and finance are obvious.
• 4:40
  Sponsor is your internal champion.
• 4:43
  Blocker is the person actively or passively resisting.
• 4:47
  And hidden veto point is the one nobody mentions until the end.
• 4:47
  Exactly.
• 4:53
  And the hidden veto point is where deals die politely.
• 4:53
  Public fintech
• 4:58
  is the clean example.
• 4:59
  On paper, commercial leadership looks powerful.
• 5:02
  In reality, legal and compliance often have more power than their titles
• 5:06
  suggest.
• 5:06
  Not because they want the deal less -- because regulatory exposure outweighs
• 5:11
  enthusiasm."Regulatory exposure outweighs enthusiasm" -- that's the whole
• 5:17
  sector in one line.
• 5:19
  A VP can love your platform,
• 5:22
  but one compliance objection can freeze everything.
• 5:22
  Private manufacturing
• 5:27
  looks different.
• 5:28
  Founder appears decisive.
• 5:29
  Everyone says, "If the founder likes it,
• 5:32
  we're in." Maybe.
• 5:34
  But the operations lead may still be the real gatekeeper because implementation
• 5:38
  lands on that team.
• 5:39
  If ops says this disrupts throughput,
• 5:41
  the founder suddenly becomes very cautious.
• 5:41
  I've seen that exact thing.
• 5:45
  Founder says yes in the room.
• 5:47
  Operations says, "Not this quarter." And guess what?
• 5:51
  "Yes" becomes "circle back in six months."And consulting is another trap.
• 5:57
  The partner who introduced the opportunity feels senior,
• 6:01
  sounds senior, probably is senior.
• 6:04
  But they may not control budget,
• 6:06
  scope approval, or final signature.
• 6:09
  They control ACCESS, not commitment.
• 6:09
  Which brings us back to the thesis.
• 6:15
  Access is not authority.
• 6:17
  And Brenda, your pushback was fair -- formal structure matters.
• 6:21
  But negotiation management fails when people stop at the formal layer
• 6:25
  and never map the political one underneath.The first clue is
• 6:29
  not title.
• 6:29
  It's who controls next steps.
• 6:32
  Who sets the second meeting?
• 6:34
  Who decides who joins?
• 6:36
  Who changes the agenda without asking?
• 6:38
  That person matters.
• 6:38
  And I'd add three softer signals: silence,
• 6:45
  calendar control, and follow-up behavior.
• 6:48
  Sometimes the most important person says almost nothing.
• 6:53
  Sometimes they never touch the deck,
• 6:56
  but everybody waits for their note afterward.
• 6:56
  Defense sector is perfect
• 7:00
  here.
• 7:00
  You'll get a buyer who speaks maybe twice in a 45-minute call.
• 7:04
  Very little reaction, almost no warmth.
• 7:07
  Then the meeting ends and nobody moves until that person sends the summary
• 7:11
  note.
• 7:12
  If the room waits for one email,
• 7:14
  that email holder has gravity.
• 7:14
  That "one email" clue is gold.
• 7:19
  People overread charisma and underread workflow.
• 7:25
  Workflow tells the truth.
• 7:25
  Medical device is similar.
• 7:29
  The clinician can be the loudest by far -- use case,
• 7:33
  outcomes, urgency, all of it.
• 7:36
  But the final decision often tracks with operations or finance because
• 7:41
  they're measuring staffing, rollout burden,
• 7:43
  reimbursement pressure, whatever the internal constraint is.
• 7:43
  Yes,
• 7:49
  and this is where teams misdiagnose support.
• 7:51
  They say, "The doctor loves us." Fine.
• 7:55
  Does the business love the change required to adopt you?
• 7:55
  AI infrastructure
• 7:59
  gives another strong clue.
• 8:00
  The person arranging the second meeting is often more important than
• 8:03
  the one speaking most in the first.
• 8:05
  If someone quietly pulls in security,
• 8:08
  data, architecture, procurement -- that person is shaping the decision
• 8:12
  architecture.
• 8:12
  Decision architecture is a great phrase,
• 8:16
  because that's what's happening.
• 8:18
  They're not just attending.
• 8:20
  They're constructing the path to yes...
• 8:23
  or to no.And let's be honest: if you still don't know who owns
• 8:28
  the final risk after meeting two,
• 8:30
  that's not ambiguity.
• 8:31
  That's bad qualification.
• 8:31
  I mostly agree.
• 8:35
  I'd soften one part.
• 8:36
  In some enterprise deals, you won't get the full map by meeting two.
• 8:40
  But you SHOULD know where authority is likely clustering -- budget,
• 8:44
  implementation, compliance, or executive sponsorship.
• 8:44
  So maybe the practical
• 8:49
  test is this: not "who likes us?" but "who can change the process tomorrow?"
• 8:56
  If one person can add stakeholders,
• 8:58
  pause legal, or pull budget review forward,
• 9:01
  that's your signal.Exactly.
• 9:05
  Negotiation starts long before pricing.
• 9:07
  It starts the moment you decide who actually matters.
• 9:10
  And if you get that wrong, every strong meeting after that is built on
• 9:14
  borrowed confidenceThat's a good place to leave it.
• 9:14
  Next one gets interesting.
• 9:14
  See
• 9:20
  you in episode two.