Internal Comms & Meetings

How to write a weekly team update as Chief of Staff and Founder's Office

Internal Comms & MeetingsFor Chief of Staff and Founder's Office4 apps10 steps~20 min to set up

Every Friday afternoon, you spend 45-90 minutes assembling the weekly team update by hand. You're pinging functional leads on Slack for status snippets they half-wrote in Notion, cross-checking deal pipeline numbers in HubSpot, pulling payroll headcount from wherever HR last dropped it, and reconciling what you remember from six different exec meetings that week. By the time you've stitched it together in a Google Doc and formatted it for the CEO to send, half the numbers are already stale and you've lost your Friday evening. The update looks polished but the process is embarrassing for someone whose job is supposed to be running the operating system of the company.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Chief of Staff and Founder's Office4 apps10 steps~20 min to set up

Outcome

What you'll set up

A Starch automation that pulls live signals from Slack, Notion, HubSpot, Google Calendar, and Gmail every week and drafts the full team update — headlines, metrics, blockers, and next-week priorities — ready for your review and edit before it goes out

A searchable meeting archive that captures key decisions and action items from exec syncs so you're not reconstructing 'what did we actually decide' from memory when writing the Friday narrative

A project tracker that rolls up cross-functional status in one view so functional leads can self-report status once and it feeds both the weekly update and your own OKR dashboard

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

Project Management Meeting Notes Email Agent Knowledge Management

Data sources & config

Starch syncs your HubSpot data on a schedule (contacts, companies, deals, owners) and your Google Calendar events on a schedule (12 months back, 3 months ahead), so meeting detection and deal metrics are always current. Starch syncs your Notion pages and databases on a schedule, meaning functional-lead status docs flow in automatically. Gmail is synced on a schedule for reading incoming status emails and thread context. Slack is connected from Starch's integration catalog; the agent queries it live to post the finished draft for your review. The Project Management app runs natively inside Starch — no external connection needed.

Prompts to copy

Every Friday at 1pm, pull this week's closed deals and pipeline movement from HubSpot, any Notion pages updated this week tagged 'weekly-status', open and closed tasks in Project Management, and my meeting summaries from this week. Draft a team update with five sections: Company metrics, What shipped, What's blocked, Wins worth calling out, and Focus for next week. Format it as a Slack message the CEO can post with one edit. Slack it to me for review first.

Every time a meeting ends on my Google Calendar that has more than 3 attendees, transcribe it, pull out decisions and action items, assign each action item to the person who said they'd do it, and add it to my meeting archive in Knowledge Management tagged by project area.

When I get an email from a functional lead with 'weekly update' or 'status' in the subject, extract the key bullets, map them to the right section of the Friday draft (metrics / shipped / blocked / wins), and queue them for inclusion. Flag anything that contradicts what HubSpot or Notion says.

Build me a project tracker for our top 5 strategic initiatives this quarter. Each initiative gets a status (On Track / At Risk / Blocked), an owner, a one-line this-week update, and a next milestone with a date. Functional leads can update their own initiative. Every Friday morning, summarize the tracker status and include it in the weekly update draft automatically.

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

Walkthrough

Step-by-step

1 Connect HubSpot, Google Calendar, Notion, and Gmail as scheduled-sync sources inside Starch. These four cover the majority of the raw material the weekly update draws from — deal data, meeting history, team docs, and inbound status emails.

2 Install the Project Management app from the Starch App Store and describe your five strategic initiatives to Starch. Tell it: 'Create a tracker with these five initiative names, assign each to its functional lead, and add a Status field (On Track / At Risk / Blocked) and a This Week field that resets every Monday.' Starch builds the tracker; share the link with your functional leads so they update it themselves.

3 Install Meeting Notes. Tell Starch: 'After every Google Calendar meeting with more than 3 attendees, generate a summary with decisions and action items, tag each item with a project area, and archive it in Knowledge Management.' Meeting content is now searchable and auto-filed.

4 Install the Email Agent app. Configure it to watch for incoming emails from your functional leads that look like status reports — subject lines containing 'update', 'status', 'weekly', or 'EOW' — and extract the key bullets into a structured staging area Starch can pull from when drafting.

5 Build the weekly update automation. Type into Starch: 'Every Friday at 1:00 PM, pull this week's HubSpot pipeline movement, Notion pages tagged weekly-status updated this week, Project Management tracker statuses, and this week's meeting action items. Draft a team update with five sections: Company Metrics, What Shipped, Blockers, Wins, and Next Week Focus. Post the draft to me in Slack for review before anything goes out.'

6 The first week, review the draft Starch posts to your Slack DM. Edit tone, add one or two things it missed, and note any section that consistently needs manual intervention. Tell Starch what to adjust: 'The blockers section should also check for tasks in Project Management that are 5+ days overdue and owned by a functional lead. Add those automatically next week.'

7 Once the draft quality is consistent, add a second Slack message step: after your review window (say, 30 minutes), Starch posts a reminder: 'Weekly update draft is ready — approve to send or edit first.' You approve, it posts to the #company or #team channel on behalf of the CEO or you, depending on your setup.

8 Use Knowledge Management to file each published weekly update automatically. Tell Starch: 'After I approve the weekly update each Friday, save a copy to Notion in a folder called Weekly Updates / 2026, titled by date.' Now you have a searchable archive of every update — useful for board prep, investor updates, and new exec onboarding.

9 Set up a Monday morning digest for yourself. Tell Starch: 'Every Monday at 8:00 AM, show me last week's update, any action items from last week's meeting archive that are still open, and HubSpot deals that moved stage or went stale over the weekend.' This closes the loop so the weekly update isn't just publishing — it's driving follow-through.

10 For the quarterly board deck cycle, extend the automation: 'Pull the last 12 weekly updates from Knowledge Management, group key metrics trends by month (HubSpot pipeline, headcount, project milestones), and draft a 6-bullet operating summary for the board packet.' You've just turned 52 weekly updates into board prep with one prompt.

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

Friday, April 11 2026 — Week 15 Update

Sample numbers from a real run

HubSpot new deals opened (week)	14
HubSpot deals closed-won (week)	3
Pipeline value added (week)	187,000
Open Project Management tasks marked Blocked	7
Meeting action items extracted (week)	23
Action items with no owner detected	4
Notion status pages updated by functional leads	5
Minutes to final approved update (vs. 75 min manually)	12

By 1:07 PM on Friday, Starch had already read the week's HubSpot data (14 new deals opened, 3 closed-won totaling $187K in pipeline added), scanned the 5 Notion pages that functional leads had tagged 'weekly-status', pulled 23 action items from the week's meeting archive, and flagged 4 of them as unassigned. The draft it posted to your Slack DM had a Company Metrics section citing the $187K pipeline figure and noting that Q2 attainment is at 61% of target with 7 weeks left. The What's Blocked section listed 7 overdue Project Management tasks — 3 of them in engineering, owned by the same person — which you wouldn't have caught without manually pinging the eng lead. You edited two sentences, added a shoutout to the sales team for a logo win, and approved. By 1:19 PM the update was in #company. The whole thing took 12 minutes, including your edits. The previous Friday it had taken 75 minutes and you'd still gotten two 'wait, what about X?' replies on Slack afterward because you'd missed a blocker the product lead buried in a Notion comment.

Measurement

How you'll know it's working

Time from Friday 1 PM to approved update sent (target: under 20 minutes, baseline: 60-90 minutes)

Percentage of action items from the week's meetings that appear in the update with a named owner (measures whether decisions are actually getting tracked)

Functional lead participation rate: how many of the 5-7 strategic initiative owners updated their status in Project Management before Friday noon (measures whether the update is a real operating cadence or you doing all the work)

Stale action item count: open items from prior weeks' meeting archives that are still unresolved after 10 days (the number the CEO will ask about on Monday)

CEO or exec edit rate: how often the CEO changes more than 2 sentences before sending (proxy for whether the Starch draft is actually capturing the right voice and priorities)

Comparison

What this replaces

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

Manually stitching Google Docs + Slack + HubSpot exports every Friday

Free and you control every word, but it takes 60-90 minutes of context-switching every week and the quality is only as good as what functional leads remembered to tell you by Thursday.

Notion AI + Notion databases as the single source of truth

Works well if your team actually lives in Notion, but HubSpot deal data and Gmail threads don't flow in automatically — you're still copy-pasting numbers by hand.

Zapier or Make automation chaining Slack + Google Docs + HubSpot

Can automate the data-pulling step, but writing the actual narrative still requires a separate LLM call you have to wire yourself, and the setup time for a multi-source workflow like this is several days of engineering-adjacent work.

Dedicated internal comms tools (Staffbase, Simpplr)

Built for enterprise broadcast comms at 1,000+ employees; overkill for a 150-person growth-stage company, adds a tool your team has to log into, and doesn't help with the data-assembly problem at all.

On Starch RECOMMENDED

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

Does Starch actually write the narrative or does it just dump bullet points?

It writes prose sections with real numbers pulled from your connected sources. The quality depends on how clearly you describe the format you want. If you tell Starch 'write the Company Metrics section as 3 sentences max, lead with pipeline, end with a trend observation,' that's what you get. Most chiefs of staff end up editing 20-30% of the draft — the machine does the assembly; you do the judgment calls.

What if a functional lead doesn't update their Notion page or Project Management status before Friday?

Starch will still run the automation, but it'll flag the missing section: 'No update received from Product this week — last Notion edit was Tuesday April 8.' You can then ping that person directly. You can also set up a Thursday afternoon reminder automation: 'Message anyone whose initiative status hasn't been updated since Monday, asking them to fill it in by noon Friday.'

Can this pull from tools other than HubSpot, Notion, Gmail, and Google Calendar?

Yes. Starch connects to 3,000+ apps through its integration catalog, plus any website through browser automation. If your team tracks engineering sprint status in Linear or Jira, connect those from the catalog and the agent queries them live when the update runs. If your finance team uses QuickBooks, Starch syncs that data on a schedule and you can include revenue or burn figures in your weekly metrics section.

Is this going to post to Slack automatically without me seeing it first?

Only if you set it up that way. The default pattern is: Starch drafts, posts to your Slack DM for review, and waits for your approval before doing anything else. You can set a review window ('if I haven't responded in 45 minutes, send me a reminder') but nothing goes to #company without a human in the loop unless you explicitly remove that step.

What are the honest limitations here?

A few worth knowing: Starch is not SOC 2 Type II certified, so if your company has strict data-handling requirements for third-party tools, check with your IT or legal team first. Gmail syncs are capped at 30 messages per page to avoid errors on long threads, which is fine for most status-email use cases but worth knowing if you're dealing with extremely high-volume inboxes. HubSpot data syncs on a schedule rather than in real time, so a deal that closes at 11 AM Friday might not appear in the 1 PM update draft — though for a weekly cadence this is rarely a problem. And the draft quality will vary in the first two or three weeks as you tune the prompt; budget 20-30 minutes per week to give Starch corrections until it's dialed in.

My CEO edits the update every week before it goes out. Does that break the automation?

No — the review step is built into the workflow. Starch posts the draft to you (or directly to the CEO if you set it that way), and the send step is a separate approval action. The CEO can edit in Slack or you can copy the draft into wherever they prefer to work on it. You lose some automation elegance if they want to edit in Google Docs, but the data-assembly part still saves you 45+ minutes regardless.