Client/Stakeholder Status Email Builder

The problem this kills

Friday afternoon, five clients, five status emails to write - and they all need to be on-brand, accurate, and say the right amount to the right person. So you copy last week's email, paste in the new dates, change the greeting, hope you didn't leave another client's milestone in there, and fire it off. Then Monday someone asks why their update was a week stale, or why it mentioned a budget figure they were never supposed to see.

Client and stakeholder status updates are high-stakes and low-glamour. They're the comms most likely to get rushed, copy-pasted, or skipped entirely when the week gets busy - and they're exactly the ones where a typo, a stale date, or one client's data leaking into another client's email does real damage to the relationship.

This tool takes your project status data and turns it into a clean, branded, tailored draft for each stakeholder - and then it makes a human read and approve every single one before it can leave the building.

What you'll build

A small internal web app, just for your delivery team, that:

• Imports your project status data from a CSV or Google Sheet (project, milestones, % complete, dates, risks, next steps - your real fields).
• Imports your stakeholder/recipient list - who gets updates, for which project(s), and at what level of detail.
• Drafts a tailored email per stakeholder using your branding and template, pulling in only the status items that stakeholder is allowed to see.
• Lets the PM edit the draft - both the recipients and the content - in a clean review screen.
• Sends via Resend only after an explicit approval click. No approval, no send. Ever.
• Dedupes on (stakeholder + period) so the same client can't get two status emails for the same week.
• Keeps a complete send log - who was drafted, what was approved, who sent it, when, and to whom - and exports it as CSV.

What's inside the Implementation Plan

The plan is a single markdown file you paste into Claude Code (a free AI coding agent). It walks the agent through building the whole tool step by step, each step ending with a ready-to-paste prompt.

The most important part: the plan opens by interviewing you about your business. Before it writes a single line, the agent asks how you report status today, what's actually in your status export, who your stakeholders are and what each one is (and isn't) allowed to see, your branding and tone, how often you send and what a "period" means, and your messy edge cases (a client with two contacts, a project on hold, a number you must never expose). It reads a short tailored spec back to you, you confirm it, and only then does it build - so you get a tool shaped to your clients and your template, not a generic one you have to fight.

Inside you'll find:

• The discovery interview and how the agent turns your answers into the data model and per-stakeholder visibility rules.
• The full build: database, login, status + recipient import with duplicate guards, the per-stakeholder draft generator, the branded template, the edit-and-approve review screen, and the Resend send.
• The hard human approval gate and the per-client confidentiality rules, enforced in code.
• Verification steps so you can prove it works, and the CSV-export fallback so it's fully usable even before you connect it to any project system.

The governance it includes (this is the point)

This isn't a mail-merge toy. The plan builds in the controls a client-facing team actually needs:

• Login so only your team can draft or send anything.
• Row-level security so people only see their own organization's projects and stakeholders.
• A complete audit trail - every draft, edit, approval, and send is logged with who and when.
• A hard human-in-the-loop gate - the AI drafts, but a person must review and approve both the recipients and the content; nothing is ever auto-sent.
• Per-client confidentiality - each stakeholder's email is built from only the status items they're cleared to see; one client's data physically can't end up in another's email.
• Duplicate guards so the same stakeholder can't be sent two updates for the same period.

Who it's for

Account managers, client-facing project managers, delivery leads, and ops/BPM folks who send recurring status updates to clients or stakeholders and want them consistent, on-brand, and safe - without hiring a developer or wedging their process into a heavyweight PM platform. You don't need to write code. You need your status export, your recipient list, your template, and an afternoon.

You've got this - paste the first prompt and let the agent interview you.