# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Test the claims no competitor is making.
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/test-the-claims-no-competitor-is-making
Page: https://www.roadwayai.com/workflows/test-the-claims-no-competitor-is-making
Library index: https://www.roadwayai.com/automation-library
---
name: test-the-claims-no-competitor-is-making
description: >-
Compares every competitor's live ad messages with your value props and tests the strong ones nobody else is saying, on the channels where you overlap with competitors most.
---
# Test the claims no competitor is making
Source: https://www.roadwayai.com/workflows/test-the-claims-no-competitor-is-making
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
Compares every competitor's live ad messages with your value props and tests the strong ones nobody else is saying, on the channels where you overlap with competitors most.
Each run, it reads every competitor's live ads from the ad libraries and compares them with your value props. When one of your strong, approved claims isn't used by anyone else, it writes headlines and hooks around it and tests them where you overlap with competitors most. It checks for its trigger on every scheduled run, so you can act on it then instead of waiting for your next review. 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, brand_voice, competitor_ad_insights, competitors, experiment_budget_pct, funnel_metrics, goal_metric, max_change_pct, min_sample_size, monthly_budget_cap, task_history, value_props
## Prompt
Test the claims no competitor is making
Compare the live ads of each competitor in [set this to your own competitors], from the ad library snapshot in [set this to your own competitor ad insights], with our [set this to your own value props], and decide for each value prop:
1. Test as an open claim
2. Already crowded
3. Skip
Context and defaults (use these; don't ask):
- 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.
- Competitor ad snapshots: [set this to your own competitor ad insights]. If none are stored, pull them from the ad libraries (Google Ads Transparency Center, Meta Ad Library, LinkedIn Ad Library) or skip.
- The value props: [set this to your own value props]. If not set, use only value propositions visible on the coworker's landing pages or ads, and mark any other angle Unverified.
- 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 brand voice: [set this to your own brand voice]. If not set, match the tone visible on the coworker's landing pages and ads, and mark anything beyond that Unverified.
- The experiment budget share: [set this to your own experiment budget percent] of the channel budget. If not set, 10%.
- The minimum number of conversions: [set this to your own min sample size] goal events per variant. If not set, 30.
- 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:
- An open claim is one of our [set this to your own value props], backed by [set this to your own approved claims], that no competitor uses in any live ad in the latest snapshot.
- Test as an open claim: write headlines and hooks around it and run a copy iteration test at [set this to your own experiment budget percent] on the channels where our auctions or audiences overlap with competitors most.
- Already crowded: two or more competitors already say it. Say who.
- Skip value props we can't back with [set this to your own approved claims].
- Judge on [set this to your own funnel metrics] with at least [set this to your own min sample size] goal events per variant.
- 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 already hurt performance. 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:
Open claim report
Summary:
Value props no competitor uses, the tests launched, and results.
Test as an open claim:
- [value prop] - [reason]
Already crowded:
- [value prop] - [reason]
Skip:
- [value prop] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/test-the-claims-no-competitor-is-making
Compares every competitor's live ad messages with your value props and tests the strong ones nobody else is saying, on the channels where you overlap with competitors most.
Each run, it reads every competitor's live ads from the ad libraries and compares them with your value props. When one of your strong, approved claims isn't used by anyone else, it writes headlines and hooks around it and tests them where you overlap with competitors most. It checks for its trigger on every scheduled run, so you can act on it then instead of waiting for your next review. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.