7 B2B Marketing Frameworks for Pipeline

7 B2B Marketing Frameworks for Predictable Pipeline

Most B2B marketing teams do not have a strategy problem. They have a framework problem.

You are the CMO or VP of Marketing. The board wants predictable pipeline. The CFO is asking, "What's the conversion assumption behind that MQL number?" And your team is running campaigns without a diagnostic model, building pipeline targets without a planning model, and measuring attribution without a measurement model. The work feels like activity theater. The board deck feels thin. Two planning cycles burn arguing about definitions.

What are B2B marketing frameworks? B2B marketing frameworks are named, attributed methodologies that turn fragmented tactics into a coherent demand engine. They give you a shared language for diagnosis, planning, execution, and measurement so the next pipeline meeting stops being a fight about whose spreadsheet is right.

Now let's get concrete. Here's the catalog: seven named frameworks, organized by what they actually do. Most published guides hand you a single framework and call it a day. We give you a catalog plus selection rules. Treat it as instrumentation for your demand engine, something you use to diagnose, calibrate, and measure, not a sequential reading order. Frameworks are the operating system. Tactics are the apps.

Every framework entry follows the same pattern: a capsule, a component list, a generic example, a common misuse, a Starr take, and a source line.

The Starr Conspiracy has applied and adapted these frameworks across 25 years of B2B tech and SaaS demand generation work. We did not invent most of them. We did learn which ones survive contact with a real pipeline meeting and which ones collapse under the first hard question from finance. Before anyone says it: yes, you already have a strategy doc. That doc is why you are here. Strategy without frameworks is a wish list with serif fonts.

And no, a framework is not bureaucracy. It is how you move faster without making up math every quarter. If you think you are too unique for frameworks, you are not. Your labels are unique. Your physics aren't.

Here's the part people screw up. The fundamentals (brand, message, positioning) are not in tension with AI-assisted production and optimization. AI augments the system. It does not replace the system. The brand layer is what keeps AI-generated execution from drifting into off-brand sludge. We don't sell AI experiments. We build marketing systems that actually work.

Framework index

• The 95/5 Rule, diagnostic
• The Ten Demand States, diagnostic
• The Demand Waterfall, planning
• The Category Design Framework, planning
• The Inbound and Outbound Operating Model, execution
• The Marketing Operations Maturity Model, execution
• The Pipeline Attribution Framework, measurement

How the catalog is organized

The seven frameworks fall into three purpose-based categories.

Diagnostic and Orientation frameworks tell you what is true about your market and your buyer right now. Use these before you plan anything. The 95/5 Rule and the Ten Demand States live here.

Strategy and Planning frameworks turn that diagnosis into a pipeline target and a category position. The Demand Waterfall and the Category Design Framework live here.

Execution and Measurement frameworks govern how the work gets built, run, and proved. The Inbound and Outbound Operating Model, the Marketing Operations Maturity Model, and the Pipeline Attribution Framework live here.

A mature demand engine uses at least one framework from each category. Skip a category and you end up with great execution on the wrong audience, or beautiful brand work that cannot prove pipeline.

Before frameworks, a pipeline meeting is three people defending three different numbers. After, it is one number with documented assumptions. That is the entire trade.

How to pick a framework

Five decision rules, mapped to the frameworks below.

1. If you cannot describe who is in-market this quarter versus who is not, start with the 95/5 Rule and the Ten Demand States. Diagnosis first.
2. If your pipeline number is built bottom-up from MQL volume rather than top-down from revenue, use the Demand Waterfall to rebuild the model.
3. If competitors are winning on "better" and you keep losing on "different," the Category Design Framework is the right tool, not another messaging refresh.
4. If inbound and outbound teams are arguing about lead ownership instead of pipeline contribution, install the Inbound and Outbound Operating Model before you touch the comp plan.
5. If your CMO cannot answer "what did marketing source last quarter" in under 30 seconds, you have a measurement problem. Run the Marketing Operations Maturity Model diagnostic first, then build the Pipeline Attribution Framework on top of it.

If you only do one thing, start with the Ten Demand States and the Demand Waterfall. Diagnosis and planning carry the rest. If your data is a mess, do not start with attribution. Fix ops maturity first or you will be weighting garbage.

If finance is already questioning your number, you are late. Pressure-test your current demand engine against one framework from each category before the next board meeting. Want help picking and installing? See our marketing strategy work.

The seven frameworks

Diagnostic and Orientation

The 95/5 Rule

The 95/5 Rule is a Diagnostic and Orientation framework developed by Professor John Dawes at the Ehrenberg-Bass Institute and popularized in B2B by the LinkedIn B2B Institute. It organizes B2B buyers into five components: the in-market segment, the out-of-market segment, mental availability, category entry points, and a budget split heuristic. The core claim is that roughly 5% of buyers are in-market in any quarter and roughly 95% are not. Use the 95/5 Rule when your team is over-indexed on short-term lead capture and starving brand investment with future buyers.

Components:

• The 5% in-market segment, addressable through demand capture.
• The 95% out-of-market segment, addressable only through brand and category memory.
• Mental availability as the bridge between the two states.
• Category entry points that trigger movement from out-of-market to in-market.
• A budget split heuristic, often cited as 60/40 brand-to-activation for B2B.

Applicability: Any B2B SaaS or tech team with both a brand budget and a demand budget; requires baseline branded-search and direct-demand tracking.

Generic example: A SaaS team reallocates a slice of paid search budget into a category-entry-point campaign aimed at the 95%, then measures change in branded search and direct demo requests two quarters out. Artifact change: the media plan grows a brand layer with its own KPI.

Common misuse: Treating the 60/40 split as a law instead of a heuristic. It is a starting point, not a verdict.

The Starr Conspiracy take: We pair the 95/5 Rule with the Ten Demand States to give planners more resolution than a binary in-or-out call. Primary outcome: forecast accuracy and brand-led pipeline contribution, measured as branded-search lift and direct-demand volume.

Source: Ehrenberg-Bass Institute (Dawes); popularized in B2B by LinkedIn B2B Institute.

The Ten Demand States

You know the symptom: stage-based lifecycle logic is forcing your team to treat very different buyers as if they belong on the same nurture track. The Ten Demand States is a Diagnostic and Orientation model developed by The Starr Conspiracy for B2B SaaS and tech to replace lead-lifecycle thinking with buyer-orientation thinking. It organizes the market into ten named states, a movement model, content and channel mapping, a state-shift measurement layer, and integration points with the 95/5 Rule and the Demand Waterfall. The states span fully unaware through actively evaluating to post-purchase advocacy.

Components:

• Ten named states spanning unaware, latent, triggered, active, and committed orientations.
• A movement model describing what causes a buyer to shift states.
• Content and channel mapping per demand state.
• A measurement layer tied to state-shift rather than form-fill.
• Integration points with the 95/5 Rule and the Demand Waterfall.

Applicability: Mid-market to enterprise B2B SaaS with a marketing automation platform (MAP), a CRM, and at least one nurture program already running.

Generic example: A demand team retags its nurture program by demand state instead of lifecycle stage and routes "triggered" accounts to a sales play while "latent" accounts go to a category-education sequence. Artifact change: the nurture map and the routing rules.

Common misuse: Bolting demand states on top of an unchanged MQL machine. If the routing and measurement do not change, neither will the pipeline.

The Starr Conspiracy take: This is the methodology backbone of our demand generation services for B2B tech clients. Primary outcome: campaign relevance and SAL acceptance rate (the rate at which sales accepts SALs into SQLs).

Source: The Starr Conspiracy, developed through B2B tech and SaaS engagements.

Strategy and Planning

The Demand Waterfall

The Demand Waterfall is a Strategy and Planning framework originally developed by SiriusDecisions (now Forrester) for B2B revenue teams. It organizes demand into sequential lead-lifecycle steps, documented conversion rates, velocity assumptions, capacity inputs, and variance tracking. The steps run from inquiry through MQL, SAL, SQL, opportunity, and closed-won. Use the Demand Waterfall when you need to build a pipeline target backward from a revenue number and defend the assumptions in a board meeting.

Components:

• Inquiry, MQL, SAL, SQL, opportunity, and closed-won steps (map to your equivalents if your labels differ).
• Documented conversion rates between each transition.
• Velocity assumptions (days in step) for cash-flow modeling.
• Capacity planning inputs for sales and SDR teams.
• Variance tracking against historical baselines.

Applicability: Teams with annual contract value (ACV) and conversion-rate history; finance must be willing to co-own the model.

Generic example: A revenue team rebuilds next year's plan by starting at the revenue target, dividing by ACV, then walking backward through conversion and velocity to land on required inquiries by quarter. Artifact change: a pipeline model spreadsheet finance can actually defend, typically with separate tabs for conversion assumptions, velocity, and capacity.

Common misuse: Using the Demand Waterfall for attribution. It is a planning tool. Using it to credit channels creates the wrong fight.

The Starr Conspiracy take: Plan with the Waterfall. Measure with the Pipeline Attribution Framework. Do not let one do the other's job. Primary outcome: forecast error reduction quarter over quarter, and CFO-defensible assumptions.

Source: SiriusDecisions / Forrester.

The Category Design Framework

The Category Design Framework is a Strategy and Planning framework developed by Play Bigger Advisors and codified in the book Play Bigger. It organizes go-to-market strategy into five components: problem naming, category naming, point of view, lightning strike, and category king economics. The thesis is that creating and dominating a new category beats competing on features inside an existing one. Use the Category Design Framework when the buyer cannot articulate the problem your product solves without borrowing your competitor's vocabulary.

Components:

• Problem naming, the act of giving the unsolved problem a label.
• Category naming, distinct from product naming.
• Point of view (POV) document that frames the category.
• Lightning strike, the high-intensity launch moment.
• Category king economics, the winner-take-most dynamics that justify the investment.

Applicability: Companies with a genuinely differentiated roadmap, executive air cover for a multi-quarter bet, and the budget for a real lightning strike.

Generic example: A platform vendor stops competing inside an analyst-defined category and publishes a POV document naming a new problem, then runs a lightning strike anchored on a flagship event and an owned research report. Artifact change: the messaging house and the analyst briefing deck.

Common misuse: Feature-level differentiators dressing themselves up as category creators. Renaming your product is not a category.

The Starr Conspiracy take: Start here when the buyer language is the competitor's language and your roadmap is genuinely different. Otherwise, fix positioning first. Primary outcome: win rate against entrenched incumbents.

Source: Play Bigger Advisors, Play Bigger (HarperBusiness).

Execution and Measurement

The Inbound and Outbound Operating Model

The Inbound and Outbound Operating Model is an Execution and Measurement framework developed by The Starr Conspiracy. It defines how demand capture (inbound) and demand creation (outbound) operate as a single integrated system rather than two competing programs. It organizes the work into five components: a shared target account list, demand-state tagging that routes accounts, a unified content library, a single marketing-to-sales SLA, and pipeline contribution reporting that credits both motions. Use this inbound and outbound B2B marketing model when teams are running parallel plays with no shared definition of a qualified account.

Components:

• A shared target account list governed by ICP fit, not channel preference.
• Demand-state tagging that routes accounts to inbound or outbound based on readiness.
• A unified content library serving both motions.
• A single SLA between marketing and sales on account follow-up, typically including a days-to-first-touch clause for inbound and a touch-cadence clause for outbound.
• Pipeline contribution reporting that credits both motions without double-counting.

Applicability: Any B2B SaaS team with both an SDR motion and an inbound demand program; requires a single source-of-truth CRM.

Generic example: A revenue team consolidates two separate target lists into one, tags accounts by demand state, and rewrites the SDR routing rule so inbound and outbound work the same account from different angles. Artifact change: account routing rules and the joint SLA.

Common misuse: Treating this as a comp plan negotiation. Fix the operating model first; the comp plan follows the system.

The Starr Conspiracy take: In our experience, most operating-model fights are masquerading as attribution fights. Start here when inbound and outbound argue about ownership in every QBR. Primary outcome: pipeline velocity (days-to-first-touch and days-in-stage) and CAC efficiency.

Source: The Starr Conspiracy.

The Marketing Operations Maturity Model

Leadership cannot agree on whether the ops function needs more headcount, better tooling, or a different mandate. That's the symptom. The Marketing Operations Maturity Model is an Execution and Measurement framework developed by The Starr Conspiracy from 25 years of B2B tech marketing operations work. It organizes ops readiness into five levels: Reactive, Functional, Integrated, Optimized, and AI-Augmented. Each level is characterized by reporting cadence, data integration, scoring sophistication, and AI governance under brand and compliance controls.

Components:

• Level 1 Reactive, manual reporting and ad hoc campaign builds.
• Level 2 Functional, a working MAP and CRM but limited integration.
• Level 3 Integrated, clean data flow and consistent attribution.
• Level 4 Optimized, predictive scoring and automated routing.
• Level 5 AI-Augmented, AI-assisted production and optimization with human oversight, brand guardrails, and compliance controls.

Applicability: Any B2B SaaS marketing org with a MAP and CRM; useful as an annual diagnostic before budget season.

Generic example: An ops team running at Level 2 audits its CRM-to-MAP sync, fixes account-to-lead matching, and stands up a single source-of-truth dashboard before touching scoring. Artifact change: the data model and the reporting view.

Common misuse: Buying Level 4 tooling while operating at Level 2. The tool does not raise the level. The discipline does.

The Starr Conspiracy take: In our audits, the median B2B SaaS marketing org sits at Level 2 to 3 and budgets as if it were at Level 4. The gap is where pipeline leaks. Before recommending attribution work, we look for clean account-to-lead matching, a stable lead-status taxonomy, and a defined reporting cadence. Primary outcome: data trust and ops throughput.

Source: The Starr Conspiracy.

The Pipeline Attribution Framework

The Pipeline Attribution Framework is an Execution and Measurement model developed by The Starr Conspiracy. It credits marketing's contribution to pipeline across multi-touch B2B buying journeys without collapsing into single-touch fiction. It organizes credit into five components: sourced pipeline, influenced pipeline, accelerated pipeline, a weighting model that prevents double-counting, and a reporting cadence aligned to the finance close. Use this B2B pipeline framework when finance and marketing report different numbers for the same quarter and neither side trusts the other's math.

Components:

• Sourced pipeline, where marketing created the first qualified opportunity.
• Influenced pipeline, where marketing touched a deal sourced elsewhere.
• Accelerated pipeline, where marketing measurably compressed deal velocity.
• A weighting model that prevents double-counting across the three.
• A reporting cadence aligned to the finance close (reconciled within the same close window), not the marketing calendar.

Applicability: Teams operating at Marketing Operations Maturity Level 3 or above; requires clean account-to-lead matching.

Generic example: A marketing team replaces a single-touch sourced report with a three-view dashboard (sourced, influenced, accelerated) and reconciles it to finance's pipeline view on the same cadence. Artifact change: the board report view.

Common misuse: Running attribution on dirty data. If account-to-lead matching is broken, attribution is fiction with a pivot table.

The Starr Conspiracy take: The goal is not to win the attribution argument. The goal is to make the attribution argument boring. Primary outcome: reporting trust between marketing, sales, and finance, measured by reconciliation to the finance close.

Source: The Starr Conspiracy, building on SiriusDecisions / Forrester attribution practice.

What this catalog is not

This is not a maturity ranking. The Ten Demand States is not "better" than the Demand Waterfall. They answer different questions. A team using all seven badly is worse off than a team using two of them well.

It is also not a closed set. The frameworks here are the ones that have repeatedly survived the move from theory to a real B2B tech pipeline. Others may earn their way in. Several popular ones will not, because they collapse the moment a CFO asks a hard question.

This is not a tips-and-best-practices post. A catalog with a decision layer is the difference between a methodology and a meme.

Diagnose. Plan from the diagnosis. Execute against the plan. Measure what the execution produced. Then do it again, faster.

Install the system

If your pipeline math gets questioned every quarter, we fix that. The Starr Conspiracy will help you select, adapt, and install the right frameworks across diagnosis, planning, execution, and measurement, before finance locks the forecast model. We diagnose demand, rebuild the plan, and make measurement boring.

Start with The Starr Conspiracy's demand generation services. We don't sell AI experiments. We build marketing systems that actually work.