[NTTP]

Client Update Writer

Brain-dump what happened, get a confident client update that keeps them reassured and informed.

Messy notes are fine: what you did, any blockers, what's next.

Free to try, no sign-up needed

Your text isn't stored. It's sent to Anthropic to generate your result, then discarded. Privacy

Prefer to write it yourself? Use the free prompt.

New to this? Read the guide.

What it produces

Real output from this tool, not a mock-up.

What went in

What happened
week 3 of the physio site. finished all the page copy and sent it monday, waiting on feedback, they said thursday. design done for homepage and two service pages, they approved homepage. started the Cliniko booking integration, hit a snag because their account is on an older API version, spoke to Cliniko support and they are moving it, should be sorted by wednesday. blog migration script written and tested on 5 posts. slight risk: if copy feedback slips past thursday the build week gets tight but we still hit launch.
Update type
Weekly
Tone
Reassuring

What came back

Hi [Name], Good progress this week on the physio site. Page copy is finished and sent over on Monday, homepage design is approved, and the two main service page designs are done and ready for your review. The Cliniko booking integration is underway; we hit a snag with their account running an older API version, but Cliniko support is upgrading it and we expect that sorted by Wednesday. We also wrote and tested the blog migration script on 5 posts, ready to run the rest once copy is signed off. The one thing we need from you: feedback on the page copy, expected Thursday. If that slips much past Thursday it tightens up build week, but we're still on track for launch. Next week: finish the remaining page designs, complete the booking integration, and run the full blog migration. [Your name]

When to use it

Use this for the regular update a client expects mid-project. Brain-dump what actually happened, including the parts that went wrong, and it comes back as something reassuring and clear. Raising a risk early in your own words is the whole point.

Common questions

Should I mention problems?
Yes, and early. A problem you raise yourself, with what you are doing about it, reads as control. The same problem discovered later reads as a cover-up. The example keeps both the API snag and the risk that late feedback squeezes the build week.
What if nothing much happened?
Say that briefly rather than padding it. A short honest update keeps the client informed and costs you nothing. Inflating a quiet week into three paragraphs is how updates stop being read.
How is this different from the wrap-up tool?
This is for progress during a project. The Project Wrap-Up and Handover Writer is for the end: what was delivered, what you are handing over, and what happens after. Sending a progress-shaped update as your final message leaves the client unsure whether the project is finished.
Is it free?
You can run it three times a day with no account. Signing in gives you renewing monthly credits, and this tool costs one credit per run with the one-click refinements included.