Marketing AgenciesReportingWorkflow Automation
The last week of the month, in a lot of agencies, is not strategy. It is five people exporting numbers from different platforms into a deck that still has last month's date in the footer.
That deck is how the retainer is justified. When it slips, the account manager spends the client call apologising for the pack instead of talking about what to change. There is a commercial ceiling as well. You cannot take on another handful of retainers if each one still costs two days of reporting.
The video is about that ceiling. The rest of this piece is the workflow underneath it: where the numbers come from, what gets consolidated, what a model can draft, and who still has to read it before a client does.
How assembling client reports by hand limits the number of retainers an agency can look after properly.
What the month actually looks like
A typical pack is not one report. It is a search section, a paid or social section, an email section, and a page of commentary that tries to explain the movement. The data lives in Google Search Console, whatever SEO platform the account uses, the email tool, and one or more social or ads accounts. Each has its own definition of a click, a session or a conversion, and each has a day when the export is simply wrong.
Someone senior usually writes the commentary from memory of the account. Someone junior usually does the exporting. The delay between those two jobs is where the month disappears.
A workflow, not a new dashboard nobody opens
The aim is the pack the client already receives, produced with less handling. A live dashboard is useful for the account team. It is a poor substitute if the client has always been sent a PDF or a short deck and will not log into anything else.
One client, one month
Collect on a schedule
Search Console, the SEO platform, the email tool and the social accounts stay where they are. A workflow pulls an API response or a scheduled export into one place, per client, before anyone opens a slide.Agree the definitions once
What counts as a lead, which channel gets the conversion, and which date range the client considers "the month" are decisions. They belong in the workflow as rules, not as a debate inside every deck.Assemble the pack
Tables and charts are filled from that single set of figures. The layout should be the one the client already knows. Changing the format and the process in the same month makes it impossible to tell which one they objected to.Draft the commentary
A model can write a first pass of what moved. It is useful because the raw tables are dull to narrate. It is not useful as the last word.A person signs it off
The account lead edits the commentary, checks anything that looks like a tracking break, and sends it. Nothing goes to the client straight from the model.
Where the integrations are easy, and where they are not
Some platforms have a proper API and will give you yesterday's numbers without a person in the loop. Others will email a CSV if you ask them the night before. A few still expect someone to click export. Pretending they are all the same is how these projects stall.
Build the first version around the sources that are stable. Leave a clearly named manual step for the one platform that will not cooperate, rather than blocking the whole pack on it. The manual step should be obvious in the workflow, with a status, so it does not become "Sarah usually remembers".
Search Console is a common anchor because the data is structured and the questions clients ask about organic search are repetitive. Email platforms are similar: sends, opens, clicks, unsubscribes, on a calendar. Social reporting is more awkward, because the definitions move and the exports are inconsistent. Treat that as a known weak joint, not as a surprise in month three.
What the model should and should not write
Commentary is the part people hope AI will simply do. It can draft "organic clicks fell, paid leads held, the email send went out on the 12th". It cannot know that the fall was a tracking tag the developer removed, or that the client launched a promotion the platform never saw.
Give the model the figures and a short note of anything the account team already knows. Ask it for a draft, with the comparisons labelled as comparisons. Then have a person who knows the account delete the sentences that are guesswork. If the model cannot see a source for a claim, the claim does not go in.
This is also why a fully autonomous "reporting agent" is the wrong shape. The numbers should move by rules. The sentences need a reader. Mixing those two jobs into one unsupervised process is how a confident, wrong paragraph reaches a client.
How to start without boiling the agency
Pick one retainer that is painful, repetitive and tolerant of a slightly rough first month. Not the client who negotiates every adjective. Run it beside the old process once, compare the hours, and only then retire the spreadsheet.
We take on monthly reporting of this kind for agencies. Where that work is still in delivery, it is not a finished result, and there is no hours-saved figure to quote for it. The test for your own firm is simpler: time the next pack honestly, including the chasing, and see how much of that time was re-keying rather than judgement.
Before you commission it
- Name the pack you are automating, and the client it is for.
- List every source, and whether it has an API, a scheduled export, or a person.
- Write down the three definitions that cause arguments.
- Decide who edits commentary, and that they see it before the client does.
- Keep the first month comparable with the old pack, so you can tell whether it worked.
If monthly reporting is the process eating the account team, that is a good candidate for a free Operations Audit. We map one pack, not the whole client list. The wider pattern of pulling recurring numbers out of source systems is the work described under reporting. For how to choose between this and a shinier AI project, the framework for what to automate first is the longer version of the same instinct.