Your Battlecard Is From 2024

It is Thursday afternoon. Your top AE is on a closed-lost call with the prospect she had been working since February. The buyer says they went with the competitor because of the workflow automation feature, the SOC 2 Type II, and a price that was nine percent under your floor. Your AE writes Pavilion in her notes and closes the tab.

You open the battlecard for that competitor in your sales wiki. It was last edited in October 2024. The feature column says No workflow automation, the security column says SOC 2 Type I in progress, and the pricing column lists a number that has been off by twenty percent for three quarters. The talk track at the bottom of the page is one your VP of Sales wrote when the company was a Series Seed and the competitor had forty employees.

Competitive intel is a function. Most Series A and B companies have not staffed it. Every six-figure deal that goes to a competitor routes through the gap between the live competitive landscape and the battlecard nobody has updated. On the org chart, the function sits nowhere. In the calendar, it eats one PMM afternoon a quarter and a Slack channel called #compete that twelve people muted in 2025.

The battlecard is the last document anyone trusts

Pull the last twenty closed-lost deals over fifty thousand ACV. For each one, log the competitor named and the date the matching battlecard was last edited. Most companies see a median of nine to fourteen months. Some battlecards have not been touched since the AE who wrote them left the company. Two or three competitors that showed up in the loss column are not on the wiki at all.

Walk through how the AE uses the page. Discovery call, prospect mentions the competitor, the AE alt-tabs to the wiki, reads the first paragraph, decides it is stale, and falls back to whatever she remembers from the last loss to that vendor. The talk track she uses on the call is improvised. The objection handling she gives is two quarters old. The pricing comparison she puts in the follow-up email is wrong by a margin the buyer notices.

The team that should own this knows it is broken. The VP of Sales asks the PMM to refresh the top three battlecards every quarterly business review. The PMM owns ten other launches and ships the refresh six weeks late, covering only the top one. The CS team forwards screenshots of competitor release notes into #compete and nobody reads them. The sales engineer finds out about the competitor's new feature on a live demo when the prospect asks why your product cannot do it.

The cost shows up as a win rate that drifts by two to four points a quarter against named competitors. The CRO writes it off as a tougher market. The board pack shows the slide and moves on. The real read is that the team is losing deals to features that shipped eight months ago, to pricing that moved six months ago, and to security postures that closed three months ago, because nobody is paid to know.

Hiring a competitive intel manager is the slow answer

The textbook fix is a competitive intelligence manager or a senior PMM with a comp focus. Loaded comp in the US runs one hundred fifty to two hundred twenty thousand a year. Months one through three go to interviewing the AEs, reading the last fifty loss notes, and rebuilding the top five battlecards from scratch. Months four through six are when the cadence locks in at one full refresh every two months and a Slack digest every Friday.

The output is good on the top three competitors. The other twelve names that show up across the pipeline get a stub page and a promise to update next quarter. The win loss program that should feed the battlecards runs at six interviews a quarter because the manager is also writing the cards, the digest, and the QBR slide. The cadence is one refresh every eight to ten weeks per competitor. The competitor ships product every three.

The fractional version is faster to start and stops at the same wall. Six to twelve thousand a month buys a fractional competitive contractor with twenty hours of senior time. The top three competitors get a clean monthly refresh. The long tail of ten to fifteen names stays stale. The Slack digest goes out, the AEs scan the subject line, and the talk track on the live call is still the one from last quarter because the digest does not live where the AE works.

Both versions assume the work is human bottleneck work. Read the competitor's release notes, their pricing page, their job board, their Glassdoor reviews, their G2 page, and their last earnings call if they are public. Rewrite the battlecard, brief the AEs, update the deck slide, update the discovery script, update the objection-handling doc. On fifteen competitors that is sixty to ninety hours of work a month. No manager clears that pile and also keeps a win loss program running.

What a fractional AI competitive intel function does

Hand the competitor list, the win loss notes, the CRM, the deal-desk pricing log, the battlecard library, the sales deck, and a list of public sources to an agent that runs every business day. The agent does the work a competitive PMM and a sales engineer would do together. The cadence is daily on signal, weekly on battlecard diffs, real-time on live calls when wired into the conversation intelligence tool. The PMM stops being the bottleneck on every refresh.

Daily signal sweep across every named competitor. The agent watches release notes, changelogs, pricing pages, job board postings, LinkedIn product posts, G2 review velocity, and SEC filings where they apply. Anything that changes gets a one-line diff in the right battlecard the same day. The PMM gets a digest of the diffs that matter on Friday morning, not a stale dump of every blog post the competitor published.

Battlecards that rewrite themselves against the diff. When the competitor ships workflow automation, the feature column updates the same day, the talk track gets redrafted against the new gap, and the objection handling gets a new entry for the AE to use the next call. The PMM reviews and approves in fifteen minutes instead of writing from scratch in four hours. The card the AE opens on Thursday afternoon reflects the world as of Thursday morning.

Win loss program that feeds the battlecards. Every closed-lost over a threshold triggers an interview brief drafted from the CRM notes, the email thread, and the deal-desk log. The agent runs the interview through a structured template, transcribes it, codes the reasons against a fixed taxonomy, and writes the patterns back into the battlecard for that competitor. Sixty interviews a year instead of six. Same shape the audit trail takes on the finance side.

Real-time prompt during the live call. When the prospect names a competitor on a Zoom call, the AE sees the current battlecard summary in a sidebar with the three talk-track lines that match the deal context. No alt-tab to a stale wiki page. No improvisation. The AE who has been at the company eight weeks runs the same competitive motion as the AE who has been there four years.

Pricing intelligence the deal desk uses. Every time the competitor's published pricing changes, every time a deal desk hears a quote from a prospect, every time a procurement contact leaks a number, the pricing log updates. The deal desk approving the discount on Tuesday has the real market price, not the number from the battlecard that was right in Q3 of last year. Same shape the renewal motion takes on the retention side.

The unit economics of a stale battlecard

A company doing one hundred fifty enterprise deals a year against fifteen named competitors with a forty percent win rate is losing ninety deals. Conservatively, ten to fifteen of those losses ride on a feature gap that has already closed, a pricing read that is wrong, or a security posture that has shifted. At an average ACV of seventy-five thousand, the revenue left on the floor is in the high six to low seven figures. The CRO sees the win rate drift and the CFO sees the missed plan, and neither one ties them to the wiki page nobody updated.

Layer in the direct spend most companies eventually add. A competitive intel manager at one hundred eighty thousand loaded, a competitive intel tool at thirty to sixty thousand a year, and a fractional contractor at seventy to one hundred thousand to fill the gaps. Call it two hundred eighty to three hundred forty thousand a year of run rate against a function that still ships a refresh every eight weeks and still misses the long tail. The win loss program runs at six interviews a year against a target of sixty.

A 14-day sprint to stand up the agent runs in the low to mid five figures. Ongoing cost lands closer to one senior contractor than a competitive team. The top three competitors get a daily refresh. The long tail of twelve names goes from stale to current. The win loss program runs at sixty interviews a year instead of six. Same shape we ran for the hiring function. Function, not headcount.

The harder number to price is the AE confidence line. An AE who walks into a discovery call knowing the current state of every competitor in the deal closes a different conversation than one who is improvising off a Q3 memory. The card she opens reflects yesterday, not last October. That is the part of competitive intel that pays for the function five times over, and it only works if every card moves at the speed the competitor moves.

What changes after the sprint

Picture the same Thursday afternoon, fourteen days after the 14-day sprint ships. The AE opens the call with the prospect who has been weighing your product against the same competitor for six weeks. The battlecard in her sidebar was refreshed at 6 AM that morning with three diffs: the competitor raised list pricing nine percent on Monday, their SOC 2 Type II report landed last Tuesday, and the workflow automation feature is now in general availability for the enterprise plan only. The PMM signed off on the rewrite over coffee.

The talk track has been rewritten against those three diffs. The objection handling for the price gap is current. The discovery questions the AE asks land on the seams that have opened in the competitor's product over the last three weeks. The follow-up email goes out at 4 PM with a pricing comparison the deal desk approved that morning. The deal closes at the original ACV on the original timeline.

If your battlecards were last edited eight months ago and your top AE is improvising every time a competitor's name comes up, the version where every card reflects yesterday and every AE runs the same competitive motion is fourteen days away. Competitive intel is a function. You can hire against it, you can buy another SaaS for it, or you can scope a sprint and have it running this month. The work is the same. The math is not.