Newsletter ROI Dashboard
Create a decision-ready snapshot of newsletter costs, revenue, attribution, and risk.
Core Rule
Use connected analytics, revenue data, platform costs, ad spend, sponsor history, paid-member data, affiliate data, and downstream business attribution when available. Do not invent revenue, costs, CAC, LTV, conversion rates, lead value, or sponsor performance.
Inputs
- Newsletter category, cadence, list size, engagement, and source attribution
- Costs: platform, ads, tools, writers, design, prospecting, integrations, time cost if estimated
- Revenue: sponsors, paid subs, affiliates, products, services, lead gen, events, donations
- Business outcomes: website traffic, demos, leads, customers, community growth, partner relationships
- Decision to support: upgrade, prune, scale ads, hire, sell, pause, monetize, change platform
Workflow
- Separate confirmed numbers from assumptions and missing data.
- Build a cost/revenue snapshot for the relevant period.
- Calculate only metrics supported by data: net revenue, payback, CAC, LTV, RPM, sponsor yield, paid conversion, lead value, or cost per issue.
- Identify platform-cost thresholds, acquisition risks, and revenue concentration.
- Map newsletter value beyond direct revenue when relevant: leads, sponsor relationships, community, product demand, brand authority.
- Recommend a decision and the minimum tracking needed to make the next decision stronger.
- Save or hand off ROI notes, metric definitions, and tracking gaps for the connected workspace.
Output Format
When a reusable artifact is useful, follow templates/newsletter-roi-snapshot.md.
Include:
- ROI snapshot
- Confirmed data vs missing data
- Metric table
- Decision recommendation
- Risks and thresholds
- Tracking fixes
- Connected-workspace handoff notes
Metric table columns:
| Metric |
Value |
Period |
Source |
Confidence |
Decision impact |
Decision table columns:
| Option |
Upside |
Risk |
Data needed |
Decision rule |
Guardrails
- Do not treat open rate or subscriber count as revenue proof.
- Do not recommend upgrading tools without a cost/revenue or workflow rationale.
- If time cost is estimated, label it clearly as an estimate.
- If attribution is weak, recommend tracking fixes before large spend decisions.
- Do not change plans, delete subscribers, pause sends, or sell assets without explicit approval.
1---2name: newsletter-roi-dashboard3description: Use when the user asks whether a newsletter is worth the cost, whether to upgrade or pay for tools, whether ads or paid acquisition are profitable, how the newsletter supports business leads or sales, or whether to keep, pause, sell, or invest more.4---56# Newsletter ROI Dashboard78Create a decision-ready snapshot of newsletter costs, revenue, attribution, and risk.910## Core Rule1112Use connected analytics, revenue data, platform costs, ad spend, sponsor history, paid-member data, affiliate data, and downstream business attribution when available. Do not invent revenue, costs, CAC, LTV, conversion rates, lead value, or sponsor performance.1314## Inputs1516- Newsletter category, cadence, list size, engagement, and source attribution17- Costs: platform, ads, tools, writers, design, prospecting, integrations, time cost if estimated18- Revenue: sponsors, paid subs, affiliates, products, services, lead gen, events, donations19- Business outcomes: website traffic, demos, leads, customers, community growth, partner relationships20- Decision to support: upgrade, prune, scale ads, hire, sell, pause, monetize, change platform2122## Workflow23241. Separate confirmed numbers from assumptions and missing data.252. Build a cost/revenue snapshot for the relevant period.263. Calculate only metrics supported by data: net revenue, payback, CAC, LTV, RPM, sponsor yield, paid conversion, lead value, or cost per issue.274. Identify platform-cost thresholds, acquisition risks, and revenue concentration.285. Map newsletter value beyond direct revenue when relevant: leads, sponsor relationships, community, product demand, brand authority.296. Recommend a decision and the minimum tracking needed to make the next decision stronger.307. Save or hand off ROI notes, metric definitions, and tracking gaps for the connected workspace.3132## Output Format3334When a reusable artifact is useful, follow `templates/newsletter-roi-snapshot.md`.3536Include:3738- ROI snapshot39- Confirmed data vs missing data40- Metric table41- Decision recommendation42- Risks and thresholds43- Tracking fixes44- Connected-workspace handoff notes4546Metric table columns:4748| Metric | Value | Period | Source | Confidence | Decision impact |49| --- | --- | --- | --- | --- | --- |5051Decision table columns:5253| Option | Upside | Risk | Data needed | Decision rule |54| --- | --- | --- | --- | --- |5556## Guardrails5758- Do not treat open rate or subscriber count as revenue proof.59- Do not recommend upgrading tools without a cost/revenue or workflow rationale.60- If time cost is estimated, label it clearly as an estimate.61- If attribution is weak, recommend tracking fixes before large spend decisions.62- Do not change plans, delete subscribers, pause sends, or sell assets without explicit approval.
Get-Maito