Internal Comms & Meetings

How to run an async standup as Foundation and Nonprofit Ops Teams

Internal Comms & MeetingsFor Foundation and Nonprofit Ops Teams3 apps11 steps~22 min to set up

Your four-person ops team runs weekly check-ins over Zoom or a shared Google Doc that nobody updates in time. Half the team is coming off site visits or donor calls, so the standup gets pushed, skipped, or turns into a 45-minute debrief. Action items from the last meeting live in someone's notes file or an old Slack thread. By the time you're back at your desk, you've forgotten what you committed to — and so has everyone else. You have no EA, no chief of staff, and no dedicated project manager. The tools that could fix this (Asana, Monday, Notion-with-all-the-templates) cost admin time you don't have.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Foundation and Nonprofit Ops Teams3 apps11 steps~22 min to set up

Outcome

What you'll set up

A weekly async standup that each team member completes on their own schedule — updates collected, summarized, and surfaced to the team without a live meeting

Automated action-item extraction from standup responses, linked to your existing task list so nothing falls through after the update is submitted

A running archive of every standup — searchable by person, program area, or grant — so you can answer 'wait, who was handling the Kresge renewal?' without digging through Slack

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

Meeting Notes Task Manager Project Management

Data sources & config

Slack is connected from Starch's integration catalog so the agent queries it live to post digests and read prior standup threads. Google Calendar is synced by Starch on a schedule to know each team member's availability and flag weeks with board meetings or site visits that might shift deadlines. Notion is synced by Starch on a schedule so grant-area context and program notes are searchable. Any donor portal or grantee reporting site that doesn't have an API can be reached through browser automation — no API needed.

Prompts to copy

Build me an async standup for a 4-person foundation ops team. Each week, prompt each team member to answer: what did you complete this week, what are you working on next week, and what's blocked. Collect responses by Thursday EOD, summarize by person, flag any blockers, and post the digest to our Slack channel.

Extract all action items from this week's standup digest and create tasks for each person. Set priority based on whether the item is grantee-facing, board-facing, or internal. Flag anything due before our next board meeting.

Show me all standup updates from the last 90 days where someone mentioned the Kresge or MacArthur grants. Summarize what's changed.

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

Walkthrough

Step-by-step

1 Connect Slack from Starch's integration catalog so the standup prompt and digest can be posted to your ops channel automatically each week.

2 Connect Google Calendar — Starch syncs your calendar on a schedule — so the automation knows when board meetings, site visits, or grant deadlines are coming up and can flag those in the standup digest.

3 Connect Notion — Starch syncs your Notion workspace on a schedule — so program area pages and grant notes are available as context when Starch summarizes blockers.

4 Tell Starch what you want: 'Every Monday at 9am, send a standup prompt to each of the four team members in Slack. Ask what they completed last week, what they're focused on this week, and what's blocked. Collect responses until Thursday EOD.'

5 Tell Starch how to handle the digest: 'On Thursday at 5pm, summarize all standup responses by person, pull out any blockers, and post the summary to #ops-standup in Slack. If a board meeting is on the calendar within 10 days, flag any board-related items in bold.'

6 Add action-item extraction: 'After posting the digest, create a task in Task Manager for every action item mentioned. Assign to the person who mentioned it. Set due date based on what they said; if no date, default to end of following week.'

7 Review the first digest manually — spot-check that Starch is reading program areas correctly (Kresge, MacArthur, community grants, etc.) and adjust the prompt if it's missing context.

8 Add a compliance layer if needed: 'If any standup mentions expenditure responsibility, 990 timing, or audit prep, flag it separately and add a task for me to review.'

9 Use the Meeting Notes app for any live calls that do happen — it transcribes in real time, extracts decisions and action items, and archives them in the same searchable history as the async standups.

10 At the end of each quarter, ask Starch: 'Summarize all standup updates from Q1 2026 by program area. What recurring blockers came up? What action items were mentioned more than once and never resolved?' Use that output to prep your quarterly ops review.

11 If a board member asks what the team has been working on, pull the archive: 'Show me all standup digests from January through March where anyone mentioned the Sunrise Fund or the workforce development portfolio.'

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 — Q1 close crunch

Sample numbers from a real run

Team members who submitted standup on time	4
Action items extracted automatically	11
Blockers flagged to ops director	2
Minutes spent in a live standup meeting	0

It's the week before the March board meeting. All four team members are running on different schedules — one is back from a site visit in Detroit, one is wrapping a 990 review with the auditor, and two are finalizing the Q1 grant disbursement report. Nobody has time for a 9am Zoom. On Monday morning, Starch posts the standup prompt to #ops-standup in Slack: three questions, 10 minutes per person, due Thursday. By Thursday at 5pm, all four have responded. Starch posts a digest: per-person summaries, two blockers flagged (one DocuSign bottleneck on a grant agreement, one QuickBooks reconciliation that's 2 weeks behind), and 11 action items pushed to Task Manager with owners and due dates. The ops director sees the digest in Slack, addresses the DocuSign hold with one reply, and forwards the QuickBooks flag to the finance contractor. No meeting scheduled. The board packet prep that usually falls off the radar because nobody tracked who was doing what? It's now a task assigned to the right person with a due date of March 14. The archive from the prior 8 weeks shows the QuickBooks reconciliation delay has come up three times — that's the quarterly ops review agenda item nobody would have noticed.

Measurement

How you'll know it's working

Standup completion rate — % of team members who submit their update before the Thursday cutoff each week

Blocker resolution time — days between a blocker being flagged in standup and the next update marking it resolved

Action item close rate — % of auto-extracted tasks marked complete by their due date, tracked by program area

Board-meeting prep lead time — days before each board meeting that all standup-flagged board items are resolved

Recurring blocker frequency — how many times the same issue (e.g., QuickBooks lag, DocuSign delays) appears in standup across a quarter

Comparison

What this replaces

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

Geekbot or Standuply (Slack bots)

Collects async updates well but doesn't extract action items, connect to your task list, or surface patterns across weeks — you still process the digest manually.

Notion + a shared standup template

Works if everyone updates it, but compliance is low on small teams with no dedicated admin, and there's no automatic task creation or blocker flagging.

Weekly Zoom standup

High-friction for a team spread across site visits and donor calls; meeting notes live in someone's personal doc and action items disappear within 48 hours.

Asana or Monday.com with standup workflows

Capable tools but require significant configuration time and ongoing admin — neither is realistic for a 4-person ops team with no dedicated project manager.

On Starch RECOMMENDED

One platform — meeting notes, task manager, project management 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

We already have Slack. Does Starch replace it or work inside it?

Works inside it. The standup prompt goes out in Slack, responses come back in Slack, and the digest posts to your existing ops channel. Starch connects to Slack from its integration catalog and queries it live. You're not moving to a new tool — you're adding automation on top of the channel you already use.

What if someone misses the Thursday cutoff?

Tell Starch how to handle it when you set up the automation — for example, 'If a team member hasn't responded by 4pm Thursday, send them a direct message reminder. If they still haven't responded by 5pm, note their update as missing in the digest.' You define the fallback behavior in plain language.

Can this pull in context from our grant management data — like which grants are in the pipeline?

Yes, with the right connections. Starch connects to Salesforce from its integration catalog and queries it live, so grant pipeline data can inform how Starch flags blockers or summarizes updates. QuickBooks is synced by Starch on a schedule, so program spend data is available too. If your grants database is something like Fluxx or Foundant that has a web interface but no API in the catalog, Starch can reach it through browser automation — no API needed.

Is my team's standup data stored securely? We have donor confidentiality concerns.

Starch is not SOC 2 Type II certified today — that's worth knowing upfront. If your foundation has strict data residency or confidentiality requirements for donor or grantee data, check with your counsel before routing sensitive information through any AI platform, including Starch. For most async standup use cases — program updates, task tracking, internal blockers — the data involved is operational, not donor-confidential.

We sometimes skip the standup for two or three weeks when things get busy. Will the system fall apart?

No. The automation runs on whatever schedule you set and you can pause it anytime by telling Starch. The archive stays intact. When you're ready to restart, the history is still searchable — so you can ask 'what was the team working on before we paused in February?' and get an actual answer.

Can Starch help prep the board packet from standup data?

That's one of the higher-value uses. After a quarter of standups, you can ask: 'Summarize all standup updates from Q1 2026 by program area. Pull out key accomplishments, unresolved blockers, and anything that came up more than twice.' That output is a first draft of your program section for the board deck — not a finished product, but a real head start for a team that currently pulls that together by hand.