Sales reps mention competitor names in opportunity notes and custom fields, but that intelligence never reaches marketing. This job queries a custom “Competitor” field on Opportunities, aggregates which competitors appear most in active and lost deals, then feeds competitor names plus deal context into Mave Agent. The output is AI-generated competitive battle cards.
==================================================BATTLE CARD: CompetitorX | Mentions: 23 | Win rate: 14/19==================================================### OverviewSeries C startup ($45M raised) positioning as "all-in-one revenue platform."Strong in SMB, weaker in enterprise.### Their Strengths- Lower entry price ($99/seat vs our $149/seat)- Faster self-serve onboarding- Strong Slack community and developer advocacy### Where We Win- No SSO/SCIM below Enterprise tier — dealbreaker for InfoSec- Dashboard-only reporting; no API export for BI tools- No dedicated CSM below $50K ACV### Killer Questions- "How important is SSO to your security team?"- "Do you need to pipe data into your existing BI stack?"### Why Customers SwitchCompliance gaps (SOC 2, SSO) and reporting limitations thatsurface 3-6 months after purchase.Sources: 3
Competitor__c is a common custom field. If your org uses a different name, run GET /services/data/v66.0/sobjects/Opportunity/describe to discover your schema.