# Sales battlecards for a small team: one page per competitor, kept alive from Pipedrive lost reasons

https://salesbond.app/blog/sales-battlecards-small-teams-pipedrive/
Published: 2026-10-02 · Updated: 2026-10-25

A sales battlecard is one page about one competitor: where you are stronger, where you are weaker, which questions to ask early, and what to say back to the three objections that competitor’s name brings into the room. A small team does not need a library of them. Two or three cards, for the competitors that actually show up in your lost deals, with one named owner and a fifteen-minute check once a month, will do more than a folder of twelve that nobody opens.

The guides that rank for this are written for product marketing. They skip the part that kills a card in a five-person team: who writes it, where the facts come from, and how it’s still true in April. That part is what this article covers, with the mechanics in Pipedrive.

## Which competitors deserve a card

Not the ones you worry about. The ones your reps keep losing to.

Ask a team to list its competitors and you get the well-funded one everyone has heard of. Look at two quarters of lost deals and the name that comes up most is often a regional shop nobody listed. [New Breed’s battlecard guide](https://www.newbreedrevenue.com/blog/create-a-competitive-battlecard) defines top-tier competitors as the ones that come up in practically every sales conversation, and that is the right test. The only honest way to run it is by counting.

Counting needs a place to write the competitor’s name. We recommend a custom deal field called *Competitor*, with a fixed list of names plus “None” and “Other”, rather than free text, because “Ridgeline” (a made-up competitor we’ll use throughout), “ridgeline inc” and “RL” are three rows in a report that should be one. In Pipedrive you create it from the account menu under Personal preferences > Data fields, choose the deal entity and click “+ Custom field”. The field then shows in the deal’s detail view and can be added as a column in the list view through the gear icon ( [Pipedrive: custom fields](https://support.pipedrive.com/en/article/custom-fields)).

If the field stays empty on half the deals, which it will at first, Pipedrive can mark it as important for a stage, so the deal shows a notice that data is missing. Or it can make the field required, and then a deal won’t move to that stage until someone fills it in. Both are set under Settings > Data fields, and both depend on your plan ( [important fields](https://support.pipedrive.com/en/article/important-fields), [required fields](https://support.pipedrive.com/en/article/required-fields)). We would start with important, not required. A rep who is blocked from moving a deal picks “Other” and moves on.

Then count. In the deals list, filter for lost deals, add the Competitor column, and sort. Pipedrive’s advanced filters combine conditions with ALL and ANY groups, so a saved filter for *status is lost* and *Competitor is Ridgeline* over the last twelve months takes a minute to build ( [Pipedrive: filtering](https://support.pipedrive.com/en/article/filtering)). Do the same for won deals. Lose to a competitor five times and it gets a card. Lose to it once and it’s a note, not a page. When the name comes up in a formal [head-to-head evaluation](https://salesbond.app/blog/competitive-bake-off-pipedrive/), the card is what you prepare from.

Where the line sits depends on your volume. Our rule for a few dozen deals a quarter: a card for any competitor named in more than a handful of lost deals over six months, and never more than three cards. The third one already goes stale first.

## What goes on a sales battlecard

One page, six blocks, and a rule from [Competiflow’s battlecard guide](https://competiflow.com/blog/competitor-battlecards-guide/) that we agree with completely: if a rep cannot act on it in the middle of a conversation, it is not battlecard content. Market sizing, funding rounds and a forty-row feature grid go somewhere else.

![Battlecard for a made-up competitor with six blocks: who they are, where we win, where we lose, objections, questions to ask, checked on](https://salesbond.app/wp-content/uploads/2026/10/sales-battlecards-small-team-pipedrive-2.png)

1. **Who they are, and who they win with.** Two lines. “Ridgeline sells to operations teams at 50 to 200 people and wins when the buyer wants a longer implementation with a consultant attached.”
2. **Where we win.** Two facts you can prove, not adjectives. Setup time, a specific capability, a contract term. If the fact came from a buyer, write the buyer’s words.
3. **Where we lose, and what to say about it.** The block that’s easiest to leave out, and the one that saves reps from being ambushed. “They have a native integration we don’t. Say so, then ask how many people would actually use it.”
4. **The three objections this name brings, with our reply.** Not all objections. The three that show up when this competitor is in the deal. Your [objection log](https://salesbond.app/blog/objection-handling-pipedrive-log-coach/) already has them if you keep one.
5. **Questions to ask early.** Two or three questions that surface the competitor’s weak spot without naming them. “When does your team need to be live in the tool?”
6. **Checked on, by whom, from what.** A date, the owner’s name, and the links the facts came from.

What to leave off: the competitor’s prices, unless each number carries a date and a link to the page it came from. Competiflow’s guide puts the problem well: some blocks on a card hold for a year, others can be wrong a week after you publish, and the card shows one date for all of them. Prices are the clearest case of the second kind, so we put the competitor’s pricing page URL in block 6 instead. The rep opens it and reads today’s number.

The other thing to leave off is anything you could not say with the competitor in the room. Cards get forwarded.

## Fill it from your own lost deals, not from the competitor’s site

The competitor’s website tells you how they want to be seen. Your lost deals tell you why buyers chose them over you, which is the only thing the card is for.

Start with the lost reasons. When a deal is marked lost, Pipedrive asks for a reason, and any comments typed with it are saved as a note on the deal, visible in the detail view ( [Pipedrive: lost reasons](https://support.pipedrive.com/en/article/lost-reasons)). So every lost deal with Ridgeline in the Competitor field has a reason and, if the rep bothered, a sentence of context. Ten lost deals with thier notes take twenty minutes to read and give you blocks 3 and 4 in rough form.

We wrote up how to make the reason list worth reading in [lost reasons in Pipedrive](https://salesbond.app/blog/pipedrive-lost-reasons/). That article suggests putting the competitor’s name in the note field; once you have the Competitor field, the field does that job and you can count it.

Then the won deals against the same competitor. Those are block 2: the moment the buyer stopped asking about Ridgeline. Can’t find it in the deal history? Ask the rep who closed it. They usually remember the sentence that turned it.

Then, if you have the afternoon, the buyer. The lost reason is the rep’s version, and [win-loss analysis for a small team](https://salesbond.app/blog/win-loss-analysis-small-team-pipedrive/) gets you the buyer’s; when the two differ, the buyer’s sentence goes on the card in quotes.

Only then open the competitor’s website, to check facts for block 6. Not to write the card.

## Put the card where the rep is when the name comes up

A battlecard in a shared drive gets read during onboarding and never again. It’s needed the moment a buyer says “we’re also looking at Ridgeline”, and at that moment the rep is in the deal, not in the drive. [Pipedrive’s guide](https://www.pipedrive.com/en/blog/sales-battle-cards) suggests keeping cards somewhere searchable and connected to the CRM. For a small team, that place is the deal itself.

You could attach the card to every deal as a file. Six deals means six copies though, and five of them are wrong the day the owner fixes block 3.

What we do instead: the card lives in one place with a stable link (a shared doc, a wiki page), and the deal note holds that link plus the three questions from block 5. Those questions are the part a rep needs on the call without opening anything. Two lines in the note, and the link always opens the current version.

The Competitor field does the rest. A manager who opens the deal sees “Ridgeline” without asking, and in the weekly review the column shows which open deals are competitive right now.

## Keep it fresh: an owner and a fifteen-minute monthly pass

Who keeps a battlecard true with no product marketer? One senior rep. Not the manager, who won’t find the time, and not “the team”, which means nobody. Pick the rep who has won the most against that that competitor, put their name in block 6, and make the card their page. One owner for twelve cards is how a library dies.

The cadence we use is monthly, fifteen minutes, in the calendar. Competiflow lands close to that: a monthly 20-minute pass per owner, plus a refresh within 48 hours when a competitor changes its prices. A quarter is long enough for block 3 to go wrong, and fifteen minutes a month is cheap. The pass is the same every time:

- Open the saved filter: lost deals, this competitor, last 30 days. Anything new goes in block 3 or 4, in the buyer’s words.
- Open the won filter for the same period. Anything new goes in block 2.
- Click the sources in block 6. If a page changed, fix the line it feeds or delete the line.
- Change the date in block 6. If nothing changed, change the date anyway. The date is what tells a rep the card was looked at.

The input for that pass is a habit you may already have: the one-sentence rule from [lost reasons in Pipedrive](https://salesbond.app/blog/pipedrive-lost-reasons/), a sentence on every lost deal above a value threshold. When a competitor is involved the sentence names them and says why. “Chose Ridgeline, wanted the consultant-led rollout.” A month later the owner reads those and the card mostly writes itself.

## What a battlecard cannot fix

Run the count from the first section and you may find something uncomfortable: the competitor is not the reason you lose.

Put the Competitor column next to the lost reason (the report for that is in [lost reasons in Pipedrive](https://salesbond.app/blog/pipedrive-lost-reasons/)) and see where the deals split. Lost on price? A card helps only where the gap was small and the rep had nothing to say. A large, consistent gap is a pricing question for the founder, and no objection reply closes it. Lost to “no decision” or “went quiet”? Then nobody beat you. Thats a process problem, and a [one-page playbook](https://salesbond.app/blog/sales-playbook-small-teams-pipedrive/) with a weekly look at stalled deals does more than any card.

A disclosure, since this is where the tool question comes up: we build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. Deal Health flags the “went quiet” pattern (no next activity, a close date in the past, a stalled stage) across the whole pipeline. [Check your CRM with SalesBond](https://salesbond.app/) to see how many of your open deals carry that pattern today.

The card fixes one thing: a rep who hears a competitor’s name and has nothing ready. For a small team that is worth two or three pages, an owner each, and fifteen minutes a month. When it starts costing more than that, the count in the first section has probably changed and so should the cards.