Internal Comms & Meetings

How to write a weekly team update on Starch

Internal Comms & Meetings15 roles covered4 Starch apps

Prefer to do this with raw AI? See how to write a weekly team update with AI →

A weekly team update is how a small operation stays coordinated without burning a calendar full of check-in meetings. At its most basic, it's a recurring summary of what happened, what's next, and what's blocked — distributed to whoever needs to know. In practice, the format varies widely: a founder running a service business produces something very different from one running a product team or a distributed ops org. But the underlying job is the same — pull together scattered information from across the business, shape it into something readable, and get it out before it's stale.

Most operators do this manually today. They open Slack, scroll their project tracker, dig through meeting notes, and try to reconstruct the week from memory. It takes longer than it should, gets deprioritized when things get busy, and ends up inconsistent enough that people stop reading it.

On Starch, the update drafts itself. Your meeting notes, open tasks, and project status feed into a draft that lands in your inbox each week — with decisions captured, action items listed, and blockers flagged. You edit, you send. What you have at the end is a clean, consistent update your team actually reads, without the hour of assembly work that usually kills the habit.

Build this on Starch → Pick your role

Internal Comms & Meetings15 roles covered4 Starch apps

Context

Why it matters

Why this is hard today

A weekly update that actually goes out builds the kind of organizational memory that prevents repeated mistakes, redundant conversations, and the 'wait, when did we decide that?' moments that waste time in growing teams. Skip it for a few weeks and you'll notice: alignment erodes, blockers linger, and the founder becomes the informal communication hub again. Done consistently, it's the cheapest coordination tool available.

Watch out for

Common pitfalls

Where this usually goes wrong

First, pulling from memory instead of records — you miss decisions that happened in side conversations or async threads. Second, mixing status with strategy in the same update, so readers can't tell what's informational and what needs a response. Third, writing it on Friday afternoon when the week is already a blur, instead of capturing inputs throughout the week as things actually happen. Fourth, making it so long that nobody reads past the first section.

Toolkit

Starch apps used

Email Agent

AI that organizes your inbox and drafts replies instantly. Smart prioritization, automated follow-ups, and one-click actions help you reach inbox zero and get through email twice as fast.

Meeting Notes

AI meeting notes that capture everything so you can focus on the conversation. Real-time transcription, smart summaries, automatic action items, and searchable meeting history.

Knowledge Management

A team knowledge base that keeps your company's information organized, searchable, and always up to date. AI-powered search finds answers instantly so your team stops asking the same questions.

Project Management

A Linear-inspired project management tool built for early-stage teams. Kanban board, list view, priority tracking, and AI-powered task management — all without leaving Starch.

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 →

Pick your role

Choose your operator

A version of this guide tailored to your role — same recipe, different starting context.