# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Cut spend on campaigns whose opportunities stall in the pipeline.
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/cut-spend-on-campaigns-whose-opportunities-stall-in-the-pipeline
Page: https://www.roadwayai.com/workflows/cut-spend-on-campaigns-whose-opportunities-stall-in-the-pipeline
Library index: https://www.roadwayai.com/automation-library
---
name: cut-spend-on-campaigns-whose-opportunities-stall-in-the-pipeline
description: >-
Ages every opportunity by the campaign that sourced it, and cuts or reroutes spend where deals sit in one stage far longer than the rest of your pipeline.
---
# Cut spend on campaigns whose opportunities stall in the pipeline
Source: https://www.roadwayai.com/workflows/cut-spend-on-campaigns-whose-opportunities-stall-in-the-pipeline
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
Ages every opportunity by the campaign that sourced it, and cuts or reroutes spend where deals sit in one stage far longer than the rest of your pipeline.
Ages every opportunity by the campaign that sourced it, and cuts or reroutes spend where deals sit in one stage far longer than the rest of your pipeline. When opportunities from a campaign sit in a stage 2x longer than the norm, it will trim spend and tighten targeting before the stuck pipeline becomes lost pipeline. 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, crm_pipeline_data, funnel_metrics, goal_metric, max_change_pct, monthly_budget_cap, sales_cycle_days, stage_aging, task_history
## Prompt
Cut spend on campaigns whose opportunities stall in the pipeline
Join [set this to your own stage aging] with campaign source data in [set this to your own CRM pipeline data], and decide for each source campaign:
1. Cut budget
2. Tighten targeting
3. Alert sales
4. Hold
Context and defaults (use these; don't ask):
- Opportunity age by stage and source campaign: [set this to your own stage aging]. If it isn't available, say so and skip the rules that depend on it.
- 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.
- 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.
- 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:
- A campaign is stalling when a large share of its open opportunities are older than twice the median stage time for [set this to your own sales cycle days], with at least 10 opportunities. If not set, 40%+ of them.
- Alert sales first when stalls look like a follow-up problem (stage notes, no activity in 14 days), and cut only when the same pattern shows across several reps.
- Cut budget by up to [set this to your own max change percent] on campaigns whose closed-won rate is also below the account average. Tighten targeting where the stalled deals share a segment (company size, role, industry).
- Never cut on stalls alone when win rate and deal size are above average: those deals just take longer.
- Judge on pipeline value and win rate from [set this to your own funnel metrics], and revisit after one full sales cycle.
- 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:
Stalled pipeline source report
Summary:
The sources with stalled deals, the actions taken, and the pipeline at risk.
Cut budget:
- [source campaign] - [reason]
Tighten targeting:
- [source campaign] - [reason]
Alert sales:
- [source campaign] - [reason]
Hold:
- [source campaign] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/cut-spend-on-campaigns-whose-opportunities-stall-in-the-pipeline
Cut spend on campaigns whose opportunities stall in the pipeline
Cut spend on campaigns whose opportunities stall in the pipeline
Ages every opportunity by the campaign that sourced it, and cuts or reroutes spend where deals sit in one stage far longer than the rest of your pipeline.
Ages every opportunity by the campaign that sourced it, and cuts or reroutes spend where deals sit in one stage far longer than the rest of your pipeline. When opportunities from a campaign sit in a stage 2x longer than the norm, it will trim spend and tighten targeting before the stuck pipeline becomes lost pipeline. 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.
