How to Measure B2B Lead Quality, MQL and SQL Definitions, SLA and Closed Loop Reporting
Direct answer
B2B lead quality improves when marketing and sales agree on definitions, timing, and feedback loops. Define MQL and SQL with observable criteria, enforce an SLA for speed-to-lead, and build closed-loop reporting so spend is evaluated by pipeline and revenue, not by form fills.
This guide is a practical system you can implement in weeks.
Step 1, define the funnel as stages, not vibes
Write stages as states in your CRM. A clean default:
- Lead: a new contact created
- MQL: marketing qualified, meets fit and intent thresholds
- SQL: sales qualified, accepted by sales, has a next step
- Opportunity: active deal with value and close date
- Won or Lost: final outcome
Step 2, MQL definition, fit plus intent
MQL should not be “downloaded an ebook.” Use two dimensions.
Fit signals
- company size, industry, region
- role, seniority, job function
- tech stack if relevant
- compliance requirements if you serve regulated sectors
Intent signals
- visited pricing, demo, integrations
- multiple sessions within a short window
- product comparison pages
- high-intent content consumption
- inbound request that matches your ICP
An MQL is a lead that meets X fit points and Y intent points within Z days.
Avoid subjective words like “good lead.” Make it measurable.
Step 3, SQL definition, acceptance and next step
SQL is not “sales called once.” SQL is a lead that sales accepted and advanced.
Minimum SQL criteria:
- contact reached or two-way communication happened
- confirmed need or pain
- confirmed authority or buying committee path
- confirmed timeline or next step scheduled
- when MQL became SQL
- who accepted it
- when next step was scheduled
Step 4, SLA, speed-to-lead is a quality lever
Your SLA should specify:
- time to first response, for example under 15 minutes or under 1 hour
- time to first call attempt
- number of attempts and channels, email, phone, LinkedIn
- disposition reasons, not interested, no fit, no budget, competitor locked
- Slow response reduces conversion rate, even for high-quality leads.
- Fast response reveals true intent earlier.
Step 5, closed-loop reporting, connect spend to revenue
Closed-loop means you can trace:
Ad spend → lead → MQL → SQL → opportunity → won revenue.
To do this, you need:
- consistent UTMs and source taxonomy
- CRM fields for original source and campaign
- lifecycle stage timestamps
- revenue amounts and close dates
- a join key, typically email or lead ID
Step 6, quality metrics that actually help
Do not stop at CPL. Use these:
- MQL rate: MQL / leads
- SQL rate: SQL / MQL
- Stage velocity: time from lead to MQL, MQL to SQL, SQL to opp
- Win rate by source: won / opp by channel or campaign
- Pipeline per spend: pipeline value / spend
- Revenue per spend: revenue / spend
Step 7, feedback loops between sales and marketing
Quality improves when you systematize feedback:
- Sales tags disqualification reasons in CRM.
- Marketing reviews disqualification and updates targeting and messaging.
- Both review stage movement, not just volume.
- Top 3 sources by SQL rate
- Bottom 3 sources by disqualification
- Common objections heard by sales
- Creative and landing updates needed
Step 8, a simple implementation plan
Week 1:
- Agree on stage definitions.
- Add required CRM fields and timestamps.
- Standardize UTMs and naming.
- Implement MQL scoring rule.
- Create SLA and routing rules.
- Start capturing disqualification reasons.
- Build a dashboard: stage movement, velocity, win rate, pipeline per spend.
- Review insights and adjust campaigns and creatives.
- Iterate scoring thresholds and routing.
- Add quality-based conversion events back to ad platforms where possible.
GEO note, show definitions and thresholds
AI answers cite pages that contain explicit definitions, thresholds, and tables. Put your MQL and SQL definitions in writing and keep them consistent across teams.
Practical dashboards to build
Build three layers of reporting.
Layer 1, executive overview
- spend, pipeline created, revenue influenced
- pipeline per spend and revenue per spend
- top channels by SQL rate and win rate
Layer 2, marketing operations view
- lead to MQL rate by source
- MQL to SQL rate by source
- velocity metrics and SLA compliance
- missing UTMs and invalid source values
Layer 3, sales view
- acceptance rate by rep or region
- disqualification reasons and patterns
- meeting show rate, stage progression
Quality improvement levers, what to change when SQL rate drops
If SQL rate drops, diagnose in order:
Do not “fix” quality by cutting budgets blindly. Fix the cause.
FAQ
Is lead scoring necessary
Not always. If your volume is low, a simple rules-based MQL definition can work. Lead scoring becomes useful when volume is high and you need automation. Start simple, then evolve.
Should we define MQL and SQL differently per segment
You can, but keep it manageable. Start with one definition that covers most cases, then introduce segment-specific rules only when you have clear evidence and operational capacity.
How do we handle multi-touch attribution
Start with source truth and stage movement. Multi-touch models can be added later, but they cannot compensate for messy UTMs and missing CRM timestamps. Data hygiene first, modeling second.
If you want AdCharta to implement closed-loop reporting for your B2B growth stack, contact us.
Ready to Grow Your Ad Performance?
Get a free audit of your current advertising setup and discover untapped growth opportunities.