Async communication, fixed.

Stop saying “Hello.” Say something.

Respect people's time. State your context. Get faster replies — with a little help from AI.

Free. Nothing you paste is stored.

Direct message · AnaTuesday
what not to do
Marko
Hey
Ana is typing
…waiting for context that never came
10:32 — 30 minutes wasted.
instead
Marko
Hey! Can you review my Figma prototype for the onboarding flow? Specifically steps 2→3. 10 min max.
Ana
On it — leaving comments on step 3 now.
Replied in 4 minutes.

Learn by example

Examples by role

Real before/after messages — copy the good ones.

Powered by Claude

Turn your vague message into a clear one.

Not a template — Claude rewrites it the way a real colleague would.

  1. Paste your vague message
  2. Claude rewrites it with context
  3. Copy and send — get a reply
CtrlEnter to rewrite
Claude's rewrite

Don't paste passwords or anything confidential. How the fixer works

Still waiting for a reply?

Kill time. Play something.

Two games for when someone sent “hi” and you're stuck waiting for the actual question.

The Friday Dispatch

One email. Every first Friday. Always worth opening.

No “hey”. No fluff. Just a new game, a workplace horror story, and one message tip — delivered the only way it should be: with context.

New game
A fresh async challenge every month
Horror story
Real “Hey” disasters from real teams
Before / after
One message, fixed. Steal it.
2 min read
That's it. No walls of text.
From: The Friday Dispatch
Subject: “We need to talk” and other war crimes
Preview — last issue
This week: the message that ends careers, a new Don't Click Hi update, and how one PM saved 2h/day by adding three words to every Slack message…