Lanzilli fixes MQL-to-SQL handoffs

Lawrence Lanzilli used a pair of May 20 X posts to argue that many pipeline failures begin at the handoff between marketing and sales, not inside late-stage sales execution. Lanzilli said broken MQL-to-SQL transitions, weak lead scoring and unclear service-level agreements can leave qualified demand sitting untouched while teams blame close rates or rep performance. A separate May 20 X video from Shamus McNutt made a related point, saying pipeline should be treated as a forecast rather than a to-do list. Together, the posts sketched a tighter operating model for revenue teams: stricter qualification, cleaner CRM stages and shared accountability across marketing and sales. ### Where does Lanzilli say pipeline usually breaks? Lawrence Lanzilli said the damage often happens when a marketing qualified lead reaches sales without a clear definition of readiness, ownership or follow-up timing. In his May 20 post, he pointed to strict lead scoring, SDR-to-AE service-level agreements and shared dashboards as the controls that keep leads from disappearing between teams. That framing shifts attention from rep execution to process design. (crunchbase.com) The argument is that sales cannot reliably convert pipeline if the entry point is inconsistent, disputed or poorly routed, according to Lanzilli’s post cited in the source briefing. ### What did he put in the “Unified Revenue Engine” playbook? A second May 20 post from Lanzilli laid out what he called a Unified Revenue Engine, with common targets and operating rules across go-to-market teams. The playbook included net revenue retention above 120%, pipeline coverage of three to four times quota, standardized CRM stages and AI-assisted deal scoring, according to the source briefing. Those metrics place retention, pipeline sufficiency and stage discipline inside one system rather than separate dashboards. Lanzilli also tied the model to pipeline inspection, suggesting that AI tools should be used to score deals and review forecast quality, not just generate activity, according to the same post summarized in the briefing. ### Why do CRM stages matter so much in this setup? Shamus McNutt said in his May 20 video that teams should treat pipeline as forecast, which requires a clean CRM to separate likely revenue from wishful thinking. That point aligns with Lanzilli’s emphasis on standardized stages, because forecast math depends on deals moving through consistent definitions. Clean stages also create a shared language between marketing and sales. If one team measures handoff quality while the other measures only late-stage conversion, the system can hide where leads are actually being lost, according to the logic in Lanzilli’s posts. ### What changes for marketing and sales teams? Shared dashboards are central to Lanzilli’s prescription because they make both teams answerable for the same movement from MQL to SQL and from SQL to pipeline. Strict scoring defines when a lead is ready, while SDR and account executive SLAs define how fast someone must act once the lead is handed over. That reduces the room for disputes over lead quality. It also turns pipeline reviews into an operational check on routing, qualification and stage hygiene rather than a backward-looking debate over whether sellers worked hard enough. ### Who is Lanzilli? Lawrence Lanzilli is chief revenue officer at DOOR3, according to his Crunchbase profile. The profile says he oversees sales and marketing and has focused on lead generation and AI-supported revenue programs at the New York technology consultancy. The posts remain available on X under Lanzilli’s account, and McNutt’s May 20 video remains on X under his account. Those posts are the next public source for any follow-up detail on the lead-scoring rules, SLA design and CRM stage definitions each operator chooses to adopt. (crunchbase.com)