B2B Lead Gen Framework Catalog

6 B2B Lead Generation Frameworks That Build Predictable Pipeline for Tech Companies

This catalog presents six B2B lead generation frameworks for tech companies, named, structured methodologies for rebuilding a qualified lead-to-pipeline engine when the old playbook stops working. Each framework includes its components, a clear "when to use" trigger, and the job it does inside a modern demand engine: diagnose, architect, execute, govern, and allocate. Use it to identify your binding constraint and pick the first framework to run, not the fifth.

Most B2B tech marketing teams do not have a lead generation problem. They have a methodology problem. They run tactics, not systems. They chase channels, not architecture. When the board asks why pipeline coverage slipped, the answer is some version of: the market got harder.

The market did get harder. That is not why your pipeline engine stopped working.

Running tactics without methodology is like tuning the radio while the engine is on fire. You inherited a playbook built for a different decade, when gated whitepapers converted, MQL counts predicted revenue, and outbound SDRs could carry a number on volume alone. Every assumption underneath that playbook has broken. Buyer committees expanded. Self-service research now consumes most of the purchase cycle before sales is contacted. Cold reply rates collapsed across most B2B SaaS categories.

You need a decision system, not another list of channels. The tactic roundups dominating YouTube, Reddit, and vendor blogs will not get you there. After 25 years building demand systems for B2B tech, the pattern is always the same: teams that recover fastest stop arguing about channels and start arguing about methodology. This is the methodology layer everyone else skips.

Four of the six frameworks below have established origins outside The Starr Conspiracy and are presented as practitioner-grade methodology, not invention. The remaining two reflect how we, The Starr Conspiracy, assemble the layer most catalogs leave unowned: the diagnostic that tells you which framework you need, and the demand architecture that sequences brand and capture into a single revenue system rather than two competing budgets.

We don't sell AI experiments. We build marketing systems sales trusts and CFOs can defend. AI accelerates segmentation and personalization. Governance still wins.

How to Read This Catalog

The six frameworks are organized by the job they do, not the channel they use:

1. Starr Demand Diagnostic (Diagnostic, Proprietary). Identifies the binding constraint and routes you to the right framework first.
2. Demand Waterfall (Diagnostic). Exposes conversion leaks stage by stage.
3. Starr Demand Architecture (Demand Architecture). Sequences brand and capture into one revenue system.
4. SPEAR Outbound (Outbound Execution). Replaces volume-first SDR motion with disciplined sequencing.
5. Pipeline Coverage Model (Pipeline Governance). Translates marketing activity into board-grade coverage math.
6. Bullseye Channel Framework (Channel Mix). Concentrates budget on channels with defensible unit economics.

Each entry includes a capsule, a labeled component list, and a plain-language statement of when to use it.

A quick note on language. We do not use "funnel stages" or "buyer's journey stages" here. We use demand states, because buyers are not on a linear conveyor belt. They occupy conditions, those conditions change, and the framework that serves a 50-person seed-stage team selling to mid-market IT is not the framework that serves a 400-person growth-stage team selling to the Fortune 500.

Now, the frameworks, organized by the job they do.

The Framework Catalog

Starr Demand Diagnostic (Diagnostic, Proprietary)

The Starr Demand Diagnostic is our proprietary entry framework, developed across 25 years of rebuilding B2B tech demand engines. We built it because most teams default to channels first, and it is usually wrong. The diagnostic scores brand strength, message clarity, demand architecture, outbound discipline, pipeline governance, and channel mix on a single scorecard, then routes the team to the framework that addresses the binding constraint (the one constraint whose removal unlocks the system) first. In our audits, the leak is typically SAL (sales-accepted lead) to SQL, not inquiry volume. Skip the diagnostic and run straight to channel tests, and you waste a quarter.

• Brand and message audit: Category position, message clarity, and competitive distinctiveness.
• Demand architecture review: How brand and capture interact across demand states.
• Outbound assessment: Segmentation, message, and cadence discipline.
• Pipeline governance check: Coverage math, sourcing mix, and forecast credibility.
• Channel allocation review: Unit economics by channel and reallocation discipline.

When to use: Use the Starr Demand Diagnostic when the engine is underperforming and leadership cannot agree on the binding constraint.

Demand Waterfall (Diagnostic)

The Demand Waterfall, originated by SiriusDecisions (stage naming varies by implementation), is the conversion-by-stage diagnostic that exposes where a lead-to-pipeline engine actually leaks. It tracks volume and conversion from inquiry through qualified pipeline, then compares actual rates to ratios the revenue team can defend. The Starr Conspiracy uses a modified Demand Waterfall as the first diagnostic in every engagement, because most teams misdiagnose a coverage problem as a top-of-funnel problem when the real failure sits two stages deeper. A common failure mode: optimizing inquiry volume while SAL-to-SQL conversion is the actual leak. The result is better conversion visibility and an end to MQL theater.

• Inquiry capture: Every raw hand-raise across owned, paid, and partner sources.
• Automation-qualified: Records that pass basic fit and intent filters.
• Teleprospecting accepted: Leads SDRs agree to work, not just receive.
• Sales accepted (SAL): Opportunities sales formally commits to pursue.
• Sales qualified pipeline (SQL): Opportunities with budget, authority, need, and timing confirmed.

When to use: Run the Demand Waterfall when pipeline coverage is below target and leadership cannot agree on where the engine is breaking.

Starr Demand Architecture (Demand Architecture)

Starr Demand Architecture is The Starr Conspiracy's proprietary framework for sequencing brand and capture into one revenue system. We built this to end the budget war between brand and demand teams. Most B2B tech companies run them as separate budgets with separate metrics, then wonder why capture spend underperforms. The architecture maps message, audience, and channel against demand states, so brand investment compounds into capture efficiency instead of competing with it. Typically fits a 100-to-500-person growth-stage company with six-figure ACV and multi-threaded committees (long enough cycles, big enough committees, that single-channel capture can't carry the number). Do not run this without a current diagnostic. Sequencing without diagnosis is theater.

• Demand-state map: Defined buyer conditions and the message each one requires.
• Message architecture: The category, brand, and offer messages tied to each state.
• Channel assignment: Which channels serve which states, and why.
• Capture mechanics: Offers, forms, and routing logic that convert intent to pipeline.
• Compounding metrics: Brand and capture KPIs that prove the system is working together.

When to use: Use Starr Demand Architecture when brand and demand teams operate as separate functions and capture efficiency is stalling despite increased spend.

SPEAR Outbound (Outbound Execution)

SPEAR, Segment, Personalize, Engage, Activate, Repeat, is a structured outbound sequence framework commonly attributed to Kyle Coleman and used by practitioners across modern B2B SaaS. It replaces volume-first SDR motions with tightly segmented, message-disciplined sequences that protect the brand while generating qualified meetings. The Starr Conspiracy applies SPEAR inside outbound execution engagements because volume-based outbound is now actively destroying brand equity in most categories, and reply-rate math no longer works at any volume. Typically fits teams with 5 to 50 SDRs and sales cycles over 60 days. The result is less wasted outbound volume and higher qualified meeting rates.

• Segment: Tight ICP and trigger-based account selection.
• Personalize: Research-backed openers tied to a verified problem.
• Engage: Multi-channel sequence across email, phone, and social.
• Activate: Clear conversion offer designed for a specific demand state.
• Repeat: Disciplined cadence and feedback loop into segmentation.

When to use: Use SPEAR when SDR reply rates have collapsed and sales leadership is questioning whether outbound still works at all.

Pipeline Coverage Model (Pipeline Governance)

The Pipeline Coverage Model is the standard governance framework that ties marketing-sourced pipeline to revenue targets through a coverage ratio, often 3 to 4x quota depending on cycle length and win rate. It forces the conversation marketing leaders avoid: whether the pipeline they are producing is sufficient, on time, and credible to sales and finance. The Starr Conspiracy treats board-grade coverage as the only marketing metric the board actually trusts; every other metric exists to explain movement inside it. Coverage without stage aging and SAL definitions is a vanity ratio. Done right, it tightens forecast confidence.

• Quota by segment: Revenue target broken down by segment and quarter.
• Coverage ratio: Required pipeline multiple by segment and stage.
• Sourcing mix: Marketing-sourced, sales-sourced, and partner-sourced contribution.
• Stage aging and velocity: Stage time and conversion against typical ranges.
• Forecast confidence: Coverage adjusted for historical conversion accuracy.

When to use: Use the Pipeline Coverage Model when marketing and sales cannot agree on whether the pipeline is real, sufficient, or on time.

Bullseye Channel Framework (Channel Mix)

The Bullseye Framework, originated in Traction by Gabriel Weinberg and Justin Mares, is a channel selection method that forces teams to test breadth, then concentrate on the channels with the strongest unit economics. For B2B tech, it is the antidote to channel-chasing and vendor-led budget decisions. The Starr Conspiracy adapts Bullseye for B2B SaaS by binding each channel test to a demand state and a coverage contribution target, so the test produces a budget decision, not just an experiment log. Typically fits teams running more than four active paid channels with no defensible CAC story. Testing without a kill threshold (for example, a CAC payback ceiling or a minimum pipeline contribution per quarter) turns into permanent spend.

• Outer ring: Every plausible channel for the category.
• Middle ring: Channels worth a structured test.
• Inner ring: The one to three channels carrying the budget.
• Unit economics: CAC, payback, and pipeline contribution per channel.
• Reallocation rule: The threshold that moves a channel in or out of the inner ring.

When to use: Use the Bullseye Framework when channel spend is fragmented across too many bets and no one can defend the allocation to finance.

How to Choose the Right Framework

If you are thinking "we just need more leads," you almost certainly do not. You need to know which lead-to-pipeline conversion is broken. Start with the Starr Demand Diagnostic. Match your condition to the framework:

• Coverage is below target and the cause is contested. Start with the Starr Demand Diagnostic, then Demand Waterfall.
• Brand and demand operate as separate budgets and capture is stalling. Run Starr Demand Architecture.
• SDR reply rates are collapsing and sales is losing faith in outbound. Implement SPEAR Outbound.
• CFO or board does not trust the pipeline number. Install the Pipeline Coverage Model.
• Channel spend is fragmented and finance is asking hard questions. Apply Bullseye.

Sequencing across a year: First 30 days, run the diagnostic and the Waterfall. Next 60 days, install architecture and coverage governance. Ongoing, run SPEAR for outbound and Bullseye for channel allocation as quarterly disciplines.

If you are resource-constrained: Pick one. Diagnostic first if you cannot agree on what is broken. Pipeline Coverage Model first if the board has lost faith in the number. Bullseye first if finance is the loudest voice in the room. Do not run three frameworks at once with a four-person team.

If you are behind on board-grade coverage in week four of the quarter, you do not have time for random channel tests. You have time for a diagnostic.

The right framework produces three outcomes: a higher qualified meeting rate, coverage predictability your CFO will sign off on, and sales alignment that ends the monthly finger-pointing about lead quality. None of this requires losing what already makes your company great. It requires connecting it to a system that compounds.

Ready to find your binding constraint? Book a 30-minute diagnostic intake with The Starr Conspiracy.

Work With Us

If pipeline coverage is under target this quarter, start with the diagnostic. We don't sell AI experiments. We build marketing systems that actually work: predictable pipeline, sales-trusted numbers, and a clear read on the binding constraint and the first 30 days of fixes.

Book a diagnostic intake call with The Starr Conspiracy. Tell us your situation. We will tell you which framework fixes it first, and if it is the wrong starting point, we will say so.