Inbound Leak vs. ABM Bet
Elena runs demand generation at a cybersecurity vendor selling to enterprises with 5,000+ employees. The company gets 300 MQLs per month. Historically 18% become SQLs, 4% become opportunities, and average deal size is $80k. The SDR team has three reps, each capable of 60 dials per day, but they also own inbound follow-up; 40% of MQLs are not touched within 48 hours, and the current SLA is 24 hours on paper but unenforced. Meanwhile, a 50-account ABM pilot produced 12 meetings, 5 opportunities, and 2 closed-won deals worth $220k in three months. Marketing wants to “go all-in on ABM.” Sales wants more inbound coverage. Elena has no extra headcount and must decide next quarter’s mix.
1. Where is pipeline leaking, and what does the ABM pilot actually prove?
Read the worked answer
Inbound math: 300 MQLs × 18% SQL = 54 SQLs; × 4% opportunity = 12 opportunities; at $80k that is $960k of potential pipeline per month before win rate. But 40% of MQLs are untouched within 48 hours, so the realized conversion is lower than the historical rate. Speed-to-lead is a likely leak: 120 MQLs per month are delayed, and response time strongly affects connect rates. ABM math: 50 accounts produced 12 meetings (24% of accounts), 5 opportunities (10% of accounts), and 2 wins worth $220k. That proves account selection and coordinated touches can work, but 50 accounts and 2 wins is a small sample. It does not prove ABM scales or that inbound is dead. The right conclusion is to fix a known, measurable inbound leak while protecting a focused ABM motion for accounts that match the pilot profile.
2. How should Elena allocate the three SDRs and set SLAs?
Read the worked answer
Split coverage by motion. Assign two SDRs primarily to inbound with a 15-minute SLA for enterprise-fit MQLs during business hours and a two-hour SLA for others. Assign one SDR to the 50 ABM accounts plus 20 lookalikes. Rotate one inbound SDR into ABM each quarter for coverage. Inbound SDRs should not chase every MQL: use HubSpot scoring and firmographic fit to route 5,000+ employee accounts to the enterprise pod and disqualify students, consultants, and small businesses quickly. Enforce SLA in the CRM with timestamps and a daily exception report. Give the ABM SDR a multi-threaded play with three contacts per account, LinkedIn, email, and calls. Tradeoff: inbound response should improve, but ABM coverage stays narrow; that is acceptable if the pilot metrics hold. The point is to stop unmeasured leakage before declaring a channel strategy.
3. What metrics and decision rules should determine whether to expand ABM next quarter?
Read the worked answer
Measure pipeline per 100 targeted accounts, meeting-to-opportunity rate, opportunity-to-win rate, and sales cycle for ABM versus inbound. Inbound baseline is 12 opportunities per 300 MQLs and $960k pipeline, adjusted downward for the 40% leakage. ABM baseline is 5 opportunities from 50 accounts, or 10 per 100 accounts, and $400k pipeline. ABM looks stronger per account, but the sample is small. Decision rule: expand ABM only if the next 50 accounts produce at least 8 opportunities and at least 2 wins, and if inbound SLA compliance reaches 90% without adding headcount. If ABM opportunity rate falls below 6% or inbound response time worsens, rebalance back to inbound. Do not judge ABM on meetings alone; meetings are an input, while pipeline and win rate are the outputs.