The problem this solves
The monthly marketing report is the most predictable deliverable in the calendar and it still eats the same two days every month. Someone senior logs into Search Console, GA4, the ad platforms, and the CRM, exports the same views, pastes them into the same template, and writes the same commentary under fresh numbers. The work is identical every month by design, which is exactly what makes spending senior time on it so hard to defend and so hard to stop.
The deeper problem is lineage. By the time a number has traveled from a platform through a spreadsheet into a slide, nobody can say precisely how it was derived: which date range, which filters, which definition of a conversion. When two slides disagree, the meeting becomes an investigation. Leadership learns to treat the report as directional, which is a polite way of saying they have stopped trusting the numbers enough to act on them.
A report that assembles itself changes both halves. The mechanical gathering happens without anyone's weekend, and every figure carries its lineage, traceable to the tool call that fetched it, with the date range and filters on record. The senior person's contribution moves to where it belongs: reading the finished draft and deciding what the numbers mean for next month's plan.
How the mission runs
- Pull organic performance. Search Console provides the organic picture for the month: clicks, impressions, position movement, and the queries and pages that drove change. The comparison window is stated explicitly in the output, so month-over-month claims in the deck are reproducible rather than approximate.
- Pull traffic and behavior. GA4 supplies sessions, engagement, and conversions across the site, segmented the way your team reads them. Definitions are pinned in the output - which events count as conversions, which channels group where - because ambiguity in those definitions is where most reporting arguments are born.
- Pull paid performance. Google Ads and Meta Ads report spend, impressions, clicks, and conversions per campaign for the month. The paid section keeps platform-reported and analytics-reported conversions as separate, labeled columns, since blending the two silently is how paid numbers lose credibility with finance.
- Pull pipeline touches from HubSpot. HubSpot closes the loop: contacts created, deals opened, and pipeline touched by marketing during the month. Connecting spend and traffic to pipeline in the same deck is what turns the report from a channel digest into a document leadership has a reason to read.
- Build the deck in Gamma. The assembled data becomes the monthly deck in Gamma: headline summary, one section per channel, the pipeline view, and a callouts slide for what genuinely changed this month. The structure repeats every month by design, so readers compare months instead of relearning the format.
- Post the summary to #leadership. A concise summary lands in Slack with the deck linked: the three numbers that moved, why they moved, and what is being done about it. The channel post is deliberately short, because the deck holds the depth and the post exists to make ignoring the report impossible.
The prompt
This is the exact objective the agent receives. Swap the obvious placeholders for your own domain, segment or channel and run it as-is from the console, Slack, or the API.
What comes back
The monthly marketing report as a finished Gamma deck - organic, traffic, paid, and pipeline in one repeating structure - plus a summary posted to #leadership with the deck linked. Every figure in both traces to the tool call that produced it, with date ranges and definitions stated, so the review conversation starts from what the numbers mean instead of where they came from.
Make it yours
- Add a review gate so the deck reaches you first and posts to #leadership only after your approval, keeping a human read between assembly and audience.
- Extend the pipeline section with revenue by original channel when your HubSpot attribution is clean enough to support the claim in front of leadership.
- Run a weekly lightweight version to a team channel with the same definitions, so the monthly deck lands on an audience that already knows the shape of the numbers.
Frequently asked questions
What happens when two sources disagree on a number?
The deck shows both, labeled by source, rather than quietly averaging or picking one. Platform-reported and analytics-reported conversions are the classic case, and keeping them as separate labeled figures with their definitions stated is what lets the report survive scrutiny from anyone who checks.
Can it run on a schedule?
Yes, that is the natural mode: scheduled for the first of the month, assembling the prior month, with the deck delivered for review or posted directly per your gate policy. The report becomes something that arrives on its own, and your involvement shrinks to the judgment layer.
How much can I customize the structure?
Fully; the prompt states what sections appear, in what order, and with what emphasis. The one recommendation is to freeze the structure once it works, because a monthly report's value compounds through comparability, and readers who know exactly where to look absorb the numbers in minutes.