Part of the 4+2 Pipeline Thrust Matrix (formerly the 4+2 Growth Matrix). The canonical source is the white paper; the name change is explained in why the name moved.
"Where does lead scoring live?" is a common question around revenue frameworks, and one of the most muddled in practice. In the 4+2 Pipeline Thrust Matrix (the 4+2), scoring is not a fifth pillar and not a permanent Enablement programme. It has three homes, depending on whether you are running it, tuning it or rebuilding it.
Get the home wrong and two things happen. Tool projects never end. Capture never owns the conversion rate sales will trust.
The short answer
| State of the work | Home in the 4+2 |
|---|---|
| Operating lead-scoring model (live, used to prioritise demand) | 02 Demand Capture |
| Routine recalibration of weights and thresholds on the same design | +1 Revenue Operations |
| Set-up from scratch, or a rebuild with new data, features or model type | +2 Revenue Enablement (until handover) |
That table is the entire rule. Everything below unpacks why it exists and how to apply it without reinventing your stack.
Why Capture owns the live model
Demand Capture's job is to turn in-market intent into qualified opportunities under a definition marketing and sales share. An operating scoring model is a Capture capability because its main job is to identify and prioritise that demand.
If the live model sits in a "RevOps / marketing ops" backlog forever, Capture's KPI (qualified opportunities, scored-lead-to-opportunity rate) has no owner who can change the motion. If it sits in a sales-enablement content library, nobody owns the conversion maths. Home it in 02 once it is live.
MQLs remain inputs. The North Star for the 4+2 is marketing-sourced plus marketing-influenced pipeline, reported separately. Scoring exists to improve the path into sourced opportunity quality, not to inflate a vanity lead count.
Why +1 owns routine recalibration
+1 Revenue Operations runs shared machinery efficiently: data hygiene, stage definitions, routing, attribution and reporting. Recalibrating weights and thresholds on an agreed design is routine tuning, not a new product.
Examples that belong in +1:
- Adjusting score thresholds after a quarterly review with sales
- Refreshing firmographic weights when ICP definitions are clarified
- Fixing data-quality rules that feed the same model
- Auditing whether scored leads meet the qualified-opportunity definition
These keep the instruments honest. They are not a licence to redesign the model under the label "optimisation".
Why +2 owns builds and rebuilds
+2 Revenue Enablement is effectiveness: build or upgrade capability, usually with an end date. First scoring design, first predictive model, or a rebuild that changes features, data sources or model type is a +2 initiative.
While the build runs:
- Name an owner and a handover date
- Agree acceptance criteria with Capture and sales (what "good enough to run" means)
- Plan the run-state home in advance: almost always 02 Demand Capture for the live model; +1 for ongoing data and threshold hygiene on that design
Builds that never hand over create drag under every pillar. More Capture spend on top of an unfinished scoring programme is thrust piled onto drag.
Tie-break questions (in order)
When a ticket is labelled "scoring" and three teams claim it, use the 4+2 tie-breaks:
- Does it change what the capability is or can do (new design, new features, new model type)? Then +2.
- Is it shared plumbing that keeps the engine running across pillars (data, routing, reporting)? Then +1.
- Otherwise, the pillar whose outcome it drives: for live prioritisation of in-market demand, that is 02 Demand Capture.
Open-opportunity consensus work is 03 Pipeline Acceleration, not scoring. Expansion and renewal motions on converted accounts sit in 04 Retention & Expansion. Do not stretch "lead scoring" to cover every ranking problem in the CRM.
Failure modes
- Scoring as eternal transformation. No end date, no Capture owner, dashboard theatre.
- MQL target without a shared opportunity definition. Scoring optimises the wrong output.
- Rebuild labelled as recalibration. Quiet design changes with no Enablement home and no acceptance test.
- Ops owns the model; marketing owns the spend. Capture cannot improve scored-lead-to-opportunity rate.
- No sales signature on the qualified-opportunity rule. Scoring becomes a marketing monologue.
How this links to foundations cutting drag
Weak scoring is a classic drag story. Capture cannot create trustworthy thrust (qualified opportunities) if the ranking layer is unowned or unauditable. Revenue Operations shows where the leak is. Revenue Enablement removes doubt by shipping a better capability, then getting out of the way.
Trust reduces friction: sales trusts a score when the definition, the data and the owner are visible. That is foundation work serving a Capture outcome, not a reason to invent a sixth pillar called "Scoring".
What to do next
- Write down which of the three states your current scoring work is in.
- If it is a build, put it on +2 with an end date and Capture as the run-state owner.
- If it is live, move operational ownership language to Demand Capture and keep +1 on data and threshold hygiene.
- Agree the qualified-opportunity definition with sales before the next model change.
For foundation detail, see Revenue Operations and Revenue Enablement. For Capture metrics, see Demand Capture. The FAQ restates the same home rule in short form.
Sources: home rules and scoring placement from Patel, 4+2 Pipeline Thrust Matrix white paper v1.0 and canon home rules (prinkit.com). No vendor benchmarks or lift percentages claimed.