Competitor Landscape into Living Battlecards
Seed Opulent with your company and known rivals; it maps the landscape, researches each competitor in depth, and keeps battlecards and positioning insights current on a schedule.
Seed the landscape and connect the research tools
Connect the intelligence sources a competitive analyst uses: Similarweb for traffic and audience, Semrush and Ahrefs for SEO and keywords, and Brand24 for mentions and sentiment. Opulent researches each rival across all of them.
Seed it once with your company and any competitors you already know, then let Opulent widen the set. Capture the battlecard shape in a playbook (a reusable, named set of steps) so every competitor is researched to the same structure.
Playbook: !battlecard Given our company and seed competitor URLs: 1. Map the landscape: confirm the seeds and find adjacent rivals we did not name. 2. Research each: positioning, pricing, traffic (Similarweb), keyword strategy (Semrush, Ahrefs), sentiment (Brand24). 3. Build a battlecard: their strengths, their weaknesses, where we win, where we lose, objection handling. 4. Extract positioning insights for us, gaps we should claim. 5. Flag what changed since the last run.
Give Opulent your own win/loss notes or sales-call themes. It grounds the "where we win" section in real deals instead of feature-list guesses that reps will not trust.
Keep the battlecards on a schedule
Battlecards rot the moment a competitor ships or reprices. Put the workflow on a schedule, a recurring run on a fixed cadence, so the set stays a living reference, not a stale doc.
Click path: Settings, then Schedules, then Create schedule. Set it weekly or monthly, choose the !battlecard playbook, and post a change summary to your sales-enablement Slack channel so reps see what moved.
The sharp edge: a scheduled run that rewrites every card in full buries the one change that matters. Have Opulent diff against the prior version and lead with what changed, not restate the whole card each time.
Watch one competitor get researched
Take a weekly run that picks up a repricing by a direct rival:
Opulent researches across all the connected sources and leads with the delta, so enablement sees the move without rereading the card.
Run: weekly battlecard refresh, rival "Northstar" Run actions: - Similarweb: organic traffic up 18% quarter over quarter, new spike from a comparison-page campaign. - Semrush/Ahrefs: bidding on our brand terms; ranking for "[category] alternative". - Brand24: sentiment dipped after a pricing change, users cite a new per-seat minimum. - Updated the battlecard: new "where we win" line on transparent pricing; added an objection-handling note. - Flagged the change: "Northstar added a seat minimum, lead with our flat pricing."
What stays current
When the run finishes, your team has a battlecard set that reflects this week, not last quarter, each claim verifiable against a source:
One battlecard per competitor with strengths, weaknesses, where you win and lose, and objection handling. A positioning-insights summary naming gaps you can claim. A change log per run showing what moved, with the source behind each change.
The change log is the proof-of-work: every update cites the traffic, keyword, or sentiment signal it came from, so a rep can trust the card in a live call.
Sharpen the intelligence
When reps say a card missed the mark, tell Opulent; write the correction into the !battlecard playbook or into memory (the notes a run recalls next time), like "track their partner ecosystem, it is how they win enterprise".
As you close and lose deals, feed the outcomes back so the "where we win" and "where we lose" sections stay grounded in reality, not marketing pages.
The natural chain: route the positioning gaps you decide to claim into Self-Evolving Pipeline Operations as messaging tests, so competitive insight turns into pipeline motion.