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.
In the 4+2 Pipeline Thrust Matrix (the 4+2), Revenue Operations is foundation +1. Its job is efficiency: run and optimise the shared machinery (data, stages, routing, attribution and reporting) that every pillar uses.
The four pillars create thrust. The two foundations cut drag. A weak foundation puts friction under every column: dirty data, no shared stage definitions, attribution nobody trusts, response times nobody measures. More media spend cannot fix a leaky pipeline. Fix the drag before you add thrust.
Revenue Operations is written out in full on first mention; RevOps is fine in passing after that.
Role: efficiency, not a fifth pillar
Foundations sit as a band under all four pillars on the master exhibit, not as journey stages. Revenue Operations does not "own demand". It makes every pillar's metric believable:
- Stages defined the same way for marketing and sales.
- Routing that meets an agreed response time.
- Attribution that can be audited.
- Routine tuning of models that already exist.
It is not "the CRM team" in disguise. It is the discipline that shows where pipeline leaks and keeps the engine's instruments honest.
What +1 includes
- Ongoing data hygiene: dedupe, enrichment, key-field completeness.
- Routing rules in run-state and speed-to-lead monitoring.
- Shared stage definitions aligned to the demand waterfall you use.
- Attribution runs and periodic marketing-mix model refresh on an existing design.
- Routine recalibration of an operating scoring model's weights and thresholds (same design).
- Forecast inputs and pipeline traceability reporting.
- Account selection, tiering and intent-data plumbing shared across ABM tiers.
- Audit of the influenced-pipeline rule (90-day buying-group lookback).
What +1 excludes (home rule)
Tie-break questions, in order:
- Does it change what the capability is or can do? Then +2 Revenue Enablement.
- Is it shared plumbing that keeps the engine running across pillars? Then +1.
- Otherwise: the pillar whose outcome it drives.
| Edge case | +1 (run / optimise) | +2 (build / upgrade) | Pillar run-state |
|---|---|---|---|
| Data hygiene and routing | Ongoing dedupe, enrichment, routing rules | New routing design, CRM or data-platform migration | n/a |
| Attribution / MMM | Running reports, periodic model refresh | First MMM, or switching attribution model | n/a |
| Lead scoring | Routine recalibration on the same design | Set-up from scratch or rebuild | 02 operates the live model |
| Stage definitions | Maintain and enforce shared definitions | Redesigning the stage model | Pillars use them |
Confusing +1 and +2 is how tool projects never end and pillars never own outcomes.
Drag role and trust
Trust is the through-line. Sales teams who trust marketing's numbers stop fighting the forecast. Revenue Operations earns that trust by:
- Reporting sourced and influenced pipeline separately (never a single summed figure without the two parts).
- Applying the influenced rule: a marketing touch on a buying-group member within 90 days before opportunity creation or before a stage advance; sales agrees the window; +1 audits.
- Making pipeline traceable to source for as much of the book as practical.
- Surfacing speed-to-lead and data completeness without turning every slide into attribution theatre.
Metrics
| Metric | Why it matters |
|---|---|
| Share of pipeline traceable to source | Instrument health |
| Speed-to-lead (median response time) | Capture depends on it |
| Data completeness on key fields | Buying-group and stage honesty |
| Scoring recalibrated on schedule | Run-state discipline |
| Forecast accuracy (where owned) | Revenue conversation credibility |
These are foundation metrics. They support the North Star; they are not a substitute for sourced and influenced pipeline contribution.
Channels and tools (generic)
Revenue Operations is not a channel pillar. Tools (categories): CRM, marketing automation, CDP or enrichment, BI and dashboards, intent-data pipes, call tracking. Partner data quality for channel motions sits here even when partner plays live in pillars 01–03.
Waterfall and ABM
- Stage definitions and conversion reporting map to +1; the pillars fund the work that moves stages.
- Account selection, tiering and intent data for ABM sit with +1; account plans in use sit in the pillar served; new ABM programme design sits in +2.
Failure modes
- RevOps as eternal project office. Builds never hand to +2 with an end date, or never hand run-state to pillars.
- Influenced pipeline without a rule. Trust dies; finance rejects the North Star.
- Scoring "owned" by RevOps forever. The live model belongs in Capture; +1 only recalibrates.
- Perfect data as a precondition for planning. You do not need a perfect warehouse to see empty cells: you need sales in the room and honesty. Baseline what you can; improve completeness in parallel.
- Reporting vanity as results. Clicks and MQLs are inputs; +1 should not baptise them as contribution.
Short worked example (illustrative)
Only part of pipeline can be traced to source. Enquiry response times are unknown. Scoring weights have not been touched in a year.
+1 initiatives: data-completeness sprint on buying-group role fields; publish weekly speed-to-lead; schedule quarterly scoring recalibration with Capture as the operating owner.
Not +1: a CRM migration (that is +2); rebuilding scoring with new features (+2); running the live scoring decisions day to day (02).
Outcome to show: higher share of pipeline traceable to source; known median response time; recalibration dates on the portfolio page under the foundation band.
What to do next
- Score foundation drag with sales: traceability, speed-to-lead, stage clarity, influenced-rule audit.
- Separate +1 run work from +2 builds on the portfolio page.
- Write the influenced-pipeline rule down; get sales to sign the 90-day window.
- Hand live scoring ownership to Capture if it still sits in a perpetual RevOps project.
- Fix the worst drag cell before approving more Capture or Creation spend.
Revenue Operations cuts drag by making the engine measurable and trustworthy. Efficiency is not bureaucracy, it is how thrust stops leaking.
Line of sight for the foundation
Revenue Operations does not set the enterprise goal. It makes the cascade measurable. Without shared stages, a clean-enough CRM and an auditable influenced rule, marketing's North Star will not survive a finance review, and sales will not sit through another dashboard defence.
Start with the minimum that supports honesty: stage definitions, source fields, buying-group role fields, response-time measurement, and the written 90-day influenced rule. Improve completeness in parallel with planning. Perfect data is not a gate on diagnose-and-select.
Operating rhythm
Monthly: foundation band on the portfolio page: traceability %, median speed-to-lead, overdue recalibrations, open audit issues on influenced credits.
Quarterly: decide which drag fixes are +1 run work versus +2 builds. Migrate nothing under the guise of "hygiene".
Practical checklist
- Shared stage definitions published.
- Sourced and influenced reported separately.
- 90-day buying-group lookback signed by sales.
- Scoring recalibration calendar (live model owned by Capture).
- Speed-to-lead SLA monitored.
- Partner and channel data quality owned.
- No vanity metrics promoted to "contribution".
Initiative catalogue (illustrative)
| # | Initiative | What it is | Home | Lead metric | Typical channel / tool |
|---|---|---|---|---|---|
| 1 | Source-field completeness sprint | Make pipeline traceable to source across sectors | +1 | Share of pipeline traceable to source | CRM + BI |
| 2 | Speed-to-lead monitoring | Publish median response time vs SLA | +1 | Speed-to-lead | CRM routing, telephony |
| 3 | Shared stage definitions | Marketing and sales use one waterfall-aligned stage model | +1 | Consistent stage use; forecast inputs | CRM admin |
| 4 | Influenced-pipeline audit | Enforce 90-day buying-group lookback | +1 | Audit pass rate; sourced/influenced split integrity | CRM + MAP |
| 5 | Routine scoring recalibration | Weights on existing Capture scoring design | +1 | Recalibrated on schedule | CRM/MAP |
| 6 | Intent-data and account-tier plumbing | Shared ABM selection data across motions | +1 | Tier coverage; data completeness | Intent + CDP/CRM |
| 7 | Partner lead-data quality | Clean partner-sourced records for industrial/channel motions | +1 | Completeness on partner fields | Partner portal + CRM |
| 8 | Healthcare buying-group field standard | Role fields for clinical/procurement/finance on opportunities | +1 | Data completeness on role fields | CRM |
| 9 | Attribution report runs (existing model) | Periodic runs of an existing attribution/MMM design | +1 | Reports on schedule | BI / MMM tooling |
| 10 | Banking opportunity hygiene | Mandatory fields for regulated-deal stages | +1 | Completeness; traceability | CRM |
| 11 | CRM / data-platform migration | Changes what the engine can do | +2 | Migration shipped; adoption 90 days | Project |
| 12 | First MMM or attribution-model switch | New model design | +2 | Build shipped; lift vs baseline after handover to +1 runs | Analytics project |
Diagnostic questions (where we stand)
- What share of pipeline is traceable to source today?
- Is median speed-to-lead known for priority enquiries?
- Do marketing and sales use the same stage definitions?
- Is the 90-day influenced rule written, sales-signed and audited?
- Is live scoring owned by Capture, with +1 only recalibrating?
- Are tool migrations mislabelled as "hygiene"?
- Can partner and multi-sector data meet the same completeness bar?
- Are vanity metrics still presented as contribution in revenue meetings?
Acceptance questions (bar for a +1 initiative)
- Is this shared plumbing that keeps the engine running across pillars (not a pillar outcome play)?
- Does it run or optimise an existing design: not change what the capability is?
- Is there a foundation metric (traceability, speed-to-lead, completeness, recalibration on schedule)?
- If it changes design or is a first-time build, has it been moved to +2?
- Does it support sourced/influenced honesty rather than attribution theatre?
- Is there an owner in RevOps (or equivalent) and a review cadence on the portfolio foundation band?
Sources
- Patel, P. (2026). The 4+2 Pipeline Thrust Matrix. https://prinkit.com/white-paper/4-plus-2-pipeline-thrust-matrix
- Lillian, J. (17 May 2017). SiriusDecisions Demand Unit Waterfall. https://www.forrester.com/blogs/meetthenewestsiriusdecisionsdemandwaterfall/
- Forrester (4 May 2021). B2B Revenue Waterfall. https://www.forrester.com/press-newsroom/forrester-debuts-next-generation-b2b-revenue-waterfall-to-help-firms-accelerate-revenue-growth/