Your Competitive Battlecards Are 14 Months Old

It is Thursday, 2:14 PM. Your AE has a $220K ACV deal on a demo call in 46 minutes. She opens the Notion page labeled Battlecards. Six cards, last edited April of last year. The prospect named a competitor in the discovery call that does not appear on any card. The pricing tier on the card for the incumbent shows a starter plan that competitor killed nine months ago. The win themes list a feature parity gap that closed in Q3.

She opens Slack, drops a message in #compete, and asks if anyone has notes on the missing competitor. Two engineers who saw the vendor at a conference reply with impressions. The head of marketing sends a Loom from six months ago that references a webinar the vendor ran on positioning. The AE walks into the demo with three-sentence memory notes and no pricing, no win themes, no proof points, no landmine questions.

The deal goes to a second call. The prospect asks a follow-up question the AE cannot answer without pinging the vendor's public pricing page live in the meeting. The forecast slips from Q3 to Q4. The head of sales asks the CMO why the battlecards are stale. The CMO asks the product marketing manager, who left in February. Nobody has owned competitive intel for eleven months.

Competitive intel is a function. Most Series B and C companies have not staffed it because the last update ran through a product marketing manager who owned three other functions and left. The function lives in the gap between the AE who needs a card an hour before a call, the sales engineer who watches competitors ship on Twitter, the CS lead who hears churn reasons every Tuesday, the CMO who owns positioning, the CRO who watches win rate slip against one specific competitor, and the founder who reads every closed-lost note. On the org chart it sits under Product Marketing. In practice it sits inside a Notion page nobody edits.

The 14 months of drift

Pull the last edit date on every battlecard in your enablement library. Count the days since the last competitor pricing change was captured. Count the closed-lost notes from the last four quarters that name a competitor with no card at all. Most companies past Series A find four to nine cards, three to six competitors missing, and 40 to 70 percent of closed-lost notes citing pricing, features, or positioning that the current cards do not address.

Walk one card. The incumbent's pricing page changed twice since the last edit. Their Series C landed in November and their enterprise motion shifted from land-and-expand to a top-down annual contract. Their new AI feature ships to 12 percent of their base and is the reason two of your last six losses happened. Their CSAT dropped after a botched migration in Q1 and their VP of Product left in March. None of that lives on the card. All of it lives in a Slack channel with 640 messages, a Gong library nobody indexed, and four Reddit threads the sales engineer bookmarked.

The team that should own this knows it is broken. The AE opens the card an hour before the demo and closes it inside two minutes. The sales engineer builds a personal cheat sheet in Apple Notes and shares it with three peers. The CS lead hears the same three churn reasons every quarter and writes them into QBR decks that never route back to sales. The win-loss interview never happens on the losses that would name the competitor's new pricing. The function sits unstaffed while the win rate against one specific competitor drops from 42 to 29 percent over four quarters.

Hiring a product marketing manager is the slow answer

The textbook fix is a competitive intel lead or a product marketing manager with a CI focus. Loaded comp in the US runs $140K to $210K a year. Months one through two go to reading the last two quarters of closed-lost notes, indexing the Gong library, and mapping the current card set against the top six competitors. Months three through six are when the first two cards get a full rebuild, the third competitor gets a card at all, and the AE sees a fresh landmine question in an enablement Slack thread the week before her demo.

The fractional version is faster to start and stops at the same wall. Six to ten thousand a month buys eight to twelve hours a week of senior CI time. The first month ships two rebuilt cards and one net-new card. Two months in, the operator gets pulled into a positioning refresh for a product launch, and the next competitor pricing change sits uncaptured for eleven weeks.

Both versions assume the work is a person maintaining a card. The work itself is watching every competitor's pricing page, changelog, careers page, LinkedIn hires, Reddit and G2 reviews, and public earnings notes on a daily cadence. Parsing every closed-lost note and every Gong call for competitor mentions inside 24 hours. Drafting the pricing update, the win theme edit, and the landmine question against the specific deal shape it affects. Routing the two-sentence brief to the AE working the account with the vendor named. On six competitors that is 50 to 80 hours a month of senior CI work, plus a rebuilt card shipping every two weeks.

What a fractional AI competitive intel function does

Hand the current battlecard library, the Gong library, the closed-lost notes from the last four quarters, the CRM competitor field, the CS churn reasons file, the public pricing pages, the changelog RSS feeds, and the AE inbox to a fractional AI agent that runs on a daily cadence. The agent does the work a competitive intel analyst, a product marketing manager, and a sales enablement lead would do together. The cadence is daily on competitor signals, per-deal on landmine briefs, weekly on card refreshes, and quarterly on the positioning rebuild. The output lands where the AE already reads, not on a page she has to remember to open.

Every competitor pricing change captured inside a day. The nine-month-old starter plan comes off the card the day the vendor kills it. The new AI tier lands on the card with the exact price, the packaging, and the two features it locks behind the higher plan. Same shape as the pricing page function on the sales side, run on the compete side.

Every closed-lost note parsed for competitor mentions inside 24 hours. The 47 losses last quarter that named a competitor route into a heat map by competitor, by deal size, by industry, and by the specific reason. The CRO reads a Monday brief showing the three losses this week, the vendor named, and the recurring theme. The win rate against the specific vendor stops being a number the CRO discovers on the board pack.

Landmine questions drafted per-deal, per-competitor, per-industry. The AE walking into a Thursday 2:14 PM demo gets a two-page brief at 10 AM the same day. Three landmine questions specific to the competitor and the industry, the two proof points that reliably close the gap, the pricing anchor that reframes the conversation, and the one migration risk to name before the buyer names it. The brief pulls from the exact Gong moment the AE's peer used the same play last month.

New competitors get a card the week they enter a deal. The competitor named in Tuesday's discovery call has a card by Thursday. Public pricing, feature set, three known wins and three known losses from public sources, the two AE peers who have seen them before, and the two landmine questions to run in the next call. The AE walks into the second call with a card that did not exist 48 hours ago.

Every AE gets a Monday brief on the six competitors in their pipeline. No AE watches six competitors. Every AE watches the two in their next four deals. The Monday brief names the pricing move, the personnel change, and the product ship that affects those two vendors. The reads take four minutes and inform every discovery call that week.

The unit economics of a stale battlecard

A Series B company at $16M ARR working four enterprise deals a quarter is burning three specific things when the battlecards run 14 months old. Win rate against the top two competitors drifts three to six points a year. On 40 competitive deals a year at $180K to $340K ACV, three points of win rate is $216K to $408K of pulled-forward revenue that lands with the competitor instead. Six points doubles the number.

The AE and sales engineer time on ad-hoc research is the second line. Every AE spends 45 to 90 minutes prepping for a competitive demo when the card is stale, against 8 to 12 minutes when it is fresh. On 40 competitive demos a quarter that is 25 to 55 hours of AE time and 15 to 25 hours of SE time on work a CI function covers, against a fully loaded hour of $180 to $260. That is $7,200 to $20,800 a quarter of senior sales time on research a card should have shipped.

The forecast accuracy line is the third. A CRO who cannot name the specific competitor pricing move driving the current quarter's slip runs a forecast the board discounts. The product marketing hire runs $150K to $210K loaded with a three to five month ramp before the second card ships.

A 14-day sprint to stand up the agent runs in the low to mid five figures. Ongoing cost lands closer to one contractor than a PMM hire. The first two rebuilt cards ship in week one. The first net-new card ships in week two. The Monday brief runs to every AE before the sprint closes.

What changes after the sprint

Picture the same Thursday, 2:14 PM moment, thirty days after the sprint ships. The AE opened the card at 10:04 AM after her Monday brief flagged the vendor as one of the two in her pipeline this week. The card carries the current pricing, the AI tier that shipped in November, the two known wins from the Gong library, the three landmine questions specific to the buyer's industry, and the migration risk her peer used to close a similar deal in June. The sales engineer read the same brief on his phone at 9:40 AM.

By the second call the AE knows the vendor killed the starter plan, has a proof point ready when the buyer asks about the AI tier, and runs the migration-risk landmine at minute 14. The buyer names the risk as the reason they are hesitating on the incumbent. The deal moves to procurement in the current quarter, closes at $240K ACV in September, and the closed-won note names the specific play. The card gets an edit that afternoon on the play that worked.

If your battlecards currently live on a Notion page last edited fourteen months ago and your AEs walk into demos with a Slack thread instead of a brief, the version where every AE reads a Monday brief on the two competitors in her pipeline and a per-deal landmine brief lands the morning of the demo is fourteen days away. Competitive intel is a function. You can hire a PMM for it, you can retain a fractional CI operator for it, or you can scope a sprint and have it running this month. The work is the same. The math is not.