The monthly client report is the document an agency's relationship depends on, and it is usually written last-minute, from memory, by the person who did the least of the work. Cogny now writes it from the record.

The new Monthly Client Report template runs on the 2nd of every month in a client's workspace and writes a client-ready summary of the month before: what was done, what it measurably changed, how the headline numbers moved, and what happens next.

TL;DR

What it reads: every change shipped in the workspace last month (campaigns, ads, keyword changes, posts, website and code changes, recurring loops), the measured result of each one, the earlier reports, and the client's connected data sources.
What it writes: a five-minute report in seven sections, from "at a glance" to "plan for next month", for you to review and pass on to the client.
What it won't do: count a change as a win before its measurement is in, invent a dollar figure, or list rejected ideas as work.
Where: Cloud workspaces, from the Loops tab. Any chat can also answer "what did we do in September?" with the same records.

What the report contains

At a glance: three to five bullets with the most important result, the work in one sentence, the main KPI move and the main thing planned next.
Headline KPIs: four to six numbers for the month against the month before, with the change in percent. It uses the core metrics you configured in the workspace first, then the KPIs in your measurement plan, then the obvious ones for the connected sources (spend, conversions, cost per conversion, ROAS, sessions, clicks).
What we did: the month's work grouped into three to six workstreams ("Google Ads efficiency", "Landing page conversion") rather than a list of tickets. A loop that ran every week is one line, not four.
Results: each change whose measurement concluded, with what we expected, what we measured and the outcome: worked, partly, didn't work or too early to tell. Changes shipped the month before whose result only came in this month are included, with their ship date.
Still being measured: shipped work waiting for its follow-up check, with the date of the check.
What we're watching: up to three findings from the month's scheduled analyses that the work doesn't already cover, and the status of every item in last month's plan: done, in progress or dropped.
Plan for next month: three to five steps, each tied to something in the report.

The report is written in your voice: "we" is the agency. It does not name the software behind the work, ticket numbers or tool names, unless your instructions ask for it.

Why the numbers can be trusted

Every change made through Cogny is a record with a stated expected outcome and a follow-up measurement, whether it was shipped from a chat, by a loop, by the code agent or by hand. The report is built from those records and from queries it runs on the client's data in the same run. Failed and inconclusive results go in the report too, in one line each with what was learned. A report that only lists wins reads as a sales pitch, and clients notice.

If little was shipped in a month, the report says so and puts the weight on the KPIs and the plan. It never pads the work list.

Making it yours

The report's instructions override the template. Typical lines agencies add:

"The client is Acme Outdoor. Write in Swedish, amounts in SEK."
"Always include Meta and Google Ads spend side by side."
"Leave out the website work — another agency owns the site."
"Report on the period from the 15th to the 14th."

Each client has its own workspace, so the report only ever sees that client's work and data.

In any chat, too

The records behind the report are open to the chat on every plan. Ask "what did we ship in September and what did it change?" or "what did last month's client report promise?" and the answer comes from the same records, with the same rules about what counts as a measured result.