Client Update Writer

The default client update is either a wall of activity bullets ("we spent 14 hours on the homepage") or a vague "all good, more next week." Both make clients anxious — one because they have to interpret, the other because they suspect you're hiding something. The Client Update Writer enforces the format that actually builds trust: traffic-light status in the subject line, one-sentence dashboard summary at the top, wins before issues, issues paired with proposed solutions, asks as a numbered list with deadlines.

The wins-first order isn't decorative — it's psychological. If you lead with the delay, the client reads the rest of the email through an anxiety lens and even the good news feels like damage control. Lead with what shipped, then surface the issue with a recommendation already attached. The client's job becomes choosing between solutions, not figuring out what to do.

The tone shifts with relationship stage. A new client in week two needs more context and warmth than an established one in month nine. Executive stakeholders get the under-150-word version — dashboard line, two wins, one issue, one ask — because they read top-down and stop early. The skill calibrates automatically rather than producing the same generic update for every reader.

It refuses to hide bad news. If you ask it to soften a RED into a GREEN, you'll get pushback — clients always find out, and hidden delays destroy more trust than disclosed ones. What you'll get instead is an honest AMBER framed professionally: own the cause, propose the fix, show the revised plan. That email is the one that keeps the account.