Internal Comms & Meetings

How to write a weekly team update as Small Customer Success Teams

Internal Comms & MeetingsFor Small Customer Success Teams3 apps12 steps~24 min to set up

Your three-person CS team owns 250 B2B accounts, and every Friday someone has to write a weekly team update that nobody has time to write well. You're pulling renewal numbers from HubSpot, churn signals from a usage dashboard that updated two days ago, open Intercom tickets from memory, and action items from a Slack thread nobody archived. The result is a 200-word email that's already stale by the time you send it, or worse — you skip it and the Monday standup takes 45 minutes because nobody has shared context. You don't have a CS-ops person. You don't have an EA. You have a Notion doc that was last updated in February and a calendar full of QBR calls.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Small Customer Success Teams3 apps12 steps~24 min to set up

Outcome

What you'll set up

An automated weekly update that pulls live data from HubSpot deals, Gmail threads, and your Intercom ticket queue — assembled by Starch and ready to send every Friday morning before you've had coffee

A running log of account-level highlights, expansion signals, and churn flags that feeds each update so nothing gets dropped between weeks

Action items from the update automatically turned into tracked tasks in Starch Project Management, assigned to whoever owns that account

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

Data sources & config

Starch syncs your HubSpot data on a schedule (contacts, companies, deals, and deal stage history) and syncs your Gmail on a schedule (threads, labels, and reply status). Intercom is connected from Starch's integration catalog — the agent queries your open and recently resolved tickets live each Friday when the automation runs. Notion is synced on a schedule for the knowledge base archive. No browser automation required for this stack, but if your usage data lives behind a login wall with no API — say, a customer health dashboard in a homegrown tool — Starch can automate that through your browser with no API needed.

Prompts to copy

Every Friday at 8am, pull this week's HubSpot deal activity for accounts in the 'At Risk' and 'Expansion Ready' stages, summarize open Intercom tickets by account, check Gmail for any threads with customers that are still unanswered after 48 hours, and draft a weekly CS team update with three sections: Wins This Week, Accounts to Watch, and Action Items Due Next Week.

Take the action items from this week's CS update and create project tasks in Starch — assign any renewal follow-ups to Maya, any onboarding items to Derrick, and flag anything overdue as urgent.

Store each weekly update in our CS knowledge base under the folder 'Weekly Updates / 2026' so we can search back when a customer references something from last quarter.

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

Walkthrough

Step-by-step

1 Connect HubSpot — Starch syncs your contacts, companies, deals, and deal owners on a schedule. This gives the automation fresh data on deal stage, close date, and account owner without anyone pulling a manual report.

2 Connect Gmail — Starch syncs your messages and labels on a schedule. The agent can identify unanswered customer threads older than 48 hours and include them in the 'Accounts to Watch' section automatically.

3 Connect Intercom from Starch's integration catalog — the agent queries open tickets, ticket age, and CSAT scores live when the Friday automation fires.

4 Connect Notion — Starch syncs your pages and databases on a schedule so completed weekly updates are archived in a searchable wiki that the whole team can access.

5 Install the Email Triage app (listed as 'Founder Inbox' in the App Store) and tell Starch: 'Flag any inbound customer email in Gmail that hasn't received a reply in more than 48 hours and include it in Friday's CS update.' This closes the gap between what's in the CRM and what's actually happening in your inbox.

6 Install the Project Management app and configure it with your three team members (e.g., Maya for renewals, Derrick for onboarding, and a shared queue for escalations). Tell Starch which task categories map to which owner.

7 Build the weekly update automation: tell Starch exactly what to pull, how to structure the update, and who to send or Slack it to. The concrete prompt is the authoring step — what you'd type becomes the logic.

8 Set the automation to run every Friday at 8am. Starch assembles the update from live HubSpot deal data, synced Gmail threads, and live Intercom ticket data, then drafts the update document.

9 Review the draft — it takes five minutes, not 45. Edit the narrative if anything looks off, then send to the broader team (or trigger the Slack post directly from Starch).

10 After sending, Starch extracts action items from the update and creates tasks in the Project Management app, assigned by owner and flagged by priority.

11 The completed update is stored in Notion under your weekly archive folder — searchable by account name, date, or keyword. Next time someone asks 'what did we say about Acme Corp in March?' you find it in 10 seconds.

12 Each week's update feeds the next one: expansion signals flagged this week appear in the 'Accounts to Watch' carryover section next Friday, so nothing falls off the radar between check-ins.

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 18 2026 Weekly CS Update — Meridian SaaS, 250 accounts

Sample numbers from a real run

Thornwood Logistics	42,000
Apex Retail Group	18,500
Grantham Medical	67,000
Dune Analytics	9,800
Clearfield Partners	31,000

It's 8:05am Friday. Starch has already run the weekly automation. It pulled HubSpot deal data for all 250 accounts, flagged Thornwood Logistics ($42,000 ARR) as 'At Risk' because their deal stage moved backward and their last activity was 19 days ago. It found two unanswered Gmail threads with Apex Retail Group ($18,500 ARR) — both older than 48 hours, both about an onboarding question that nobody closed. It queried Intercom live and surfaced 4 open tickets for Grantham Medical ($67,000 ARR), two of which are over 5 days old with no response. The draft update lands in the team's Slack at 8:06am: Wins This Week — Dune Analytics ($9,800) signed the expansion contract; Clearfield Partners ($31,000) completed onboarding and hit their first value milestone. Accounts to Watch — Thornwood, Apex, Grantham, flagged with reasons. Action Items Due Next Week — Maya: follow up with Thornwood by Tuesday; Derrick: close the Apex onboarding thread today; shared queue: resolve Grantham tickets before EOD Friday. Maya reviews the draft, changes one line about Thornwood, and sends it. The whole process took seven minutes. The update is archived in Notion under 'Weekly Updates / 2026 / April' and searchable by account name. Next Friday, Thornwood's flag carries forward automatically if nothing changed.

Measurement

How you'll know it's working

Time to send weekly update (target: under 15 minutes from draft to sent)

Unanswered customer emails older than 48 hours (should be 0 going into the weekend)

Accounts flagged 'At Risk' week-over-week (trend, not just snapshot)

Action items created vs. action items closed from the previous week's update

Open Intercom ticket age by account (average days open per account, surfaced each Friday)

Comparison

What this replaces

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

Gainsight or ChurnZero

Purpose-built CS platforms with deep health-score infrastructure — but six-figure contracts, a CS-ops person to configure, and months to onboard; Starch connects to the data you already have in HubSpot and Intercom and lets you build the surfaces you actually need without a dedicated admin.

Manual Notion doc + Slack post

Free and familiar, but someone has to write it every week — and they're pulling numbers from three tabs, which means it's either stale or it doesn't get done.

HubSpot reports + email digest

HubSpot's built-in reports cover deal activity well but don't pull in your Intercom ticket data, Gmail thread status, or action items — and the digest format is rigid, not narrative.

Notion AI or Confluence

Good for summarizing documents you've already written, but can't pull live data from HubSpot or Intercom — you'd still be copying and pasting numbers by hand before it can summarize anything.

On Starch RECOMMENDED

One platform — project management, founder inbox, 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

Our HubSpot data is a mess — deals in the wrong stage, owners not updated. Will the update just reflect bad data?

Yes, and that's actually useful: when the update surfaces a deal with no activity for 30 days and an owner who left the company, that's the CRM hygiene flag you needed. You can tell Starch to add a 'Data Quality' section to the update that highlights records with missing or stale fields — turns the messy CRM into a weekly cleanup prompt rather than something you ignore.

We use Zendesk, not Intercom. Can Starch still pull our ticket data?

Yes — connect Zendesk from Starch's integration catalog; the agent queries your open tickets live when the Friday automation runs. Same structure, different source.

Is the weekly update actually sent automatically, or does someone still have to push a button?

Starch drafts it automatically on schedule. You can configure it to send automatically to Slack or email, or you can set it to 'draft and notify me' so a human reviews it before it goes out. For a three-person team covering 250 accounts, most teams start with the review step and switch to fully automated once they trust the output.

We store our customer health notes in Google Docs, not Notion. Can Starch archive there instead?

Google Drive is reachable from Starch's integration catalog, so the agent can query documents live. For writing new archive content, Notion is the scheduled-sync provider with the deepest integration for this workflow — if you need to stay in Google Docs, that's a browser automation pattern rather than a native sync.

Is Starch SOC 2 Type II certified? Our customers ask about data security.

Not yet — Starch is not SOC 2 Type II certified today. If that's a hard requirement for your procurement process, it's worth flagging. It's on the roadmap, and we'd rather you know now than find out later.

What happens if the HubSpot sync is a few hours old by the time the Friday automation runs? Will the data be stale?

HubSpot syncs on a schedule, so there's a window of a few hours between the last sync and when the automation runs. For a weekly update, that's almost never a problem — deal stage changes and activity logs don't shift meaningfully in a three-hour window. If you need truly real-time deal data (say, for an end-of-quarter update on a Friday close day), you can trigger the automation manually at any point to pull the freshest sync.