Orchestrated competitive response (L4)
When a competitor ships a launch or a price change, an orchestrated workflow drafts the updated battlecard, flags every open deal where that competitor is present, and notifies the owning reps with the changed lines only.
The steps
- 01
Watch a named source list
Tool: Claude
Monitor competitor pricing pages, release notes, and newsroom feeds. Named sources only. Social chatter produces false alarms that burn rep trust. Owner: product marketing. DoD: source list documented per competitor.
- 02
Draft the diff, not the document
Tool: Notion
The workflow proposes changed lines against the current battlecard with the source link per line. Product marketing approves or rejects each line. Pitfall: regenerating whole battlecards, which destroys approved language. DoD: changes ship as reviewable diffs.
- 03
Match to open pipeline
Tool: Salesforce
Query open opportunities where that competitor is recorded and above a value threshold. Only those owners get notified. Owner: RevOps. DoD: notification list is scoped to affected deals.
- 04
Notify with the action
Tool: Slack
The rep gets the changed lines, the affected deal, and one recommended next step. Not a link to a page, a specific move on a specific deal. Owner: enablement. DoD: each alert names a deal and a next step.
Tools in this playbook
Building the team behind this workflow?
Next playbooks
Unfamiliar terms are defined in the AI and Revenue Dictionary. Related frameworks live in the framework library.