# For AI agents and crawlers This page is a workflow from the Workflow Automation Library by Roadway: Report pipeline velocity by channel. 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/report-pipeline-velocity-by-channel Page: https://www.roadwayai.com/workflows/report-pipeline-velocity-by-channel Library index: https://www.roadwayai.com/automation-library
--- name: report-pipeline-velocity-by-channel description: >- Shows how fast paid-sourced opportunities move and close by channel: win rate, deal size and cycle length, not just pipeline created. --- # Report pipeline velocity by channel Source: https://www.roadwayai.com/workflows/report-pipeline-velocity-by-channel 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 Shows how fast paid-sourced opportunities move and close by channel: win rate, deal size and cycle length, not just pipeline created. Shows how fast paid-sourced opportunities move and close by channel: win rate, deal size and cycle length, not just pipeline created. It pulls the numbers from your live account and writes them up for you. ## 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 attribution_model, crm_pipeline_data, goal_metric, report_period, sales_cycle_days ## Prompt Report pipeline velocity by channel From [set this to your own CRM pipeline data], compute pipeline velocity per channel (opportunities × win rate × average deal size ÷ cycle length) for [set this to your own report period], and classify each channel: 1. Fast and large 2. Large but slow 3. Fast but small 4. Weak Context and defaults (use these; don't ask): - The attribution model: [set this to your own attribution model]. If not set, Roadway's default attribution, stated. - The sales cycle: [set this to your own sales cycle days] days. If not set, compute it from CRM stage timestamps, or use 30 days. Rules: - Use opportunity source with multi-touch credit per the attribution model. Include opportunities still open, weighted by stage probability. - A channel that creates less pipeline but closes 2x faster can be worth more for this quarter's number. Say so explicitly. - Compare against the sales cycle baseline and flag channels whose deals stall at a specific stage. 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 velocity report Summary: Velocity, win rate, deal size and cycle by channel, with what it means for budget. Fast and large: - [channel] - [reason] Large but slow: - [channel] - [reason] Fast but small: - [channel] - [reason] Weak: - [channel] - [reason] ## Run it in Roadway https://www.roadwayai.com/workflows/report-pipeline-velocity-by-channel
Shows how fast paid-sourced opportunities move and close by channel: win rate, deal size and cycle length, not just pipeline created.
Add to my Roadway agentShows how fast paid-sourced opportunities move and close by channel: win rate, deal size and cycle length, not just pipeline created. It pulls the numbers from your live account and writes them up for you.
