Dashboards tell you what happened. This tells you what to do about it. The output is written as decisions, so the weekly review is ten minutes rather than an hour of exporting.
The same metrics every week
Open rate, reply rate, bounce rate and click rate, per campaign, for the last seven days, compared against the previous period. Fixed definitions, so nobody spends the review arguing about what counts as a reply.
Averages are reported but never lead, because an average across twelve campaigns hides both the one worth doubling and the one quietly burning domains.
It ends in decisions, not charts
Every campaign gets exactly one of three recommendations: pause, optimise, or scale. That constraint is the point. A dashboard tells you what happened and leaves the judgement to a meeting; this arrives with the judgement already made and the reasoning attached, so the meeting is a review rather than an analysis session.
What it flags first
How teams run it
Monday morning, before the pipeline meeting, delivered into chat rather than as a file. Format matters here: a document gets skimmed once and forgotten, a short briefing in the channel where the team already talks gets read and acted on.
Runs well with
Skills compound. These are the ones we usually install alongside it.