Latest / MATCH B2B INSIGHTS / Why Active Pipelines Stall in Enterprise Sales

Transcript

Why Active Pipelines Stall in Enterprise Sales · MATCH B2B INSIGHTS

• 0:00
  Welcome to MATCH B2B Insights, the podcast where we- we- we actually expose what
• 0:05
  drives enterprise revenue and cut through the B2B noise.
• 0:09
  I'm Benny Fluman, founder and CEO of MATCH B2B, and today I am joined by my co-host,
• 0:15
  Dan Mercer, a veteran CFO who has lived on both sides of the budget sheet.
• 0:20
  Dan, welcome back to the mic.
• 0:22
  Thanks, Benny.
• 0:23
  It- it's good to be here.
• 0:25
  You know, I was actually thinking about our topic today because just last week,
• 0:28
  I- I was looking at a pipeline review for one of our business units.
• 0:32
  They had thirty-two enterprise deals listed in 'late stage.'
• 0:36
  Every single one of them had been sitting there for over ninety days.
• 0:39
  Ninety days.
• 0:41
  The sales team kept telling me, 'Oh, the tech team loves the demo,
• 0:44
  the users are super excited, they're logging into the trial.'
• 0:48
  But when I asked, okay, when does the contract get signed?
• 0:53
  Silence.
• 0:54
  It- it was pure pipeline theater.
• 0:56
  Pipeline theater.
• 0:57
  I- I love that term, Dan, because it- it's so incredibly common.
• 1:01
  You've got SDRs celebrating because they booked twenty demo calls,
• 1:05
  and marketing is high-fiving over a spike in whitepaper downloads.
• 1:09
  But what they're actually collecting are...
• 1:11
  what I call 'tourists.'
• 1:13
  These are people who have plenty of time to look at cool software,
• 1:16
  they love the slick UI, they- they ask for custom dashboards,
• 1:21
  but they don't have a single dollar of budget authority.
• 1:23
  There's a massive, massive chasm between user interest and economic urgency.
• 1:29
  Exactly.
• 1:30
  The user wants to make their day-to-day life slightly easier.
• 1:33
  That's a nice-to-have.
• 1:35
  But as a CFO, I don't sign checks for 'slightly easier.'
• 1:39
  I sign checks when there is a risk of a five percent hit to our operating margin,
• 1:44
  or a contractual SLA penalty that's going to cost us two hundred thousand dollars
• 1:48
  next quarter if we don't fix a specific bottleneck.
• 1:51
  If the sales rep can't show me how their software prevents that specific loss,
• 1:55
  the deal is dead.
• 1:57
  It just sits in the pipeline forever until the rep finally marks it closed-lost due
• 2:01
  to, you know, 'no decision.'
• 2:03
  Right, and 'no decision' is actually your biggest competitor in B2B.
• 2:07
  It's not the other vendor down the street.
• 2:09
  It's- it's the comfort of doing absolutely nothing.
• 2:13
  When a vendor spends all their energy showing off their product capabilities,
• 2:17
  their shiny AI features, their integrations, they're completely missing the point.
• 2:22
  They are assuming the customer has already decided to buy *something*,
• 2:26
  and now they're just comparing features.
• 2:28
  But in reality, the customer is still trying to figure out if this problem is even
• 2:33
  worth the pain of changing.
• 2:35
  If you don't build that logical urgency from day one, you're just entertaining
• 2:39
  tourists.
• 2:40
  Let's talk about that gravity of the status quo, because I think a lot of founders
• 2:44
  underestimate just how comfortable inefficiency can be.
• 2:48
  People look at a manual, spreadsheet-based process and think,
• 2:52
  'That's a nightmare, they must want to replace it.'
• 2:54
  But to the company, that spreadsheet is a known, predictable quantity.
• 2:59
  They know exactly how much it costs, they know who owns it,
• 3:03
  and they know how to work around its flaws.
• 3:05
  It- it has a massive gravitational pull.
• 3:08
  Well, because there's a friction tax to change.
• 3:11
  What- what people forget is that buying software isn't just about paying the
• 3:14
  subscription fee.
• 3:16
  There's a fully loaded cost of change.
• 3:18
  I have to allocate project management resources, I have to retrain fifty employees,
• 3:23
  we risk losing data during migration, and there's a highly predictable dip in
• 3:27
  operational productivity during the first thirty days of transition.
• 3:31
  If a software license costs fifty thousand dollars, the *actual* cost of
• 3:36
  implementation might be two hundred thousand in lost time and risk.
• 3:39
  So if the vendor is only proving fifty thousand dollars of value,
• 3:43
  they're already deep in the red in my book.
• 3:45
  Let's anchor that with a real scenario.
• 3:47
  Take HR technology.
• 3:49
  I worked with a company selling an automated onboarding platform.
• 3:52
  They were pitching a mid-sized enterprise that was onboarding about forty new hires
• 3:56
  a month using a messy mix of PDFs, emails, and manual data entry into their payroll
• 4:02
  system.
• 4:03
  The HR team was complaining constantly about the administrative burden.
• 4:07
  The vendor's sales deck was full of slides about 'employee experience,'
• 4:12
  'seamless digital signature workflows,' and 'modern brand perception for new hires.'
• 4:17
  And let me guess...
• 4:19
  the HR Director loved it, but the CFO killed it?
• 4:22
  Dead on arrival.
• 4:23
  Because the HR Director went to the CFO and said, 'We need forty thousand dollars a
• 4:28
  year for this onboarding tool because it makes our workflow so much nicer.'
• 4:32
  And the CFO looked at the spreadsheet and said, 'Look, our manual process might be
• 4:37
  tedious, but we aren't missing compliance deadlines, our payroll is accurate,
• 4:41
  and the current HR staff is already paid for.
• 4:44
  The manual pain is tolerable.'
• 4:46
  The status quo won because the vendor didn't quantify the actual commercial risk of
• 4:51
  those manual errors.
• 4:52
  They sold 'delight' instead of risk mitigation.
• 4:56
  Right.
• 4:57
  If they had shown that manual data entry errors were causing a three percent payroll
• 5:01
  discrepancy rate that cost ninety thousand dollars a year in compliance fines and
• 5:06
  wage corrections...
• 5:07
  now you've got my attention.
• 5:09
  Now the status quo isn't comfortable anymore--it's actively costing me money.
• 5:14
  That's the shift from a nice-to-have to a must-have.
• 5:18
  This brings us to a major pet peeve of mine: the absolute obsession in B2B GTM with
• 5:24
  'user delight.'
• 5:25
  We've had a decade of product-led growth advice telling everyone that if you just
• 5:29
  design a beautiful interface and make the onboarding flow frictionless,
• 5:33
  the product will sell itself.
• 5:35
  But when you are selling five- or six-figure enterprise deals,
• 5:39
  user delight doesn't show up on the balance sheet.
• 5:42
  It really doesn't.
• 5:43
  I've never seen a line item on an income statement for 'delighted employees.'
• 5:47
  I mean, look, I want our team to have good tools, but when we're allocating capital,
• 5:53
  'delight' gets pushed to the bottom of the list every single time.
• 5:57
  We have to translate capabilities into financial outcomes.
• 6:01
  Walk me through how you actually do that, Benny.
• 6:04
  Say you have a highly technical product...
• 6:06
  how do you bridge that gap?
• 6:08
  Okay, let's take a complex tech product-say, a supply chain platform with real-time
• 6:13
  AI anomaly detection.
• 6:15
  A standard GTM message would be: 'Our advanced AI algorithms analyze your supply
• 6:21
  chain data in real time to detect anomalies and send instant dashboard alerts to
• 6:26
  your inventory managers.'
• 6:27
  To a technical user, that sounds incredible.
• 6:30
  They can picture the clean dashboard, the instant alerts.
• 6:33
  But to you, Dan, as the CFO...
• 6:36
  what does that actually mean?
• 6:38
  Honestly?
• 6:39
  It sounds like more noise.
• 6:41
  It sounds like my team is going to spend all day looking at alerts instead of doing
• 6:44
  their actual jobs.
• 6:46
  It- it doesn't tell me why I should write a check.
• 6:49
  Exactly.
• 6:50
  So we have to translate that feature into a balance sheet outcome.
• 6:53
  Instead of talking about AI algorithms and alerts, we say: 'By detecting supply
• 6:59
  chain anomalies seventy-two hours faster than manual audits,
• 7:02
  we enable you to reduce your excess safety stock buffer by fifteen percent.
• 7:07
  For a company of your size, that frees up six million dollars in working capital
• 7:11
  from your warehouse within the first six months, while maintaining your ninety-nine
• 7:16
  point eight percent order fulfillment rate.'
• 7:18
  See the difference?
• 7:20
  We didn't lead with the AI.
• 7:22
  We led with the six million dollars of freed-up working capital.
• 7:26
  Now *that* is a business case.
• 7:28
  You've connected a technical feature directly to liquidity.
• 7:31
  Let me give you another example from my world--cybersecurity.
• 7:35
  Most security vendors sell 'threat intelligence dashboards' or 'comprehensive
• 7:40
  vulnerability scanning.'
• 7:42
  They show scary slides of hackers and talk about 'peace of mind.'
• 7:46
  But peace of mind isn't a financial metric.
• 7:49
  If a security team wants a seven-figure budget for a new vulnerability management
• 7:53
  platform, they need to frame it around exposure mitigation.
• 7:57
  For example: 'We have twelve hundred legacy systems that are subject to GDPR
• 8:01
  compliance.
• 8:03
  A single data breach on these systems carries a regulatory fine exposure of up to
• 8:07
  four percent of global turnover, which is forty million dollars.
• 8:12
  This tool reduces our detection-to-remediation window from eighty days to four
• 8:16
  hours, reducing our modeled risk exposure by eighty-five percent.'
• 8:21
  That is a forty million dollar mitigation case.
• 8:24
  That's how you get a board-level sign-off.
• 8:26
  That- that is a perfect bridge to how you actually evaluate these proposals,
• 8:30
  Dan.
• 8:30
  Because when a business case like that lands on your desk, you aren't just looking
• 8:35
  at the ROI number the vendor put in their PDF brochure.
• 8:38
  You're running your own internal calculus.
• 8:41
  What are the core metrics you're actually calculating when a proposal comes through?
• 8:45
  I reduce every single purchasing decision to three variables.
• 8:48
  First: Cost per Outcome.
• 8:51
  This is not just the software license price.
• 8:53
  I calculate the fully loaded cost--the software, the internal engineering hours
• 8:58
  required for implementation, the cost of retraining, and any third-party consulting
• 9:03
  fees.
• 9:04
  What is the total cash outflow required to get to the *actual* result?
• 9:08
  If a vendor tells me their tool costs fifty thousand, but we have to spend a hundred
• 9:13
  and fifty thousand in custom integration work, my Cost per Outcome is two hundred
• 9:18
  thousand.
• 9:19
  I need that math to be completely transparent.
• 9:21
  And what's the second variable?
• 9:23
  Time to Cash.
• 9:25
  How long until we actually see the savings or the revenue increase hit our bank
• 9:29
  account?
• 9:30
  If a product has a thirty-month implementation cycle before we realize a single
• 9:34
  dollar of savings, that's a massive risk in a volatile market.
• 9:38
  I look for solutions that have a payback period of under eighteen months,
• 9:42
  ideally under twelve.
• 9:44
  If you can show me that cash starts flowing back to us in month four,
• 9:48
  that deal moves to the front of the line.
• 9:50
  And the third?
• 9:51
  Downside Risk.
• 9:53
  What happens if this project fails?
• 9:55
  If we pull the plug after nine months, are we stuck in a three-year contract?
• 10:00
  Did we dismantle our old system so we can't go back?
• 10:04
  I look for vendors who can mitigate that risk--whether that's through phased
• 10:07
  rollouts, clear pilot criteria, or SLA guarantees.
• 10:12
  If a vendor is confident in their product, they should be willing to share some of
• 10:16
  that operational risk.
• 10:18
  If they demand a massive upfront commitment with no safety valves,
• 10:22
  I start getting very nervous.
• 10:24
  This is exactly why GTM teams need to stop sending those generic,
• 10:28
  over-simplified ROI calculators-you know, those PDFs where you plug in three numbers
• 10:34
  and it magically says 'Your ROI is four hundred percent!'
• 10:38
  No executive believes those.
• 10:40
  We need to equip our internal champions with realistic, conservative,
• 10:45
  fully transparent financial models.
• 10:47
  Give them a spreadsheet where they can adjust the variables,
• 10:50
  test the worst-case scenarios, and actually defend the assumptions in front of their
• 10:54
  finance team.
• 10:55
  So how do we actually build that urgency?
• 10:57
  A lot of sales teams try to create artificial urgency.
• 11:01
  They say, 'Oh, if you sign by the end of the quarter, I can give you a twenty
• 11:05
  percent discount.'
• 11:06
  Or, 'This pricing is only good until Friday.'
• 11:09
  But to an experienced buyer, that just smells like desperation.
• 11:13
  It doesn't create logical urgency.
• 11:16
  It absolutely does not.
• 11:18
  It actually makes me want to wait even longer because I know they're desperate to
• 11:22
  hit their quota.
• 11:23
  Real urgency has to be logical, not promotional.
• 11:27
  It has to come from the cost of doing nothing--what we call the 'cost of delay.'
• 11:32
  Yes, let's look at a concrete logistics example to show how you quantify that.
• 11:37
  Imagine a company with a fleet of five hundred delivery trucks.
• 11:41
  They're looking at route optimization software that costs one hundred and twenty
• 11:44
  thousand dollars a year.
• 11:46
  The software can reduce their fuel and maintenance costs by seven percent.
• 11:50
  If the sales rep just keeps pitching 'smarter routing' and 'happier drivers,'
• 11:56
  there's no real timeline.
• 11:57
  The deal stalls.
• 11:58
  But if you walk me through the math...
• 12:00
  let's say their monthly fuel bill for those five hundred trucks is three million
• 12:04
  dollars.
• 12:05
  A seven percent reduction is two hundred and ten thousand dollars a month in
• 12:08
  savings.
• 12:09
  If the software license is ten thousand a month, the net savings is two hundred
• 12:13
  thousand dollars every single month.
• 12:16
  So, if we delay this decision by ninety days to 'think about it,'
• 12:20
  that three-month delay doesn't just push the project out--it literally costs the
• 12:24
  company six hundred thousand dollars in flushed fuel costs.
• 12:27
  That is the cost of delay.
• 12:29
  Exactly.
• 12:30
  Now the sales rep doesn't need to offer a twenty percent discount to close the deal
• 12:34
  by Friday.
• 12:35
  The customer can see that every week they delay is costing them fifty thousand
• 12:39
  dollars of pure cash.
• 12:41
  That is logical urgency.
• 12:43
  It- it reframes the status quo from 'safe and comfortable' to 'actively bleeding
• 12:48
  capital.'
• 12:48
  You make the decision to do nothing feel commercially riskier than making the
• 12:53
  change.
• 12:53
  And that- that is the shift.
• 12:55
  When the internal champion goes to their CFO, they aren't asking for money to buy a
• 13:00
  new toy.
• 13:01
  They're presenting a business case showing that the company is currently losing two
• 13:04
  hundred thousand dollars a month, and here is the exact implementation plan,
• 13:09
  the fully loaded cost, and the risk mitigation strategy to stop that leak.
• 13:14
  That is a deal that gets approved.
• 13:16
  This brings us to our closing challenge for every founder, CEO,
• 13:20
  and GTM leader listening today.
• 13:22
  Go look at your website, look at your sales deck, look at the outbound sequences
• 13:27
  your SDRs are sending right now.
• 13:29
  Are you selling an impressive product with cool features, or are you proving why
• 13:33
  your buyer can no longer afford to do nothing?
• 13:36
  If you're selling the product, you are going to keep losing deals to 'no decision.'
• 13:41
  You have to weaponize the cost of delay and speak the language of economic impact.
• 13:46
  Well said, Benny.
• 13:48
  If you can't prove who is paying for the status quo, you aren't ready to sell yet.
• 13:52
  All right, good chatting, talk soon.
• 13:54
  Thanks, Dan.
• 13:55
  Talk soon.