# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Send a daily ARR digest.
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/send-a-daily-arr-digest
Page: https://www.roadwayai.com/workflows/send-a-daily-arr-digest
Library index: https://www.roadwayai.com/automation-library
---
name: send-a-daily-arr-digest
description: >-
A short daily read of paid spend since the last run and the ARR it brought in by channel, measured by Roadway, against the usual level.
---
# Send a daily ARR digest
Source: https://www.roadwayai.com/workflows/send-a-daily-arr-digest
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
A short daily read of paid spend since the last run and the ARR it brought in by channel, measured by Roadway, against the usual level.
This workflow pulls spend since the last run and attributed ARR per channel and writes up what moved. You get a short report with the numbers behind every line, so you can check it yourself.
## 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
conversion_lag_days, funnel_metrics, goal_metric, sales_cycle_days, slack_delivery
## Prompt
Send a daily ARR digest
Pull spend since the last run and Roadway-attributed ARR per channel, and classify each channel:
1. Ahead of the usual level
2. In line with the usual level
3. Behind the usual level
Context and defaults (use these; don't ask):
- ARR: total ARR (new + expansion - contraction - churn, total_arr in Roadway), as your Roadway funnel defines annual recurring revenue (for example the ARR on closed-won deals in your CRM, or on subscriptions in your billing system). If [set this to your own goal metric] is new-customer ARR, use total ARR from [set this to your own funnel metrics] if it's mapped and say so. If it isn't mapped, say the report covers new-customer ARR only. If [set this to your own goal metric] isn't ARR at all, use the ARR stage in [set this to your own funnel metrics] and say so. If no ARR stage is mapped, say so and stop.
- The time from click to [set this to your own goal metric]: [set this to your own conversion lag days] days, or [set this to your own sales cycle days] days for sales-led deals. If not set, compute it from Roadway's click and stage timestamps and state it. Don't judge days that haven't had time to convert.
- The delivery channel: [set this to your own slack delivery]. If Slack isn't connected, deliver in the run's thread.
Rules:
- Compare each channel with its usual ARR per dollar. Ahead of the usual level is 1.2x or more, behind is under 0.8x, and anything in between is in line.
- ARR often closes days or weeks after the click, so show spend since the last run next to ARR closed since the last run from earlier clicks, and say which is which.
- Flag any channel with spend and no ARR for longer than the time from click to ARR, and list open pipeline from that channel if the CRM has it.
Decision standard:
- Justify every keep, cut, bid, budget or test decision with Roadway-attributed ARR ([set this to your own goal metric]) and ARR per dollar of spend against the account average. 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: ARR per dollar = Roadway-attributed ARR ÷ Roadway spend. Don't substitute platform-reported conversion value or ROAS.
- 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:
Daily ARR pulse
Summary:
Spend, attributed ARR and ARR per dollar by channel vs. the usual level.
Ahead of the usual level:
- [channel] - [reason]
In line with the usual level:
- [channel] - [reason]
Behind the usual level:
- [channel] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/send-a-daily-arr-digest
This workflow pulls spend since the last run and attributed ARR per channel and writes up what moved. You get a short report with the numbers behind every line, so you can check it yourself.