All posts
L4 Maturityinbound 7 min read

Lead Scoring v2: Integrating First-Party Data & LLM Features (L4)

Move beyond rule-based lead scoring. Learn how to use LLMs, product usage data, and first-party intent to double your MQL-to-SQL conversion rates.

Run the playbook

Lead scoring v2 with first-party + LLM features (L4)

Replace the rule-based score with a model that uses product usage, intent, and LLM-derived fit-from-website features.

Why this matters

The "MQL" is a broken concept in most B2B organizations. When sales teams complain that "marketing leads suck," they are usually right. Traditional rule-based scoring—where a lead gets 10 points for a whitepaper download and 5 points for being in the "Software" industry—is too blunt for the modern $10M-$500M ARR company.

The cost of sticking with "v1" rule-based scoring is hidden but catastrophic:

  1. SDR Burnout: Reps waste 40% of their day disqualifying "Fortune 500" leads that are actually low-intent researchers.
  2. Slow Lead Velocity: High-intent leads from mid-market companies sit in queues because they didn't meet an arbitrary "company size" threshold.
  3. Low MQL→SQL Rates: Most companies see a dismal 10-15% conversion rate here. By moving to a hybrid LLM-derived model, you should expect to see this jump to 35% or higher within the first two quarters.

Level 4 scoring isn't just about math; it's about using LLMs to "read" a company's website and job boards the way a human would, then combining that "Fit" with real-time "Intent" (product usage and pricing page visits).

How it works

Step 1: Aggregate historical conversion data

You cannot predict the future without a clean map of the past. Export 18–24 months of data from Salesforce or HubSpot. You need a binary outcome: Did this lead become an Opportunity (Is_SQL = 1) or not (0)?

  • The Technical Shift: Use a connector like Coefficient to sync your CRM to a spreadsheet or push it into Snowflake.
  • The Catalyst: Join this data with product usage from Mixpanel or Amplitude. If a lead converted, how many team members did they invite during their trial? If they didn't, did they ever hit your "Aha" moment?
  • Time Commitment: 4–6 hours of cleaning. Don't skip the "Source" flag; "Trial" lead behavior is a different species than "Webinar" lead behavior.

Step 2: Engineer LLM-derived fit features

Standard CRM "Industry" fields are garbage. "Digital Marketing" could mean a 2-person agency or a $500M SaaS platform.

Replace these with LLM-derived features using Clay or Browse.ai. For every lead domain, use a GPT-4o prompt to extract non-obvious signals.

  • Prompt Example: "Analyze this company's homepage. Are they hiring for AI roles? Do they mention SOC2 compliance? Do they target Enterprise or SMB personas?"
  • The Value: Now, instead of just "Industry: Software," your model knows "Fit: Enterprise-ready, AI-native, Targeting HR personas." This enrichment typically costs less than $0.05 per lead using the OpenAI API—a fraction of the cost of a wasted SDR call.

Step 3: Build the hybrid scoring model

This is where you merge the "Fit" (from Clay/LLMs) with "Intent" (from your website) and "Usage" (from your product).

You can build a logistic regression in a Jupyter Notebook or use a dedicated platform like MadKudu or Mutiny. Aim for a weighted formula:

  • 40% LLM Fit Score (e.g., Value prop match)
  • 40% Product Usage (e.g., Invited 5+ users)
  • 20% Website Intent (e.g., 3+ visits to the pricing page)

The Goal: Your top 10% of scored leads should account for at least 60% of your historical conversions.

Step 4: Calibrate thresholds with Sales

Sales will reject a "black box" score. Conduct a "Blind Taste Test." Show your SDR Manager 20 leads—10 high-score, 10 low-score—without showing the numbers. Ask them which they'd call first.

If they pick a low-score lead because "They are hiring a VP of Sales," go back to Step 2 and add "Hiring for Sales Leadership" as an LLM-derived signal. This workshop aligns the team and ensures the threshold for "MQL" is high enough that reps actually get excited about them.

Step 5: Deploy to CRM and trigger routing

Push the Predictive_Score_v2 back to Salesforce/HubSpot. Use Zapier or Make to automate routing.

Crucial Step: Don't just show a number. In a custom CRM field, display the "Why." Use the LLM to summarize: "High Fit: Hiring 5+ AI Engineers; Recent SOC2 announcement; 3 Pricing page visits in 24hrs." When Sales sees the logic, adoption skyrockets.

Step 6: Quarterly audit and re-calibration

Models "drift" as markets change. Every 90 days, run a Precision/Recall report.

  • Precision: What % of our "High Score" leads actually converted?
  • Recall: What % of our total wins did we miss with the model?

Tools you need

  • Enrichment/LLM: Clay (essential for GTM enrichment), Browse.ai, OpenAI GPT-4o API.
  • Data/Analytics: Snowflake/BigQuery, Mixpanel/Amplitude, Coefficient.
  • Scoring Engines: MadKudu (for L4 sophistication) or Mutiny.
  • Execution/CRM: Salesforce/HubSpot, Zapier.

KPIs to track

  • MQL→SQL Conversion Rate: Target a >100% improvement over rule-based scoring.
  • Lead-to-Opp Velocity: How many days from first touch to Opportunity Created?
  • SDR Productivity: Meetings booked per 100 leads called.

Common pitfalls

  • API Cost/Rate Limits: Don't run your entire 50,000-lead database through GPT-4o at once. Start with a 500-lead sample to refine the prompt.
  • Over-weighting "Fit": A VP at a Fortune 500 company (High Fit) who hasn't visited your site in 3 years is a cold lead. Never let Fit override Intent.

When to graduate to the next level

Once your hybrid scoring is consistently delivering a 35%+ MQL→SQL rate, move to Level 5: Autonomous GTM. This involves using Lindy or Claude Code to not just score the lead, but to automatically draft and send hyper-personalized outbound sequences based on the LLM-derived reasons why that lead is a high fit.

scoringmlrevops

Ready to ship it? Open the playbook

Lead scoring v2 with first-party + LLM features (L4)

Step-by-step instructions, the tools to use, and the KPIs to watch — already wired into the Revenue AI Strategy workspace.

Open playbook