How to run an async standup on Starch

Internal Comms & Meetings11 roles covered4 Starch apps

An async standup is how distributed and hybrid teams stay aligned without a daily calendar block. Instead of pulling everyone into a meeting at 9am, each person answers the same three questions — what did I do yesterday, what am I doing today, is anything blocking me — on their own schedule, usually in Slack or email. The team reads updates when they have context, not when a calendar invite fires.

What this looks like in practice varies: a four-person product team might post in a Slack channel every morning; a solo operator managing contractors might send a Friday summary by email; a ops-heavy team might tie updates directly to open tasks in their project tracker. The format is flexible. The discipline isn't.

On Starch, the daily friction disappears. Your open tasks from Project Management surface automatically in the standup prompt. Responses come back into a single thread — no hunting across Slack channels or inboxes. By the time you sit down in the morning, yesterday's blockers are flagged, today's priorities are listed next to who owns them, and anything unanswered from the previous round is already marked for follow-up. You see a clean daily digest, not a pile of messages to sort through.

Internal Comms & Meetings11 roles covered4 Starch apps
Context

Why it matters

Why this is hard today

Without a consistent async standup, blockers sit invisible until someone asks. Duplicated work compounds across a small team because nobody knew the other person had already started. Context lives in people's heads, which means every handoff requires a meeting. A reliable standup loop surfaces problems in hours, not days, and creates a lightweight record of what actually shipped — which matters when you're reporting to investors or reviewing a quarter.

Watch out for

Common pitfalls

Where this usually goes wrong

Collecting updates but never acting on blockers — the standup becomes performance. Letting the format drift so some people post paragraphs and others post one word, making the updates useless to compare. Running the standup in Slack but tracking tasks in a separate tool, so nothing ever syncs and the updates go stale immediately. Skipping the follow-up loop — if nobody reviews yesterday's blockers before today's updates go out, the standup is just a log nobody reads.

Toolkit

Starch apps used

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →
Pick your role

Choose your operator

A version of this guide tailored to your role — same recipe, different starting context.

Run run an async standup on Starch

You're on the list! We'll be in touch soon.