Customer story · Attribution & Lead Lifecycle

Two scoring models were running at once — and good-fit leads were the casualty

A PE-backed financial-services platform had two lead-scoring models running in parallel, and the fit component was subtracting points from leads that should have been prioritised. LeanScale consolidated them into a single dual-score model and shipped an interim fix that put blocked leads back in front of a rep.

ProofWhat happened on a real engagement.
Fintech & Financial ServicesSector
Enterprise / PE-backedStage
6–12 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

Two lead-scoring models were running at the same time — a general model and a campaign-specific one — with no single answer to what a good lead was. The fit component could subtract points, which meant genuinely good-fit, highly engaged leads scored below the routing threshold and never reached a rep's queue at all. A lean two-person marketing and revenue-operations team was under board pressure to grow pipeline and could not defend a number it did not control.

#The approach

One model carrying two visible scores

Consolidated the two competing models into a single system with two separately visible scores — engagement and ICP fit — so a lead's behaviour and its fit stay legible on their own instead of collapsing into one opaque number nobody trusts.

An interim fix that unblocked the queue immediately

Shipped an interim change so the fit component can only add points, never subtract, releasing good-fit, high-engagement leads into the rep queue while the full model was still being built — value in week one rather than at go-live.

Predictive scoring folded into the design

Added the platform's native predictive scoring into the model design rather than running it as a competing signal on the side.

One documented source of truth

Documented the scoring model on a single live enablement site so sales and marketing argue from the same definition instead of two different decks.

A reactivation model for the 'not ready' pile

Built a 90/180-day reactivation model for leads marked not-ready, with a short reactivation sequence, so disqualified leads get systematically re-touched instead of ageing out of the database.

#Outcomes

Two models became one

The general and campaign-specific scoring flows were collapsed into a single dual-score engagement plus ICP-fit model, documented on one live enablement site as the source of truth.

A blocked lead became a booked meeting

Immediately after the fit-score fix, a previously blocked good-fit lead surfaced in the rep queue, was called, and converted to a booked meeting the team said would not otherwise have been made.

In their words

What the customer said

“I have to say they did so much and they did not notify us that so many things got across the finish lines. So this was really exciting. So thank you for sure.”
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.

Tools
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