Internal Comms & Meetings

How to write a weekly team update as CPG Founders

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

Every week you owe your team — co-packer contacts, retail buyers, 3PL reps, maybe two full-time employees — some kind of update on where things stand. But pulling it together means hopping between your Shopify dashboard, a Slack thread about the FBA restock, a Google Doc with this week's co-packer schedule, and whatever notes you scrawled during Monday's call with your broker. You spend 45 minutes assembling a recap that should take 10. Half the action items from last week never made it into the update because nobody wrote them down in the first place. The result is a weekly email your team half-reads and that you half-believe captures reality.

Build this on Starch → See the apps used

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

Outcome

What you'll set up

A weekly team update that auto-pulls this week's open tasks, decisions from recent meetings, and priority issues — so you're recapping what actually happened, not what you remember happening

A searchable archive of every update and the meeting notes behind it, so when your co-packer asks 'didn't we agree on a shorter lead time?' you can pull the exact call

A drafting workflow that produces a first-pass update in your voice, organized by functional area (production, retail, e-comm, finance), and routes it to the right people without you formatting 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 Project Management Knowledge Management Email Agent

Data sources & config

Meeting Notes captures and transcribes team calls in real time. Project Management tracks open tasks across your team. Knowledge Management (connected to Notion via Starch's scheduled sync) stores past updates and company docs in a searchable wiki. Email Agent connects to Gmail via Starch's scheduled sync and queries it live to draft and route the final update. No additional integration setup needed beyond connecting your Gmail and Notion accounts.

Prompts to copy

Every Friday at 4pm, pull all action items created this week from Project Management, pull summaries from any meetings logged in Meeting Notes since last Friday, and draft a weekly team update organized by these sections: Production & Co-packer, Retail & Wholesale, E-comm & FBA, Finance & Cash. Flag any overdue tasks. Write it in plain language, no jargon. Save the draft to Knowledge Management under Weekly Updates > 2026 and send me a Slack message with a link.

Create a task for Sarah to follow up with our co-packer on the revised MOQ for the summer SKU, priority high, due Thursday.

Search our meeting notes and weekly updates from the past 60 days for any mention of the Whole Foods deduction dispute and summarize what we decided.

Draft a reply to our broker's email about the Q3 promo calendar — pull in whatever we said about promo windows in last week's update and confirm the dates.

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

Walkthrough

Step-by-step

1 Connect Gmail through Starch's scheduled sync and Notion through Starch's scheduled sync so your inbox and existing docs are both reachable.

2 Install the Meeting Notes app from the Starch App Store and run it on your weekly ops call — it transcribes the conversation, extracts action items, and saves a structured summary automatically.

3 Install the Project Management app and have Starch migrate your current task list: type 'Import our open tasks from this Google Sheet and assign them to team members based on the names in column C.'

4 After your first week of using both apps, tell Starch: 'Every Friday at 4pm, pull all tasks created or updated this week and all meeting summaries since last Friday and compile them into a draft weekly update.'

5 Specify the sections that match your CPG ops reality: Production & Co-packer updates, Retail & Wholesale (including any deduction disputes or promo commitments), E-comm & FBA (restock status, ASIN performance), Finance & Cash (any Plaid or Stripe data you want surfaced). Starch builds the template and populates it each week.

6 Review the draft — typically a 5-10 minute read at this point, not a 45-minute assembly job. Edit inline or tell Starch 'add a note that we're holding the spring SKU launch until we clear the current 3PL backlog.'

7 Starch sends the final update via Email Agent to your distribution list (team, co-packer contact, broker if relevant) and archives it in Knowledge Management under a consistent folder structure.

8 Any action items extracted from the update are automatically created as tasks in Project Management with owners and due dates, so they don't disappear into an email thread.

9 At the start of the following week, tell Starch: 'Summarize which action items from last week's update are still open' — this becomes the standing first item in your Monday check-in.

10 When a new employee, co-packer rep, or investor asks for context, point them to Knowledge Management: 'Find everything we've said about our FBA restock cadence in the past six months.' They get the answer in seconds without pinging you.

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

Week of April 14, 2026 — post-Expo West crunch

Sample numbers from a real run

Open tasks pulled from Project Management	14
Overdue tasks flagged	3
Meeting summaries ingested (co-packer call, Monday ops, broker sync)	3
Minutes to produce final draft	8

The week after Expo West, your ops are a mess: you committed to a new Sprouts velocity program, your co-packer moved your next production run two weeks, and your FBA restock is sitting at 18 days of cover. You had three calls Monday through Wednesday, none of which had formal notes. On Friday at 4pm, Starch pulls 14 open tasks from Project Management — flags three as overdue (the deduction dispute spreadsheet, the revised label artwork approval, and a Q2 PO confirmation to your 3PL). It ingests summaries from all three meeting transcripts and drafts an update with four sections. The Production section notes the co-packer delay and surfaces the action item you agreed to on the call: 'confirm revised schedule in writing by April 18 — Owner: you.' The Retail section mentions the Sprouts program commitment and links to the meeting note where the velocity targets were discussed. The E-comm section flags 18 days of FBA cover against a 22-day replenishment lead time and marks it red. Finance is clean this week. You spend 8 minutes editing, add one sentence about the label redesign timeline, and send. The whole update is in inboxes by 4:30pm — and every action item is already a task in Project Management.

Measurement

How you'll know it's working

Time to produce weekly update (target: under 15 minutes including review)

Percentage of action items from previous update completed by following Friday

FBA days of cover flagged and tracked week-over-week

Number of overdue co-packer or distributor commitments surfaced per update

Search queries answered from Knowledge Management archive without founder intervention

Comparison

What this replaces

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

Google Docs + manual notes

Free and familiar, but you're still assembling the update by hand every week and the archive is unsearchable without knowing exactly what you called the file.

Notion + Notion AI

Good wiki and decent AI search, but Notion doesn't pull task status or meeting transcripts automatically — you're still doing the aggregation step yourself.

Slack channel digest

Low-friction to send but no structure, no searchable archive, and action items disappear into the thread within 48 hours.

Loom weekly video update

High trust, personal tone — but not skimmable, not searchable, and you're still spending 20+ minutes recording and editing each week.

Monday.com or Asana + manual writeup

Strong task tracking, but the narrative weekly update is still a manual step you write in a separate tool, and nothing connects the two automatically.

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

Can Starch pull my Shopify inventory or FBA restock data into the weekly update automatically?

Shopify and Amazon are reachable from Starch's integration catalog — connect them and the agent queries them live when your update runs. For FBA specifically, Starch can also automate through your Seller Central browser session — no API required. Tell Starch: 'Pull current FBA days of cover for each active ASIN from Seller Central and include it in the E-comm section of the weekly update.' That section becomes a live snapshot every Friday, not a number you typed in on Tuesday.

What if I don't use Notion — I keep everything in Google Docs?

Google Drive is reachable from Starch's integration catalog and the agent queries it live. Your existing docs are accessible; Starch can search across them and pull relevant context into the update. If you want to start storing updates in a more structured archive going forward, Knowledge Management handles that natively without requiring a Notion account.

Does Starch store all my meeting transcripts? What about sensitive co-packer pricing conversations?

Meeting notes and summaries are stored in Starch's database. Starch is not SOC 2 Type II certified yet — that's an honest limit worth knowing if you're handling genuinely sensitive supplier contracts or investor information. For most weekly ops calls, the convenience trade-off is worth it; for your most sensitive negotiations, you may want to keep those transcripts out of Starch until certification ships.

Can the weekly update go to different people depending on section — like, just the production section to my co-packer contact?

Yes. Tell Starch: 'Send the Production & Co-packer section to ops@mycopacker.com and send the full update to my internal team list.' Email Agent handles the routing and can use different subject lines per recipient group. You define the logic once; it runs the same way every week.

We use QuickBooks for accounting. Can the Finance section pull actual numbers instead of me typing them in?

Yes. Starch syncs your QuickBooks data on a schedule — invoices, bills, vendors, payments, and journal entries are all available. Tell Starch: 'Include a Finance snapshot in the weekly update: total bills paid this week, outstanding receivables, and current cash balance from Plaid.' Note that QuickBooks report views like P&L are temporarily unavailable due to an upstream fix in progress, but entity-level data syncs normally so you can build the same summary from raw transaction data.

What happens if I miss the Friday 4pm window because I'm at a buyer meeting?

The automation runs on the schedule you set regardless of where you are. If you want to review it before it sends, set it to draft-only on Friday and send-approved on Saturday morning — or tell Starch: 'If I haven't approved the draft by 6pm Friday, send it automatically.' You control the release logic.