# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Send a daily MRR 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-mrr-digest
Page: https://www.roadwayai.com/workflows/send-a-daily-mrr-digest
Library index: https://www.roadwayai.com/automation-library
---
name: send-a-daily-mrr-digest
description: >-
A short daily read of paid spend and the MRR it added, by channel, month to date against each channel's usual pace, measured by Roadway.
---
# Send a daily MRR digest
Source: https://www.roadwayai.com/workflows/send-a-daily-mrr-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 and the MRR it added, by channel, month to date against each channel's usual pace, measured by Roadway.
This workflow pulls month-to-date spend and attributed MRR 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, slack_delivery
## Prompt
Send a daily MRR digest
Pull month-to-date spend and Roadway-attributed MRR added per channel, compare with each channel's usual pace, 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):
- MRR: your [set this to your own goal metric], as your Roadway funnel defines monthly recurring revenue (usually from subscriptions in your billing system, with annual plans counted the way your funnel already counts them). If [set this to your own goal metric] isn't MRR, use the MRR stage in [set this to your own funnel metrics] and say so. If no MRR stage is mapped, say so and stop.
- The time from click to first paid month: [set this to your own conversion lag days] days, including any free trial. If not set, compute it from Roadway's click and subscription start 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:
- Ahead of the usual level is 10%+ more MRR added than its usual pace for similar spend, behind is 10%+ less, and anything in between is in line.
- List new paid subscriptions since the last run by channel with their MRR, and the trials from paid clicks that are due to convert this week.
- Flag any channel with spend and no new paid subscriptions for longer than the time from click to paid subscription.
Decision standard:
- Justify every keep, cut, bid, budget or test decision with Roadway-attributed MRR ([set this to your own goal metric]), MRR per dollar of spend and payback months 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: MRR per dollar = Roadway-attributed MRR ÷ Roadway spend, and payback months = Roadway spend ÷ Roadway-attributed MRR. 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 MRR pulse
Summary:
Month-to-date spend, MRR added and MRR per dollar by channel vs. the usual pace.
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-mrr-digest
This workflow pulls month-to-date spend and attributed MRR per channel and writes up what moved. You get a short report with the numbers behind every line, so you can check it yourself.