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.
Teams talk about "more pipeline" as if volume alone were the problem. In the 4+2 Pipeline Thrust Matrix (the 4+2), two forces sit on the same engine: thrust and drag. Four pillars create thrust. Two foundations cut drag. Trust reduces friction. The operating rule is blunt: fix the drag before you add more thrust.
This page stays inside the metaphor and the home rules. It does not invent physics equations, employer case studies or unpublished benchmarks.
What "thrust" means here
Thrust is a noun for the forward push initiatives give pipeline: adding volume, speeding deals and keeping customers. It is not a verb. You do not "thrust revenue". You fund work that creates thrust.
In the 4+2, thrust comes from the four pillars:
| Pillar | Thrust it creates |
|---|---|
| 01 Demand Creation | Future volume: preference among buyers who are not shopping yet |
| 02 Demand Capture | Volume now: qualified opportunities sales will own |
| 03 Pipeline Acceleration | Speed: consensus and proof so open deals stall less |
| 04 Retention & Expansion | Continuity: renewals and expansion that keep the engine running; proof that feeds Creation |
Everyday shorthand after the first full mention is "the 4+2".
What "drag" means here
Drag is friction that slows or leaks pipeline. Typical sources:
- Dirty CRM data and incomplete buying-group fields
- No shared definition of a qualified opportunity
- Slow routing and missed response SLAs
- Attribution nobody trusts in a revenue meeting
- Missing playbooks, proof or skills when a deal needs them
- Weak handovers between motions (signal lost; cutting that friction is foundation work)
Drag is not "sales being difficult". It is structural friction under every pillar. More media spend cannot fix a leaky pipeline.
Why two foundations, not more pillars
The 4+2 puts drag-cutting work in a band under all four pillars, not as fifth and sixth journey stages.
- +1 Revenue Operations is efficiency: run and optimise shared machinery (data, stages, routing, attribution and reporting).
- +2 Revenue Enablement is effectiveness: find where the engine can improve, then build or upgrade capabilities (systems, models, proof, playbooks and skills), usually with an end date. Once live, run-state hands over to the pillar it serves, or to +1 if it is shared plumbing.
That split stops two common failures. First, treating RevOps as "the CRM team" with no link to pipeline leakage. Second, parking every tool project in an endless "enablement" backlog that never hands over.
Fix drag before adding thrust
The manifesto line is practical, not motivational. If stages disagree, scoring is untrusted, or response times are invisible, Capture spend buys form fills sales will ignore. If Acceleration has no consensus packs, more sourced opportunities simply lengthen the queue. If renewals have no owners, new-logo Capture papers over a leaking base.
A useful quarterly question, with sales in the room: where does pipeline leak, and is the leak thrust (empty pillar) or drag (weak foundation)? Empty Creation is a thrust gap. Unauditable influenced reporting is a drag gap under +1. A scoring rebuild with no end date is drag under +2.
How this shows up in planning
- Diagnose each pillar and each foundation: empty, thin, noisy or crowded.
- Baseline two or three metrics that sales already believes.
- Select a few owned initiatives for the weakest leak. If the leak is drag, fund +1 or +2 before another Capture campaign.
- Map each initiative to one home (main job only; knock-on effects noted, not double-counted).
- Run and measure against the North Star: marketing-sourced plus marketing-influenced pipeline, reported separately.
The how-to guide walks the six method steps. This page only locks the metaphor so budget conversations stay honest.
What thrust vs drag is not
- Not a claim that marketing "owns" revenue alone. The cascade starts from enterprise goal and sales target.
- Not a replacement for the demand waterfall, MEDDPICC or ABM. Those measure flow or run deals; the 4+2 plans the initiative portfolio.
- Not rocket imagery, gym language or "blast-off" copy. The metaphor is an engine under load: thrust forward, drag against, foundations as the airframe that keeps instruments honest.
- Not permission to invent velocity formulas. Volume and speed appear as planning language; the North Star stays sourced and influenced pipeline value.
Practical tells you are adding thrust onto drag
- Marketing reports MQLs as the result while sales asks for qualified opportunities.
- Influenced pipeline has no written 90-day buying-group rule and no Revenue Operations audit.
- Lead scoring is a permanent "transformation" with no handover to Capture run-state.
- Creation and Capture share one "demand gen" budget, so Creation is cut whenever bookings slip.
- Retention proof never reaches Creation, so brand content stays generic.
Each of those is a drag story wearing a thrust costume. Name it that way in the portfolio review.
What to do next
Read the Revenue Operations and Revenue Enablement pages for foundation detail, and the glossary for the short definitions. For the full cascade and worked example, use the white paper.
Fix the drag you can prove. Then add thrust where the empty cell hurts next quarter's pipeline.
Sources: metaphor and operating rule from Patel, 4+2 Pipeline Thrust Matrix white paper v1.0 (prinkit.com). No external performance benchmarks claimed on this page.