How long does writing a weekly client update by hand actually take?

For me it was roughly forty minutes per client. With eight active accounts that is over five hours every week of senior time spent on retrieval and formatting, not on actual thinking.

What changed when I started using AI to draft client updates?

The drafts went from forty minutes each to twelve minutes to review and approve. The lead is now editing one or two sentences per email instead of authoring nine paragraphs.

Does the client know the update was AI-drafted?

No. The draft goes from Orbis to the lead's Slack DMs. The lead reviews, edits, and approves. The email is sent from the lead's Gmail, signed by them. There is no AI signature, no auto-send to the client. Trust stays human.

What if our agency has a strong house writing voice?

Orbis is trained on six months of your sent client emails before it drafts anything. After three to four weeks the drafts read like the lead who owns the account, not like a generic AI.

Does this replace the account manager?

No. It changes what they do on Friday. The lead is now reviewing eight drafts instead of authoring eight emails. The time saved goes back into actually calling two of the clients.

Why I stopped writing my own weekly client updates

For the first two years of running my agency, I wrote every weekly client update by hand. Eight active clients, every Friday, roughly forty minutes per email. I am being generous with the forty minutes. Some Fridays it was an hour. Some Fridays I pushed it to Sunday night and pretended I was being thoughtful.

The math is simple and embarrassing. Eight clients times forty minutes is just over five hours, every week, of a senior person stitching together what was already in Slack, Notion, and the team's last three calls. Five hours of looking up what shipped, who said what on Tuesday, whether the timeline still made sense, and then turning it into a paragraph that read like I had been thinking about each account all week.

I had not been thinking about each account all week. I had been running the agency. The Friday email was a performance of attentiveness, written quickly because attentiveness had not actually been possible.

"The Friday email was a performance of attentiveness, written quickly because attentiveness had not actually been possible."

Why the work was always a tax

Weekly client updates are the canonical example of high-leverage-looking work that is actually low-leverage. They feel important because the client reads them. They look senior because they go out under the founder's name. They are not, in fact, senior work. They are pattern-matching on what already happened, formatted into prose.

The format is also nearly identical every week. What shipped. What is in flight. What is blocked. What is coming next. A line of strategic context. A clear call to action. I had written hundreds of these. The thinking inside each one took two minutes. The retrieval, formatting, and tone took thirty-eight.

If I had an account manager, that person would have done this work. I did not have an account manager. I had me, two senior leads, and a team of designers and strategists who should not have been writing client emails on a Friday afternoon either.

The dumb thing I tried first

The first version of what is now Orbis was not a product. It was a Sunday-night habit. I would paste the week's Slack threads into a Claude conversation, ask for a draft, and rewrite the parts that did not sound like me. It took about twelve minutes per client instead of forty. That alone saved me three and a half hours a week, which is most of a workday.

What I did not expect was how much better the drafts got once Claude had context on the client. After about three weeks of feeding the same accounts the same way, the drafts stopped needing structural edits. I was rewriting two sentences out of nine. By week six I was approving most of them.

The problem was that this habit lived in my head. It worked because I knew which Slack channels to copy, which Notion docs were canonical, and what tone each client wanted. If anyone else on the team had tried to do the same thing, the drafts would have been generic, and they would have stopped doing it within a month.

What I actually built

The version of Orbis that runs my agency now does three things on the weekly-update problem.

First, it watches the client channels in Slack continuously. Not on Friday afternoon. All week. It builds up a running picture of what shipped, what was discussed, what was promised. When Friday comes there is no retrieval problem, because the retrieval has been happening in the background.

Second, it drafts the email in the agency's house voice. We loaded six months of sent client emails as voice training. The drafts now sound like the lead who owns the account, not like a generic AI. This is the part that took the longest to get right, and it is the part that separates Orbis from a Zapier template.

Third, it routes the draft to the account lead in their Slack DMs, with a one-click approve and edit flow. The lead reads it, makes any changes they want, and approves. The email goes out from their Gmail, signed by them. Most weeks the edits are cosmetic. Some weeks the lead overrides the draft entirely. Both are fine.

The point is that the lead is now reviewing instead of authoring. Reviewing is a fifteen-minute job. Authoring was a forty-minute job. We do this across roughly forty client accounts now, and the time saved adds up to most of an FTE.

What this is not

This is not a story about replacing account managers. We hired our first dedicated account lead nine months ago, and she is still the person every client trusts. What changed is what she does on a Friday. She no longer writes eight updates. She reviews eight drafts and uses the saved time to actually call two of the clients.

This is also not a story about prompting tricks. The reason this works is not that I figured out the right system prompt. It is that the system is wired into the actual flow of work. Slack, Gmail, the agency's voice, the per-client context, the lead's review, the sent email. If any of those links is missing the whole thing collapses back into a Sunday-night chore.

I think this is what most agencies miss when they try to use AI for client work. They reach for it at the moment the work is due, instead of letting it run in the background all week. The version that runs all week is the one that produces drafts good enough to send.

If you are doing this by hand

You probably know within thirty seconds whether this matches your week. If you are a founder or a senior account lead at an agency between five and twenty-five people, and you are still writing weekly client updates yourself, you are doing five hours a week of work that does not require you.

The fix is not a Notion template, a writing assistant browser extension, or a Zapier flow that pulls a list of links into an email. Those are improvements at the margin. The fix is a layer that lives between Slack, Gmail, and the people on your team, and that thinks of itself as the agency's coordination layer rather than as a writing tool.

That layer is what we built into Orbis for creative agencies and Orbis for marketing agencies. If you want it configured for your specific workflows on day one, the Orbis Launch Sprint is two weeks, fixed scope, $7,500.

I will write more about the other pieces of the agency week that broke the same way. Pre-review briefings, internal deliverable chase, retainer reports. They all share the same shape. A senior person doing pattern-matching work because nobody else has the context. Most of agency operations is this. Most of agency operations does not need to be.