.png)
.jpg)
.jpg)
%20(1).jpg)
.png)
Account
Tier 1
Example Co A
Overlap score35 / 35
Intent score35 / 35
- Motion
- Partner-sourced co-sell outreach
- Owner
- Account owner
- SLA
- 4 business hours
Ecosystem-Led Marketing: Awareness and Demand
October 21, 2026
|
13
minutes
How to build a demand generation framework (6-step guide)
How to build a demand generation framework (6-step guide)
.png){kind=icon}
Build a demand generation framework in six steps using partner ecosystem overlap. Includes scoring rubrics, tiered campaigns, and routing rules.
A demand generation framework is a repeatable operating model that tells your B2B team which accounts to target, which signals to act on, how to hand accounts to sales, and which metrics prove each stage works. It replaces a pile of tactics with defined stages, owners, and measurements. This guide walks you through building one in six steps, using partner ecosystem data as your targeting signal.
Before you start:
- Who it's for: RevOps managers, GTM systems analysts, and partner operations specialists who configure the CRM and reporting.
- What you need: admin access to your CRM (Salesforce or HubSpot), a documented ideal customer profile (ICP), a Crossbeam account with a few connected partners, and optionally an intent provider such as Demandbase or Bombora.
- What you'll produce: a target account segment, enrichment fields, a scoring rubric, campaign briefs, routing rules, a dashboard spec, and a review cadence.
- Difficulty and time: intermediate, roughly two to four weeks of part-time work.
What is a demand generation framework?
Ivris Tech defines it as "the system a B2B team uses to create demand, capture it, and convert it into revenue on purpose instead of by accident." The "on purpose" part matters because of buyer timing. The Ehrenberg-Bass Institute's 95:5 rule holds that only around 5% of business buyers are in-market in any given quarter. The other 95% won't buy for months or years.
Buyers also decide early. 6sense's 2025 B2B Buyer Experience Report found that buyers fill roughly four slots on a Day One shortlist and buy from one of those vendors about 95% of the time. Buyers now reach out at about 61% of their journey, up from the 69% mark a year earlier.
So your framework needs two tracks. Demand creation earns a place on the shortlist before anyone is shopping. Demand capture converts the buyers who show intent. A tactic list blends them, but a framework gives each its own goal, channels, and metrics.
How does demand generation differ from lead generation and ABM?
Demand generation is the umbrella system. Lead generation and account-based marketing (ABM) are motions that run inside it. Treat them as interchangeable, and your dashboards will measure the wrong things.
Your framework uses all three. Demand generation sets the stages and metrics. Lead generation feeds the capture stage. ABM focuses spend on the accounts your scoring model puts at the top.
What are the components of a demand generation framework?
Every working framework has stages, and each stage has a goal, inputs, and a metric. This build uses six, and Crossbeam supplies the account-level signal that most frameworks lack. Ecosystem-Led Growth (ELG) is the go-to-market strategy that treats your partner ecosystem as a primary source of pipeline and revenue. Here, it supplies the targeting layer.
Step 1: How do you identify audiences with ecosystem overlap?
Your first artifact is a target account segment built from ecosystem overlap: accounts that appear in both your CRM and a partner's CRM as customers, prospects, or open opportunities. The partner side of that match is second-party data, meaning data a partner shares with you directly, under controls you both set.
- Connect with partners in the Crossbeam Network, starting with those who serve your ICP.
- Run overlap detection to surface shared accounts.
- Sync results to your CRM and set matching logic: domain first, then company name plus country.
- Filter by ICP fit, overlap strength (number of partners, customers, or prospects), and relationship context, meaning which partner knows the account and how close they are.
To extend the list past your CRM, Crossbeam's Pipeline Generation surfaces net new accounts, partner-sourced prospects that sit outside your CRM. Pushing overlap fields onto account records is covered under Crossbeam's account enrichment.
Checkpoint: spot-check 20 overlap accounts. Each should exist in your CRM and match your ICP on industry, size, geography, and tech stack.
Warning: overlap alone isn't a target list. Add an ICP filter and a trigger event, such as a funding round, a new executive hire, or someone who recently became a customer of your partner.
Step 2: How do you enrich overlap accounts with intent and buying group data?
Overlap tells you who is adjacent to your ecosystem. Intent data tells you when to move. Bombora's Company Surge signals track when a company's employees consume an abnormal volume of content around specific B2B research topics across a cooperative publisher network. Demandbase Intent monitors online browsing patterns of prospective and current customers.
Pick five to eight topics tied to the problem you solve, then add these fields to the account object:
- intent_topic
- intent_last_seen (date)
- intent_window_days
- buying_role (economic buyer, champion, technical evaluator)
- priority_score
Map each intent account to a buying group by listing the two or three roles you must reach. Buyers contact vendors early, so identifying roles before the surge fades matters.
Checkpoint: build a CRM filter for "overlap = true AND intent_last_seen within 30 days AND buying_role is not empty." If you can't express it as a segment, you can't route on it.
Warning: topic mismatch inflates your list. Treat any intent window older than 30 days as stale and drop its points.
Step 3: How do you score, segment, and prioritize accounts?
Your artifact here is a scoring rubric that combines three inputs. These weights are a starting point, so tune them against your own conversion data after 60 days.
Map bands to actions: 80 to 100 is Tier 1 (co-sell outreach), 60 to 79 is Tier 2 (ABM), 40 to 59 is nurture, and below 40 is monitor only.
CRM deliverables: three score fields, one tier field, a "score reason" text field, and segment rules for each tier. Define MQL status here so marketing and sales share vocabulary.
Checkpoint: open a Tier 1 account as a rep would. The overlap partner, intent topic, and score reason should all be visible before any outreach.
Warning: lead-only scoring misses the buying group. Roll contact activity up to the account.
Step 4: How do you run ABM and co-marketing campaigns on your top accounts?
Turn each tier into a play. Co-marketing campaigns work best when the partner already has a relationship with the account, because the invitation carries relationship context instead of a cold pitch.
Give every campaign a brief: goal metric, tier, partner, asset, landing page, and UTM set. Add a required "How did you hear about us?" field on forms to capture self-reported attribution that UTMs miss.
Checkpoint: each live campaign has one goal metric and consistent tags in your CRM.
Warning: gate intent assets (ROI calculators, pricing guides, demo requests), and keep early education ungated so it can build shortlist presence.
Step 5: How do you route leads and enable sales co-sell?
An EQL, or Ecosystem-Qualified Lead, enters your funnel through partner overlap rather than a cold form fill. Crossbeam defines it as a partner-vetted contact: ecosystem data and the partner relationship confirm fit before the lead ever reaches your queue. Add a lead source value for EQLs so routing treats them distinctly from other leads.
Write routing as explicit logic. Sample rule: IF tier = 1 AND intent_last_seen is within 14 days, THEN assign to the account owner (or the segment SDR if none) and create a task. Sample SLAs (service level agreements, the maximum time a rep has to act on a routed account): Tier 1 within four business hours, Tier 2 within one business day.
Signal-aware outreach means timing and wording a message from the signals on the account: the partner connection, the intent topic, the role. Push those fields into your sequencing tool, so reps see them.
Playbook A, webinar follow-up: attendee scored, Tier 2 and up routed within one day, email references the session topic and partner.
Playbook B, co-marketing event: partner introduces the account, EQL created within 24 hours, joint follow-up.
Checkpoint: report meeting rate by tier, and confirm every handoff carries the same fields.
Step 6: How do you measure demand creation and demand capture?
Track creation and capture separately. Capture metrics lag, so judging creation by them punishes the work that builds your shortlist position.
Build two dashboard views: creation progress and capture conversion (EQL to SQL, SQL to opportunity, pipeline created). Review stage performance monthly. Each quarter, shift budget toward the tactics that moved creation metrics.
Warning: pipeline-influenced counts touch, so report it next to attributed pipeline, never in place of it.
Which prompts and templates speed up the build?
Paste these into your AI tool of choice and adjust the brackets. If you work in Clay, the Clay MCP brings Crossbeam partner context into the same workflow.
- "From this list of overlap accounts and our ICP ([criteria]), return the top 50 with a one-line reason each."
- "Write messaging for a [role] at an account with intent on [topic] and a connection through [partner]."
- "Draft a co-marketing invite from [partner] to [account type] about [topic], under 120 words."
- "Write landing page copy for [webinar], with one headline, three benefits, and one CTA."
- "Turn this scorecard into routing rules with owner, SLA, and fallback."
Campaign brief skeleton:
Campaign name:
Tier / segment rule:
Partner:
Goal metric and target:
Asset and landing page:
UTM set (source / medium / campaign / content):
Owner and SLA:
Review date:
What does a completed scorecard look like?
Use one row per account, so reps see the "why" next to the action.
What should you do when your framework stalls?
What have you built, and what comes next?
You now have a six-stage framework: an overlap-based target segment, intent and buying-role fields, a weighted scoring rubric, tiered campaigns, routing rules with SLAs, and a dashboard that separates creation from capture.
Next, run the model on one tier for 60 days, compare scores against actual meeting and opportunity rates, and adjust weights. Then add partners to the Crossbeam Network to widen your overlap set.
Ready to wire ecosystem signals into your CRM? Register on Crossbeam for free.
Frequently asked questions about demand generation frameworks
What is the definition of a demand generation framework in B2B marketing?
It's the system a B2B team uses to create demand, capture it, and convert it into revenue on purpose. It defines stages, channels, owners, and metrics so results are repeatable.
What are the main demand generation framework components?
Audience identification, enrichment, scoring and segmentation, ABM and co-marketing activation, routing to sales, and measurement. Each has a goal and metric.
What is the difference between demand creation and demand capture?
Creation builds awareness and shortlist presence among buyers who aren't shopping yet. Capture converts buyers already showing intent. Measure them with separate leading and lagging metrics.
How long does it take to build a demand generation framework?
A first version usually takes two to four weeks of part-time work. Expect to adjust scoring weights after 60 days of real conversion data.
