Internal Comms & Meetings

How to write meeting notes as Small Legal and Compliance Teams

Internal Comms & MeetingsFor Small Legal and Compliance Teams3 apps12 steps~24 min to set up

Your two-person legal team runs on meetings — vendor-risk calls, MSA redline sessions, policy-review walkthroughs with HR, DSAR intake calls with IT — and nobody has an EA to take notes. One of you is in the meeting trying to think, and the other is either also in the meeting or covering something else. You end up with a Zoom auto-transcript that's 47 pages long, action items scattered across Slack DMs, and a follow-up email you write from memory two hours later. The specific commitments — 'we'll add a data-residency clause before countersigning,' 'IT needs to pull the subprocessor list by Thursday' — are gone by Monday.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Small Legal and Compliance Teams3 apps12 steps~24 min to set up

Outcome

What you'll set up

A live Meeting Notes app that transcribes every legal and compliance call in real time, auto-generates a structured summary with decisions and action items, and archives everything in a searchable history so 'didn't we discuss this in the vendor-risk call last month?' is answerable in ten seconds.

Action-item extraction that pulls the specific to-dos from each call — who owns them, what the deadline is — and routes them into a Task Manager so nothing gets buried in a transcript nobody re-reads.

A Gmail-connected workflow that drafts the post-meeting follow-up email — the one that memorializes what you agreed to and who owes what — so you're not writing it from memory while also reviewing a DPA.

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 Email Agent

Data sources & config

Starch syncs your Gmail data on a schedule so the Email Agent can draft follow-ups grounded in the actual thread history. Google Calendar is also synced on a schedule so meeting context (attendees, agenda, linked documents) is pulled automatically. Notion connects from Starch's integration catalog — the agent queries it live when archiving notes or cross-referencing your contract tracker. Zoom and Google Meet recordings are reachable through browser automation — no separate API setup needed.

Prompts to copy

Transcribe this call and give me a summary with: (1) the specific redline items we agreed to, (2) any compliance obligations mentioned with deadlines, and (3) action items assigned by name. Archive it under 'Vendor Risk — [vendor name] — [date]'.

Pull all action items from today's meeting notes where the owner is me or Sarah and the deadline is before end of week. Add them to my task list with P1 for anything with a contract deadline and P2 for everything else.

Draft a follow-up email to the vendor's legal contact summarizing what we agreed in today's call: the two redline items we're accepting, the data-residency carve-out we're requesting, and the fact that they owe us an updated subprocessor list by Thursday. Keep it under 200 words and match the tone of the thread.

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

Walkthrough

Step-by-step

1 Connect Google Calendar via scheduled sync so Starch knows which meetings are happening and who's on them — vendor-risk calls, MSA reviews, and policy-attestation walkthroughs all get picked up automatically.

2 Install the Meeting Notes starter app from the App Store. Out of the box it transcribes, summarizes, and extracts action items. You'll customize it to use legal-specific section headers: 'Redline Commitments,' 'Compliance Obligations,' 'Open Items with Deadlines.'

3 Wire in Notion from Starch's integration catalog so the agent queries your existing contract tracker live and can link each meeting archive to the relevant contract record without you doing it manually.

4 Connect Gmail via scheduled sync so the Email Agent has the full thread history for every vendor and counterparty — not just the last message, but the full back-and-forth context that determines tone and what's already been agreed.

5 For calls recorded in Zoom or Google Meet, tell Starch to pull the recording through browser automation if you don't have a direct API — Starch automates the transcript download through your browser with no API needed.

6 After each meeting, Starch generates a structured summary: decisions made, redline items agreed to, compliance obligations raised, and named action items with deadlines. You review and confirm in under two minutes.

7 Confirmed action items flow automatically into the Task Manager with priority levels assigned based on whether they have a contract deadline (P1) or are follow-up research (P2/P3). Nothing lives only in the transcript.

8 For any meeting where you need to send a follow-up email memorializing commitments, tell the Email Agent which thread to reply to and what was agreed — it drafts the email grounded in both the transcript summary and the full Gmail thread history.

9 Archive every meeting note under a consistent taxonomy — 'Vendor Risk,' 'Contract Review,' 'Policy Attestation,' 'DSAR Intake' — so when a subpoena or audit asks what was discussed with a specific vendor in Q1, you can find the exact call and the exact moment.

10 At the end of each week, run a prompt against the Task Manager to surface every open action item from meeting notes that hasn't been closed — so the 'subprocessor list by Thursday' commitment doesn't quietly expire.

11 If a counterparty later disputes what was agreed on a call, search the meeting archive by vendor name and date. You get the verbatim transcript segment plus the structured summary — both available in under ten seconds.

12 Customize the Meeting Notes app further as your workflow develops: add a section for 'clauses flagged for escalation,' auto-tag notes that mention GDPR or CCPA obligations, or trigger a Slack message to your compliance lead whenever a call surfaces a new data-processing commitment.

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

Acme SaaS Vendor-Risk Call — March 12, 2026

Sample numbers from a real run

Redline items agreed to accept	2
Data-residency carve-out — requested, pending vendor response	1
Subprocessor list — owed by vendor by March 17	1
P1 action items extracted and added to task list	3
Follow-up email drafted and sent within 15 minutes of call end	1

On March 12 you ran a 45-minute vendor-risk call with Acme SaaS — a new analytics tool IT wants to onboard for the data team. Before Starch, your process was: one of you took notes in a Google Doc while trying to participate in the call, you cleaned it up afterward, you wrote the follow-up email from memory, and the action items ended up in a Slack DM that one of you maybe starred. This time: Starch captured the full transcript through browser automation from the Zoom recording, generated a structured summary with the two redline items you agreed to accept (limitation of liability cap and the mutual NDA carve-out for pre-existing IP), flagged the data-residency clause as an open item requiring a custom addendum, and noted that the vendor owes you an updated subprocessor list by March 17. Three P1 action items went straight into the Task Manager — 'draft data-residency addendum,' 'calendar reminder for March 17 subprocessor-list deadline,' and 'update Notion contract tracker with Acme status: pending addendum.' The Email Agent drafted a 180-word follow-up to Acme's counsel, grounded in the Gmail thread history from the past three weeks, memorializing exactly what was agreed and what they owe you. You reviewed and sent it within 15 minutes of the call ending. When IT follows up two weeks later asking why the contract isn't signed yet, you search 'Acme' in the meeting archive and pull up the exact moment in the transcript where you flagged the data-residency issue — timestamp and all.

Measurement

How you'll know it's working

Time from meeting end to follow-up email sent (target: under 20 minutes, no reconstruction from memory)

Percentage of meeting action items captured in Task Manager vs. lost in transcripts or Slack (target: 100% of items with a named owner and deadline)

Mean time to locate a specific past commitment when a counterparty or internal stakeholder disputes what was agreed (target: under 60 seconds via meeting archive search)

Number of open vendor-risk action items past their stated deadline (should be visible in one Task Manager view, not spread across three tools)

Hours per week spent on post-meeting write-up and follow-up drafting (baseline vs. after Starch — most teams see this cut by 60–70%)

Comparison

What this replaces

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

Otter.ai or Fireflies.ai

Good transcription, but the output is a wall of text — you still manually extract action items, write the follow-up email, and update your contract tracker. Starch does all three steps, connected to the tools where the work actually lands.

Notion AI + manual process

Notion AI can summarize a pasted transcript, but it doesn't pull the transcript itself, doesn't know your Gmail thread context, and doesn't push action items anywhere. You're still the integration layer between every step.

Ironclad or Evisort

Purpose-built for contract lifecycle management at scale, but six-figure pricing assumes a dedicated legal-ops person to configure and run them — not a 2-person team that also handles DSARs and subpoena responses.

Zoom AI Companion or Google Meet AI notes

Captures the transcript inside the meeting platform, but it stays there. You still manually move action items, write the follow-up, and update Notion. The output doesn't connect to anything you work in.

EA or paralegal taking manual notes

Accurate and contextual, but you don't have one, and even if you did, the output is only as organized as whoever wrote it — not searchable by clause type, vendor name, or obligation deadline across six months of calls.

On Starch RECOMMENDED

One platform — meeting notes, task manager, email agent 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 use Microsoft Teams and Outlook, not Google Meet and Gmail. Does this work?

Yes. Starch syncs your Outlook data on a schedule the same way it syncs Gmail — messages, events, and calendar data. For Teams calls, Starch can pull recordings through browser automation if Teams doesn't expose a direct API connection. You don't need to switch any tools.

We have confidential attorney-client communications on some of these calls. Where does the transcript data go?

Starch is not SOC 2 Type II certified today — that's worth knowing before you decide which calls to route through it. Many legal teams use it for vendor-risk and compliance calls, and treat A/C privileged strategy sessions differently. That's a real distinction to make, not one to paper over.

Our contract tracker lives in Notion. Will Starch overwrite it or create a parallel system?

Starch connects to Notion from its integration catalog and queries it live when your apps run. The meeting-notes workflow can be set up to write back to your existing Notion database — adding a new row, updating a status field, or linking a meeting record to an existing contract entry. It augments what you already have rather than replacing it with a new system you now have to maintain.

We already use DocuSign. Can Starch pull in signature status as part of the meeting-follow-up workflow?

DocuSign is reachable from Starch's integration catalog — the agent queries it live when your automation needs it. You can build a workflow that checks the DocuSign status of a contract referenced in a meeting and includes the current signature stage in the follow-up email draft, so you're not manually looking it up before you write.

The Task Manager is listed as 'currently in development.' Can we still use it?

You can request beta access today. In the meantime, the Meeting Notes app still extracts action items — they just need to land somewhere else. Starch can push them to an existing tool you're already using: a Notion database, a Google Sheet, or a direct Slack message to whoever owns the item. You tell Starch where you want action items to go and it routes them there.

How is this different from just searching the Zoom auto-transcript?

Zoom auto-transcripts are unsegmented text — you're ctrl+F-ing through 40 pages for the one sentence where someone said 'we'll add a data-residency clause.' Starch generates a structured summary with named sections (decisions, redline commitments, open items, action items), archives it in a searchable database tagged by vendor and date, and connects the output to your follow-up email and task list. The transcript is still there if you need the verbatim moment — but you start from structure, not from raw text.