How to write meeting notes as Educators, Coaches, and Course Creators
You run a 1:1 coaching call or a live cohort session, you're fully present in the conversation, and then it ends — and suddenly you owe three people follow-up resources, you promised to send a revised curriculum outline, and one student asked a question you said you'd 'look into.' You have zero notes because you were coaching, not typing. You replay the Zoom recording at 1.5x speed forty minutes later, scribble things on a sticky note, and still miss the action item about the student who was struggling with module 3. Multiply that by five calls a week and a six-week cohort and you've lost dozens of commitments. There is no EA. There is no ops person watching the recording.
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 Google Calendar data on a schedule, 12 months back and 3 months ahead) to know which calls happened and match summaries to the right student. Notion is connected via Starch's scheduled sync so summaries are written directly to your knowledge base. Task Manager captures extracted action items in your personal task list. Gmail is connected through Starch's scheduled sync so follow-up draft emails can be queued from action items without switching tools.
Step-by-step
See this running on Starch
Connect your tools, describe what you want, and the agent builds it. Closed beta is free.
Week 3 of April 2026 Cohort — five 1:1 check-ins
| Calls completed | 5 |
| Total call time (minutes) | 220 |
| Action items extracted automatically | 23 |
| Action items assigned to students | 15 |
| Action items assigned to you (coach) | 8 |
| Minutes spent writing notes manually | 0 |
| Follow-up emails drafted by Starch from action items | 8 |
On Tuesday you ran five 45-minute 1:1 coaching check-ins back to back. By the time your last call ended at 4pm you had zero written notes — but Starch had already transcribed all five sessions, generated a 5-bullet summary for each, and extracted 23 action items. Fifteen were student commitments ('Maya → submit revised landing page copy before Thursday session'). Eight were yours: send a resource on pricing anchoring to two students, reschedule Jordan's next session, update the module 4 worksheet based on the common confusion three students had. Those eight landed automatically in your Task Manager tagged 'coaching follow-up' with a 48-hour due date, so nothing got lost in the post-call fog. By Wednesday morning Starch had posted each student's summary to their individual Notion page — so when you opened Thursday's prep, you could ask 'what did Maya and Jordan both struggle with in week 3?' and get a synthesized answer across both transcripts in seconds. You sent all eight follow-up emails before noon on Wednesday. In previous cohorts that usually took until Friday, if it happened at all.
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 it work with Zoom recordings, or only live calls?
Will it write directly into my Notion pages, or just generate text I copy over?
Can it tell the difference between my action items and the student's action items?
What if I use Google Meet instead of Zoom?
I'm not SOC 2 certified — is Starch?
Can it search across all my past sessions, or just recent ones?
I teach live cohort sessions with 20 people in the room — does this still work, or is it only for 1:1s?
Related guides for Educators, Coaches, and Course Creators
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 →A customer knowledge base is the document — or collection of documents — that answers the questions your customers ask repeatedly.
Read guide →Lifecycle email flows are the automated message sequences that go out when someone signs up, goes quiet, upgrades, churns, or hits any other meaningful moment in their relationship with your product or service.
Read guide →An outbound email sequence is a structured series of messages sent to prospects who haven't heard from you yet — or haven't responded.
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.