Sales battlecards for founders with no product marketer

What changes when the founder builds the card

Our battlecard method has three required inputs, two optional ones and eleven steps. It is the skill behind our Battlecard tool (read 2026-10-14). Most of it holds for a founder, and our guide on how to build a competitive battlecard walks all eleven steps. These six parts change, in the method's order.

1. Required input 2: write your positioning first. The card needs your current messaging, at least a positioning statement, so its counter-language matches it. The method refuses to run without it, because the card does not write the pitch. With no positioning written down, write the positioning statement before the card. Steps 2 to 6 of our positioning method follow April Dunford's method in Obviously Awesome (2019).
2. Required input 3: take objections from your own calls. The method accepts only objections from calls that happened, in the buyer's words. In our view, a founder who ran the calls already holds them. Write down the buyer's sentence after each call, not your summary of it.
3. Optional input 4: log the deals you won and lost. The method treats field signal from won and lost deals against this rival as optional but preferred. In our view, at founder stage that signal sits in your memory. One line per deal, naming the rival and the reason the buyer gave, is enough to start.
4. Step 5: name your own weakness. The card states at least one weakness on your side, as plainly as theirs. The method's reason: a card that only flatters your side gets ignored the first time a buyer contradicts it. We think a founder finds this line the hardest to write, because the product is their own.
5. Step 7: write the when-to-walk line. Every objection gets the point where the honest answer is "we are not the right fit." The method's reason: a card without that line teaches sellers to bluff, and technical buyers detect bluffing fast. In our view, a founder chasing early revenue benefits most from deciding this before the call.
6. Step 11: get a second reader. The method has someone other than the author review the card before sellers get it. If you write the card and sell from it, the second reader can be a co-founder, an adviser or your first sales hire.

Worked sample: Plausible's GA4 page, read for card lines

In our view, real cards stay inside sales teams, so a public comparison page is the closest public copy. Plausible's page compares its analytics product with Google Analytics 4 (GA4), a free tool its reader may already run. We read it for the lines a card against GA4 could take, through steps 3, 5, 7 and 9. One section reads:

"What GA4 does better"

"If you need deep custom attribution modeling or enterprise-scale reporting with SQL access, GA4, especially with BigQuery, has more depth. If your business runs heavily on Google Ads, the tight integration between GA4 and Google’s ad products is hard to replicate elsewhere."

Read on 2026-10-14. Source: Plausible vs Google Analytics 4

Further down, a question heading and its first line read:

"Why isn’t Plausible free while GA4 is free?"

"GA4 is free because Google’s business runs on data."

Read on 2026-10-14. Source: Plausible vs Google Analytics 4

What the copy does well. The page gives the rival's strengths their own heading and names two specific cases: SQL-level reporting through BigQuery, and Google Ads integration. That is step 3 done in public, and it hands a card two "Where they win" lines. A later section lists the use cases Plausible does not fit, such as session replay and free hosted analytics. In our reading, that section does the work of step 5 and gives a seller ready when-to-walk lines for step 7.

What a card could not take as written. The free question reads like a buyer objection, but the page does not say a buyer asked it on a call. The method takes objections only from real calls, so it stays a lead until someone confirms it. Its answer opens on Google's business model. Step 7 keeps that framing out of a seller's own answer, because the buyer may run GA4 today. The page also says Plausible charges a subscription to cover its costs, and in our view that is the better start for the honest answer. Step 9 asks for one more check: the GA4 strengths are Plausible's description of a rival's product. A card dates them against a public Google source, or marks them UNVERIFIED.

The fix: the card lines this page can fill. The open slots stay questions, because the method fills them from your messaging and your calls.

## Where they win
- Deeper custom attribution and SQL-level reporting with BigQuery;
  tight Google Ads integration. Source: plausible.io/vs-google-analytics,
  checked 2026-10-14. UNVERIFIED until checked against a Google source.

## Our honest weaknesses against them
- No session replay or user-level product analytics (the page's
  fit section, checked 2026-10-14)

## The real objections
| [the page's free-versus-GA4 question, as a lead: confirm a buyer said it on a call] | [honest answer: what the subscription pays for, from your messaging] | [when to walk: the buyer needs free hosted analytics] |

Common mistakes

• Writing the card before the positioning. The method needs your messaging first, so the card points at language you already use. Write the positioning statement, then the card.
• Listing the objections you expect. The method's reason for real objections only: invented ones train sellers for a conversation nobody has.
• Running down the tool the buyer already uses. The method never discredits a product the buyer already owns. In our view, a founder does better to answer with what the price pays for.
• One card for every rival. The method builds one competitor per card. Start with the rival that shows up in your real deals.
• A card with no review-by date. The method dates every card 30 days out and sweeps live cards each month. A card past its date gets flagged as stale.

Questions people ask

Why are my sales battlecards useless?

Our method gives three reasons cards fail. A stale card is worse than none, because it is confidently wrong. A card that only flatters your side gets ignored the first time a buyer contradicts it. Invented objections train sellers for a conversation nobody has. The fixes are a dated profile, at least one honest weakness, and objections in the buyer's own words.

Do I need battlecards before I hire sales reps?

The method's trigger is a rival, not a headcount. It builds a card when a named competitor shows up in a real deal, because that card gets opened rather than filed. In our view, a founder who sells alone gains from writing one anyway. It makes you put your weakness and your walk-away point on paper before the next call.

Sources

• Plausible vs Google Analytics 4 (GA4), Plausible, https://plausible.io/vs-google-analytics, read 2026-10-14
• Indie Hackers posts "Your sales battlecards are probably useless, here's how to fix them as a founder" and "7 battlecard tools founders should know about as they scale their sales team", as listed in web search results, read 2026-10-14. Indie Hackers blocked our logged-out fetch, so we cite the titles only.
• Obviously Awesome, April Dunford, 2019 (book)
• Our battlecard method skill, as run by the Battlecard tool (ours, read 2026-10-14)
• Our positioning statement method skill, as run by the Positioning statement tool (ours, read 2026-10-14)