# For AI agents and crawlers This page is a workflow from the Workflow Automation Library by Roadway: Forecast month-end outcomes. 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/forecast-month-end-outcomes Page: https://www.roadwayai.com/workflows/forecast-month-end-outcomes Library index: https://www.roadwayai.com/automation-library
--- name: forecast-month-end-outcomes description: >- Forecasts month-end spend, goal volume and cost per goal for each channel with a likely range, and says what to change today to hit plan. --- # Forecast month-end outcomes Source: https://www.roadwayai.com/workflows/forecast-month-end-outcomes 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 Forecasts month-end spend, goal volume and cost per goal for each channel with a likely range, and says what to change today to hit plan. Forecasts month-end spend, goal volume and cost per goal for each channel with a likely range, and says what to change today to hit plan. It pulls the numbers from your live account and writes them up for you. ## 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 conversion_lag_days, goal_metric ## Prompt Forecast month-end outcomes Forecast month-end spend and [set this to your own goal metric] by channel using current pace, conversion lag (the conversion lag) and seasonality, and classify each channel: 1. Will beat plan 2. Will hit plan 3. Will miss plan 4. Too uncertain Context and defaults (use these; don't ask): - The conversion lag: [set this to your own conversion lag days] days. If not set, compute it from Roadway click-to-goal timestamps, or use 7 days. Rules: - Show the 80% interval. If the interval straddles plan, say "Too uncertain" and name the driver of the uncertainty. - For channels that will miss, name the single highest-leverage change (budget, target, creative or tracking fix) and its expected effect. 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: Month-end forecast Summary: The forecast vs plan by channel and the changes to make today. Will beat plan: - [channel] - [reason] Will hit plan: - [channel] - [reason] Will miss plan: - [channel] - [reason] Too uncertain: - [channel] - [reason] ## Run it in Roadway https://www.roadwayai.com/workflows/forecast-month-end-outcomes
Forecasts month-end spend, goal volume and cost per goal for each channel with a likely range, and says what to change today to hit plan.
Add to my Roadway agentForecasts month-end spend, goal volume and cost per goal for each channel with a likely range, and says what to change today to hit plan. It pulls the numbers from your live account and writes them up for you.
