Generate dynamic sales battlecards from competitor, call, and review signals

Start in Notion or Klue and create one battlecard brief per competitor, not one giant generic card. Define the card type as displacement, renewal defense, objection handling, enterprise evaluation, or feature comparison because each one needs different talk tracks. Add fields for competitor_name, deal_motion, target_segment, sales_stage, owner, source_cutoff_date, approval_status, and refresh_trigger. Limit the first pass to 3-5 competitors where sellers are actively losing, hesitating, or asking the same questions. QA check: if a rep cannot tell when to use the card in one sentence, the scope is still too broad.

Use Klue to collect current competitor evidence from pricing pages, product pages, release notes, help docs, webinars, comparison pages, and field-submitted intel. For every signal, capture source URL, date_seen, signal_type, claim_or_change, buyer_relevance, confidence level, and whether the source is public, internal, or seller-reported. Do not summarize everything into one paragraph yet; keep each signal atomic so later synthesis can separate evidence from interpretation. Flag any stale source older than 90 days unless it is evergreen product documentation. QA check: every claim that might appear in the card must trace back to a dated source or be marked as unapproved field intel.