# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Add target accounts when they hire a new leader or raise funding.
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/add-target-accounts-when-champions-change-jobs-or-companies-raise-funding
Page: https://www.roadwayai.com/workflows/add-target-accounts-when-champions-change-jobs-or-companies-raise-funding
Library index: https://www.roadwayai.com/automation-library
---
name: add-target-accounts-when-champions-change-jobs-or-companies-raise-funding
description: >-
Asks Clay to check your target accounts for a new leader in your buyer's function or a fresh funding round, then adds the accounts that qualify to your LinkedIn company targeting with a message that fits. Needs the Clay MCP connected in Roadway.
---
# Add target accounts when they hire a new leader or raise funding
Source: https://www.roadwayai.com/workflows/add-target-accounts-when-champions-change-jobs-or-companies-raise-funding
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
Asks Clay to check your target accounts for a new leader in your buyer's function or a fresh funding round, then adds the accounts that qualify to your LinkedIn company targeting with a message that fits. Needs the Clay MCP connected in Roadway.
Each run, the agent takes your target accounts and asks Clay about them through the MCP: who recently joined in your buyer's function, and whether the company has raised money. Clay answers when asked and does not send alerts, so a change is picked up on the next run, and every lookup uses your Clay credits, which is why a run checks at most 25 accounts. Accounts that qualify are proposed as LinkedIn company targets with a message that fits the trigger. It works at the account level and does not track individual people.
## 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
account_change_signals, auto_approve, crm_pipeline_data, funnel_metrics, goal_metric, icp, max_change_pct, monthly_budget_cap, target_accounts, task_history
## Prompt
Add target accounts when they hire a new leader or raise funding
Use the Clay MCP to check my target accounts ([set this to your own target accounts]) for a new leader in the buyer function or a recent funding round, compare them with [set this to your own CRM pipeline data], and decide for each account:
1. Add to ABM targeting
2. Move to late-stage messaging
3. Hold
4. Remove
Context and defaults (use these; don't ask):
- Clay: use the Clay MCP connected in Roadway. Clay answers only when asked and sends no alerts, and every lookup uses Clay credits. If it isn't connected, say so and stop.
- Account changes you already track (new leaders, funding rounds): [set this to your own account change signals]. If it isn't set, ask Clay for them for each account you check.
- The target account list: [set this to your own target accounts]. If it isn't set, use the accounts in Clay's CRM view. If neither is available, say so and stop.
- Accounts and opportunities with stages and amounts, from the CRM or from Clay's CRM view: [set this to your own CRM pipeline data]. 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 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:
- Account-level only. Use company names and domains, and do not look up or track individual people. Roadway does not use contact data.
- Strong signals, found by asking Clay: someone joined the account in the last 30 days in the buyer function (the roles in [set this to your own ICP]), or the account raised a funding round in the last 30 days.
- Check at most 25 accounts per run, starting with the ones checked longest ago ([set this to your own task history]), because every Clay lookup uses credits.
- Add to ABM targeting: add the account as a LinkedIn company target, matched by name and domain, with a message that fits the trigger (new leader: first 90 days playbook; funding: scale story). Roadway cannot upload company lists to Meta or Google Ads, so for those list the accounts for the customer's own audience sync and stop at a proposal.
- Move to late-stage messaging when [set this to your own CRM pipeline data] shows an open opportunity. Remove accounts that became customers or opted out.
- Cap new accounts per run to 50, and check the LinkedIn audience size before spending.
- 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:
Account change signal report
Summary:
The signals found, accounts added or moved, and their engagement and pipeline.
Add to ABM targeting:
- [account] - [reason]
Move to late-stage messaging:
- [account] - [reason]
Hold:
- [account] - [reason]
Remove:
- [account] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/add-target-accounts-when-champions-change-jobs-or-companies-raise-funding
Add target accounts when they hire a new leader or raise funding
Add target accounts when they hire a new leader or raise funding
Asks Clay to check your target accounts for a new leader in your buyer's function or a fresh funding round, then adds the accounts that qualify to your LinkedIn company targeting with a message that fits. Needs the Clay MCP connected in Roadway.
Each run, the agent takes your target accounts and asks Clay about them through the MCP: who recently joined in your buyer's function, and whether the company has raised money. Clay answers when asked and does not send alerts, so a change is picked up on the next run, and every lookup uses your Clay credits, which is why a run checks at most 25 accounts. Accounts that qualify are proposed as LinkedIn company targets with a message that fits the trigger. It works at the account level and does not track individual people.
