# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Shift budget toward the product lines gaining revenue.
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/shift-budget-toward-the-product-lines-gaining-revenue
Page: https://www.roadwayai.com/workflows/shift-budget-toward-the-product-lines-gaining-revenue
Library index: https://www.roadwayai.com/automation-library
---
name: shift-budget-toward-the-product-lines-gaining-revenue
description: >-
Reads revenue by plan or product line, and shifts budget toward the lines that are growing profitably, away from the ones that are flat or shrinking.
---
# Shift budget toward the product lines gaining revenue
Source: https://www.roadwayai.com/workflows/shift-budget-toward-the-product-lines-gaining-revenue
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
Reads revenue by plan or product line, and shifts budget toward the lines that are growing profitably, away from the ones that are flat or shrinking.
Reads revenue by plan or product line, and shifts budget toward the lines that are growing profitably, away from the ones that are flat or shrinking. When revenue mix shifts between product lines or plans, it will reweight budgets, copy and landing pages toward the line with momentum. It keeps watching for this trigger, so you can respond within hours instead of at the 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
auto_approve, cost_guardrail, cost_per_goal_baseline, funnel_metrics, goal_metric, max_change_pct, monthly_budget_cap, pay_back_target, plan_mix, promo_calendar, seasonality_calendar, task_history
## Prompt
Shift budget toward the product lines gaining revenue
Read [set this to your own plan mix] and Roadway-attributed revenue by product line, and decide for each product line:
1. Shift budget in
2. Shift budget out
3. Refresh copy and pages
4. Hold
Context and defaults (use these; don't ask):
- Revenue by plan or product line: [set this to your own plan mix]. If it isn't available, say so and skip the rules that depend on it.
- The seasonality calendar: [set this to your own seasonality calendar]. If not set, assume no seasonal adjustment and say so.
- The promo calendar: [set this to your own promo calendar]. If it isn't available, say so and skip the rules that depend on it.
- 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.
- Target months for a customer to pay back their acquisition cost: [set this to your own pay back target]. If not set, 12 months.
- 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:
- Momentum = 60-day revenue growth and new customer growth, adjusted for [set this to your own seasonality calendar] and any promotion in [set this to your own promo calendar].
- Shift budget in for lines that have been growing clearly, for long enough to trust the trend, whose cost per goal is under [set this to your own cost guardrail]. Shift budget out from lines that shrink or whose payback is outside [set this to your own pay back target], by up to [set this to your own max change percent] per run.
- Refresh copy and pages when a line gains momentum but its ads still describe the old positioning.
- Keep a floor for strategic lines that need to stay visible, and never cut a line's brand defense.
- Report profit by line, not blended return on spend.
- 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:
Product line reallocation report
Summary:
The lines gaining and losing, the budget moves, and the revenue effect.
Shift budget in:
- [product line] - [reason]
Shift budget out:
- [product line] - [reason]
Refresh copy and pages:
- [product line] - [reason]
Hold:
- [product line] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/shift-budget-toward-the-product-lines-gaining-revenue
Reads revenue by plan or product line, and shifts budget toward the lines that are growing profitably, away from the ones that are flat or shrinking. When revenue mix shifts between product lines or plans, it will reweight budgets, copy and landing pages toward the line with momentum. It keeps watching for this trigger, so you can respond within hours instead of at the next review. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.
