# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Pace lead generation to open sales capacity.
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/pace-lead-generation-to-open-sales-capacity
Page: https://www.roadwayai.com/workflows/pace-lead-generation-to-open-sales-capacity
Library index: https://www.roadwayai.com/automation-library
---
name: pace-lead-generation-to-open-sales-capacity
description: >-
Reads open demo slots and lead backlog, then scales lead campaigns up when reps have room and throttles them when leads would sit untouched.
---
# Pace lead generation to open sales capacity
Source: https://www.roadwayai.com/workflows/pace-lead-generation-to-open-sales-capacity
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 open demo slots and lead backlog, then scales lead campaigns up when reps have room and throttles them when leads would sit untouched.
Reads open demo slots and lead backlog, then scales lead campaigns up when reps have room and throttles them when leads would sit untouched. When open demo slots rise or fall against the lead backlog, it will raise or cut lead-gen budgets so paid leads match what sales can work. 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, business_hours, crm_pipeline_data, funnel_metrics, goal_metric, max_change_pct, monthly_budget_cap, opportunity_cost_target, sales_capacity, task_history
## Prompt
Pace lead generation to open sales capacity
Read [set this to your own sales capacity] and lead response times in [set this to your own CRM pipeline data], and decide for each lead-gen channel:
1. Scale up
2. Hold
3. Throttle
4. Switch to nurture offers
Context and defaults (use these; don't ask):
- 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.
- 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 hours sales or support can respond: [set this to your own business hours]. If it isn't available, say so and skip the rules that depend on it.
- Target cost per opportunity: [set this to your own opportunity cost target]. 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:
- Capacity is open demo slots and rep availability for the next 7 days against forecast leads. Compare it with leads untouched for more than 1 business hour ([set this to your own business hours]).
- Scale up when open slots clearly exceed forecast leads and cost per qualified lead is under [set this to your own opportunity cost target], by up to [set this to your own max change percent] per run. If not set, by 30%+.
- Throttle (cut budgets up to [set this to your own max change percent]) when the backlog is over 2 days or the speed-to-lead target is missed. Prefer cutting the channels with the lowest qualified-lead rate first.
- Switch to nurture offers (content, calculator, webinar) when capacity is full for 5+ days, so demand is kept without burning sales time.
- Never judge on lead count alone: report cost per qualified lead and the share of leads contacted within 1 hour.
- 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:
Sales capacity pacing report
Summary:
Capacity versus lead flow, the channels scaled or throttled, and speed-to-lead.
Scale up:
- [channel] - [reason]
Hold:
- [channel] - [reason]
Throttle:
- [channel] - [reason]
Switch to nurture offers:
- [channel] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/pace-lead-generation-to-open-sales-capacity
Reads open demo slots and lead backlog, then scales lead campaigns up when reps have room and throttles them when leads would sit untouched. When open demo slots rise or fall against the lead backlog, it will raise or cut lead-gen budgets so paid leads match what sales can work. 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.
