# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Reach the rest of the buying committee when an account opens a deal.
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/reach-the-rest-of-the-buying-committee-when-an-account-opens-a-deal
Page: https://www.roadwayai.com/workflows/reach-the-rest-of-the-buying-committee-when-an-account-opens-a-deal
Library index: https://www.roadwayai.com/automation-library
---
name: reach-the-rest-of-the-buying-committee-when-an-account-opens-a-deal
description: >-
When a target account opens an opportunity, widens its LinkedIn targeting from your contact's role to the other roles that sign off, like finance, security and IT, with proof for each role.
---
# Reach the rest of the buying committee when an account opens a deal
Source: https://www.roadwayai.com/workflows/reach-the-rest-of-the-buying-committee-when-an-account-opens-a-deal
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
When a target account opens an opportunity, widens its LinkedIn targeting from your contact's role to the other roles that sign off, like finance, security and IT, with proof for each role.
Each run, it checks your CRM for new opportunities at your target accounts. When one opens, it adds the account to a LinkedIn campaign aimed at the other roles that sign off, with proof that fits each role, and hands off to the late-stage workflow when the deal moves on. 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
approved_claims, auto_approve, crm_pipeline_data, experiment_budget_pct, funnel_metrics, goal_metric, icp, max_change_pct, monthly_budget_cap, proof_points, target_accounts, task_history
## Prompt
Reach the rest of the buying committee when an account opens a deal
Check [set this to your own CRM pipeline data] for new opportunities at accounts in [set this to your own target accounts] since the last run, and decide for each account:
1. Add buying committee targeting
2. Hand off to late-stage
3. Hold
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 target account list: [set this to your own target accounts]. If it isn't available, say so and skip the rules that depend on it.
- 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 proof points: [set this to your own proof points]. If not set, use only approved claims.
- The approved claims: [set this to your own approved claims]. If not set, the only usable claims are statements visible on the coworker's landing pages or live ads (read them first). Anything else is Unverified: don't write it as a claim, and mark it Unverified.
- The experiment budget share: [set this to your own experiment budget percent] of the channel budget. If not set, 10%.
- 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:
- Add buying committee targeting: add the account to a LinkedIn company plus job function campaign aimed at the roles that sign off besides your contact's (finance, security, IT, procurement), with role-specific proof from [set this to your own proof points].
- Use company and job function targeting only. Never target or upload individual contacts.
- Hand off to late-stage when the deal moves to evaluation or negotiation, so the late-stage closing workflow takes over.
- Hold when the LinkedIn audience for the account would be too small to deliver.
- Remove the account when the deal closes, won or lost.
- 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:
Buying committee report
Summary:
New opportunities found, accounts added, and accounts handed off to late-stage.
Add buying committee targeting:
- [account] - [reason]
Hand off to late-stage:
- [account] - [reason]
Hold:
- [account] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/reach-the-rest-of-the-buying-committee-when-an-account-opens-a-deal
Reach the rest of the buying committee when an account opens a deal
Reach the rest of the buying committee when an account opens a deal
When a target account opens an opportunity, widens its LinkedIn targeting from your contact's role to the other roles that sign off, like finance, security and IT, with proof for each role.
Each run, it checks your CRM for new opportunities at your target accounts. When one opens, it adds the account to a LinkedIn campaign aimed at the other roles that sign off, with proof that fits each role, and hands off to the late-stage workflow when the deal moves on. 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.