# Your Champion Isn't Enough > [!info] Deep-read port — Readwise notes field already contained a full 18-section analysis. > Ported from the existing deep-read (Refactor Appendix). Vendor content — Common Room's conclusion is that its own tooling answers the coverage problem it diagnoses. The mechanics are sound; the statistics are secondhand via aggregator blogs, and the headline correlation (won deals have more contacts) has an unaddressed reverse-causal reading. > [!question] Lingering Questions > - Does continued targeting after champion conversion actually improve outcomes, or mostly increase spend on accounts already going to close? > - Do the five coverage questions generalize to consensus processes with no CRM and no owner of the stakeholder map — open source RFCs, standards ratification, foundation funding? > - At what point does buying-group outreach cross from air cover into spam that damages the champion's internal credibility? > [!tip] Article Ideas > - "Your champion isn't enough" applied to open source governance: the five coverage questions (who's in the group, who's engaged, who's gone dark, which role has zero contact, what does each person care about) mapped onto a WordPress make-proposal or WPOCC project charter. Private-hold: needs the cross-domain observational check first. > [!link] Cross Reference > - [[3. Resources/MOCs/DevRel MOC]] — stakeholder coverage as a generalizable consensus-building framework > - [[3. Resources/MOCs/Open Source Governance MOC]] — the unrepresented-role failure mode maps directly onto proposal stalling > [!quote] Vocabulary > - *multi-threading* — engaging multiple stakeholders in a buying group simultaneously rather than relying on a single champion > - *air cover* — continued outreach/support to a group after an initial internal advocate has converted, so the advocate isn't relitigating the case alone ## Author's thesis Stalled deals share a common autopsy: one strong champion, and five people in the decision room who never heard the pitch. That's not a champion-quality problem, it's a coverage problem — most ABM programs suppress outreach to an account the moment a champion converts, which is exactly when the internal sell (to the other 5-9 buying-group members) begins. ## Key arguments (≤3) 1. Buying groups run 6-10 stakeholders who research independently; deals with 5+ engaged stakeholders close more, and 40%+ of B2B deals stall on internal misalignment, not competitive loss. 2. Two practitioner plays fix this: expand (not suppress) targeting after champion conversion with decision-stage content (Kuehnle/Loxo); run a monthly staleness review with an explicit dormancy threshold and no marketing-to-sales handoff (Potter/ForgeX). 3. Neither play survives as a one-time task — both require continuously answering who's in the group, who's engaged, who's gone dark, and which role has zero contact. A stale account map collapses back into "we should loop in the CFO sometime." ## Claim atoms ### Stalled deals reveal coverage gaps, not weak champions > [!quote] ID: rw_champion_h1 > That's not a champion problem. It's a coverage problem. Reframes an unactionable quality judgment into a measurable quantity — changes both the metric and the intervention. Transfers directly to any multi-party consensus process. ### Proactive ABM shapes the narrative before buyers ask > [!quote] ID: rw_champion_h2 > ABM is either reactive or proactive. Most teams choose reactive without realizing it. Sam Kuehnle (Loxo) naming a default nobody chose deliberately — operating on the buyer's timeline versus ahead of it. ### Warm the committee so the internal sell precedes the meeting > [!quote] ID: rw_champion_h3 > When your champion walks into that leadership meeting, the people in the room already know your story. The post's thesis in one sentence. The operational move: invert the standard rule that suppresses targeting once an account converts. ### A dormancy threshold turns coverage into a reviewable question > [!quote] ID: rw_champion_h4 > Lisa is the CMO and critical to this deal, but she hasn't engaged in 75 days. What can we do? Davis Potter (ForgeX). A binary threshold with a named human attached converts a vague aspiration into something a monthly meeting can act on. The interval matters far less than having one. ### Multi-threading needs continuous state, not a checklist item > [!quote] ID: rw_champion_h5 > Both plays sound simple. Neither survives as a line on a rep's task list. The post's strongest reasoning — identifies the real dependency (continuously fresh knowledge of who's engaged/missing) that intermittent manual effort can't supply, independent of whether the vendor's product is the right answer. ## Permanent candidates - **The unrepresented role predicts failure better than the dormant one** — strongest candidate; generalizes past sales to any multi-party consensus process (governance proposals, standards, grants). Promoted below. - Withdrawing support at champion conversion is when advocacy is most needed — the Kuehnle-inversion claim; secondary candidate, more sales-specific, held back this pass. ## Processing checklist - [ ] Retrieve the primary Gong and Gartner sources before citing the 6-10-stakeholder or contact-count figures — currently sourced through aggregator blogs - [ ] Check whether the 90-95%-engagement-at-close figure is selection on the dependent variable (compare against closed-lost deals) - [x] Connect into the relevant MOC — [[3. Resources/MOCs/DevRel MOC]] ## Links - [[3. Resources/MOCs/DevRel MOC]] — stakeholder-coverage mapping as a transferable consensus-building tool for advocacy and proposal work - [[3. Resources/Readwise/Articles/Your Champion Isn't Enough]] — source document, full deep-read