For three years we sent clients a monthly report: fourteen pages, nine charts, a glossary. Our email analytics said 23% of recipients opened it and the median time inside was 47 seconds. We were spending six hours a month producing a document that was, functionally, unread.
So we replaced it with a memo that fits in a text message: what changed, what caused it, what happens next. One sentence, three clauses. Reply rate went from almost never to 78% within two send cycles.
This is the format, the numbers behind it, and the two situations where the long report still earns its keep.
Why the monthly report fails
The monthly report fails because it is built to demonstrate effort, not to transfer a decision. Fourteen pages of charts answer a question no client is asking — did you work hard — and bury the two they are asking: is this working, and what should I do about it? Reports written to justify a retainer read like invoices. Clients treat them accordingly.
The data is blunt. Across our client base last year, monthly PDF reports averaged a 23% open rate and 47 seconds of attention per open. The one client who read every page was the one preparing to cancel.
The failure is not the client's. A report that needs a table of contents is a report designed for the sender.
We asked clients what they did with the PDFs. Two filed them unread. One printed them for a binder nobody opens. The rest let them sink down the inbox.
Attention is the scarcest thing your client owns. A format that demands twenty minutes loses to one that demands ten seconds.
What clients actually want to know
Every client question reduces to three: what changed since last time, why did it change, and what are you doing next. A busy owner can absorb those in one sentence each. Everything else in a report — methodology, screenshots, channel-by-channel tables — is supporting evidence they will only request when one of the three answers surprises them.
We confirmed this by asking. Of eleven clients surveyed in January, ten said they would prefer one honest paragraph over the full report. The eleventh forwarded our PDFs to a spreadsheet-loving CFO. Evidence has an audience — it is just not the decision-maker.
The three questions also map to what you should be measuring weekly anyway. If answering them takes more than five minutes, the problem is instrumentation, not communication.
Write for the decision-maker. Attach for the CFO.
The one-line memo formula
The memo is one sentence with three clauses: the change, the cause, the next move. "AI citations rose from 9 to 31 this month, mostly from the FAQ rewrites on your top five pages, so next we are extending the same structure to the location pages." Under 40 words, no adjectives, at least one number. If the sentence cannot carry a number, the work probably did not move anything.
Bad news uses the identical shape. "Leads dropped 18% after the June algorithm shift, the loss is concentrated in blog traffic, so we are moving effort to the pages still converting." Clients forgive drops. They do not forgive fog.
Cap it at 40 words. The discipline is the product.
One memo per week beats one report per month. Cadence builds more trust than volume.
Three memos we actually sent in June
Real examples land better than templates, so here are three memos from June, lightly anonymized. A coffee roaster: "Wholesale inquiries doubled to 14 after the sourcing page rewrite, so we are building a wholesale FAQ next." A law firm: "Perplexity now cites you for 6 of 20 tracked questions, up from 2, driven by the attorney bio rewrites." A cleaning company: "Mobile bounce fell from 61% to 44% after we cut the hero animation, so the calmer design is now permanent."
Notice what is absent: no "we are pleased to share," no "as per our strategy." The memo starts with a number and ends with a verb.
Each took under four minutes to write, because the measurement already existed. The memo is cheap when the instrumentation is real.
The law firm memo drew a reply in four minutes: one word, then a referral. Fourteen pages never once did that.
Steal the shape, not the sentences.
Back it with a live appendix, not a PDF
The memo needs a place to point when a client wants depth, and that place should be a live dashboard link, not an attachment. We keep one URL per client with the running numbers: citations tracked, traffic, leads, and the change log of what shipped. The memo links to it. About one client in four clicks through in a given week, which is fine — the link's job is availability, not readership.
A PDF is a snapshot that ages the moment you export it. A link is an open door. The difference in perceived honesty is bigger than it sounds.
Ours is a one-page dashboard the engine updates nightly. A shared spreadsheet works just as well in month one.
Never gate the appendix behind a meeting. Availability is the message.
Automate the memo without faking the voice
We draft memos with an agent that reads the week's metrics and change log, then writes the three clauses in our house style. A human reads every draft before it sends, edits about a third, and kills the occasional one that is technically true but tone-deaf. Drafting time fell from six hours a month to roughly 40 minutes, and the send has not been missed once in five months.
The rule that keeps it honest: the agent may only cite numbers that exist in the metrics store. No summarizing vibes. If the week genuinely moved nothing, the memo says so — flat week, test still running, next read on Friday.
A flat week reported plainly builds more credibility than a padded one dressed up.
When the long report still earns its keep
Two moments justify the full document: renewals and strategy resets. At renewal, a client is deciding whether the year was worth it, and a twelve-month narrative with cumulative numbers answers that better than 52 one-liners can. At a strategy reset, the long form forces you to defend the plan in writing before you spend anyone's money on it. We now produce exactly two long reports per client per year, and both get read.
Everything between those two moments is memo territory.
The report was never the deliverable. The result was. Shrink the reporting until the result is the only thing left in view — and if you want the memo, the dashboard, and the nightly numbers wired up without building any of it yourself, that operating layer is what we install for every Avakata client.