A Competitor Battlecard Your Reps Actually Use
Turn 'how do we compare to them?' into a battlecard reps reach for mid-call — honest strengths, real weaknesses, and the trap questions that expose the difference.
A battlecard that only lists your wins is one reps stop trusting the first time it's wrong.
Useful competitive intel is honest: where you genuinely beat them, where they beat you, and the questions that make the real difference visible to the buyer. Store your positioning and what you keep losing on, and the card becomes a tool reps reach for, not marketing they ignore.
Reps can tell when a battlecard is spin. The moment it claims a win they've lost in the field, they file the whole thing under fiction.
A battlecard earns trust by being honest about where you lose — that's what makes its claims about where you win believable.
This is a sales tool, not a hit piece. Accuracy about the competitor matters; a card built on a strawman gets a rep embarrassed when the buyer knows better.
| Complexity | Easy |
| Tools needed | Claude Pro or above, Claude Desktop → Cowork mode, on macOS or Windows, Claude Projects |
| Time to build | ~25 min first time · ~10 min per competitor after that |
| Best for | Founder or sales lead who arms the team for competitive deals — B2B software and services |
What this solves
Reps freezing or overselling when a prospect names a competitor — and battlecards so one-sided the team stopped trusting them.
The problem
A prospect says “we’re also looking at [competitor],” and the rep freezes or oversells. Marketing made a battlecard once, but it’s a feature checklist where every row conveniently favors you — so reps don’t believe it, because they’ve lost deals on things the card claims to win. What they actually need in that moment is honest: where you really are stronger, where you’re genuinely not, and the one or two questions that make the difference obvious to the buyer without trashing the competitor. That kind of card takes real thinking to build, which is why it usually doesn’t get built — and the generic one gathers dust.
The fix is producing an honest, specific battlecard fast enough to keep current as competitors change.
Ingredients
- Claude Subscriptions — Cowork and Projects aren't available on the free plan
- Platforms & Modes — Cowork runs in the desktop app only — not on web or mobile. This recipe researches a competitor and builds a structured card — multi-step work that runs in Cowork
- Claude Projects — Your positioning and your real win/loss patterns are constant. A Project stores them so every battlecard is built from how you actually compete, not a generic feature grid
How it works
You compete against the same handful of players, and your positioning and win/loss patterns are constant. A Project stores them so every card is grounded in how you actually win and lose, and stays consistent across the team.
- Open Claude Desktop and click Cowork in the mode selector across the top (Chat · Cowork · Code).
- In the left panel, find Projects and click the + button.
- Choose Start from scratch. Name the project “Competitive Intel” or “Battlecards” and let Claude set up its folder.
- You’ll know it worked when the project appears in the left panel with its own folder and an instructions field.
Your project has a folder on your computer — that’s where the two working files live.
- Ask Claude, right in the project: “Create two files in this project’s folder:
positioning.mdandwinloss.md. Leave them empty — I’ll fill them in.” (Or create them yourself in any text editor and save them into the project folder.) - Fill in both files using the descriptions below.
- Confirm Claude can see them: ask “List the files you can see in this project.” Both filenames should come back. If they don’t, see If It Doesn’t Work.
positioning.md
What you’re genuinely good at and who you’re the right fit for — honestly, including the buyers you’re not right for. This anchors the card in reality.
Example: “We win with non-technical teams that value support and governance. We’re not the fit for buyers who want maximum configurability and have engineers to run it. Our edge: implementation speed and a real human on support.”
winloss.md
What you actually win and lose on against each competitor — the patterns from real deals, not the marketing story.
Example: “vs. [Competitor A]: we win on ease and support; we lose on advanced reporting and integrations count. They lose deals on slow onboarding. Their pricing is opaque — that’s a real friction we can name.”
Open your Project in Claude Cowork. Give Claude the specifics for this run, ask for the main output, then follow up for any additional pieces you want. The exact wording for each prompt — with what it’s asking for and why — is in What you actually type below.
Check three things before this goes to the team:
- It admits where you lose. A card with no honest weaknesses is one reps won’t trust. Confirm the “where they win” section is real, not a backhanded compliment. That honesty is what makes the rest credible.
- The competitor claims are accurate. A card built on an outdated or wrong description of the competitor gets a rep embarrassed when the buyer knows the product better. Check that public claims are current and that inferences are flagged as such.
- The questions surface difference without mudslinging. Good discovery questions let the buyer notice the gap themselves. If the suggested moves are attacks on the competitor, they’ll backfire — push for questions, not jabs.
Before it ships: does it match what your reps see in the field? Pull in a rep who’s lost to this competitor and check the card against their experience. Real deal knowledge is the truth-test no research replaces.
What you actually type
Name your files explicitly the first few runs, and ask Claude to show its work on anything that matters.
“Build a battlecard for [Competitor A] using `positioning.md` and `winloss.md`, plus current public info on them. Give me: where we honestly win, where they win (don't spin it), two discovery questions that surface our advantage without trashing them, and how to respond when a buyer says 'we're also looking at them.' Flag anything about the competitor you're inferring vs. confirmed.”
“Tighten this to a single screen a rep can glance at mid-call.”
A single-screen battlecard with four labeled parts: where you honestly win, where the competitor wins, two discovery questions that surface the difference, and a response to 'we're also looking at them.' Claims about the competitor are labeled confirmed or inferred. If the 'where they win' section is empty or reads like a backhanded compliment, it missed — the card isn't honest enough for a rep to trust.
- It doesn't know your deals. The win/loss patterns come from `winloss.md` — a card built without real field data is a guess about how you compete.
- Public info on the competitor goes stale. Pricing pages change and features ship; re-check before a big deal, and keep the monthly refresh from Extra Credit.
- It won't win the deal. The card arms the conversation; the rep still has to ask the discovery questions and listen to the answers.
If it doesn’t work
- No Cowork tab in Claude Desktop — update the app to the latest version and confirm you’re on a paid plan; Cowork isn’t on the free tier. On Windows, Cowork also needs the Virtual Machine Platform feature enabled — if the tab still won’t appear, that’s the fix.
- Claude can’t see
positioning.mdorwinloss.md— the files aren’t in the project’s folder, or they’re in a different folder than the one the project owns. Open the project, check which folder it points to, and move the files there. Then re-run “list the files you can see.” - The card claims a win your reps keep losing — your
winloss.mdis the marketing story, not the field record. Add the deals you actually lost and what you lost them on, then rebuild. The card can only be as honest as the file behind it. - The discovery questions read like attacks on the competitor — jabs backfire the moment the buyer likes the other product. Ask: “Rewrite the questions so the buyer notices the gap themselves — no mention of the competitor’s weaknesses.”
Extra credit
Small additions that pay back the next time you run it.
- Interactive card — build it as a live artifact with a tab per competitor so reps open one page instead of digging through docs.
- Keep it current — set a scheduled task to re-check each competitor’s public changes monthly and flag what moved.
- Feed it win/loss — after competitive deals, paste the outcome into
winloss.mdso the cards sharpen on real results, not assumptions.
“The battlecard a rep trusts is the one that admits where you'd lose — because then they believe it about where you win.”
What this teaches you about Claude Cowork
The recipe is one application. The principles apply to everything you’d hand to Claude.
Honesty is the feature. A battlecard’s value is trust, and trust comes from admitting where you lose. Storing your real win/loss patterns is what lets the card be honest — which is exactly what makes reps reach for it instead of ignoring it.
Accuracy about the other side matters. The card is only as good as its description of the competitor. Flagging inferences and checking public claims keeps a rep from confidently stating something the buyer can disprove on the spot.
Field truth beats research. Claude assembles the card; your reps’ real experience validates it. The recipe is strongest when it pairs fast research with the deal knowledge that only the people in the room have.
Who this is for
Founder or sales lead who arms the team for competitive deals in B2B software and services (5–100 employees).
The pain: Reps freeze or oversell when a prospect names a competitor
The outcome: Every competitive deal runs on an honest card the rep reaches for mid-call
Published June 25, 2026 · 0 views