Internal Comms & Meetings

How to write meeting notes as Small RevOps Teams

Internal Comms & MeetingsFor Small RevOps Teams3 apps12 steps~24 min to set up

You run a two-person RevOps shop supporting 30 reps. Every sales call, every QBR, every pipeline review has action items that need to land in HubSpot, get tracked against the right opportunity, or turn into a Slack message to a rep who won't check their email. Right now that means one of you is half-listening to a Zoom call while typing furiously into a Google Doc, then spending 20 minutes after the meeting reformatting notes, chasing down who owns which follow-up, and manually pasting deal-specific actions back into HubSpot contact records. The doc lives in a Drive folder nobody bookmarks, and when someone asks 'what did we decide about the SMB territory split in February?' the answer is a 10-minute search through meeting recordings you may or may not have saved.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Small RevOps Teams3 apps12 steps~24 min to set up

Outcome

What you'll set up

Automatic transcription and structured summaries for every sales review, forecast call, and deal debrief — with action items already sorted by owner before the call window closes

A searchable meeting archive that links back to the HubSpot contacts, deals, or opportunities discussed, so context is one search away instead of one Slack thread away

A repeatable post-meeting workflow that pushes decisions and next steps into the right places — HubSpot deal records, a shared task list, or a Slack digest — without you manually copying anything

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 CRM

Data sources & config

Starch connects directly to HubSpot via scheduled sync, so deal and contact data is always current when meeting summaries reference a specific account or opportunity. Gmail is connected via scheduled sync so that email threads related to the same deal appear alongside meeting context. Task Manager runs natively in Starch and receives action items directly from the Meeting Notes app. Zoom or Google Meet recordings are pulled in through browser automation — no API required for the meeting platform itself.

Prompts to copy

Transcribe my weekly pipeline review calls, generate a summary with key decisions and deal-specific action items, and assign each action item to the rep or manager who owns it.

After each meeting summary is generated, create tasks in Task Manager for every action item with the owner's name and a due date based on what was discussed.

When a HubSpot deal is mentioned in a meeting summary, log the relevant decisions and next steps as a note on that deal record in my CRM app.

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

Walkthrough

Step-by-step

1 Install the Meeting Notes app from the Starch App Store — it transcribes in real time and generates a structured summary with decisions, action items, and owner assignments after each call ends.

2 Connect HubSpot via Starch's scheduled sync so that when a rep mentions 'the Acme Corp renewal' in a call, the app can match that to the live deal record and attach context correctly.

3 Connect Gmail via Starch's scheduled sync so prior email threads on the same account surface alongside the meeting summary, giving you the full conversation history without switching tabs.

4 Tell Starch: 'Transcribe my weekly pipeline review calls, generate a summary with key decisions and deal-specific action items, and assign each action item to the rep or manager who owns it.' The Meeting Notes app is configured from this prompt.

5 Add the Task Manager app and tell Starch: 'After each meeting summary is generated, create tasks for every action item with the owner's name and a due date based on what was discussed.' P1 items — blockers, at-risk deals — get flagged automatically.

6 Wire the CRM app to Meeting Notes with this prompt: 'When a HubSpot deal is mentioned in a meeting summary, log the relevant decisions and next steps as a note on that deal record.' Reps see the update in HubSpot; you didn't have to touch it.

7 Set up a post-call Slack digest: tell Starch 'After each pipeline review, send a Slack message to the #revops channel summarizing decisions made, deals that moved stages, and open action items with owners and due dates.' Starch automates this through your browser — no Slack API setup needed on your end.

8 Build a searchable meeting archive by telling Starch: 'Keep a history of all meeting summaries, indexed by deal name, rep name, and date, so I can search for any decision made in a past call.' When someone asks what was decided about SMB territory in Q1, you type it and get the answer.

9 For recurring calls like your Monday forecast review, set a schedule: 'Every Monday at 9 AM, remind me to start the pipeline review recording and pull the current HubSpot pipeline snapshot so it's ready before the call.' Starch syncs HubSpot data on schedule, so the snapshot is current.

10 Review the weekly task completion report from Task Manager to see which action items from the prior week's calls were closed and which are overdue — and surface that in the next forecast review without building a manual tracker.

11 Periodically tell Starch: 'Show me all meeting action items from the last 30 days that are still open, grouped by rep.' This becomes your accountability layer for follow-through without a separate project management tool.

12 As the archive grows, use Knowledge Management alongside Meeting Notes — tell Starch: 'When a decision is made in a meeting that affects our territory model, quota methodology, or compensation rules, flag it and save it to the RevOps knowledge base.' The answer to 'what did we decide?' becomes a search, not a memory.

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

March 2026 Pipeline Review — West Region Close Call

Sample numbers from a real run

Acme Corp (renewal, $84,000 ARR)	84,000
Thornfield SaaS (new logo, $36,000 ARR)	36,000
Maple Street Media (at-risk, $22,000 ARR)	22,000
Ridgeline Healthcare (stalled, $48,000 ARR)	48,000

Your Monday forecast call runs 45 minutes. Acme Corp comes up: the renewal is $84K but the champion left, and the AE needs to loop in legal by Thursday. Thornfield SaaS is moving fast at $36K — needs a redlined MSA back by Wednesday. Maple Street Media ($22K) hasn't responded in two weeks and needs a break-up email. Ridgeline Healthcare ($48K) stalled because pricing wasn't approved — the CRO said she'd escalate to the CFO by EOD. Meeting Notes captures all of it. By the time the call ends, the summary shows four action items: AE contacts Acme legal (due Thursday), AE sends Thornfield redline (due Wednesday), AE sends Maple Street break-up email (due Tuesday), CRO escalates Ridgeline pricing (due today). Task Manager creates all four tasks with the correct owners. Starch logs each decision as a note on the corresponding HubSpot deal record — no copy-pasting. The #revops Slack digest goes out at 11 AM: four action items, four owners, $190K in plays, zero manual effort from your team. On Thursday when the CRO asks 'what's the status on Ridgeline?' you search the meeting archive and pull the exact moment the escalation was committed — timestamp and all.

Measurement

How you'll know it's working

Action item capture rate — percentage of verbal commitments from pipeline calls that land as tracked tasks with owners and due dates

Follow-through rate — percentage of meeting action items closed before the next pipeline review

Time to HubSpot note — minutes between call end and deal record update (target: automated, not manual)

Meeting archive search hits per week — how often the team uses past meeting context instead of asking a person

Forecast accuracy delta — whether decisions made in pipeline reviews actually predict close outcomes, traceable back to specific call summaries

Comparison

What this replaces

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

Gong

Gong gives you deep call intelligence and rep coaching analytics, but it's priced for full sales orgs and doesn't write action items back into HubSpot or create tasks in a shared tracker without manual steps or an additional integration.

Otter.ai + manual HubSpot logging

Otter transcribes accurately and is cheap, but someone still has to read the transcript, extract action items, log them to HubSpot, and create tasks — which is exactly the 20-minute post-call tax you're trying to eliminate.

Notion meeting notes + Zapier to HubSpot

You can build a reasonable system here, but you're maintaining a Zapier workflow, a Notion template, and a manual action-item extraction step — three things to break, none of which understand the content of what was said.

Chorus.ai

Strong transcription and deal intelligence, but similar to Gong it's built for sales managers coaching reps, not a two-person RevOps team trying to close the loop between what was said and what gets tracked.

On Starch RECOMMENDED

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

Does Starch actually write back to HubSpot, or does it just summarize?

Starch syncs your HubSpot data on a schedule for reading — deals, contacts, owners. For writing back (logging a note to a deal record), you describe the workflow and Starch automates it through HubSpot's integration in the catalog. The exact write-back behavior depends on how you configure the workflow, so it's worth testing with a live deal before rolling out to the full team.

We use Salesforce, not HubSpot. Does this still work?

Yes. Connect Salesforce from Starch's integration catalog — the agent queries it live when your apps run. The Meeting Notes and CRM workflows work the same way; you'd reference Salesforce opportunity records instead of HubSpot deals in your prompts.

What happens if the meeting isn't recorded — like an in-person whiteboard session?

Meeting Notes is built around audio transcription from calls. For unrecorded sessions, you can paste your rough notes into Starch and ask it to structure them into a summary with action items — it's not automatic transcription, but it's faster than formatting a doc by hand.

We're not SOC 2 Type II. Is Starch?

Starch is not SOC 2 Type II certified today. If your RevOps workflow involves sensitive customer contract data or regulated information, that's worth weighing. For internal pipeline reviews and forecast calls, most small RevOps teams find this acceptable — but it's an honest limit worth knowing upfront.

How does Starch handle Zoom calls versus Google Meet?

Starch automates both through your browser — no native Zoom or Google Meet API integration is required. It can pull recordings or work with live transcription depending on how you configure the workflow. If your calls are in Google Calendar (which Starch syncs on a schedule), the meeting context — who's invited, which deal it's about — can be connected to the summary automatically.

We already have a Notion doc for meeting notes. Can Starch work alongside it?

Yes. Starch connects directly to Notion via scheduled sync. You can tell Starch to save meeting summaries to a specific Notion database, or pull existing Notion pages into the searchable archive. You don't have to abandon the doc structure you already have.

Can Starch tell us which reps consistently don't close their meeting action items?

Once action items are tracked in Task Manager with rep names attached, yes — tell Starch 'show me all open action items from pipeline calls in the last 60 days, grouped by rep' and it will surface the pattern. This is a custom view you describe; it's not a pre-built report, but it takes one prompt to build.