--- title: Inbound vs. Outbound Leads description: "Struggling with low MQL actuals? Your lead qualification process might be the culprit. Discover how inbound and outbound leads follow different paths—and how using the SPICED framework can help your RevOps team refine lifecycle stages for a more accurate pipeline. Learn the manual and automated strategies to bridge the gap and fix MQL tracking in your CRM." canonical: "https://vasco.app/blog/inbound-vs-outbound-leads" date: "2025-03-15T00:00:00.000Z" author: Sophie Geoffrion jobTitle: "Brand & Content Lead" readingTimeMinutes: 3 contentType: article intent: playbooks-methods pillar: "GTM & RevOps execution" --- # Inbound vs. Outbound Leads _Why Your MQL Count Looks Off—And How to Fix It_ ## Your MQL Count Looks Off—And the CRM Might Be to Blame **Growthly** is a fast-growing SaaS startup that just closed its Series A. With pressure to scale efficiently, their GTM leaders are laser-focused on pipeline health. But there’s a problem. Their MQL count looks **way too low**. The VP of Sales is worried: “If we don’t have enough MQLs, how do we hit our targets?” The Lead Gen Manager is confused: “I have plenty of leads with booked calls, but they’re not showing up as MQLs.” Enter the **RevOps Engineer**. Unlike sales and marketing, they have [**full visibility into how data flows across the bowtie**](/blog/the-bowtie-model). After digging into the CRM, they uncover the issue: Growthly’s definition of an MQL is **too rigid**. Leads are only counted as MQLs **after** their first call—ignoring those who already showed buying intent. The result? An artificially weak pipeline. ## How RevOps Solves the MQL Puzzle Using SPICED ### Let’s Pause for a Minute: What is SPICED? The **SPICED framework** provides a structured approach to lead qualification, ensuring that leads are assessed based on: - **Situation** → What’s their context? (Company size, industry, tech stack) - **Pain** → What’s frustrating them? (Challenges that brought them here) - **Impact** → Why does it matter? (Revenue, cost, or experience impact) - **Critical Event** → Why now? (Trigger forcing action) - **Decision** → How will they choose? (Buying process, decision-makers) For Growthly, **MQLs should meet at least the first two criteria: Situation and Pain.** ![The SPICED framework provides a structured approach to lead qualification, ensuring that leads are assessed based on their situation, their pain, the impact, the critical event and the decision.](https://cdn.sanity.io/images/ys8gstp8/production/83d65c30eb7d1960795ee6e467bd03a87fe5a77e-958x768.png?w=1600&fit=max&auto=format) SPICED helps Growthly refine its lifecycle stages, ensuring that inbound and outbound leads are qualified consistently. By structuring lead data around Situation and Pain, SPICED acts as a framework for better pipeline visibility—essentially serving as one of Growthly’s key sales and marketing alignment tools. P.S. We have a tactical guide on how to implement SPICED directly in your HubSpot. Read [The Smart Guide to Acquisition Lifecycle Stages & CRM Setup here](/blog/lifecycle-stages-and-crm-setup), written by Vasco's very own Head of Sales & CS, Justin Hudon. ### Inbound vs. outbound: same same, but different The key difference between **inbound** and **outbound** leads? **Which SPICED criteria are known at acquisition:** - **Inbound leads** engage with Growthly (e.g., download content, attend webinars). This suggests they **have a Pain (P)**—but their **Situation (S) is unknown**. - **Outbound leads** are proactively sourced based on ICP criteria (industry, size, CRM). Their **Situation (S) is known**, but their **Pain (P) is unclear**. To transition to **MQL**, Growthly must **fill in the missing piece** for each type of lead. ## Bridging the Gap: Manual vs. Automated Lead Qualification **For Small Teams: A Hands-On Approach** When the pipeline is manageable, the GTM team actively fills the gaps: - **Inbound leads** → Research firmographics (LinkedIn, Clearbit, lead forms). - **Outbound leads** → Use personalized outreach or discovery calls to validate pain. - **Once S & P are identified** → Convert to MQL, enroll in nurture, notify sales. **For Scaling Teams: Automating Qualification** As lead volume grows, manual work won’t scale. Larger teams can: - **Enrich inbound leads automatically** (Clearbit, Apollo, 6sense, progressive profiling). - **Detect outbound pain signals** via intent data, engagement scoring, AI-driven outreach. - **Automate lifecycle transitions** in CRM, triggering nurture workflows at MQL. Whether manual or automated, **the goal remains the same**: ensure every MQL meets **both S & P criteria** before moving forward. > **Want more granularity?** In your CRM, leverage **Lead Status** to track how leads interact with your activities—whether inbound or outbound. This helps gauge their engagement level and proximity to becoming an MQL, ensuring a more data-driven qualification process. If you're scaling your automated outreach, try a dedicated partner like [Growth Today](http://www.growthtoday.co/). Their proven tactics and email automations will help you grow your outreach as quickly as your sales team can keep up. ## Wrapping It Up: A Healthier Pipeline The **RevOps Engineer updates the CRM**, and sends a quick Slack update follows in **#gtm-team**: _"Hey team—MQL tracking is now fixed! Inbound leads move forward once we confirm their Situation, outbound leads once we validate their Pain. No more waiting for a call. Your pipeline just got a whole lot more accurate. _🚀_"_ A collective sigh of relief. The VP of Sales sees a healthier pipeline, the Lead Gen Manager gets credit for their work, and the GTM team breathes easier. But in RevOps, optimization is never truly "done"—as Growthly evolves, so will its lifecycle definitions. A well-structured bowtie isn’t static; it adapts to the company’s reality, ensuring that lead qualification always reflects the business’s growth and strategy. ## FAQ ### What is the difference between inbound and outbound leads? Inbound leads come to you through content, webinars, or organic channels, signaling interest or pain. Outbound leads are proactively sourced based on firmographic criteria like industry or company size. ### What is the SPICED framework for lead qualification? SPICED stands for Situation, Pain, Impact, Critical Event, Decision. It helps qualify leads by asking: what’s their context, what problem do they have, why it matters, what triggered them now, and how they’ll decide. For MQLs, teams often require at least Situation and Pain to be known. ### How should inbound leads be qualified? Inbound leads typically show Pain through engagement (downloads, webinars, content views). To qualify them as MQLs, you need to fill in the missing Situation (company size, industry, tech stack) via lead forms, enrichment tools, or light research before moving them to the next stage. ### How should outbound leads be qualified? Outbound leads start with known Situation (ICP fit) but unclear Pain. Qualification means validating their problem through personalized outreach, discovery calls, or intent data. Once both Situation and Pain are confirmed, the lead can transition to MQL and enter nurture or handoff workflows. ### Should inbound and outbound leads follow the same lifecycle? Yes, inbound and outbound leads should follow the same lifecycle stages and definitions. Using a shared SPICED‑based model ensures consistent qualification, so MQLs reflect real buying intent regardless of channel and avoids double‑counting or ghost pipeline. ### Why is lead status important for inbound vs. outbound? Lead status helps track how inbound and outbound leads interact with your activities, showing engagement level and proximity to becoming MQLs. A clear status model makes it easier to spot bottlenecks, adjust messaging, and ensure both channels contribute to an accurate, healthy pipeline. ### How does this apply to a revenue architecture platform like Vasco? A revenue architecture platform like Vasco enforces consistent lifecycle stages, and supports SPICED‑based qualification. It surfaces when Situation or Pain is missing, automates transitions, and gives RevOps a single view of pipeline health across channels.