Key Takeaways

  • Sales forecast accuracy serves as the definitive diligence metric for judging sales leadership competence, proving whether front-line managers actively interrogate pipeline or pass unverified rep optimism up the chain.
  • John McMahon points to his post-merger integration work at Cisco and BMC to demonstrate that missing revenue targets stems from weak frontline qualification, not simply poor rep effort.
  • True forecast precision requires managers to distinguish between enthusiastic internal coaches and genuine economic buyers who control corporate budget allocation.
  • Pipeline diligence fails when acquirers rely on aggregate CRM dashboards instead of auditing deals against The Three Core Deal Qualification Questions.

The Three Core Deal Qualification Questions

When auditing enterprise pipeline, McMahon insists that revenue predictability comes down to frontline manager discipline. As McMahon explains, “the greatest sign of a whether or not a manager is truly involved with their people is how accurate they can forecast.” (play from 46:37) If a manager oversees five sales reps, precision shows “that you're either involved in all those deals personally or you're also able to really qualify the hell out of the deals where you could not personally go to.” (play from 46:53)

To enforce that rigor, McMahon uses three strict questions on every committed pipeline asset:

  • Question 1: Why do they have to buy?: Validates customer pain. Verifies whether the sales rep has uncovered deep, business-critical pain points rather than superficial interest.
  • Question 2: Why do they have to buy from us?: Validates technical and business differentiation. Verifies that the specific differentiators locked into the buyer's decision criteria map directly back to the customer's identified pain points.
  • Question 3: Why do they have to buy now?: Validates urgency and compelling event. Forces the rep to articulate the measurable negative business consequences to the customer of delaying or failing to solve the problem immediately. If the rep cannot identify negative consequences of inaction, the deal will stall.

As McMahon notes, rep answers reveal their actual grasp of the account. Asking “Tell me why they have to buy” (play from 49:11) exposes whether the rep understands client pain, while “Tell me why they have to buy from us” (play from 49:18) proves whether technical differentiators map to those business problems. If the rep cannot answer the timing question, the deal is dead: “Because if they can't explain the negative consequences of not solving the problem now, they truly still don't understand the problem.” (play from 49:31)

When This Works (and When It Doesn't)

This questioning sequence functions best in high-ACV enterprise software deals with complex procurement cycles, multiple stakeholders, and custom contract terms. Operating partners can deploy it during 100-day post-acquisition reviews or pre-LOI commercial diligence to strip phantom opportunities from stated backlog. It immediately exposes whether management has built repeatable sales qualification or is riding a wave of legacy renewals.

The model fails in low-ticket, high-velocity transactional sales where deal volumes prevent line managers from touching individual transactions. In product-led growth models or self-serve software motions, purchasing decisions are driven by credit-card swipes rather than formal decision criteria. Applying deep interrogation to $10,000 annual contract values adds manager friction without improving revenue predictability.

Why It Matters

Private equity software underwriting often assigns aggressive post-close growth targets while assuming existing pipeline quality is sound. McMahon's focus on manager forecast accuracy shows that revenue variance is usually a management failure rather than a rep headcount defect. In an environment where enterprise software multiples leave zero margin for post-close revenue misses, diligence teams that audit frontline qualification uncover true booking velocity months before it shows up in EBITDA.