Internal Comms & Meetings

How to run a team retrospective as CPG Founders

Internal Comms & MeetingsFor CPG Founders3 apps10 steps~20 min to set up

Your team retro lives in a Google Doc that someone started, half-filled, and then forgot to share with the co-packer ops lead. Action items from last quarter's retro — fix the FBA replenishment logic, sort out the deduction dispute workflow, update the lot traceability SOP — got buried in a Slack thread and nobody followed up. You're a 4-person team running the operational complexity of a 20-person company, and the retro is the one meeting where you're supposed to catch everything slipping through the cracks. Instead, you spend the first 20 minutes reconstructing what happened last quarter from memory, and the last 10 minutes assigning tasks that won't get tracked anywhere.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor CPG Founders3 apps10 steps~20 min to set up

Outcome

What you'll set up

A searchable archive of every retrospective, with decisions, action items, and owners captured automatically — so 'what did we decide about the co-packer SLA last quarter?' takes 10 seconds to answer

A live task board where every action item from the retro is assigned, prioritized, and due-dated before anyone leaves the call

A running knowledge base where retro outcomes feed your SOPs — so the lesson learned from the Q1 FBA stockout doesn't live in one person's head

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 Project Management Knowledge Management

Data sources & config

Meeting Notes transcribes and summarizes the live retro call. Starch connects directly to Notion via scheduled sync so any existing SOPs or wiki pages are available as context when you're updating documentation. Connect Slack from Starch's integration catalog; the agent queries it live to pull unresolved threads that belong in the retro. Project Management and Task Manager live natively in Starch — no additional connections required.

Prompts to copy

Transcribe today's team retro, summarize the top 5 decisions, extract all action items with owners and due dates, and flag anything that was an open item from last retro that didn't get resolved

Create tasks for every action item from this retro: assign the FBA replenishment audit to Sarah, P1, due in two weeks; assign the co-packer SLA review to Marcus, P2, due end of month; assign the deduction dispute SOP update to me, P1, due Friday

Save a knowledge base entry titled 'Q2 Retro Outcomes — April 2026' with the decisions and SOPs we updated today, tag it under Operations and Fulfillment, and flag it for review in 90 days

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

Walkthrough

Step-by-step

1 Before the retro, tell Starch: 'Pull any open action items from our last three retros and list them as agenda items for today's meeting.' This takes 30 seconds and means you're not starting from a blank page.

2 Run the retro with Meeting Notes active. Tell the app: 'Transcribe this call, and after it ends, generate a summary with decisions made, problems named, and action items called out.' You run the conversation; Starch takes notes.

3 After the call ends, review the auto-generated summary. It will surface decisions and action items grouped by theme — shipping/fulfillment, co-packer issues, sales, internal ops — with owners assigned based on who said what.

4 Open Project Management and tell Starch: 'Convert all action items from today's retro into tasks, assign owners, set priority levels based on what the team flagged as urgent, and give each task a due date two weeks out unless we said otherwise.' Every item lands on the board without clicking through a form.

5 Check which items were carry-overs from last retro. Tell Starch: 'Flag any task that appeared in the last retro and wasn't completed — I want to see the pattern.' If the deduction dispute workflow has been on the list for three quarters, that's a signal it needs a dedicated project, not another to-do.

6 For any decision that changes how your team operates — a new lot traceability check step, a revised co-packer communication protocol — tell Knowledge Management: 'Create a new SOP entry for [decision] and link it to the existing fulfillment wiki page.' The lesson gets captured before everyone forgets.

7 For items that touched a recurring process (FBA reorder triggers, FSMA audit prep), tell Starch: 'Update the existing wiki entry on [topic] to reflect what we decided today.' Starch syncs your Notion data on a schedule, so it knows what documentation already exists.

8 Send the retro summary to the team. Tell Meeting Notes: 'Draft a Slack message summarizing today's retro decisions and action item list, formatted as a brief team update.' Paste and send — no reformatting required.

9 Set a mid-sprint check-in. Tell Project Management: 'Flag any retro tasks that are overdue or haven't been updated in 7 days and send me a summary next Monday morning.' This is the follow-up mechanism that makes retros actually stick.

10 Before the next retro, tell Starch: 'Pull all tasks created from the last retro and their current status, and draft a pre-retro summary showing what we closed, what's still open, and what's overdue.' You walk into the next retro already knowing the score.

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

April 2026 Quarterly Retro — 4-person CPG team, $3.2M ARR brand

Sample numbers from a real run

Open action items carried over from Q1 retro	7
Action items created in Q2 retro	11
Tasks assigned and tracked in Project Management before call ended	11
SOP entries updated in Knowledge Management same day	3
Minutes spent reconstructing last quarter's decisions	4

The April retro covered five themes: FBA replenishment failures in March (two stockouts on a hero SKU), a co-packer missed a production run due to unclear lead time communication, FSMA lot traceability records were incomplete for two batches, two distributor deduction disputes were still unresolved from February, and onboarding a new part-time ops contractor had no documented process. Meeting Notes transcribed the 55-minute call and generated a summary with 11 action items in under two minutes. Starch pulled the 7 open items from the Q1 retro — 4 of them had been re-raised in Q2, which the team hadn't realized because they were in a Slack thread nobody could find. All 11 new tasks were assigned and due-dated in Project Management before anyone closed their laptop. Three SOP entries were updated in Knowledge Management: the co-packer lead time communication protocol, the FBA reorder trigger thresholds, and a new onboarding checklist for ops contractors. When the ops contractor started two weeks later, she could find everything without asking the founder a single question.

Measurement

How you'll know it's working

Retro action item close rate: % of tasks created in each retro that are completed before the next retro

Carry-over rate: how many action items reappear across consecutive retros (signals systemic problems vs one-offs)

Time-to-document: how long between a retro decision and a corresponding SOP update landing in the wiki

Open item age: average days an action item sits unresolved across the team's project board

Decision retrieval time: how quickly a team member can answer 'what did we decide about X' without pinging the founder

Comparison

What this replaces

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

Google Docs + Slack

Free and familiar, but action items live in two places, nothing gets tracked to completion, and searching for a decision from six months ago means scrolling through docs and threads manually.

Notion (standalone)

Great for the wiki layer, but you're still manually transcribing action items and copy-pasting into a task tracker — Starch connects Meeting Notes, Project Management, and Knowledge Management so the handoff is automatic.

Loom + Linear

Linear is a solid task tracker and Loom captures async context, but they don't talk to each other, and neither connects to your Notion SOPs or auto-extracts action items from a live call.

Otter.ai + Asana

Otter transcribes well, but you still have to manually move action items into Asana, tag owners, and set priorities — Starch does all three steps in one prompt after the call ends.

On Starch RECOMMENDED

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

FAQ

Frequently asked questions

Does Starch actually join and transcribe the call, or do I have to record it separately?

Meeting Notes works from a recording you bring to it — upload a recording or paste a transcript, and Starch handles the rest. It doesn't auto-join your Zoom or Google Meet as a bot today. If your team already records calls, the workflow is: retro ends, upload the recording, and Starch generates the summary and action items. If you don't record, the founder or an attendee can paste notes in and Starch structures them.

We run retros in Notion already. Does Starch replace that or work alongside it?

Starch syncs your Notion data on a schedule, so your existing Notion pages are available as context. You can keep Notion as your SOP home and use Starch to update it automatically after each retro. Or you migrate the wiki to Starch's Knowledge Management app — your call. You don't have to rip anything out to get started.

Our retros have a lot of CPG-specific discussion — co-packer issues, FSMA audit prep, FBA velocity. Will the action item extraction actually understand the context?

Yes. The extraction is based on what was said and who said it, not on generic templates. If someone says 'Marcus, can you get the lot traceability records cleaned up before the FSMA audit in June,' that becomes a task assigned to Marcus, tagged with whatever priority you set, due in June. You review the output before anything gets created, so you can correct anything that landed wrong.

What if our team is fully async — we do written retros, not live calls?

Paste the written retro into Meeting Notes and tell Starch: 'Extract decisions and action items from this retro doc, assign owners, and create tasks in Project Management.' Same output, no call required. Works well for distributed teams or founders who do a solo weekly review alongside a team async retro.

Is Starch SOC 2 certified? Our co-packer agreement requires data handling standards.

Starch is not SOC 2 Type II certified today. If a formal certification is required by a co-packer, retailer, or partner agreement, that's a real constraint worth naming. For most small CPG teams running internal retros and SOPs, the practical risk is low — but we'd rather you know upfront than find out later.

Can I connect our existing project tool (Asana, Linear, ClickUp) instead of using Starch's Project Management?

You can connect Asana, Linear, ClickUp, Jira, and others from Starch's integration catalog; the agent queries them live when your apps run. So if you'd rather push retro action items into your existing Linear board than use Starch's native Project Management, you can describe that and Starch builds the automation. You're not forced to switch tools.