Demand Gen

Origin & evolution

Demand generation grew out of B2B marketing automation in the early 2000s, when the tooling to nurture and score interest at scale first arrived. Eloqua, founded in 1999 and shipping its platform from the early 2000s, is widely credited with popularising the modern discipline and the "modern marketing" vocabulary around it (Chili Piper). Marketo followed in 2006, and the category became a recognised marketing function with its own budget and headcount.

The thinking has since divided demand generation from two adjacent activities. Lead generation, the older idea, captures contact details from people already showing intent. Brand marketing builds long-run salience. Demand generation sits across both: it manufactures interest in cold audiences at the top of the funnel⬇️FunnelGrowthA conversion funnel tracking user progressionView reference → and converts it lower down (Salesforce). The current debate, sharpened by practitioners like Refine Labs, pushes against gating everything behind a form. The argument is that most demand is latent, so the programme should educate broadly and capture only the small slice that self-identifies as in-market (Cognism).

How it works in practice

A Series B data platform sets a demand gen program with a single target: sourced pipeline of £4M for the year. The programme spans four standing motions. A content engine publishes weekly to a cold audience. A paid-social motion amplifies that content to a 50,000-account target list. A webinar🎥WebinarCustomer EducationA live or recorded webinarView reference → series runs monthly. A nurture track scores and routes anyone who raises a hand.

Inside that programme, individual campaigns come and go: a product-launch push in Q2, a conference-tied burst in Q3. The programme is the chassis; the campaigns are the trips. By year end, marketing reports that the cold-audience content drove 60% of self-reported pipeline, while the gated nurture track converted the already-interested faster. The programme keeps running into the next year; the Q2 launch campaign does not.

Demand Gen Program vs. its neighbours

• Marketing campaign plan📆Marketing Campaign PlanMarketingA marketing campaign planView reference → is bounded: a defined objective🏁ObjectiveStrategyA strategic goal (OKR)View reference →, dates, and budget for one push. A demand gen program is the ongoing engine that commissions and retires those campaigns over time.
• Lead is the captured individual, a single record of intent. The programme is the system that produces leads, among other outputs like influenced revenue and brand lift.
• GTM strategy🏹GTM StrategyGo-To-MarketA go-to-market strategyView reference → sets the where and the why: which segments, which motion, which positioning🎪PositioningGo-To-MarketProduct positioning statementView reference →. The demand gen program is one execution arm the strategy uses to generate demand, sitting downstream of the strategic choices.

In the graph

In the Unified Product Graph, demand_gen_program📣Demand Gen ProgramGo-To-MarketA demand generation program lives in the go-to-market domain and connects upward through gtm_strategy_generates_demand_via_demand_gen_programGTM Strategygenerates demand viaDemand Gen Programhierarchy. That edge encodes the relationship cleanly: strategy is the parent decision⚖️DecisionStrategyA recorded decision with context, rationale, and consequencesView reference →, the programme is the standing engine it spins up to create demand. Campaigns and leads then hang off the programme, so a query can walk from a strategic choice down to the specific pipeline it produced and check whether the engine is actually serving the strategy that justified it.