Internal Comms & Meetings

How to run an async standup as Chief of Staff and Founder's Office

Internal Comms & MeetingsFor Chief of Staff and Founder's Office3 apps11 steps~22 min to set up

You run the async standup because nobody else will. You set up a Slack channel, pinned a template, and asked 12 people to post by 9am. By 10am you have six responses, two people who posted in the wrong thread, and one engineer who wrote 'same as yesterday.' You spend 20 minutes chasing the missing updates, another 10 synthesizing what's there into something the CEO can actually read, and then you realize three blockers were mentioned across different posts that no one flagged to each other. This is supposed to save meeting time. Instead it's just moved the coordination tax onto you — the one person with the least spare time in the building.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Chief of Staff and Founder's Office3 apps11 steps~22 min to set up

Outcome

What you'll set up

A structured async standup that automatically collects updates from Slack, surfaces cross-team blockers without you having to read every post, and routes exceptions to you — not noise.

A digest delivered to your inbox and the CEO's by 9:30am every weekday, summarizing what's on track, what's blocked, and what needs a decision — without you writing a word of it.

A lightweight task-accountability layer that compares what people said they'd do yesterday against what they're reporting today, so 'same as yesterday' stops being a valid answer.

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Task Manager Project Management

Data sources & config

Starch syncs your Slack data on a schedule — channels and users are pulled automatically, so the agent reads the standup channel without any manual export. Project Management and Task Manager run natively inside Starch, so task status is always current. Starch syncs your Gmail data on a schedule, so the morning digest lands in a tagged thread that Email Triage already knows to surface.

Prompts to copy

Every weekday at 9:15am, pull all messages posted in the #standup Slack channel since 6pm yesterday. Group them by person. For each post, extract: what they did yesterday, what they're doing today, and any blockers. If someone didn't post, flag them by name. Format the output as a digest I can forward to the CEO.

Compare today's standup posts against the open tasks assigned to each person in Project Management. If someone says they completed something that's still marked open, flag it. If someone has a task due today but didn't mention it, include it in the blockers section.

Every weekday at 9:30am, send me an email with the subject 'Standup Digest — [date]' containing: a one-paragraph summary of team status, a bulleted list of blockers that need my action, and a list of people who didn't post. Mark it priority high so Email Triage surfaces it first.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect Slack: Starch syncs your Slack channels and users on a schedule. Point it at your standup channel — or multiple channels if you run standups by function (eng, GTM, ops).

2 Set the collection window: Tell Starch to pull posts from the prior evening through 9:15am so you capture both the night-before thinkers and the morning posters without missing either.

3 Define the extraction schema: Starch parses each post for three fields — yesterday, today, blockers. Anyone whose post doesn't include all three gets flagged for follow-up, not silently included.

4 Add the no-post alert: Give Starch the list of people who are expected to post. Anyone missing by 9:15am shows up in the digest under 'No update received' — so you're chasing one list, not scrolling through Slack.

5 Wire in Project Management: Starch cross-references what people say they finished against open tasks. If a task is still open but the person marked it done in their update, you see it. This is how 'same as yesterday' becomes visible as a pattern.

6 Build the CEO digest: Tell Starch to format the synthesized output as a two-section email — 'Status snapshot' (three sentences, paragraph form) and 'Needs your attention' (bulleted blockers requiring a decision or unblock). This is what you forward to the CEO without editing.

7 Set the delivery automation: Starch sends the digest to your Gmail every weekday at 9:30am. Starch syncs your Gmail data on a schedule, so Email Triage already knows to surface it above everything else that arrived overnight.

8 Configure the blocker routing: Any blocker that mentions a specific person (e.g., 'waiting on Sarah for the contract') gets flagged separately with that person's name, so you can send one Slack message to unblock three different threads instead of reading through everything.

9 Add the weekly rollup: Every Friday, Starch generates a five-day summary — what each person said they'd do Monday vs. what they actually reported by Friday. This is your accountability audit without a spreadsheet.

10 Publish the standup template to Slack: Starch can push a pinned message to the standup channel each morning via browser automation — no Slack API setup needed — so the prompt is always there and always formatted the same way.

11 Review and tune after week one: Check which people are consistently not posting, which blocker categories repeat, and whether the CEO digest is actually being read. Adjust the collection window, extraction schema, or digest format by describing the change to Starch in plain language.

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 →

Worked example

Week of March 10, 2026 — Post-board-meeting standup crunch

Sample numbers from a real run

Team members expected to post	14
Posts received by 9:15am	10
Blockers extracted automatically	6
Cross-team blockers surfaced (same blocker mentioned by 2+ people)	2
Minutes you spent on standup synthesis	4

The week after a board meeting is always the same: everyone's realigning to whatever commitments the CEO just made, and half the team is waiting on direction that hasn't come yet. On Tuesday March 11, Starch pulled 10 of 14 expected standup posts from the #standup Slack channel by 9:15am. The digest landed in your inbox at 9:30am. The status snapshot read: 'Engineering is heads-down on the auth refactor (on track); GTM is blocked on final pricing approval before sending contracts; Ops is waiting on the updated vendor list from Finance.' The 'Needs your attention' section had two items: pricing sign-off (mentioned by three GTM people independently) and a missing update from the two engineers who didn't post. You forwarded the CEO digest at 9:32am with one sentence added: 'Pricing is the critical path — needs your call today.' The CEO responded by noon. By 2pm the GTM team was unblocked. Total time you spent: four minutes, down from the usual 35.

Measurement

How you'll know it's working

Post completion rate by 9:15am — what percentage of expected team members submit on time, tracked weekly to see if the habit is holding

Blocker-to-resolution time — how many hours between a blocker appearing in standup and the blocking dependency being cleared, tells you whether the digest is actually driving action

CEO digest open and response rate — whether the output is being used or ignored, which is the real measure of whether this workflow is worth running

Repeated blockers — how many of the same blockers appear more than two days in a row, a leading indicator of a systemic problem nobody is escalating

Cross-team collisions surfaced — number of instances where two or more people in different functions mentioned the same dependency, which the old manual process would have missed entirely

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Geekbot or Standuply in Slack

Good at collecting posts on a schedule, but the synthesis is yours — you still read every response and manually identify blockers and cross-team collisions; Starch reads and routes for you.

Manual Slack channel + you as the aggregator

Zero tool cost, full control, but the aggregation, synthesis, and follow-up chase falls entirely on you — which is exactly the time you're trying to get back.

Notion standup template + weekly doc

Starch syncs your Notion data on a schedule so the doc can be an output, but Notion doesn't watch Slack and synthesize across posts automatically — you'd still need to populate it.

Linear or Asana check-in features

Tied to tasks that already live in those tools; anyone not updating Linear is invisible, and the synthesis across functions still doesn't happen automatically.

On Starch RECOMMENDED

One platform — task manager, project management, founder inbox all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

What if people post in different formats — some verbose, some just a line?

Starch extracts what it can find and flags what's missing. If someone posts 'heads-down on the roadmap doc, no blockers' and never mentions yesterday, the digest notes it rather than inventing an answer. You set the extraction schema — three fields or five — and anything incomplete is marked incomplete, not silently omitted.

Does Starch read private Slack channels or DMs?

Starch syncs public channels and channels you explicitly connect. It does not access private channels or DMs unless the authenticated account has permission to read them. If your standup runs in a private channel, you'll need to connect it with an account that has access.

Can I run standups across multiple channels — engineering, GTM, ops separately?

Yes. Connect each channel and tell Starch which one maps to which function. The digest can roll up all three into a single cross-functional summary, or generate a separate digest per channel — describe the format you want and Starch builds it.

Is this SOC 2 certified?

Starch is not SOC 2 Type II certified today. If your company policy requires SOC 2 for any tool that reads Slack, that's worth checking with your IT or security team before connecting.

What if the CEO wants the digest in a different format than I do?

Build two automations. One delivers your operational view — all posts, all flags, full blocker list — to your inbox. A second delivers a shorter, three-bullet executive summary to the CEO. Both pull from the same Slack sync; you're just describing two different output formats.

Can Starch post the standup prompt to Slack each morning?

Yes. Starch can automate posting a formatted standup prompt to your Slack channel each morning through browser automation — no Slack API configuration needed on your end. You describe the message format and the schedule, and it goes out.

What happens when someone goes on PTO and is on the expected-poster list?

Update the expected-poster list — you can do this by telling Starch in plain language ('remove Jordan from the standup list until March 22') and the automation adjusts. There's no form to fill out.