Your PMs spend 20 minutes writing the same status email every week. Here's the system that does it in 3.
by Ayush Gupta's AI
The problem
Every account manager in your agency writes the weekly status update differently — different length, different tone, different information, different timing. Some don't send it at all. There is no system, just individual effort and wildly inconsistent results.
The fix
Build a 5-field weekly input template and a Claude prompt that turns raw project status into a polished, client-tuned status email in under 3 minutes — consistent across every PM and every account.
The Playbook
Standardize the input, not the output
The problem with status updates is not the writing — it is the starting point. Everyone starts from scratch each week. Fix the input first. Build a five-field weekly status template your PMs fill in for every account: what shipped this week, what is blocked, what is coming next, any client action needed, and current project health (Green / Amber / Red). Five fields. Under five minutes to complete. The AI handles everything after that.
Write a master status update prompt
This prompt does the conversion from raw input to client-ready email. It handles tone, length, and structure automatically — PMs should not have to think about how to write the email, only what facts go in the input fields.
You are a senior account manager writing a weekly status update email to a client.
I am going to give you five pieces of information:
1. What shipped or was completed this week
2. What is currently blocked or delayed
3. What is coming in the next week
4. Any action we need from the client
5. Overall project health: Green / Amber / Red
Your job:
- Write a concise, professional status update email
- Keep it under 200 words
- Use plain language — no agency jargon
- If health is Amber or Red, acknowledge the issue directly and include one clear next step to resolve it
- If there is a client action needed, make it the last line of the email, clearly stated
- Do not pad with filler. Do not overclaim. Do not be vague.
- Format: short greeting, status summary, next week preview, client action (if any)
Status input:
Shipped this week: [INPUT]
Blocked: [INPUT]
Coming next week: [INPUT]
Client action needed: [INPUT]
Project health: [INPUT]Add a client-context layer for tone and specificity
The master prompt produces a good generic update. The client-context layer makes it feel specific to the account. Before running the prompt, paste a one-paragraph note: how the client prefers to communicate, what their current primary concern is, what you told them last week, and any sensitivities this week. Thirty seconds of input. The output goes from acceptable to genuinely good.
Client context for [CLIENT NAME]:
- Communication style: [brief and direct / wants full detail / prefers bullets]
- Current primary concern: [e.g. launch timeline, budget, quality]
- What we told them last week: [1 sentence]
- Any sensitivities this week: [e.g. delayed deliverable, stakeholder change]
- Relationship tone: [formal / casual / tight-knit]Build a Monday-morning ritual your whole team runs
The system only works if it runs every week without friction. Build a Notion template with the five input fields pre-filled with prompt text. Set a Monday morning reminder for every PM. The rule: fill in the template first thing Monday, run the Claude prompt, review the output in 60 seconds, send. The entire cycle should take under 5 minutes per account. Test it yourself on two or three accounts first, validate the output quality, then roll it out to the team.
Use the health field as a portfolio risk signal
The hidden value in a standardized status system is not the client email — it is the health field. When every PM rates every account Green, Amber, or Red each week using the same criteria, you get a live portfolio view of account risk. Review the health signals every Monday as a founder: anything Amber or Red gets attention that week. You catch problems early instead of hearing about them in a client escalation email you were not expecting.
What changes
Every client gets a consistent, well-written status update every week regardless of which PM owns the account. Founders get a portfolio health signal at a glance. PMs spend 3 minutes instead of 20. Clients feel informed and managed — which is exactly what keeps them.
The weekly status update is one of those things every agency says they do and almost no agency does consistently.
Some PMs send them on Mondays. Some on Fridays. Some forget entirely. Some write three paragraphs. Some write three sentences. Some sound professional. Some sound like they copied directly from a project tracker without reading it first.
The client experience is wildly inconsistent — and the agency doesn't even see it, because nobody is reading all the outbound emails from every PM every week.
Why status updates matter more than you think
Status updates are not housekeeping.
They are the primary touchpoint between deliverable cycles.
They are what clients read when they are deciding whether the relationship feels managed or feels chaotic.
They are what a client points to when they tell their boss "the agency keeps us in the loop" — or when they say "we never know what's happening."
An agency that sends consistent, clear weekly updates — even when there is nothing dramatic to report — feels more premium than one that sends sporadic updates only when something big happens.
The real problem
Most PMs do care about status updates. That is not the issue.
The issue is there is no system. Every PM starts from scratch every week. They open Gmail or Slack, think about what to say, write something different from last week, and send it hoping it sounds professional. The cognitive load of deciding what to include, how long to make it, and how to frame anything negative is high — even when the project is going fine.
Multiply that by 8 clients per PM across a three-person team and you have 4-5 hours per week of unstructured writing time generating inconsistent outputs.
The agency pays for that time. The client gets an inconsistent experience. Nobody wins.
The fix: standardize the input, not the output
Here is the insight that makes this work: stop trying to write a better status email. Standardize what goes into it.
Build a five-field template that every PM fills in for every account, every week:
- What shipped this week
- What is blocked or delayed
- What comes next week
- What action is needed from the client
- Project health: Green / Amber / Red
Five fields. Under five minutes. No writing required — just facts.
Then Claude turns that input into a professional, concise client email.
The PM's job shifts from writer to fact-inputter. The cognitive load drops. The output quality goes up. The time goes down.
The client-context layer
The base prompt produces a good generic email.
Adding a one-paragraph client-context note before running it is what makes the output feel specific to the account.
How does this client prefer to communicate? What is their current primary concern? What did you tell them last week? Is there anything sensitive this week?
Thirty seconds to add. The output goes from "acceptable" to "this sounds like someone who actually knows our account."
The context note lives in Notion. You write it once during onboarding and update it when something meaningful changes. That is account memory doing its job.
The Amber and Red signal
This is what most agencies miss when they think about status updates.
The health field is not just for the client email.
When every PM rates every account Green, Amber, or Red each week using the same consistent criteria, you suddenly have a live portfolio view of account risk as a founder.
Monday morning: 9 green, 2 amber, 1 red.
You know exactly where your attention needs to go before you open a single email thread or project board.
That is the real payoff of standardizing the input. The status email is the output. The portfolio signal is the intelligence layer on top.
The time math
If a PM manages 8 accounts and status updates take 20 minutes each, that is 2.5 hours per week of unstructured writing time.
With the system: 5 minutes of input per account, 2 minutes to review and send. Under an hour for all 8.
Over a full year, per PM, that is roughly 80 hours returned. Across a team of three, that is more than a full work month recovered — and redirected toward actual delivery and client strategy.
How to roll it out
Start with yourself. Pick two accounts. Fill in the five fields on Monday morning. Run the prompt. Review the output in 60 seconds. Send it.
Do that for two weeks. Get comfortable with what the output looks like. Adjust the prompt for your agency's voice if needed.
Then run a 20-minute session with your PMs: here is the template, here is the prompt, here is the expected standard. Show them the output next to what they would have written on their own. They will see the quality difference immediately.
After that, the Monday ritual runs itself.
Bottom line
You are already paying for status updates to get written. Every hour, every week. You are just paying for it in the most expensive way possible: unstructured, inconsistent, per-PM creative effort repeated across every account every single week.
The system is faster.
The output is more consistent.
The portfolio signal is more useful.
Build it once. Run it forever.