Latest / MATCH B2B INSIGHTS / The Political Deal Map Behind Enterprise Sales

Transcript

The Political Deal Map Behind Enterprise Sales · MATCH B2B INSIGHTS

• 0:09
  [בני פלומן] Welcome back to MATCH B2B Insights.
• 0:12
  I'm בני פלומן.
• 0:14
  This is Part 4 of our six-part series on negotiation management in global
• 0:18
  B2B environments.
• 0:19
  Joining me today are Brenda and Brian Newman.
• 0:22
  In episode one, we talked about why access is not authority.
• 0:26
  In episode two, we looked at why signal is not stage.
• 0:30
  In episode three, we focused on silence,
• 0:33
  body language, and how to interpret what buyers don't say.
• 0:36
  Today we're on episode four: Organizational Politics and the Political
• 0:41
  Deal Map behind enterprise sales.
• 0:43
  Picture a champion on Tuesday saying,
• 0:46
  "It's moving." Good call, good energy,
• 0:48
  budget sounds real.
• 0:49
  Then Thursday, legal appears.
• 0:51
  Friday, procurement asks for vendor forms.
• 0:54
  Monday, security sends a 47-question review.
• 0:57
  Same deal, same product, same value - but now the deal is no longer moving
• 1:02
  forward.
• 1:03
  It's being re-evaluated by the organization.
• 1:05
  Now it's fragmented, because each new stakeholder is optimizing for a
• 1:09
  different kind of safety.That 47-question security review is
• 1:14
  so specific it hurts.
• 1:16
  And the phrase that gets sellers in trouble is "it's moving."
• 1:20
  Moving where?
• 1:22
  Because from the champion's seat,
• 1:24
  "moving" might mean they like you.
• 1:26
  From procurement's seat, "moving" means you cleared commercial terms.
• 1:30
  From legal's seat, it means risk is bounded on paper.
• 1:34
  Those are not the same thing.In pipeline
• 1:34
  reviews,
• 1:39
  this is where forecasts get fictional.
• 1:41
  Rep logs "next step completed," champion is engaged,
• 1:45
  maybe even a target close date is in CRM.
• 1:48
  But no fields for legal owner,
• 1:49
  no security status, no procurement path.
• 1:52
  So confidence gets built on ONE relationship while three unseen
• 1:52
  workstreams
• 1:57
  haven't even started.
• 1:58
  I've seen deals seat at 70 percent probability for three weeks,
• 2:02
  then suddenly slip 45 days because security entered for the first time.
• 2:02
  Exactly.
• 2:06
  The mistake is thinking delay equals objection.
• 2:09
  Often it doesn't.
• 2:10
  Procurement is not there to love your positioning.
• 2:13
  Legal is not there to admire your deck.
• 2:15
  Security is not there to celebrate innovation.
• 2:18
  They are there to prevent downside.
• 2:20
  So if your champion says, "Everyone's aligned," I want one immediate
• 2:24
  follow-up: aligned on what, exactly?
• 2:27
  Business case?
• 2:28
  Commercial terms?
• 2:30
  Data handling?
• 2:31
  Implementation exposure?
• 2:33
  Alignment is a dangerously vague word.Let me try to explain
• 2:37
  it back.
• 2:38
  The seller sees extra stakeholders as friction after the decision.
• 2:42
  You're saying the committee is the decision.
• 2:45
  Not a postscript -- the actual mechanism.
• 2:45
  Almost.
• 2:49
  The committee is the mechanism of organizational permission.
• 2:54
  Deals don't move when one person is convinced.
• 2:57
  They move when the organization becomes safe enough to approve.
• 3:01
  A champion can create motion.
• 3:03
  They usually cannot create institutional safety alone.
• 3:07
  And that is why false progress feels so convincing.
• 3:09
  Meetings happen.
• 3:11
  Emails happen.
• 3:12
  Your internal team says, "Great engagement." Meanwhile,
• 3:17
  the buying system has not yet decided it can absorb the risk of saying
• 3:20
  yes.
• 3:20
  And you can spot this early in CRM if you're disciplined.
• 3:24
  Three signs.
• 3:25
  First, all notes come from the same contact for,
• 3:28
  say, 21 days.
• 3:29
  Second, next steps are seller-owned -- demo,
• 3:32
  proposal, follow-up -- instead of buyer-owned,
• 3:35
  like legal intro or security review kickoff.
• 3:38
  Third, stage advancement happens before new stakeholders are named.
• 3:42
  That combo is deadly.
• 3:44
  It looks clean in Salesforce...
• 3:46
  until it explodes in forecast call.
• 3:46
  That "21 days from one contact" thing
• 3:52
  -- I'm gonna remember that.
• 3:53
  Because it sounds active, but it's basically a one-person bubble.
• 3:59
  Right.
• 4:00
  And reps defend it by saying, "But the champion is strong." Maybe.
• 4:05
  I've had strong champions who disappeared the second procurement asked
• 4:08
  for redlines they couldn't sponsor internally.
• 4:10
  Not because they stopped liking us.
• 4:12
  Because the deal stopped being theirs alone.This is also
• 4:15
  where a lot of companies misdiagnose the problem.
• 4:18
  They say, "We need better closing." No.
• 4:22
  Sometimes you need better political reading.
• 4:24
  At Match B2B, we see this constantly with companies entering U.
• 4:24
  S.
• 4:28
  and European enterprise accounts: the offer is credible,
• 4:32
  meetings are happening, interest is real - but the team is reading enthusiasm
• 4:36
  as progress and activity as control.
• 4:39
  Those are not revenue mechanics.
• 4:41
  Those are surface signals.
• 4:43
  If you cannot map how the organization makes itself feel safe,
• 4:47
  the deal is still fragile, no matter how warm the champion sounds.
• 4:51
  This is exactly what we see with companies we work with at Match B2B.
• 4:56
  Most teams don't lose deals because there is no interest.
• 4:59
  They lose because they don't understand how the organization actually
• 5:03
  decides.
• 5:03
  That's why we built our model in two clear stages.
• 5:07
  First, a setup phase where we define ICP,
• 5:10
  signals, data, and messaging, and build the pipeline correctly.
• 5:14
  Then a second phase that includes that setup plus three months of structured
• 5:19
  activity where we generate real conversations and real opportunities.
• 5:23
  But the key point is commitment.
• 5:26
  We commit to targets and results.
• 5:28
  And if those targets are not reached within those three months after
• 5:31
  the setup, we continue working for free until they are.
• 5:34
  Because pipeline is not about effort.
• 5:36
  It's about building a system that actually produces results.
• 5:36
  So here's
• 5:41
  the framework.
• 5:42
  We call it the Political Deal Map.
• 5:45
  Four questions.
• 5:46
  Who drives the deal?
• 5:48
  Who owns the risk?
• 5:50
  Who slows the process?
• 5:51
  And who can quietly stop it without ever saying "no" publicly?
• 5:54
  If you don't have all four, you do not have a map.
• 5:58
  You have optimism.
• 5:59
  If you don't have all four, you don't have a deal.
• 6:02
  You have momentum without control.That fourth one
• 6:06
  -- "quietly stop it" -- is the one people miss,
• 6:09
  right?
• 6:09
  Because nobody wants to believe a deal can die without a dramatic rejection.
• 6:15
  But that's exactly how enterprise deals die.
• 6:18
  Just...
• 6:19
  calendar drift, unanswered redlines,
• 6:22
  "we're still reviewing."Yep.
• 6:24
  In field terms, the quiet stopper is often not the loudest person.
• 6:28
  It might be a security lead who never joins the sales call but controls
• 6:32
  the review queue.
• 6:32
  Or a finance approver who asks one margin question and then everything
• 6:36
  pauses.
• 6:37
  In one pipeline I ran, we started tagging deals with "hidden blocker suspected"
• 6:42
  when close dates moved twice without a named new stakeholder.
• 6:46
  That tag alone improved forecast honesty fast.
• 6:46
  And this is where sellers
• 6:51
  need usable questions, not theory.
• 6:53
  Ask: "Who else needs to feel comfortable before this moves?" Ask: "Where do deals
• 6:53
  like this usually get slowed down internally?"
• 7:01
  Ask: "When legal, procurement, or security gets involved,
• 7:01
  whose approval matters most?"
• 7:07
  Ask: "If this stalls, what usually causes it on your side?" Ask: "Who typically
• 7:07
  enters this process later that we haven't involved yet?"
• 7:16
  And ask: "If we wanted to move this faster, which function would we need to
• 7:16
  engage earlier?"
• 7:22
  Those questions are not aggressive.
• 7:24
  They're diagnostic.
• 7:24
  I like "feel comfortable" better than "approve."
• 7:30
  "Approve" sounds formal and a little threatening.
• 7:33
  "Feel comfortable" gets at the real issue,
• 7:35
  which is organizational confidence,
• 7:38
  not just signatures.
• 7:38
  Exactly.
• 7:41
  Because signatures are the artifact.
• 7:43
  Safety is the decision.
• 7:45
  And once you hear the answers,
• 7:47
  reduce friction one stakeholder at a time.
• 7:50
  Don't send the same deck to everyone.
• 7:52
  Procurement needs commercial clarity.
• 7:54
  Legal needs bounded terms.
• 7:56
  Security needs credible handling of exposure.
• 7:59
  The champion needs language to carry your case internally.
• 8:02
  One deal, different proof.
• 8:02
  Operationally,
• 8:06
  I'd add one simple rule: every late-stage deal should have named contacts
• 8:10
  or named functions for all four Political Deal Map roles in CRM.
• 8:14
  Not "TBD." Named, or at least functionally named.
• 8:18
  Driver: VP Ops.
• 8:20
  Risk owner: security team.
• 8:22
  Slow point: procurement review.
• 8:25
  Quiet stopper: legal counsel, maybe.
• 8:28
  The moment a rep can't fill one of those in,
• 8:30
  that's not admin work - that's a discovery gap.
• 8:33
  If a deal is at 70 percent and you cannot name these roles,
• 8:37
  the stage is wrong.
• 8:37
  And if a founder says,
• 8:40
  "But asking all this will slow the deal down"...
• 8:44
  I actually think the opposite.
• 8:46
  You're trading hidden delay for visible process.
• 8:49
  Which is healthier, even if it's less flattering in the moment.
• 8:55
  Less flattering, yes.
• 8:56
  More real, definitely.
• 8:58
  I've had deals move faster after we asked,
• 9:01
  "Where does this usually get stuck?" because the buyer said,
• 9:03
  "Actually, let's pull security in now." Better a hard conversation in
• 9:08
  week two than a silent freeze in week eight.[בני פלומן] If this sounds
• 9:12
  familiar, don't ignore it.
• 9:13
  Go to LinkedIn, find me, בני פלומן,
• 9:16
  and send me a message.
• 9:17
  Just write what you're seeing in your pipeline.
• 9:19
  Where deals are slowing down, where things feel unclear.
• 9:22
  From there, we'll have a conversation and look at it together.
• 9:25
  If you don't know who needs to feel safe,
• 9:28
  you're still early - no matter what your CRM says.That's the
• 9:32
  line.
• 9:33
  Safe enough to say yes.
• 9:33
  And if it doesn't feel safe internally,
• 9:38
  the pipeline number is just theater.