How to keep your battlecards updated: 3 levels of automation

TL;DR

Method 1: The manual approach
Method 2: A Claude Cowork workflow
Method 3: A dedicated competitive intelligence tool
Which approach is right for you?

Battlecards go stale so fast

Every PMM knows the feeling: you spend hours building out a battlecard, finally get it into the hands of your sales team, and within a few weeks someone's flagging that the pricing is wrong, or they now offer the same feature as you do.

Your competitors are evolving every week, and a lot can change in 3–4 weeks:

Pricing adjustments. New tiers, seat-based vs usage-based shifts, introductory discounts that quietly become permanent.
Feature launches. Even small ones. A new integration, a refreshed dashboard, a capability that used to be Enterprise-only and is now in the base tier.
Messaging shifts. The language on their homepage changes. They stop talking about "ease of use" and start talking about "enterprise-grade security." That's a strategic signal, and your sales team needs to know.
Review trends. G2 and Trustpilot scores fluctuate. New complaints emerge that you can use in a deal. Old weaknesses get addressed and you shouldn't still be leaning on them.
Hiring changes. A competitor just posted five SDR roles in a market you operate in. That's worth knowing before it gets reflected in a dried up sales pipeline.

That's a lot of data points to keep track of for 3-4 or more competitors. Depending on your current situation, here are the 3 ways to keep your battlecards up to date

Method 1: The manual approach

This is where most PMMs and founders start.

How it works:

You decide on a battlecard refresh cycle. Maybe your industry is quite mature with big players that don't change so much so you can decide to refresh your battlecards once every quarter.

You build a set of bookmarks for competitor pricing pages, blogs, and G2 profiles. You set calendar reminders to check them every couple of weeks. When you spot something that's changed, you update the relevant battlecard section and ping sales in Slack with the updated battlecard.

Some teams go further and build a shared Slack channel where anyone who spots a competitor update can drop it in for visibility. When you notice a significant change, you could make an update in the moment or if it's not so significant, you can keep it noted for the refresh cycle to come around.

What it actually costs:

The time commitment is the obvious one. PMMs we've spoken to consistently report spending 3+ days per battlecard refresh-cycle on manual competitor research when they're doing this seriously across multiple competitors.

But the less obvious cost is cognitive overhead. You're carrying the mental load of remembering to check. Maybe during the time that the refresh cycle was meant to happen is a particularly busy week and it gets delayed.

Manual processes break during busy periods. When you're deep in a product launch, battlecard maintenance is at the bottom of the priority list and can be forgotten about until it becomes more pressing. And at that point, maybe you're already losing deals because of it.

Where it breaks down:

Inconsistency. You check when you remember to, not when something changes.
Coverage gaps. You can realistically monitor two or three competitors this way. Beyond that, something always falls through.
Distribution. You end up with many docs in a single folder and it becomes difficult to maintain good organization.
No history. It's not easy to see patterns in the changes over time.

Verdict: A legitimate starting point, and good enough for very early stage teams or those with one or two competitors. But the ceiling is low, and the anxiety is real.

Method 2: A Claude Cowork workflow

This is the approach that's been generating a lot of interest, and it's worth taking seriously because it does work as a semi-automated workflow.

Claude Cowork is genuinely capable of helping you build a more systematic competitor monitoring workflow. Here's what that looks like in practice.

How it works:

You set up a structured folder system on your computer like a /competitive-intelligence directory with subfolders for each competitor, raw data snapshots, and your battlecard outputs. Then you build a workflow where Claude helps you gather, analyse, and structure competitor information.

A typical setup looks like this:

You create a Claude Skill defining the skill to be a competitive intelligence analyst for your business.
Create a directory on your machine for each competitor you want to track and a file with the full list of competitors you want to track and all competitor sources.
Create a template prompt that you can copy/paste into the chat asking it to gather the competitor data for you, analyze it and create a new battlecard from the analysis it did. Be explicit about saving the data into the competitor directories that you created.
Claude generates a structured summary of changes: pricing updates, new features, messaging shifts.
When you want to update battlecards, simply paste the prompt to get Claude to gather the data, analyze it and create a newly updated battlecard that you can distribute to your team.

With a well-built prompt template, Claude can produce genuinely impressive analysis. It understands context, can interpret strategic signals, and writes output that's actually usable in a battlecard format.

Where it gets impressive:

If you invest the time to set this up properly, you get something meaningfully better than a manual process. Claude can hold a lot of context at once, spot patterns across multiple competitor inputs, and produce structured, well-written analysis in a fraction of the time it would take you to write from scratch.

Where it breaks down:

Here's the honest part: none of it happens automatically.

Every step in that workflow requires you to initiate it and be very intentional with the input and outputs you expect. Claude doesn't check competitor pages on its own. It doesn't remember what last month's pricing was unless you explicitly feed it the previous snapshot. It doesn't alert you when something changes because it has no idea anything changed until you ask.

The specific gaps:

No background monitoring. Claude Cowork has no persistent process running between your sessions. It only knows what you tell it, when you tell it.
Memory doesn't carry over. If you analysed a competitor last month, Claude has no recollection of that session. You have to manage the data continuity yourself. Saving files, naming them consistently, loading previous snapshots into each new session.
JavaScript-heavy pages cause problems. Many pricing pages render dynamically. Claude can misread or miss content entirely if it can't access the rendered version properly.
Accuracy isn't guaranteed. Claude can hallucinate pricing tiers that don't exist, or miss hidden enterprise pricing that isn't on the public page. You need to manually verify anything critical before it goes into a battlecard.
Team access is tricky. Your output lives in local files on your machine. If a sales rep needs the latest battlecard the night before a call they can't just pull it up, you have to send it to them.

The fundamental issue is that Claude Cowork is a brilliant tool for doing competitive analysis when you sit down to do it. But battlecard maintenance isn't a task you do once. It's a continuous process. And Claude Cowork requires you to be the system. you have to remember to run it, manage the data, and push the outputs somewhere your team can access them.

Verdict: A significant upgrade over pure manual work, and genuinely worth it for teams who have the technical inclination to set it up properly. But it's a workflow you maintain, not a system that runs. The reliability ceiling is still determined by how consistently you show up to operate it.

Method 3: A dedicated competitive intelligence tool

This is what you graduate to when the manual and semi-automated approaches hit their ceiling (which they will), usually around the time you're tracking 5 or more competitors seriously and sales starts pushing back on battlecard quality.

How it works:

A dedicated CI platform monitors your competitors continuously, across all the sources that matter - their website, pricing page, blog, G2 profile, LinkedIn, and more. When something changes, it surfaces that change to you rather than requiring you to go looking.

With Faro specifically, this works in two layers:

Layer 1: Continuous monitoring. Faro tracks your competitors across eight sources daily. Pricing page updated? You get an alert. New blog post that signals a strategic shift? Surfaced. G2 review trend changing? You'll see it. This happens in the background, without you needing to schedule a session or remember to check.

[Screenshot placeholder: Faro competitor alert feed — showing a real-time change notification for a competitor pricing update, with the specific change highlighted]

Layer 2: Context-aware analysis. This is where it gets interesting. Faro doesn't just show you what changed, it interprets the change through the lens of your specific business. You tell Faro your ICP, your competitive positioning, and how you go up against each competitor. When something changes, Faro factors in that context. A competitor adding an enterprise feature means something different depending on whether you're targeting the same segment.

[Screenshot placeholder: Faro battlecard view — showing auto-updated pricing section with a "Last updated" timestamp and summary of what changed]

What this changes for battlecard maintenance:

The monitoring work disappears. You're not checking sites, not running sessions, not managing file systems. Changes are reflected in battlecards immediately.

Distribution gets solved too. Because everything lives in Faro rather than on your local machine, your sales team can access current battlecards directly on the app or directly in Slack. When a section updates, they see the latest version. You can push Slack alerts when material changes happen so reps know to check.

[Screenshot placeholder: Faro Slack alert — "Competitor X updated their pricing. Enterprise tier now starts at £350/mo, up from £275/mo. Battlecard updated."]

The honest limitations:

No tool is magic. While Faro does setup your competitors and sources automatically, you still have to provide your business context. The analysis layer is only as good as the context you give it.

And a dedicated tool is a budget decision. If you're at a very early stage and tracking one competitor loosely, it's probably not where you start.

Verdict: The right approach for PMMs who are tracking five or more competitors seriously, are losing deals to outdated competitive positioning, or are spending more than a two days on manual competitor research.

Which approach is right for you?

The honest answer depends on where you are right now.

	Manual	Claude Cowork	Dedicated Tool (Faro)
Time cost	Hours-days	Hours–days	30 minutes
Monitoring	When you remember	When you run it	Continuous
Team access	Manual distribution	Manual distribution	Centralized access
Accuracy	Accurate	Needs verification	Data verification layers
Best for	Just starting out	Technical PMMs who want control	Teams tracking 5+ competitors seriously

Start manual if you're at the very beginning, tracking one or two competitors, and not yet losing deals because of outdated intel. Get a feel for what you need to monitor before investing in tooling.

Move to Claude Cowork if you're technically comfortable, want more structure and analytical depth, and have the discipline to run the workflow consistently.

Move to a dedicated tool if you're tracking five or more competitors, your team is in multiple active competitive deals, or you've had a moment where sales used outdated information in a live deal. That last one is usually the tipping point.

The goal in all three cases is the same: a battlecard your sales team can trust, updated fast enough to be accurate, and distributed in a way that means they're always working from the latest version.

The approach is just a question of how much of that you want to do yourself.

Curious how Faro handles battlecard updates automatically? See it in action →