# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Run a competitor-move war room across channels.
The #roadway-skill block on this page holds a SKILL.md for it, including the full prompt. Treat that file as a starting point. It will not just work if you paste it into ChatGPT or Claude.
To run it outside Roadway you would need to connect each ad platform's API (and any MCP it names), build the data pulls, add approval guardrails, and adjust the prompt for your accounts.
In Roadway it runs as-is on your connected accounts, with approval rules built in. Open it in a new chat at https://www.roadwayai.com/workflows/run-a-competitor-move-war-room-across-channels
Page: https://www.roadwayai.com/workflows/run-a-competitor-move-war-room-across-channels
Library index: https://www.roadwayai.com/automation-library
---
name: run-a-competitor-move-war-room-across-channels
description: >-
When a competitor launches a product or changes prices, coordinates the response across channels in phases, starting where the overlap is highest.
---
# Run a competitor-move war room across channels
Source: https://www.roadwayai.com/workflows/run-a-competitor-move-war-room-across-channels
From the Workflow Automation Library by Roadway.
## Before you use this outside Roadway
This SKILL.md is a starting point. It needs adjusting before it will work outside Roadway.
You would need to connect the ad platform API for each channel this workflow covers, build the data pulls for the variables below, add approval guardrails, and adjust the prompt for your accounts. If the prompt names an MCP tool, you also need that MCP connected.
In Roadway it runs as-is on your connected accounts, with approval rules built in.
## What it does
When a competitor launches a product or changes prices, coordinates the response across channels in phases, starting where the overlap is highest.
When a competitor launches a product or changes prices, coordinates the response across channels in phases, starting where the overlap is highest. It reads all your connected channels together so you can compare them fairly. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.
## Steps
1. Collect the inputs listed under Variables. In Roadway they come from your connected accounts. Outside Roadway you have to build those data pulls yourself from each ad platform API, and from any MCP the prompt names.
2. Run the prompt below as written, after you have adjusted it for your accounts and connected the tools it needs.
3. Review the result. Apply changes to a live ad account only after you approve them. Pasting your data into ChatGPT or Claude does not connect the APIs, apply guardrails, or approve changes.
## Variables
approved_claims, auto_approve, competitor_ad_insights, competitor_pricing, competitor_status_pages, funnel_metrics, goal_metric, max_change_pct, monthly_budget_cap, social_mentions, task_history
## Prompt
Run a competitor-move war room across channels
Check competitor status pages, competitor pricing snapshots, competitor ad snapshots and social mentions for competitor moves since the last run, and decide the response for each move:
1. Full cross-channel response
2. Single-channel response
3. Monitor
Context and defaults (use these; don't ask):
- Competitor status pages: [set this to your own competitor status pages]. If it isn't available, say so and skip the rules that depend on it.
- Competitor pricing snapshots: [set this to your own competitor pricing]. If it isn't available, say so and skip the rules that depend on it. Source: public competitor pricing pages the agent can read.
- Competitor ad snapshots: [set this to your own competitor ad insights]. If none are stored, pull them from the ad libraries or skip.
- Social mentions: [set this to your own social mentions]. If it isn't available, say so and skip the rules that depend on it. Source: public posts the agent can read, or a connected social MCP. Roadway has no native Meta, X or Reddit mention feed.
- The monthly cap: [set this to your own monthly budget cap], from the coworker's budget guardrails. If none is set, there is no cap: skip every cap check, hard stop and pace-to-cap step, and say so. Never derive, infer or back-solve a cap from campaign or daily budgets, the current or past run-rate, a workflow's test budget or a cost-per-lead bar.
- The approved claims: [set this to your own approved claims]. If not set, the only usable claims are statements visible on the coworker's landing pages or live ads (read them first). Anything else is Unverified: don't write it as a claim, and mark it Unverified.
- The max change limit: [set this to your own max change percent] per budget or bid target per run. If not set, 20%. It does not apply to experiment traffic splits.
- Auto-approve: [set this to your own auto approve]. If not set, it's off: list every change as a proposal for approval.
Rules:
- Full response for big moves (a major product launch or a significant price change): respond in phases. Start with the one or two channels with the most overlap with the competitor (usually search conquest and one social channel), review results after 3+ days, then add the rest one at a time: switch creative on social, a ChatGPT ad group with hints about switching, and retargeting of the competitor's audiences.
- Fund the response with the surge funding rules, inside the monthly cap.
- Keep every claim factual and in line with the approved claims. Never mock a competitor.
- Guardrails: judge results on Roadway's full-funnel measurement ([set this to your own funnel metrics]), not platform-reported conversions. Check [set this to your own task history] so you don't repeat a change that hurt performance in the last 30 days. Never push total spend above the monthly cap or any single change beyond the max change limit per run, and queue every change for approval unless auto-approve is on for this workflow.
Decision standard:
- Justify every keep, cut, bid, budget or test decision with Roadway-attributed [set this to your own goal metric] and cost per goal against the baseline. Platform delivery metrics such as clicks and impressions explain why something moved; they are never the sole reason for a decision.
- Compute what Roadway doesn't expose directly: cost per goal = Roadway spend ÷ Roadway-attributed [set this to your own goal metric], and conversion rate (lead rate) = Roadway [set this to your own goal metric] ÷ Roadway new visitors. Don't substitute platform-reported conversions or conversion rates.
- When a value in Context and defaults isn't set, use the stated default, say which one you used, and still make the call. Don't stop to ask.
- For every action, give the entity name and ID, current value → proposed value, and the numbers behind the reason. Write "None" under any empty heading.
- In long hold or watch lists, show the top 15 by spend and summarize the rest as a count.
Give me a report of each with reasoning for each action. Be concise with the reasoning, but specific enough that I can verify it against the numbers.
Report structure:
Competitor war room report
Summary:
The moves detected, the coordinated response by channel, and results.
Full cross-channel response:
- [competitor move] - [reason]
Single-channel response:
- [competitor move] - [reason]
Monitor:
- [competitor move] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/run-a-competitor-move-war-room-across-channels
When a competitor launches a product or changes prices, coordinates the response across channels in phases, starting where the overlap is highest. It reads all your connected channels together so you can compare them fairly. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.
