The pain

It's 4pm on a Friday. The week is in your head as a blur of meetings, half-finished slack threads, and the one thing you actually shipped. Now five different people need you to make sense of it for them — in five slightly different voices — by the end of the day.

You don't dread the work. You dread the proof of the work.

Twenty-five minutes per recap. Five clients. Two hours, every Friday, forever. Not hard. Just relentless. Maybe that's the worst kind of task: the one too small to feel like work and too repeated to ever go away.

Who has it

Service freelancers. Fractional anyone. Retainer consultants. Anyone whose business is ongoing work for several specific people who need to feel kept-in-the-loop.

The pain shows up wherever the model is "you, on retainer." It scales linearly with clients and never goes away on its own.

The fix

One Claude Project that drinks your week and pours it back out as a recap in your voice.

You feed it three things — calendar entries, the threads with that client, and a short bullet dump of what you actually did. It hands you a draft. You edit two minutes. You send.

Setup (30 min, once)

  • Create a Claude Project. Name it "Client recap drafter."
  • Drop in 3–5 sample recaps you've already written. These are the voice anchor. Without them, you get the generic AI mush — that flat, slightly customer-service tone that makes the client suspect you've stopped paying attention.
  • Write the system prompt. Keep it short:
    • > You write Friday recaps for [name]'s clients. Match the voice in the examples exactly. Section headers: Shipped, In Progress, Blocked, What I Need. Plain English. No buzzwords.
  • Test on one client. Edit. Adjust the prompt until output needs only two minutes of polish. The voice is a knob, not a cliff — turn it gently.

    • Running it (15 min, weekly)

  • Open the project. Paste this week's calendar excerpts, thread excerpts, and your bullet dump.
  • Read the draft. Edit lightly. Send.

    • That's it.

    What it looks like running

    The input is messy. Eleven calendar entries. Three Slack threads. A bullet dump that says: shipped homepage v3, fixed checkout bug, started SEO audit, blocked on copy from Anna.

    The output is a clean four-section recap your client can scan in thirty seconds. The Blocked and What I Need sections sit exactly where their eyes land. They reply faster. You move on.

    Eight hours a month back. No client complaints. No 4pm-Friday decision fatigue.

    Why this works

    This is the smallest possible Editor-tier workflow — AI as Editor. The trust ask is the one any solo operator can answer yes to: "Can AI produce text I'd be willing to put my name on?"

    The voice anchors solve that. Without them you ship AI prose. With them you ship your prose, written faster.

    It also runs as an agent loop once you trust it. Every Friday at 3:30pm, the draft lands in your inbox before you've even thought about writing it. You stop being the one who has to remember.

    Maybe the deeper win isn't the eight hours. It's that Friday at 4pm stops feeling like a deadline and starts feeling like a deck-clearing.