Monthly client reports without the deck.

The ten-hour problem

The question came from a marketing agency that builds a PowerPoint for each client every month. Ten to twelve hours of the month go into it. The screenshots go stale between the export and the meeting, the same charts are rebuilt by hand, and the person doing it suspects the client flips to the last slide. A second thread, from a freelancer asking how to cut down on client reports, described the same work from a smaller shop: too many hours, the same shape every time, the sense that most of it is not read.

Neither poster wanted to report less. They wanted to spend the hours on the part that matters and stop rebuilding the part that does not.

What the replies agreed on

• Drop the static deck. A slide export is a snapshot of numbers that have already moved. Give each client a live view they can open whenever they want.
• Standardise the shape. One report structure across every client, so month two is an update, not a new build.
• Automate the numbers. Pull from the ad platforms and analytics directly. Nobody should be retyping figures into a slide.
• Write a short narrative. Three or four sentences: what changed, why, what happens next. The replies were clear that this is the part clients actually read.
• Send a link, not a file. One reply described sending an HTML report on a company link instead of an attachment, so the client always has the current version.

Numbers and narrative are different jobs

The most useful idea in the thread was the split. The numbers pull is mechanical and should be automated, whether by a reporting tool, a script, or an agent you point at the data. The narrative is judgement and should be written by the person who ran the campaign. When both live in one deck, the mechanical part eats the hours and the judgement gets three minutes at the end.

Separating them changes where the time goes. The page with the numbers builds itself. The narrative gets the attention, and it is short, because a client who wants the detail can scroll to it, and a client who does not can read four sentences and know where they stand.

The report as a page

The practical form is one HTML page per client per month, on a private link. The top is the narrative. Below it, the numbers and charts the agent or the reporting tool produced. The client opens it from the email you sent, on any device, with nothing to install or sign into. If the figures are sensitive, add a passcode, or an email gate so anyone at the client's company can open it and nobody else can.

We wrote the step-by-step version in send a client report as a link, not a PDF attachment. The short form: build the page, publish it, send the URL. From Claude, ChatGPT, Codex or any agent with the MCP connection, the publish is one call and the URL comes back in the reply.

The monthly loop

Month two is where the page beats the deck. Instead of a new file and a new email, you update the page in place at the same URL. The client's bookmark from last month now shows this month. Previous months sit in a client space, one address per client that lists every page you have sent them, which is as close to a portal as the thread's participants wanted to get: read-only, kept current as a by-product of doing the work, nothing to log into.

You also stop guessing whether it landed. A page shows when it was opened and by roughly how many people. On paid plans it shows how far it was read and where attention went, which tells you whether the narrative is doing its job or whether the client is scrolling straight to one chart. That is a better input to next month's four sentences than silence.

When a deck is still right

A quarterly business review presented in a room is a deck. A board pack that has to be archived unchanged is a PDF. The monthly report is neither: it is a status update that the client wants to check, not present, and it changes every month by definition. Build the deck for the meeting that needs one. Send the page for everything else.