Home›Use cases›Battle cards
“Generate once, fork for every audience.”
Use case

Battle cards that win by persona, not just by product

Stop writing generic competitive cards that sales ignores. pmmAgent elevation turns your competitive context into a structured briefing — then forks it for every buyer in the room.

Start freeNo credit card

Everything structured before a word is written

pmmAgent elevation for battle cards produces a briefing with four layers — so every card variant starts from the same solid foundation.

Audience-specific objection inventory

Objections mapped by persona — not a generic list. The CISO's objections are different from the VP Eng's. Both surfaced before copy begins.

Proof point architecture

Your evidence ranked by relevance to each persona — not one undifferentiated list applied to every audience variant.

Competitive framing per rival

One named competitor per fork, each with its specific known gaps your product fills — not a generic "we're better" claim.

Reframe language

A one-line reframe for each persona that puts the competitive conversation on your terms — ready for a rep to say out loud.

Same competitive facts. Three different cards.

Once the briefing is elevated, you fork across your audience dimensions. What changes is the framing. What stays constant is the evidence.

Fork dimensions for battle cards: persona (CISO / VP Eng / Procurement), competitor (one per named rival), objection type (security-led / cost-led / integration-led)
CISO

Risk, compliance, and organisational accountability

What changes
  • Objection language shifts to compliance exposure
  • Proof points framed around audit outcomes and security posture
  • Reframe targets risk reduction, not feature parity
What stays the same
  • All competitive facts
  • The core evidence base
  • Product differentiation logic

One competitive fact. Two personas. Two cards.

The same underlying fact produces completely different output depending on the persona fork.

Without pmmAgent
Generic card output
"pmmAgent is more efficient than Competitor X because it doesn't require re-configuration."
No personaNo objectionNo proof

A rep cannot say this out loud in a meeting.

With pmmAgent — CISO fork
Forked card output
"Every time your team adds a segment in Competitor X, your compliance documentation needs re-verification. pmmAgent's briefing layer is established once and inherited by every fork — your audit trail doesn't reset."
CISO personaCompliance objection handled
Reframe line

Reconfiguration is a compliance event. Forking isn't.

Ready to see it in action?

Start free and run your first elevation free — no credit card required.

Start free
No credit card