Your Competitive Intel Deck Lists Four Competitors and Sales Cites Two on Calls

It is Wednesday, 10:04 AM. Your CMO opens the competitive intel deck the PMM team keeps in the shared drive. Four competitors listed on the cover slide. Last edited timestamp reads March 14th. She scans the Gong dashboard next to it. Trailing 30 days, sales calls where any competitor was named by the prospect: 84. Calls where the rep cited a positioning point from the deck: 19. Calls where the rep named a competitor the deck does not list: 47.

She opens the win-loss log. 34 closed-lost deals in Q3 with a competitor reason attached. The top reason reads "went with Competitor B" 14 times. Competitor B is on the deck. The battlecard for Competitor B carries a pricing claim that stopped being true in May, a feature-gap column the vendor closed in June, and a proof point sourced from a G2 review written in 2024. The AE opens the battlecard before the second call, reads the pricing line, quotes it to the prospect, and the prospect corrects the AE on the demo. The deal moves to closed-lost with a reason that reads "trust issue."

The founders in this seat keep asking the PMM to "refresh the battlecards this quarter" and wondering why the sales cite rate on competitors sits under 25 percent. Competitive intel is not a slide deck. Competitive intel is a five-stage queue that starts with a signal firing on a competitor's site and ends with a rep landing the right counterpunch inside a live call. Four surfaces feed the queue and none of them own it end to end.

The four competitors on the deck and the eleven the prospects name

Pull the Gong transcripts for the trailing 90 days and rank every competitor name mentioned by a prospect. The deck lists four. Prospects name fifteen. Eleven of those fifteen mentions carry no battlecard, no positioning, no proof point, no objection handler. The AE hears "we are also looking at Competitor G" on the discovery call and the rep responds with "great, I can send you a comparison." The comparison never lands because the PMM never wrote one.

Sort the eleven unlisted competitors by mention frequency. The top three account for 62 percent of the unlisted volume. One is an incumbent that pivoted into the category eight months ago and the PMM never scanned the release notes. One is a $12M seed startup that shipped a wedge product against the exact ICP in June and closed three head-to-head deals against you in July. One is an adjacent platform the buyer is stitching together with two point tools to avoid your price band, and the AE has zero framing for the "build versus buy against three vendors" conversation.

The Series B version of this function runs a nightly scan against the top 25 named vendors in the trailing 180 days of Gong transcripts, G2 category pages, LinkedIn ad libraries, and TechCrunch funding feeds. Every new competitor named on more than two calls in a rolling 30-day window fires a battlecard-generation task the next morning. The battlecard lands in the shared drive with a draft positioning statement, three proof points sourced from public evidence, a pricing estimate from the vendor's site or their partners' resale listings, and a three-line objection handler the AE can read in the browser tab during the live call. The four-competitor deck grows to the fifteen the prospects name, and the sales cite rate moves from 23 percent to the low sixties inside a quarter.

The five signals firing every day nobody wires into the battlecard

The competitive surface fires signals every day the PMM never reads. G2 posts 47 new reviews across the tracked category in a rolling 30-day window. Competitor changelogs publish 22 releases in the same window. LinkedIn Sales Navigator flags 14 buyer-committee members at target accounts who joined a competitor's user group in the last two weeks. The pricing page of the top-three competitor updated three times in Q3. The public roadmap of Competitor B shipped four features that overlap the objection handler the deck still cites as a moat.

None of the five signals rewrite the battlecard inside the week. The PMM opens the shared drive Friday afternoon when the CMO pings her about a lost deal, reads the outdated slide, and drafts a note that reads "will refresh next sprint." The refresh does not ship because the PMM owns four launches, two analyst briefings, the case-study pipeline, and the ICP research the PMM launch tracker already reads late every quarter. The competitive intel queue lands at the bottom of the priority stack and stays there.

The Series B version wires every signal into a battlecard update loop that fires inside 24 hours of the signal landing. A G2 review with a 3-star rating against a competitor and a specific feature complaint routes to the objection-handler section with the reviewer quote and the review link attached. A competitor release note that closes a feature gap the battlecard cites as a moat flags the moat as expired and drafts a replacement talking point sourced from the current product surface. A pricing-page change on the top-three competitor updates the pricing column with a timestamp and a diff. The PMM stops writing the battlecard from scratch on a Friday afternoon and starts reviewing 15-minute exception patches from her Monday queue.

The live-call layer that turns intel into revenue

The battlecard sitting in a shared drive nobody opens is a shelfware asset. The signal that a battlecard is working is whether the AE cites it inside the next 48 hours of live calls. Instrument the Gong feed against the battlecard content and the cite rate becomes the number that predicts the win-rate delta against a named competitor. Three surfaces decide whether the AE reads the card before the call.

The stuck version of this function ships a quarterly battlecard refresh, sends it to sales in a Slack post with three fire emojis, and never wires the content into the surface the AE reads inside the call. The AE opens Salesforce, reads the account plan, joins the Zoom, and the battlecard sits in a Notion page four clicks away. The Series B version pushes the battlecard summary into the Salesforce opportunity record as a pinned card the AE reads inside the browser tab during the call, into a Chorus or Gong pre-call brief that fires 30 minutes before the meeting, and into the Slack DM the AE reads while pouring coffee at 8:47 AM.

Wire the loop back the other way. Every Gong call tagged with a competitor mention routes a two-question ping to the AE inside the hour: which battlecard line did you cite, and what did the prospect push back on. The answers feed the next battlecard update. The copilot seat the CRO bought last year drafts a summary of the last 30 competitive calls the PMM reads in six minutes on Monday. The battlecard stops being a Q1 artifact and starts being a living document that ships a new version every ten days on the strength of the field feedback the AE would never have written into a shared drive.

The unit economics of a Senior PMM against an agent stack

Run the two paths against the Senior Product Marketing Manager req sitting in the drafts folder at $175K base plus 15 percent variable and equity refresh. Path A closes the req in October, ramps the PMM through Q1, and adds a second body to the two-person PMM team already carrying launches, analyst work, and the case-study pipeline. Loaded year-one cost lands $242K to $286K for the PMM. Competitive intel gets 20 percent of her calendar because launches eat 60 and analyst prep eats another 15. The battlecard refresh cadence moves from quarterly to every six weeks. Sales cite rate on named competitors moves from 23 percent to 34. Win rate against Competitor B moves from 41 percent to 44. Sourced revenue lift reads two additional closed-won deals a quarter at $340K.

Path B ships a two-sprint fractional AI competitive intel function at $56K to $84K in build across the first 30 days and $4K to $7K a month to run. Sprint one lands the competitor-scanning layer against Gong transcripts, G2, LinkedIn, changelogs, funding feeds, and the pricing-page monitor. Sprint two lands the battlecard-generation and update loop against the signal stream plus the live-call push into Salesforce, Gong pre-call briefs, and the Slack routing.

The fractional AI department runs the CI queue on the cadence the signals fire, not the cadence a PMM can squeeze in on a Friday afternoon. Loaded year one lands $104K to $168K plus a fractional PMM lead at $5K a month who owns the positioning judgment, the message architecture, and the exception review. Total $164K to $228K against a $242K to $286K path A. Battlecard count grows from 4 to 15. Sales cite rate on named competitors moves from 23 percent to 64. Win rate against Competitor B moves from 41 percent to 57. Sourced revenue lift reads nine additional closed-won deals a quarter at $1.5M against the same AE headcount. The 14-day sprint that stands up the scanning layer costs less than the analyst-firm subscription the PMM renewed in July.

The four numbers a CMO runs before the next PMM req

The founders reading this are three weeks from posting a PMM req on the strength of a "we need better competitive positioning" narrative. Before the offer letter goes out, run four numbers against the CI function, not the headcount. Score the queue, not the hire.

Battlecard coverage ratio. Divide the number of competitors with a current battlecard by the number of unique competitors named by prospects in Gong across the trailing 90 days. A healthy function runs above 80 percent. A stuck function runs 25 to 35 percent, and the AE hears eleven competitor names the deck never mentioned.

Battlecard freshness. Measure the median days since the last edit across every active battlecard. A healthy function runs under 21 days. A stuck function runs 90 to 180 days, and the pricing claim on the top-three competitor stopped being true two quarters ago.

Sales cite rate. Divide the sales calls where the AE cited a battlecard positioning point by the calls where a prospect named a competitor in the trailing 30 days. A healthy function runs above 60 percent. A stuck function runs under 25 percent, and the battlecard sits four clicks away from the surface the AE reads before the call.

Win rate delta against named competitors. Compare the win rate on deals where a named competitor appears in Gong against deals with no competitor mention. A healthy function runs within 8 points. A stuck function runs 18 to 26 points down, and the CFO opens the board pack asking why the head-to-head loss column keeps growing. Any two numbers in the stuck zone means the queue is the problem, not the headcount, and you can scope the CI function in a 30-minute call this week.