Claude Code logo
Claude Code template
docs.claude.com

Sales Battle Card Generator

Internal battle cards where every competitor claim is dated and sourced — and the 'when they win' section is mandatory. Never publishes externally.

NewNew8.8 KB snapshotStarter VM
Claude Code logo

What's inside

Harness

Claude Code

Plan

Starter

vCPU

1

Memory

2 GiB

Snapshot

8.8 KB

How it works · ~3 minutes

  1. 01 · Fork

    New isolated microVM on your subdomain — creator state included.

  2. 02 · Your keys

    Log into Claude Code with your own model credentials (BYOK).

  3. 03 · Ask it to work

    Open the terminal and give it a real job. You keep what ships.

30-day money-back on your first purchase · no free trial · keys never leave the VM

About this template

The card that only lists wins gets your rep ambushed

Marketing produces six things you're better at, cites none of them, and never mentions the two deal types the competitor genuinely wins. The rep uses it once, gets blindsided on a loss it didn't warn about, and never opens it again.

"When they win" is mandatory

Every card names the specific situations where the competitor is the better choice, and the honest move for the rep — usually acknowledge and requalify, not counter.

A card with no loss section is not finished. That's in the rules file, not left to taste.

Every competitor claim carries a URL and a date

Public sources only: pricing pages, docs, changelogs, status pages, public reviews. No rumours, no rep anecdotes, no "we heard from a customer".

Anything unsourceable becomes [UNVERIFIED — do not say]. Pricing older than 90 days is marked STALE rather than silently trusted, because competitor pricing moves.

And the bottom section is what we could not verify — the things you believe but nothing public supports. That list is what a rep must not say out loud.

One screen, five sections

  1. Positioning — the difference in one sentence
  2. Their top 3 objections about you — with responses that are allowed to concede
  3. Your 3 wedges — each tied to a sourced fact, not an adjective
  4. When they win — the honest losses
  5. Landmines — questions that surface a real weakness

Landmines are questions, never assertions. "How does their export work at your volume?" — so the prospect discovers it rather than being told. That's the difference between a rep sounding informed and sounding threatened.

It won't disparage

No mockery, no adjectives about their quality, no speculation about their company's health. A rep quoting a snide battle card in writing is a discoverable document.

Internal only — and it enforces that

A competitor claim that's fine in a rep's hands is a legal problem on a landing page. Ask it to turn a card into public comparison copy and it refuses.

Re-run it quarterly

It diffs against the existing card: what moved on their pricing page, what shipped in their changelog. A battle card decays fast, and the diff is the update.

What you supply

Your own Claude Code login. Sources are public pages.

Drop your lost-deal notes into ~/battlecards/sources/ — those are the real objections, and invented ones waste the card.

Where this stops

It drafts internal cards. It won't publish, won't assert a competitor's roadmap, churn, margins or internal numbers, won't claim win rates you didn't supply, and won't say a competitor "is losing".

Verified on build: the skill, the working tree, the never-publish guard, the sourcing rule, the mandatory loss section and the five-section structure are present on a fresh fork. Running it on your own competitor is yours to do.

Inside this fork

Forking copies this template into a brand-new, fully isolated microVM on your own subdomain. Here's exactly what lands in it.

  • Claude Code agent

    The upstream harness, pre-installed — same version the creator ran.

  • Starter VM

    1 vCPU · 2 GiB RAM · 10 GiB disk.

  • Creator's /persist data

    The captured persist volume is copied byte-for-byte into your fork.

  • BYOK — your keys, your VM

    Add your model API keys after forking; they live only inside your microVM.

What this agent can do

1 skill

  • battle-card-generator

    Build an internal sales battle card from public sources — positioning, objections, wedges, honest losses, and neutral landmine questions.…

What you'll configure after forking

Secrets are scrubbed from shared templates — these are the names you supply in your agent's terminal once it boots.

Environment variables

  • ANTHROPIC_API_KEY

Your turn

Your own Sales Battle Card Generator, live in about 3 minutes.

Forking copies this Claude Codeagent into a brand-new, fully isolated microVM on your own subdomain — the creator's /persist state and all. Add your own keys after it boots; they never leave the box. Don't love it? Your first jurniti purchase comes with 30 days to get every cent back.

New paid VM · BYOK · 30-day money-back on your first purchase · ~3 min to provision

Starter · fork

$25/ mo

Needs 1 of your own API key