# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Send a weekly opportunity report.
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/send-a-weekly-opportunity-report
Page: https://www.roadwayai.com/workflows/send-a-weekly-opportunity-report
Library index: https://www.roadwayai.com/automation-library
---
name: send-a-weekly-opportunity-report
description: >-
Ranks the biggest dollar opportunities across every channel this week (budget-limited winners, wasted spend, expansion and tests to run) so Monday's approval queue starts with what matters.
---
# Send a weekly opportunity report
Source: https://www.roadwayai.com/workflows/send-a-weekly-opportunity-report
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
Ranks the biggest dollar opportunities across every channel this week (budget-limited winners, wasted spend, expansion and tests to run) so Monday's approval queue starts with what matters.
Ranks the biggest dollar opportunities across every channel this week (budget-limited winners, wasted spend, expansion and tests to run) so Monday's approval queue starts with what matters. It reads your live account and turns the numbers into a short written report.
## 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
connected_channels, cost_guardrail, cost_per_goal_baseline, experiment_budget_pct, goal_metric, slack_delivery
## Prompt
Send a weekly opportunity report
Across [set this to your own connected channels], find this week's opportunities and rank each by expected monthly impact on [set this to your own goal metric] at or under the cost guardrail:
1. Scale
2. Cut waste
3. Expand
4. Test
Context and defaults (use these; don't ask):
- The cost guardrail: [set this to your own cost guardrail], from the coworker's Guardrails. If not set, 1.3x the baseline cost per goal. A workflow qualification bar (for example "cost per lead under $100 to build a page") is not a ceiling.
- The baseline cost per goal: [set this to your own cost per goal baseline]. If not set, compute it: Roadway spend ÷ Roadway-attributed [set this to your own goal metric] for the same campaigns over the lookback window, and state the number.
- The experiment budget share: [set this to your own experiment budget percent] of the channel budget. If not set, 10%.
- The delivery channel: [set this to your own slack delivery]. If Slack isn't connected, deliver in the run's thread.
Rules:
- Scale: campaigns limited by budget, rank or frequency that beat the baseline cost per goal on attributed numbers. Estimate the extra volume at the cost of the next goal, not the average cost per goal.
- Cut waste: spend on entities 2x over baseline with no attributed results, overlapping audiences, and overcredited platform conversions.
- Expand: winners on one channel that don't exist on another (search themes, creative angles, audiences).
- Test: the highest expected-value test in the experiment backlog that fits the experiment budget share.
- Every line has a dollar estimate, a note on how sure we are and the workflow or coworker that would execute it. Deliver it to the delivery channel on Friday or Monday morning.
- Delivery-constrained (budget-limited) means it spent nearly all of its daily budget on most recent days and, on search, lost impression share to budget. If not set, 95%+ of the daily budget on 4+ of the last 7 days, and 10%+ impression share lost to budget.
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.
- Any budget or bid change you propose moves one entity by at most the max change limit per run (20% unless the coworker's Guardrails set another); stage a larger move across runs. Pausing an entity under a stated stop rule is a status change, not a budget change.
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:
Weekly opportunity report
Summary:
The top 5 opportunities by expected impact, the total estimated upside, and what needs approval.
Scale:
- [opportunity] - [reason]
Cut waste:
- [opportunity] - [reason]
Expand:
- [opportunity] - [reason]
Test:
- [opportunity] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/send-a-weekly-opportunity-report
Ranks the biggest dollar opportunities across every channel this week (budget-limited winners, wasted spend, expansion and tests to run) so Monday's approval queue starts with what matters.
Ranks the biggest dollar opportunities across every channel this week (budget-limited winners, wasted spend, expansion and tests to run) so Monday's approval queue starts with what matters. It reads your live account and turns the numbers into a short written report.
