Sales Battlecard Generator

Generate per-competitor battlecards with objection scripts, win themes, and trap-setter questions reps can use on live calls.

Generate per-competitor battlecards with objection scripts, win themes, and trap-setter questions reps can use on live calls. Battlecards rot the day they ship. This refreshes them on demand and keeps the rep talking like the deal is theirs.

This is the whole blueprint, nothing held back: the model, the tools, the exact prompt, the source on disk, and the setup. Everything you need to run Sales Battlecard Generator yourself is on this page, and it deploys in an afternoon.

What it does

Sales Battlecard Generator handles the work end to end:

  • Research competitor positioning, pricing, and recent product changes
  • Mine public reviews and support threads for recurring objections
  • Build a structured battlecard with verbatim scripts and trap-setter questions
  • Validate every claim against research and flag the unsupported ones

The anatomy

An agent is a composition, not a prompt: a model, the tools it is allowed to call, the integrations that give those tools reach, and the rules that keep it honest. Here is Sales Battlecard Generator on one card.

Sales Battlecard Generatorblueprint
Model
claude-sonnet-4-6
Tools
research_competitorextract_objectionsbuild_battlecardvalidate_card
Integrations
Brave SearchZod
Guardrails
each objection must include a 1-2 sentence script the rep can say verbatim.; trap-setter questions must expose a real product gap, not generic fud

The instructions

Every run is governed by this prompt. It is short on purpose: enough to make Sales Battlecard Generator reliable, not so much that it can misread itself. Copy it as a starting point for any agent you build.

Sales Battlecard Generator
You are a competitive enablement strategist. You produce battlecards reps can read mid-call. WORKFLOW: 1. Call research_competitor to gather positioning, pricing, and recent moves. 2. Call extract_objections from public reviews and support discussions. 3. Call build_battlecard with sections: positioning, traps, objections, win themes, do-not-say. 4. Call validate_card to flag claims that aren't supported by the research. RULES: - Each objection must include a 1-2 sentence script the rep can say verbatim. - Trap-setter questions must expose a real product gap, not generic FUD. - Never include legally risky claims (security incidents, lawsuits). - One battlecard per competitor; refuse to merge multiple into a single card.

The source, on disk

Three files carry the whole agent: the definition with its tools, the environment it expects, and the setup. Walk them.

sales-battlecard-generator/sales-battlecard-generator.ts1.2 KB
1import { agent, tool } from "@agent-sdk"
2import { z } from "zod"
3
4const competitorInput = z.object({
5 competitor: z.string(),
6 ownProduct: z.string(),
7})
8
9export default agent({
10 model: "claude-sonnet-4-6",
11 permissionMode: "bypassPermissions",
12 maxTurns: 18,
13 systemPrompt: `...`, // see System Prompt section above
14 tools: {
15 research_competitor: tool({
16 description: "Pull positioning, pricing, recent product changes",
17 inputSchema: competitorInput,
18 execute: async ({ competitor, ownProduct }) => { /* Brave Search */ },
19 }),
20 extract_objections: tool({
21 description: "Mine reviews and support threads for recurring complaints",
22 inputSchema: z.object({ competitor: z.string() }),
23 execute: async ({ competitor }) => { /* G2, Reddit, support */ },
24 }),
25 build_battlecard: tool({
26 description: "Assemble battlecard with positioning, traps, objections, win themes",
27 inputSchema: z.object({ research: z.any(), ownProduct: z.string() }),
28 execute: async ({ research, ownProduct }) => { /* markdown card */ },
29 }),
30 validate_card: tool({
31 description: "Flag unsupported claims",
32 inputSchema: z.object({ card: z.string() }),
33 execute: async ({ card }) => { /* warnings */ },
34 }),
35 },
36})

The business case

If you run an agency, Sales Battlecard Generator is also a product. It sells into sales enablement, revops, product marketing, and the numbers work at very small scale.

$2,400

setup you can charge

$400/mo

monthly retainer

4

jobs off your plate

Ship it

The whole install is a handful of commands and the keys from the env file. Run the list, then point Sales Battlecard Generator at real work.

Deploy checklist

0 of 4

That is the entire blueprint: one model, 4 tools, and a prompt. Built by hand it costs you an afternoon. Inside Ultron it costs you a sentence, because you can build this exact agent in the workforce and watch it run before you commit to anything.

Build Sales Battlecard Generator in Ultron

1
Describe what you want

Start from this blueprint or your own words. Ultron reads the intent and picks the tools.

2
It builds the agent

The model, the tools, the prompt, the console. Assembled in front of you, nothing to wire.

3
Watch it run

Test it live in the chat, then put it to work. You review what it does, it does the rest.

Keep reading