# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Conquest competitor customers after acquisitions, shutdowns and sunsets.
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/conquest-competitor-customers-after-layoffs-acquisitions-and-shutdown-news
Page: https://www.roadwayai.com/workflows/conquest-competitor-customers-after-layoffs-acquisitions-and-shutdown-news
Library index: https://www.roadwayai.com/automation-library
---
name: conquest-competitor-customers-after-layoffs-acquisitions-and-shutdown-news
description: >-
Watches competitor news for acquisitions, shutdowns and product sunsets, and launches switch campaigns on Search, Bing and LinkedIn for customers who suddenly have a reason to look.
---
# Conquest competitor customers after acquisitions, shutdowns and sunsets
Source: https://www.roadwayai.com/workflows/conquest-competitor-customers-after-layoffs-acquisitions-and-shutdown-news
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
Watches competitor news for acquisitions, shutdowns and product sunsets, and launches switch campaigns on Search, Bing and LinkedIn for customers who suddenly have a reason to look.
Watches competitor news for acquisitions, shutdowns and product sunsets, and launches switch campaigns on Search, Bing and LinkedIn for customers who suddenly have a reason to look. When a competitor is acquired, shuts down or sunsets a product, it will open a calm, helpful switch campaign on their brand and category terms within a day. It keeps watching for this trigger, so you can respond within hours instead of at the next review. You get a short report covering what it did or proposes, the numbers behind it, and anything waiting on your approval.
## 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_events, competitors, cost_guardrail, cost_per_goal_baseline, funnel_metrics, goal_metric, max_change_pct, monthly_budget_cap, offers, surge_budget_pct, task_history, top_landing_pages
## Prompt
Conquest competitor customers after acquisitions, shutdowns and sunsets
Scan [set this to your own competitor events] for each name in [set this to your own competitors], and decide the response for each competitor:
1. Launch switch campaign
2. Prepare but hold
3. Wind down
4. No action
Context and defaults (use these; don't ask):
- Competitor news (layoffs, funding, acquisitions, shutdowns, leadership changes): [set this to your own competitor events]. If it isn't available, say so and skip the rules that depend on it. Source: public news coverage the agent can read.
- Named competitors and their domains: [set this to your own competitors]. If it isn't available, say so and skip the rules that depend on it.
- 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 offers: [set this to your own offers]. If not set, use the CTAs already in live ads.
- The top landing pages: [set this to your own top landing pages]. If not set, rank pages by Roadway lead rate ([set this to your own goal metric] ÷ new visitors) for the same intent over the lookback window.
- The surge limit: [set this to your own surge budget percent] above the normal daily budget. If not set, 25%.
- The cost guardrail: [set this to your own cost guardrail], from the coworker's Guardrails. If not set, 1.3x [set this to your own cost per goal baseline]. A workflow qualification bar (for example "cost per lead under $100 to build a page") is not a ceiling.
- 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 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:
- Act on events that put customers at risk: an acquisition or shutdown announcement, a product sunset, a support or engineering cut that leaves customers without help, or a pricing change that moves plans out of reach. Layoffs alone are not a trigger. Ignore funding rounds, hires and awards.
- Launch switch campaign: bid on "[competitor] alternative", "[competitor] vs [you]" and "switch from [competitor]" on Google and Microsoft, and use LinkedIn company targeting for the competitor's customers. Never target a competitor's employees.
- Tone: factual and helpful. No gloating or speculation, and use only claims from [set this to your own approved claims]. Offer a migration path (import tool, concierge setup, price lock) from [set this to your own offers].
- Send traffic to a comparison or migration page in [set this to your own top landing pages], and keep conquest spend inside the surge limit [set this to your own surge budget percent] above the normal daily budget.
- Wind down 30 days after the news cools, or when cost per goal passes [set this to your own cost guardrail] once it has enough spend and goal events to judge.
- 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 news conquest report
Summary:
The competitor events found, the campaigns launched or held, and results.
Launch switch campaign:
- [competitor] - [reason]
Prepare but hold:
- [competitor] - [reason]
Wind down:
- [competitor] - [reason]
No action:
- [competitor] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/conquest-competitor-customers-after-layoffs-acquisitions-and-shutdown-news
Conquest competitor customers after acquisitions, shutdowns and sunsets
Conquest competitor customers after acquisitions, shutdowns and sunsets
Watches competitor news for acquisitions, shutdowns and product sunsets, and launches switch campaigns on Search, Bing and LinkedIn for customers who suddenly have a reason to look.
Watches competitor news for acquisitions, shutdowns and product sunsets, and launches switch campaigns on Search, Bing and LinkedIn for customers who suddenly have a reason to look. When a competitor is acquired, shuts down or sunsets a product, it will open a calm, helpful switch campaign on their brand and category terms within a day. It keeps watching for this trigger, so you can respond within hours instead of at the next review. You get a short report covering what it did or proposes, the numbers behind it, and anything waiting on your approval.
