# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Set the monthly cap from pipeline and cash forecasts.
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/set-the-monthly-cap-from-pipeline-and-cash-forecasts
Page: https://www.roadwayai.com/workflows/set-the-monthly-cap-from-pipeline-and-cash-forecasts
Library index: https://www.roadwayai.com/automation-library
---
name: set-the-monthly-cap-from-pipeline-and-cash-forecasts
description: >-
Recomputes next month's cap from forecast pipeline coverage, revenue targets and how fast spend pays back, instead of a static number set once a quarter.
---
# Set the monthly cap from pipeline and cash forecasts
Source: https://www.roadwayai.com/workflows/set-the-monthly-cap-from-pipeline-and-cash-forecasts
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
Recomputes next month's cap from forecast pipeline coverage, revenue targets and how fast spend pays back, instead of a static number set once a quarter.
Recomputes next month's cap from forecast pipeline coverage, revenue targets and how fast spend pays back, instead of a static number set once a quarter. It watches spend against the limits you set and shows you what it would change. 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
crm_pipeline_data, goal_metric, pay_back_target, transaction_revenue
## Prompt
Set the monthly cap from pipeline and cash forecasts
Using [set this to your own CRM pipeline data] or transaction revenue, the revenue target, and channel response curves, propose next month's budget cap:
1. Increase cap
2. Keep cap
3. Decrease cap
Context and defaults (use these; don't ask):
- Transaction revenue: [set this to your own transaction revenue]. If not available, use the CRM or source-of-truth goal count.
- The payback target: [set this to your own pay back target]. If not set, 12 months.
Rules:
- Increase when pipeline or revenue coverage of next quarter's target is under plan and cost of the next customer still meets the payback target.
- Decrease when coverage is ahead of plan or cost of the next customer has crossed the payback threshold.
- Give the expected change in [set this to your own goal metric] and pipeline for each option. This is a proposal for humans: never apply it automatically.
- If no campaign qualifies to receive budget, still make the justified cuts and report the freed budget as unallocated savings for approval. Never pause the entity producing the most [set this to your own goal metric] at or below baseline.
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:
Dynamic cap proposal
Summary:
The proposed cap with the forecast it is based on.
Increase cap:
- [option] - [reason]
Keep cap:
- [option] - [reason]
Decrease cap:
- [option] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/set-the-monthly-cap-from-pipeline-and-cash-forecasts
Set the monthly cap from pipeline and cash forecasts
Set the monthly cap from pipeline and cash forecasts
Recomputes next month's cap from forecast pipeline coverage, revenue targets and how fast spend pays back, instead of a static number set once a quarter.
Recomputes next month's cap from forecast pipeline coverage, revenue targets and how fast spend pays back, instead of a static number set once a quarter. It watches spend against the limits you set and shows you what it would change. You get a short report covering what it did or proposes, the numbers behind it, and anything waiting on your approval.
