2026-10-01 · Gavril team

Kill the client standup: async rituals that work better

We've said it about internal meetings: most are status updates wearing a calendar slot. Client calls are worse — prep time, small talk, and a readout of things everyone could have known already. Thirty minutes weekly per client is a full workday a month, per PM, spent narrating a board.

Someone writing on a whiteboard

What replaces the call

The async pulse. A short update in the client's chat on a fixed rhythm: shipped, in progress, blocked-on-you, next. Under 100 words, in their language, generated from the board so it's never stale and never skipped. The rhythm does the psychological work the meeting used to do — the client feels held without holding a slot.

On-demand answers. The real reason clients like calls: it's the one place questions get answered immediately. Give them that in chat instead — "where's the homepage?" answered from live data in seconds — and the appetite for meetings drops fast.

Decision-only meetings. Keep meetings for what synchronous time is actually good at: choices with trade-offs, kickoffs, hard conversations. The agenda test is one question — what are we deciding? No answer, no meeting.

The trap

Async fails when it becomes a place to hide. Two guardrails: blocked-on-you items go out the moment they appear (not in the next pulse), and questions that stall in chat for a day escalate to a human automatically. Async isn't less communication — it's the same communication with the waiting removed.

Run it for a month and the weekly call quietly becomes biweekly, then "as needed". No client has ever complained about fewer meetings and faster answers.

← All posts