How to write meeting notes as Foundation and Nonprofit Ops Teams
Your four-person ops team runs on meetings — weekly program officer check-ins, grantee site visit debriefs, board prep calls, expenditure responsibility reviews, 990 compliance walkthroughs. Nobody has an EA. The person who was supposed to take notes is also the person presenting. Action items get buried in a shared Google Doc that nobody updates after Tuesday, or they live in someone's inbox until a grantee follows up two weeks later asking why the agreement still hasn't been countersigned. You've lost track of who owns a grant decision because the debrief notes from the site visit are in three different places — a Zoom transcript PDF, a follow-up email thread in Gmail, and a sticky note from the program manager who just went on parental leave.
What you'll set up
Apps, data, and prompts
The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.
Meeting Notes connects to Google Calendar (Starch syncs your calendar data on a schedule) to identify upcoming calls and pull attendee lists automatically. Gmail is also synced on a schedule so post-meeting follow-up threads can be linked to the meeting record. Task Manager receives action items directly from Meeting Notes. Knowledge Management stores the searchable archive. No additional browser automation or live-query connections are required for the core workflow, though Salesforce can be connected from Starch's integration catalog so meeting notes tied to a specific grantee are queryable alongside your grant pipeline.
Step-by-step
See this running on Starch
Connect your tools, describe what you want, and the agent builds it. Closed beta is free.
May 2026 Spring Cohort Site Visit Debrief
| Action items extracted from 47-minute call | 9 |
| Action items that would typically be lost by end of week | 4 |
| Minutes to review and approve the Starch summary | 2 |
| Grantees in the discussion (each needing a follow-up) | 3 |
Your program director ran a 47-minute debrief after site visits with three education grantees. Normally, the notes would be in a shared Google Doc that gets updated once and then ignored. This time, Starch transcribed the full call and generated a summary: two funding concerns flagged for grantee B (a budget variance of roughly $12,000 against the approved program budget), one pending grant agreement modification for grantee A that needs legal review before the July 1 disbursement, and six general action items split across three team members. The program director spent two minutes reviewing the summary, approved it, and the nine action items (including the two flagged urgent) dropped into Task Manager — P1 for the legal review with a due date of June 10, P2 for the budget variance conversation with a due date of June 17. The full transcript and summary were archived in Knowledge Management under 'Education Portfolio — Spring 2026 Site Visits.' Three weeks later, when the board's finance committee asked whether the foundation had documented the budget variance conversation before approving the next disbursement, the program director searched Knowledge Management in under 30 seconds and shared the exact excerpt.
How you'll know it's working
What this replaces
The other ways teams handle this today, and how the Starch version compares.
One platform — meeting notes, task manager, knowledge management all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.
Try it on Starch →Frequently asked questions
Does Starch record the audio of our calls, or does it just transcribe?
We use Salesforce for our grant pipeline, but it was set up by a consultant three years ago and the schema is a mess. Can Starch still connect to it?
What about confidentiality? Some of our grantee conversations are sensitive — funding decisions, compliance concerns, site visit findings.
We don't have a dedicated grants management team — it's the four of us wearing five hats each. Is Starch built for that, or is it another tool that assumes we have an IT person?
Can Starch help us produce the written record we need for expenditure responsibility compliance?
We already use QuickBooks. Can meeting action items about budget variances actually connect to our financial data?
Related guides for Foundation and Nonprofit Ops Teams
Vendor and category spend analysis means knowing, at any point in time, where your money is actually going — which vendors are getting paid, how much, how often, and whether that number is creeping up or down relative to last month.
Read guide →AP invoice approval is the process of reviewing incoming vendor bills, confirming they match purchase orders or contracts, getting the right sign-off, and releasing payment.
Read guide →A 13-week cash flow forecast is a rolling, week-by-week view of what hits your account and what leaves it — covering roughly one quarter ahead.
Read guide →An annual operating budget is a forward-looking plan that maps expected revenue against planned spending for the next 12 months, broken into categories you'll actually track — payroll, software, marketing, COGS, facilities.
Read guide →Write Meeting Notes for other operators
The AI stack built for the founder's office.
Read guide →The AI stack built for small finance teams.
Read guide →The AI stack built for small RevOps teams.
Read guide →The AI stack built for small marketing teams.
Read guide →Ready to run write meeting notes on Starch?
Request closed-beta access. Everything is free during beta.