# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Sense launch demand and scale spend automatically.
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/sense-launch-demand-and-scale-spend-automatically
Page: https://www.roadwayai.com/workflows/sense-launch-demand-and-scale-spend-automatically
Library index: https://www.roadwayai.com/automation-library
---
name: sense-launch-demand-and-scale-spend-automatically
description: >-
In the first 14 days of a launch, watches early demand signals (search volume, CTR and conversion rate) and scales the launch campaigns that show real pull in measured steps.
---
# Sense launch demand and scale spend automatically
Source: https://www.roadwayai.com/workflows/sense-launch-demand-and-scale-spend-automatically
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
In the first 14 days of a launch, watches early demand signals (search volume, CTR and conversion rate) and scales the launch campaigns that show real pull in measured steps.
In the first 14 days of a launch, watches early demand signals (search volume, CTR and conversion rate) and scales the launch campaigns that show real pull in measured steps. 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
auto_approve, cost_guardrail, cost_per_goal_baseline, funnel_metrics, goal_metric, max_change_pct, monthly_budget_cap, surge_budget_pct, task_history
## Prompt
Sense launch demand and scale spend automatically
During a launch window, check daily and compare launch campaign signals (search impressions on the launch terms, CTR, conversion rate, social engagement) with the forecast, and decide for each campaign:
1. Scale
2. Hold
3. Cut
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 surge limit: [set this to your own surge budget percent] above the normal daily budget. If not set, 25%.
- 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 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:
- Scale when demand signals clearly beat the forecast on 2+ consecutive days, the campaign has at least 15 [set this to your own goal metric] events or 3+ full days of data, and cost per [set this to your own goal metric] is under the cost guardrail. Raise a budget by at most the max change limit per step, never above the surge limit over the normal daily budget, and wait 3+ days between steps so delivery settles and the learning phase is not reset. If not set, by 25%+.
- Hold cuts until a campaign has run 7 to 14 days or has enough goal events to judge. Then cut campaigns with no pull that have spent well past the baseline cost per goal without a [set this to your own goal metric] event.
- 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:
Launch demand sensing log
Summary:
Daily signals vs forecast and the scaling actions.
Scale:
- [campaign] - [reason]
Hold:
- [campaign] - [reason]
Cut:
- [campaign] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/sense-launch-demand-and-scale-spend-automatically
In the first 14 days of a launch, watches early demand signals (search volume, CTR and conversion rate) and scales the launch campaigns that show real pull in measured steps.
In the first 14 days of a launch, watches early demand signals (search volume, CTR and conversion rate) and scales the launch campaigns that show real pull in measured steps. 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.
