Internal Comms & Meetings

How to write a weekly team update as Professional Services Founders

Internal Comms & MeetingsFor Professional Services Founders4 apps12 steps~24 min to set up

Every Friday afternoon, someone on your team is copying project status out of Notion, chasing utilization numbers from Harvest or a spreadsheet, scanning Gmail threads for client blockers, and pasting it all into a Slack message or a Google Doc that half the team ignores. At a 12-person consultancy, the weekly update is the one artifact that should keep everyone aligned on pipeline, utilization, client health, and who's underwater — but it takes 90 minutes to assemble from five different tools and it's stale by the time it lands. You've tried shared Notion pages. You've tried a standing Friday Slack thread. Neither pulls the actual data; they just remind people to fill in blanks.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Professional Services Founders4 apps12 steps~24 min to set up

Outcome

What you'll set up

An automated weekly team update that pulls live data from your project tracker, calendar, and email into a single structured digest — drafted by Starch, reviewed by you, sent in minutes not hours

A running archive of every weekly update with searchable decisions, flagged blockers, and client status changes — so 'what did we agree on three weeks ago?' has an actual answer

Action-item extraction from the update itself, auto-assigned to the right people in Starch's Project Management app so nothing lives only in a Slack message

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 connects directly to Google Calendar (scheduled sync) to pull calendar events and estimate utilization by person. HubSpot deals are queried live from Starch's integration catalog so pipeline status reflects whatever your team updated this week. Gmail is synced on a schedule so Starch can surface active client threads and flag unanswered messages without you manually forwarding anything. Project and task data lives in Starch's Project Management app natively. Meeting notes from client calls are captured and stored in the Meeting Notes app, also natively in Starch — no external transcription tool needed.

Prompts to copy

Every Friday at 4pm, pull all tasks that moved status this week across active projects, flag anything overdue or blocked, and draft a weekly team update organized by client — include utilization by person if I have calendar data available

Summarize any client-facing email threads from this week that had more than two back-and-forths, flag any unanswered threads older than 48 hours, and add those flags to the weekly update draft

Extract all action items from this week's meeting notes, group them by owner, and append them to this Friday's team update as a 'what we committed to' section

Save this week's team update to our Knowledge Management wiki under 'Weekly Updates > 2026 > Week 16' and tag it with the client names mentioned

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

Walkthrough

Step-by-step

1 Connect Google Calendar as a scheduled-sync provider so Starch can see this week's external and internal meetings by person — this becomes the basis for utilization estimates.

2 Connect HubSpot from Starch's integration catalog; the agent queries it live so your pipeline stage and deal health are current as of Friday, not last Monday's export.

3 Confirm Gmail is synced on a schedule in Starch so the Email Agent can surface client threads that went quiet, escalations, or anything that needs a response before the weekend.

4 Use the Project Management app to make sure active client projects have tasks with owners and due dates — the weekly update draft will pull task movement directly from here.

5 Set up a Friday 4pm automation: 'Draft this week's team update. Pull overdue and blocked tasks by project from Project Management. List any HubSpot deals that changed stage this week. Flag Gmail threads with clients that have had no reply in 48+ hours. Estimate hours by person from calendar events tagged as client work.'

6 Starch drafts the update in a structured format — one section per active client, a pipeline summary, a utilization snapshot, and a blockers list. Review takes five minutes because the data is already in it.

7 The Meeting Notes app feeds the 'decisions and commitments' section automatically — any action item captured in a meeting this week gets surfaced in the update draft without you copy-pasting from transcripts.

8 Edit the draft in Starch, approve it, and trigger the send — either as a Slack message (connect Slack from Starch's integration catalog; the agent posts it live) or as an email to the team via Gmail.

9 Starch saves the finalized update to the Knowledge Management wiki automatically under a consistent folder structure, tagged by client and week — so the update doubles as your institutional memory.

10 Action items extracted from the update are created as tasks in Project Management with owners and due dates, triggered by the prompt: 'Turn the commitments section of this week's update into tasks and assign them to the named owners.'

11 The following Friday, the automation runs again — but now it also notes which action items from last week's update were completed versus still open, so accountability is built into the cadence without a separate standup.

12 Over time, the Knowledge Management app's AI search means any team member can ask 'what did we decide about the Meridian scope change?' and get the answer from a past weekly update rather than digging through Slack history.

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 16 Update — April 2026, Thornfield Advisory

Sample numbers from a real run

Client: Meridian Group (Strategy engagement)	0
Billable hours logged via calendar: 34h of 40h target	0
HubSpot pipeline: 2 deals moved to Proposal stage	0
Overdue tasks across all projects: 3	0
Unanswered client emails >48h: 1 (Meridian, cc'd partner)	0

It's Friday at 4:15pm. The automation runs. Starch pulls from Google Calendar and sees that across the four active client engagements, the team logged 34 of a target 40 billable hours this week — utilization is 85%, which is healthy, but two of those hours were a team member covering for a colleague, which the calendar data flags because the event was duplicated. HubSpot shows two deals moved from 'Discovery' to 'Proposal' — the Kessler Manufacturing opportunity and an unnamed inbound from the website. The Email Agent surfaces one unanswered thread: a Thursday morning email from Meridian's procurement lead asking for a revised SOW, copied to your partner. That thread is now 52 hours old. Meeting Notes from Tuesday's Meridian working session contributed three action items: finalize the revised SOW (owner: you), schedule stakeholder interviews (owner: Priya), and send the benchmark data deck (owner: Marcus). The draft update is assembled in about 90 seconds. You read it, add one sentence about the Kessler proposal timeline, and send it to the team Slack channel. Priya responds immediately — she didn't realize the SOW reply was still sitting unanswered. Total time from automation trigger to sent update: 11 minutes.

Measurement

How you'll know it's working

Weekly billable utilization by person (actual hours on client work vs. capacity, derived from calendar)

Unanswered client communications older than 48 hours at week-end

Overdue tasks by project and owner at Friday close

Pipeline deals that changed stage or went stale during the week

Action item close rate: what percentage of last week's commitments were completed

Comparison

What this replaces

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

Manual Notion + Slack standup

Takes 60-90 minutes to assemble because the data lives outside Notion and someone has to fetch it — Starch pulls the data automatically so you're editing a draft, not building one from scratch.

Kantata / Projector / Deltek

Enterprise PSA tools built for 200+ person firms; multi-quarter implementation, per-seat pricing that doesn't pencil for a 12-person shop, and they require your whole team to change how they log time — Starch sits on top of the tools your team already uses.

Zapier or Make automation

You can wire Slack and Notion together, but you can't ask it to 'draft a summary of this week's client blockers' — it moves data, it doesn't read it and synthesize it.

ChatGPT with manual copy-paste

Works if you're willing to manually pull task lists, email threads, and calendar data every Friday and paste them in — Starch connects to those sources directly so the context is already there when the draft runs.

Harvest + Float + separate weekly email

Harvest and Float give you the utilization numbers, but someone still has to combine them with pipeline and client comms into an update — Starch is the layer that assembles the final artifact.

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 pull utilization data, or do my team members have to enter hours somewhere?

Starch estimates utilization from Google Calendar — it looks at events tagged as client work during the week. If your team uses calendar events consistently for client meetings and work blocks, you get a utilization estimate without a separate time-tracking entry step. If you need precise logged hours, you can connect a tool like Harvest from Starch's integration catalog and the agent queries it live when the update runs. Either way, you're not asking people to fill in a separate form on Friday afternoon.

What if my pipeline is in a Google Sheet instead of HubSpot?

Connect Google Sheets from Starch's integration catalog; the agent queries it live. You'd tell Starch: 'When drafting the weekly update, pull the pipeline tab from our deal tracker sheet and summarize deals by stage.' It's not as structured as a CRM sync, but it works if your sheet has consistent columns.

Can Starch send the update automatically without me reviewing it?

Yes, but we'd suggest keeping the review step for client-facing or sensitive content. The better setup for most consultancies is: automation drafts at 4pm Friday, you get a notification, you spend five minutes reviewing, then you approve and send. The draft does the heavy lifting; you stay in control of what goes out.

Is the weekly update archive actually searchable, or does it just pile up?

The Knowledge Management app uses AI-powered search across everything stored in it, so you or a team member can search 'Meridian scope change' or 'what did we commit to for Kessler in March' and get the answer from the relevant weekly update. It auto-categorizes new content and can flag documentation that's gone stale — which matters when a client asks about something from six months ago.

Does Starch read my Gmail threads, and is that a privacy concern?

Starch syncs your Gmail on a schedule and reads message content to surface things like unanswered client threads. The OAuth consent screen currently shows the underlying connector's name rather than Starch's — that's a known limit we're transparent about, and Starch-verified OAuth is on the roadmap. If that's a blocker for your firm's data policy, it's worth knowing upfront rather than after setup.

We use Outlook, not Gmail — does this still work?

Yes. Starch syncs Outlook messages, events, and calendars on a schedule, the same way it handles Gmail and Google Calendar. The setup steps are identical; just connect Outlook instead.

What happens if a team member updates a task after the weekly update has already been sent?

The update is a snapshot of Friday at the time it runs. Task updates after that point show up in next week's update — specifically in the 'completed from last week' section. If something urgent changes over the weekend, you can manually trigger a quick re-draft by prompting Starch directly rather than waiting for the Friday automation.