The Weekly Client Update
A weekly update is read by two people who happen to be the same person: the client with thirty seconds on his phone, and the same client at his desk before the call. The two-layer format that serves both, the five fields every project answers, and the seven rounds of editing that produced them.
v4
The Two-Layer Client Update
· Tighter: a
one-paragraph opening on why length stopped signalling effort, the layers explained after
the example rather than before it, four numbered failure modes, and eighteen tap-open
expansions carrying the depth.
v3
The Two-Layer Client Update
· Rewritten as a
readable framework article: the two-reader problem, a diagram of the fold, the four ways it
still goes wrong, and the skill moved to the end.
v2
The skill, downloadable
· The whole format
packaged as a Claude skill you can download and run on your own notes, with install steps
for Claude Code and the Claude apps. The reasoning below it is unchanged.
v1
Two readers, one email
· The two-layer
format, an anonymised GTM engineering update as the worked example, nine rules, and the
seven editing rounds that produced each one.