How to use the Sales Battlecard Generator.
Battlecards need dated evidence and questions a salesperson can use. Keep uncertain competitor claims separate from demonstrated product differences.
Make the workflow fit your task.
Organize the competitor comparison around buying questions, verified differences and appropriate fit. Date the evidence and distinguish known capabilities from unknowns so a salesperson can discuss trade-offs without inventing parity.
- What you provide
- Supplied competitor facts and product evidence.
- What you get
- Comparison notes, qualifying questions and proof points.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Competitor A supports scheduled imports; your product supports reviewed manual comparisons.
Completed example
Position manual review for occasional updates; acknowledge scheduled imports as a different requirement rather than claiming parity.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should a battlecard hide an area where a competitor is stronger?
Acknowledge different requirements honestly. Clear fit guidance is more useful than an unsupported claim that your product covers every use case.
Why is the battlecard becoming inaccurate over time?
Review dated capability claims against current primary information. Preserve the source so changes can be checked efficiently.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑