Does it decide budget?

No. It reports and it flags. A budget change stays with a person, and the review gate sits before the report circulates rather than after somebody has acted on it.

Can it explain a number?

Every figure traces back to the source rows it came from. That traceability is what makes the report reviewable, and it separates a number you can defend from one you have to take on trust.

The monthly report is the same joins rebuilt every cycle

Today

Exports pasted into a spreadsheet one person understands

Every cycle, somebody pulls an export from each channel by hand and pastes it into a spreadsheet whose formulas one person understands.
The channels define their metrics differently, so the totals disagree and the meeting spends its first half reconciling them instead of using them.
The report lands after the decision it was meant to inform.
And every follow-up question means building it again.

With agents

Assembly runs continuously, and the meeting starts at the exception

The report is current when it is asked for.
The definitions live in one place.
The discussion starts at the exception.

How an agent runs it

The recurring report is the same set of joins rebuilt every cycle. Move the assembly into a job that runs continuously and the meeting changes character.

Channel data on your schedule

Pulls performance data from each channel you authorize, on the schedule you set.

Metrics normalized to your definitions

Normalizes metrics to your definitions, so one word means one thing across every channel.

Spend joined to pipeline

Joins spend to the pipeline records, so the report carries both sides of the question.

The report in your format

Assembles the recurring report in your existing format rather than in a new one nobody asked for.

Threshold moves, by segment

Flags moves that cross the thresholds you set, naming the segment that caused them.

Human gate

Routes the commentary, and anything that would change budget, to the marketing owner for review before the report circulates.

Prior periods kept intact

Keeps prior periods intact, so a comparison means what it says it means.

Results

What changes when the report assembles itself

Current when it is asked for

Assembly runs on a schedule rather than starting when somebody requests it.

Definitions in one place

Normalization happens once inside the workflow instead of separately inside each export, so two channels stop reporting the same word differently.

The discussion starts at the exception

Threshold flags arrive with the segment that caused the move attached, so the first question already has its evidence next to it.

Where this fits

Workflow / Automate a Workflow

Tier 1 through the Automate a Workflow door: one workflow, end to end. Reporting is straightforward to scope because the output already exists and everyone agrees on what it should contain. It extends toward a marketing operations role that carries more of the cycle. The wider role is where this can lead. It is not scoped into this engagement.

Automate a Workflow names the workflow tier, while How It Works names the review gate pattern.

Tier 1 / Prove

How It Works

Questions, answered

Any channel that exposes an authorized way to read its data under your access policy. That is a question about permissions rather than about a brand, and fit is audited before anything gets built.

Campaign reporting that assembles itself