# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Scale spend when pipeline coverage falls behind the quarter.
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/scale-spend-when-pipeline-coverage-falls-behind-the-quarter
Page: https://www.roadwayai.com/workflows/scale-spend-when-pipeline-coverage-falls-behind-the-quarter
Library index: https://www.roadwayai.com/automation-library
---
name: scale-spend-when-pipeline-coverage-falls-behind-the-quarter
description: >-
Compares pipeline coverage with the quarter's target every week, and raises spend on the most efficient sources when coverage trails, inside the cap.
---
# Scale spend when pipeline coverage falls behind the quarter
Source: https://www.roadwayai.com/workflows/scale-spend-when-pipeline-coverage-falls-behind-the-quarter
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
Compares pipeline coverage with the quarter's target every week, and raises spend on the most efficient sources when coverage trails, inside the cap.
Compares pipeline coverage with the quarter's target every week, and raises spend on the most efficient sources when coverage trails, inside the cap. When pipeline coverage falls below target with weeks left in the quarter, it will lift budgets on sources with the best cost per pipeline dollar, and ease off when coverage recovers. It checks for this trigger every time it runs, so you can react 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, crm_pipeline_data, funnel_metrics, goal_metric, max_change_pct, monthly_budget_cap, pay_back_target, pipeline_coverage_target, pipeline_target, sales_capacity, sales_cycle_days, task_history
## Prompt
Scale spend when pipeline coverage falls behind the quarter
Compare open pipeline in [set this to your own CRM pipeline data] with [set this to your own pipeline target] and [set this to your own pipeline coverage target], and decide for each channel:
1. Scale up
2. Reallocate
3. Hold
4. Ease off
Context and defaults (use these; don't ask):
- Leads, contacts, accounts and opportunities with stages, amounts and click IDs: [set this to your own CRM pipeline data]. If it isn't available, say so and skip the rules that depend on it.
- The pipeline target for the quarter: [set this to your own pipeline target]. If it isn't available, say so and skip the rules that depend on it.
- The pipeline coverage target: [set this to your own pipeline coverage target]. If not set, 3x the remaining quota.
- Median days from lead to qualified lead or opportunity: [set this to your own sales cycle days]. If it isn't available, say so and skip the rules that depend on it.
- Sales capacity (open demo slots, rep availability, lead backlog): [set this to your own sales capacity]. If it isn't available, say so and skip the rules that depend on it.
- 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:
- Coverage = open pipeline expected to close this quarter ÷ remaining target. Adjust for [set this to your own sales cycle days]: pipeline created after the cycle cutoff will not close this quarter, so scale for next quarter instead.
- Scale up channels with a cost per pipeline dollar under target and budget-limited delivery, by up to [set this to your own max change percent] per run, but only inside [set this to your own monthly budget cap].
- Reallocate from channels with lead volume but a weak lead-to-opportunity rate to those with proven opportunity rates.
- Ease off when coverage passes the target, or when sales capacity is the constraint ([set this to your own sales capacity]).
- Treat early-quarter scale-ups differently: add spend where payback inside [set this to your own pay back target] still holds.
- 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:
Pipeline coverage scaling report
Summary:
Coverage versus target, the channels scaled or eased, and the expected pipeline effect.
Scale up:
- [channel] - [reason]
Reallocate:
- [channel] - [reason]
Hold:
- [channel] - [reason]
Ease off:
- [channel] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/scale-spend-when-pipeline-coverage-falls-behind-the-quarter
Compares pipeline coverage with the quarter's target every week, and raises spend on the most efficient sources when coverage trails, inside the cap. When pipeline coverage falls below target with weeks left in the quarter, it will lift budgets on sources with the best cost per pipeline dollar, and ease off when coverage recovers. It checks for this trigger every time it runs, so you can react 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.
