Sales template

Battlecard From Notes

Turn raw competitor intel into a sales battlecard: landmines, traps to set, and win themes.

A self-running competitive enablement desk. Paste your messy notes about a competitor (from a lost deal, a review site, a prospect call, a teardown) and it returns a rep-ready battlecard: how to position, the landmines they'll drop on you, traps to set in your favor, their strengths to respect, and the win themes that close. Example input: "CompetitorX: cheaper, strong brand, but slow support, no SSO on lower tiers, locks data on export. Lost two deals to them on price." Example output: strict JSON with competitor, our_positioning, their_strengths[], their_weaknesses[], landmines_they_set[] (claim + your_counter), traps_to_set[] (question + why), win_themes[], and how_to_win.

The flow this template ships
InputLLM (Claude)Output
Core$0.18 / call3 steps wiredSales

Who pays: Sales enablement and product marketing: every competitive deal needs a current battlecard reps can carry.

How it runs
Runs on demand

Each accepted caller request triggers the 3-step flow once. Ordinary services may expose a free preview; payment-enabled calls may settle through x402; company or otherwise unready services may be unavailable.

$0.18 per card, suggested

The template opens with this intended price loaded. Launch publishes the service and its current call state. An ordinary service may preview; only a separately payment-enabled service exposes x402 terms for paid USDC calls.

Built on core nodes

The wired flow uses built-in nodes only. Any external action shows the Connection it needs for live use; a Connection is a reviewed link to your own webhook or account, and nothing external fires in preview.

Related templates
Start building

Open Battlecard From Notes in the studio

The 3-step flow arrives wired, with its suggested price loaded, and ready for a free builder preview. Make it yours, then launch with its public call state reported.

Open this template →
Three connected Agent Studio views showing one agent as an org-chart seat, a workflow, and a paid service endpoint.
Seat, flow, serviceThe same agent as a seat, a flow, and a service.