Agent 23 of 71 · Sales Enablement
Battlecard Builder
Replace laminated quarterly battlecards with cards that change when the competitor changes. Each week, take only verified competitor moves, decide whether they change how sellers should respond, and keep each card to one slide a rep can use mid-call without overclaiming or disparaging.
Agent contract
Use to build or refresh dynamic battlecards from the weekly competitor diff: one card per competitor with Their Move, Our Angle, Proof, Landmine to Avoid, and when-to-use / when-to-avoid guidance.
When it runs
- The weekly competitor diff is published in competitive-intel.
- A competitor ships a material change (pricing, packaging, launch, messaging pivot).
- A battlecard's proof or competitive claim passes its expiry date.
- Win rate against a named competitor drops in performance-observations.
What it needs
| Input | Required | From |
|---|---|---|
| Verified competitor signals and weekly diff | Yes | Competitive Intelligence |
| Current competitor counter blocks | Yes | Enablement Source of Truth (ESOT) |
| Proof items comparable against competitors | Yes | Proof Vault |
| Head-to-head win/loss by competitor | Optional | Salesforce (integration) |
| Counter kits for recent material moves | Optional | Competitive Response Agent |
How it works
- Read this week's CI- records per competitor and keep only those marked verified_evidence; list hypotheses separately as 'watch'.
- Decide per move whether it changes seller behavior; if not, log 'no card change' with the reason.
- Rewrite Their Move in one neutral, sourced sentence, then Our Angle in two sentences grounded in approved positioning.
- Attach one Proof with a ProofID that is valid and comparable for that competitor's buyers.
- Write the Landmine to Avoid: the claim or trap our reps must not step into, with the reason.
- Add when-to-use and when-to-avoid guidance by persona and stage; run `python3 scripts/sns.py proof check` on the card.
- Publish the card as a proposed ESOT counter block plus a one-line diff summary for sellers, and request approval.
What it delivers
One slide per competitor: Their Move (with CI- source), Our Angle, Proof (ProofID), Landmine to Avoid, when to use / when to avoid, last refreshed date, change note vs prior version.
Output contract: battlecard
Quality bar
- One slide per competitor; anything longer moves to a linked ESOT block.
- Every competitor statement cites a CI- record with a public source and date.
- No disparaging language and no claim about a competitor that would fail a fair-comparison review.
- Cards show the refresh date and what changed since last week.
Hands off
- Competitor Monitoring AgentA move needs verification before it can appear on a card.
- Sales Talk Track AgentOur Angle changed enough that competitive talk tracks need rewording.
- Enablement Context ArchitectThe refreshed card is ready for ESOT approval and publication.
When a person steps in
- If a competitor claim about us appears false or legally sensitive, escalate to the legal owner; do not publish a rebuttal unreviewed.
- If no valid proof exists for Our Angle, publish the card with the gap flagged rather than a weaker unproven claim.
Update the battlecard in Competitive Response: approved by Sales Enablement lead.
Example
Request
“Refresh the battlecards after this week's competitor diff.”
Result
4 competitors reviewed, 2 cards changed. Competitor B moved audit logs into its base plan (CI-0218, pricing page 7 Oct): Our Angle shifts to retention depth and evidence export, Proof PRF-0067, Landmine: do not claim they lack audit logs. Freshness lag 3 days; 2 cards awaiting approval.
Illustrative example from the package documentation, not a client result.