# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Cut the targets that keep producing the same closed-lost reason.
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-the-targets-that-keep-producing-the-same-closed-lost-reason
Page: https://www.roadwayai.com/workflows/cut-the-targets-that-keep-producing-the-same-closed-lost-reason
Library index: https://www.roadwayai.com/automation-library
---
name: cut-the-targets-that-keep-producing-the-same-closed-lost-reason
description: >-
Reads why paid-sourced deals are lost and trims the campaigns and audiences behind a repeated reason, like too small or no budget. It needs a closed-lost reason field in your CRM and stops if there isn't one.
---
# Cut the targets that keep producing the same closed-lost reason
Source: https://www.roadwayai.com/workflows/cut-the-targets-that-keep-producing-the-same-closed-lost-reason
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 why paid-sourced deals are lost and trims the campaigns and audiences behind a repeated reason, like too small or no budget. It needs a closed-lost reason field in your CRM and stops if there isn't one.
Each run, it reads why paid-sourced deals were lost in your CRM. When one reason keeps showing up for a campaign, like too small or no budget, it proposes tighter targeting there and moves the budget to campaigns that win more. If your CRM has no closed-lost reason field, it says so and stops. It checks for its trigger on every scheduled run, so you can act on it then instead of waiting for your 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_per_goal_baseline, cpa_guardrail, crm_pipeline_data, funnel_metrics, goal_metric, icp, max_change_pct, monthly_budget_cap, task_history
## Prompt
Cut the targets that keep producing the same closed-lost reason
Read the closed-lost reason on paid-sourced opportunities in [set this to your own CRM pipeline data], find campaigns where one reason makes up a much larger share of lost deals than across the rest of paid, and decide for each campaign:
1. Tighten targeting
2. Move budget
3. Keep as is
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 stop.
- The closed-lost reason: the field in your CRM that records why a deal was lost. If no closed-lost reason field is mapped, or most lost deals leave it blank, say so and stop.
- The ideal customer profile: firmographics, roles, pains: [set this to your own ICP]. If it isn't available, say so and skip the rules that depend on it.
- 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, and state the number.
- The cost guardrail: [set this to your own CPA 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 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 repeated reason is one closed-lost reason that makes up a clearly larger share of a campaign's lost deals than across the rest of paid, with enough lost deals to tell.
- Tighten targeting: propose tighter company size, seniority, geo or negative keywords on that campaign, matched to the reason (for example, "too small" means raise the company size floor).
- Move budget: move the saved budget to campaigns with better stage-to-won rates, in steps no bigger than [set this to your own max change percent].
- Keep as is when the reason isn't something targeting can fix, like a lost champion.
- Use company-level fields only. Don't look up individual people.
- 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 already hurt performance. 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:
Closed-lost reason targeting report
Summary:
Whether the closed-lost field is usable, the repeated reasons found by campaign, and the targeting and budget changes.
Tighten targeting:
- [campaign] - [reason]
Move budget:
- [campaign] - [reason]
Keep as is:
- [campaign] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/cut-the-targets-that-keep-producing-the-same-closed-lost-reason
Cut the targets that keep producing the same closed-lost reason
Cut the targets that keep producing the same closed-lost reason
Reads why paid-sourced deals are lost and trims the campaigns and audiences behind a repeated reason, like too small or no budget. It needs a closed-lost reason field in your CRM and stops if there isn't one.
Each run, it reads why paid-sourced deals were lost in your CRM. When one reason keeps showing up for a campaign, like too small or no budget, it proposes tighter targeting there and moves the budget to campaigns that win more. If your CRM has no closed-lost reason field, it says so and stops. It checks for its trigger on every scheduled run, so you can act on it then instead of waiting for your next review. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.