Case: A co-marketed webinar series returned 6.2x — but 80% of return came from one of five partners
A data-integration vendor ran five co-marketed webinars in 2023 with five ecosystem partners, splitting promotion and lead-sharing 50/50. Aggregate reporting looked clean: $48K invested (production, paid promotion, staff time), $298K in influenced pipeline, a tidy 6.2x return.
Decomposed by partner, the picture inverted:
— Partner A (overlapping ICP, complementary product) drove ~80% of qualified pipeline.
— Two partners netted near-zero — their audiences were practitioners, not buyers.
— Two were modestly positive.
The averaged 6.2x masked that four of five events were break-even-to-loss once fully costed. The single strong pairing was carrying the program.
What distinguished Partner A was measurable beforehand: audience-overlap analysis showed 34% shared firmographic ICP versus under 10% for the weak pairings. The vendor had simply not run that check before committing.
A causation note: high overlap correlates with results but doesn't guarantee them — Partner A also had a more engaged list (38% webinar open rate vs. a 22% program average). Overlap and list health were confounded.
This tracks with co-marketing research from the partner-economy literature (e.g., Crossbeam's overlap reports): account overlap is among the strongest available pre-indicators of co-sell and co-market success, yet most programs are still scheduled by relationship convenience rather than overlap data.
The trade-off in acting on this: concentrating on high-overlap partners deepens reliance on a few relationships and can starve ecosystem breadth that pays off later.
Implications: Report co-marketing ROI per-partner, never blended. A healthy blended number can hide that your program is one good pairing wearing four costumes.
Pipeline Papers
@PipelinePapers
Case: A co-marketed webinar series returned 6.2x — but 80% of return came from one of five partners
Этот пост опубликован в Telegram-канале Pipeline Papers. Подписаться можно по ссылке: @PipelinePapers.