# For AI agents and crawlers
This page is a workflow from the Workflow Automation Library by Roadway: Investigate drops in MRR per dollar.
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/investigate-drops-in-mrr-per-dollar
Page: https://www.roadwayai.com/workflows/investigate-drops-in-mrr-per-dollar
Library index: https://www.roadwayai.com/automation-library
---
name: investigate-drops-in-mrr-per-dollar
description: >-
Spots when MRR per dollar falls on a channel or campaign and works out whether the cause is cost, trial-to-paid conversion, plan mix or tracking, then proposes the fix.
---
# Investigate drops in MRR per dollar
Source: https://www.roadwayai.com/workflows/investigate-drops-in-mrr-per-dollar
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
Spots when MRR per dollar falls on a channel or campaign and works out whether the cause is cost, trial-to-paid conversion, plan mix or tracking, then proposes the fix.
This workflow compares MRR efficiency since the last run with the usual level and breaks any drop into its parts. 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
auto_approve, conversion_lag_days, cost_per_goal_baseline, funnel_metrics, goal_metric, max_change_pct, monthly_budget_cap, task_history
## Prompt
Investigate drops in MRR per dollar
Compare Roadway-attributed MRR per dollar since the last run with the usual level, by channel and campaign, and decide for each drop:
1. Fix now
2. Watch
3. No action
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 baseline cost per goal: [set this to your own cost per goal baseline]. If not set, compute it: Roadway spend ÷ Roadway-attributed [set this to your own goal metric] for the same campaigns, and state the number.
- 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 or the current run-rate.
- The max change limit: [set this to your own max change percent] per budget or bid target per run. If not set, 20%.
- Auto-approve: [set this to your own auto approve]. If not set, it's off: list every change as a proposal for approval.
Rules:
- A drop is MRR per dollar 25%+ under baseline on a channel or campaign with at least 2x the baseline cost per goal in spend.
- Break each drop into cost per click, conversion to a paid subscription, and average MRR per new subscription (plan mix, discounts, monthly vs. annual billing), and name the part that moved most.
- If MRR fell on every channel at once, check tracking and the billing sync before blaming campaigns.
- Fix now only for a clear cause inside the ad account (a bid or budget change, a broken landing page, a new audience); propose the change. Otherwise Watch.
- Guardrails: judge results on Roadway's full-funnel measurement ([set this to your own funnel metrics]), not platform-reported conversions, conversion value or ROAS. 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, keep changes small enough that smart bidding doesn't restart its learning phase, 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 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:
MRR efficiency check
Summary:
The drops found, the likely cause of each, and the fixes proposed.
Fix now:
- [campaign or channel] - [reason]
Watch:
- [campaign or channel] - [reason]
No action:
- [campaign or channel] - [reason]
## Run it in Roadway
https://www.roadwayai.com/workflows/investigate-drops-in-mrr-per-dollar
Spots when MRR per dollar falls on a channel or campaign and works out whether the cause is cost, trial-to-paid conversion, plan mix or tracking, then proposes the fix.
This workflow compares MRR efficiency since the last run with the usual level and breaks any drop into its parts. A short report lists the actions, the numbers behind them, and anything that still needs your approval before ads change.