Customer story · Attribution & Lead Lifecycle

Deciding which system owns the MQL — and making the number defensible

A marketing-technology company could not stand behind its MQL, lead-source or attribution numbers. LeanScale gave one system clear ownership of the MQL, reconciled the count record by record, and rebuilt lead source, attribution and inbound routing around that decision.

ProofWhat happened on a real engagement.
Marketing & Sales TechnologySector
Growth-stageStage
3–6 monthsDuration
2Min read

Anonymized. The company is described by sector and stage only — no customer is named, and quotes are attributed by role.

#The challenge

Marketing and sales could not stand behind their MQL, hand-raiser, lead-source or attribution numbers. Return-to-marketing automation was overriding MQL status, the marketing automation platform and the CRM disagreed about which of them owned scoring, and the same dashboard could swing from under 200 MQLs to around 1,700 depending on how a filter was set. Lead source was flat-tagged, so whole channels disappeared into a generic bucket, and hand-raiser reporting sat on a live checkbox that automation kept clearing. Leadership needed one reconcilable spine it could report on all the way up.

#The approach

Deciding who owns the MQL

Made the marketing automation platform the sole owner of MQL, lead score and the hand-raiser flag, and reduced the CRM to reacting — stamping MQL dates, routing, and returning cold records to nurture. Deactivated the conflicting return-to-marketing movers so only the intended Gong-triggered flow survives.

Reconciling the count

Root-caused the dashboard swing to a counting-method problem rather than a data problem, then reconciled the CRM to the marketing platform one-to-one at the record level for a full quarter, so the number is defensible before anyone reports on it.

Lead source and first/last-touch rebuild

Rebuilt third-party-sourced lead attribution to route by the record owner's role instead of flat-tagging everything as prospecting, standardized the UTM-channel-to-lead-source mapping, restored BDR as its own lead source, and backfilled historical records so first- and last-touch land together.

Hand-raiser reporting that survives automation

Rebuilt hand-raiser reporting on the hand-raise event date — which survives return-to-marketing — instead of a live checkbox, and corrected the marketing performance dashboard so hand-raisers stop under-counting.

Inbound routing rebuild

Rebuilt inbound lead distribution: an even round-robin across the small domestic BDR team that also absorbs location-unknown leads, a separate path for known international leads, and 180-day activity-based stickiness so a returning lead goes back to whoever worked it — deployed to production with monitoring dashboards.

#Outcomes

A lead count marketing reports on

By mid-engagement the marketing owner described the lead count as reliable and accurate, and was using it to report upward to leadership.

MQLs reconciled one-to-one

The CRM and the marketing automation platform were reconciled to tie one-to-one at the record level across a full quarter of MQLs, making the count defensible.

Routing live with monitoring

The rebuilt inbound routing went to production with monitoring dashboards confirming it holds as built, with no routing errors observed.

Hand-raisers reconciled

Hand-raisers for the quarter reconciled to roughly three dozen and now report on an event-date basis that survives return-to-marketing automation.

Embedded delivery

A seven-person team worked the review window, spanning marketing operations and revenue operations.

In their words

What the customer said

“we kind of finally have it where, at least on the [marketing platform] side, we have our lead count. Like, any leads we capture, like, that number is reliable, and I feel like it's accurate.”
“We trust you. We appreciate all you're doing to make this happen. Thank you so much.”
The method behind it

This ran the Attribution playbook

The delivery standard this engagement followed.

Connected

In the knowledge graph

Every entity below has its own page, aggregating what we measured, what we recommend and what guests said.

Related

More on these topics

Method Revenue Systems

Attribution

Every Attribution project moves through the same four phases. Know what you produce in each — and know that, like CPQ, this is a project you win or lo…

32 sections · 20 min read
Method GTM Structure

Lead Routing

Every Lead Routing project moves through the same four phases. Know what you produce in each one. 1 Blueprint Pick the routing model, map the channels…

40 sections · 18 min read
Proof Attribution & Lead Lifecycle

Replacing weekly manual dashboard clean-up with nightly correction flows

A cybersecurity company's marketing-ops team was hand-correcting lead tier and channel values every week to keep dashboards defensible. LeanScale repl…

3 sections · 2 min read
Proof Attribution & Lead Lifecycle

Scoring intent when nobody fills out a form: a behavioral MQL model and the attribution layer under it

A B2B software company sells into a small, finite target list where form fills are far too rare to qualify on. LeanScale built a capped behavioral sco…

3 sections · 7 min read
Proof Attribution & Lead Lifecycle

When a picklist rename silently broke a dozen pipeline reports

A B2B software company could not reconcile what its BDR team generated with what its dashboards showed. LeanScale rebuilt inbound and outbound attribu…

3 sections · 2 min read
Proof Attribution & Lead Lifecycle

Closing the gap between MQL and pipeline

A growth-stage workforce-technology company was losing inbound leads and event contacts between MQL and pipeline, with attribution that did not agree …

3 sections · 2 min read