Internal Comms & Meetings

How to write a weekly team update as Small RevOps Teams

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

Every Friday afternoon, one of you pulls pipeline data from HubSpot, pastes Slack updates from 30 reps into a doc, checks Apollo for sequence activity, cross-references Gmail for any deal threads that moved, and tries to stitch all of it into a coherent team update before the 4pm forecast call. The other person is still answering 'can you pull me a list of all opps over $50k that haven't been touched in 14 days?' The update itself takes 90 minutes of copying, formatting, and second-guessing whether the numbers are stale. Half the reps don't read it anyway because it looks like a spreadsheet export.

Build this on Starch → See the apps used

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

Outcome

What you'll set up

A Starch app that automatically pulls pipeline movement, rep activity, and sequence performance from HubSpot, Apollo, and Gmail every week — no manual copy-paste required

A structured weekly update that surfaces stale deals, quota attainment by territory, and top open actions — formatted for human consumption, not as a data dump

A shareable digest that goes out automatically on your chosen schedule, so the Friday scramble becomes a 10-minute review instead of a 90-minute production

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

Sales Agent CRM Project Management

Data sources & config

Starch syncs your HubSpot data on a schedule (contacts, companies, deals, owners) and your Gmail data on a schedule (messages and threads). Apollo.io is connected and synced on a schedule for sequence and contact activity. Salesforce and Pipedrive are reachable from Starch's integration catalog and queried live if your team runs on either of those instead.

Prompts to copy

Every Friday at 2pm, pull this week's pipeline changes from HubSpot — new deals created, stage movements, deals closed won or lost, and any deal over $20k that hasn't had an activity logged in 10 days. Group by territory and rep. Format as a weekly digest.

Check Gmail for any inbound replies to active deal threads from the last 7 days. Flag any thread where a prospect replied but no rep has responded yet. Include the deal name, rep owner, and days since last reply.

Pull Apollo sequence activity from this week — emails sent, open rate, reply rate, and which sequences drove the most first-reply conversations. Summarize in 3 bullet points.

Combine the pipeline snapshot, unanswered thread flags, and sequence summary into a single weekly RevOps update. Write it in plain English, not tables. Open with what moved, close with what needs attention before Monday.

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

Walkthrough

Step-by-step

1 Connect HubSpot — Starch syncs your deals, contacts, companies, and owners on a schedule so every automation runs against current data, not a stale export.

2 Connect Apollo.io — Starch syncs sequence activity, contact status, and reply data so you can tie outbound effort to pipeline movement without manually cross-referencing two dashboards.

3 Connect Gmail — Starch syncs your messages and labels on a schedule. This lets the weekly update flag deal threads where reps haven't responded to prospect replies, which is the thing that actually kills deals and nobody catches until the forecast call.

4 Open the Sales Agent CRM starter app from the Starch App Store. It's pre-wired for HubSpot and Apollo. Fork it and tell Starch what your territory model looks like: 'Add a territory field that groups reps by region — West, East, and APAC — and show quota attainment per territory on the summary view.'

5 Build the pipeline movement automation: tell Starch 'every Friday at 2pm, pull all HubSpot deal stage changes from the last 7 days, deals created this week, and closed won/lost. Flag any deal over $20k with no activity in 10+ days. Group by rep and territory.'

6 Add the unanswered-thread check: 'Scan Gmail for replies from prospects on active deal threads in the last 7 days. Flag any where the prospect sent the last message and no rep reply has come yet. Include deal name, owner, and days since prospect reply.'

7 Add the Apollo sequence summary: 'Pull this week's Apollo sequence stats — emails sent, open rate, reply rate by sequence name. Highlight the top two sequences by first-reply rate and flag any sequence with zero replies sent in the last 5 days.'

8 Wire the three outputs into a single weekly narrative: tell Starch 'Combine the pipeline snapshot, unanswered thread flags, and sequence summary into one plain-English update. Start with what moved in pipeline this week. End with a short action list — stale deals, unread replies, sequences to check.'

9 Set delivery: tell Starch to post the digest to a specific Slack channel at 3pm every Friday, giving you an hour to scan it before the forecast call. Starch connects to Slack from its integration catalog and sends it live.

10 Use the Project Management app for the action items that come out of the digest — 'create a task for every stale deal flagged in the weekly update, assign it to the deal owner, due Monday' — so follow-through doesn't get lost in a chat message.

11 The first Friday it runs, spend 10 minutes reviewing the output and adjusting the prompt. Most teams refine once: either adding a field they care about (like last meeting date from Google Calendar) or trimming a section that's noise for their reps.

12 From week two onward, your Friday contribution to the weekly update is reading it, not building it.

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 March 21, 2026 — Q1 Close Sprint

Sample numbers from a real run

HubSpot deals advanced in stage this week	11
HubSpot deals closed won (week)	3
Deals over $20k with no activity in 10+ days (flagged)	4
Prospect replies with no rep response (flagged via Gmail)	2
Apollo sequences active this week	6
Top sequence reply rate (Enterprise Cold — Q1 End)	18

It's Friday March 21, the last full week of Q1. At 3pm, the Starch digest drops in #revops-digest on Slack. The pipeline snapshot shows 11 deals advanced, 3 closed won, and $340k in new deals created — but 4 deals over $20k haven't had any activity logged in 10+ days, two of which are in the East territory and have a combined value of $95k. The Gmail scan caught two prospect replies that no rep has responded to: one from a CFO who replied to an outbound sequence 3 days ago, and one from a VP of Sales who asked for updated pricing on a $60k deal. Neither flag would have been caught before the forecast call without someone manually reviewing inboxes. The Apollo summary shows the 'Enterprise Cold — Q1 End' sequence running an 18% first-reply rate, well above the team average of 9%, worth calling out in the all-hands. The action list at the bottom of the digest is four items. You spend 10 minutes on it before the 4pm call. The CRO asks about the $95k East territory stall — you already have the answer.

Measurement

How you'll know it's working

Pipeline coverage ratio by territory (total open pipeline vs quota, by rep group)

Deal age on stalled opportunities — average days since last activity on deals over $X threshold

Rep response time to inbound prospect replies (caught via Gmail thread monitoring)

Outbound sequence reply rate by sequence name, week over week

Deals created vs deals closed lost in the same 7-day window — net pipeline health

Comparison

What this replaces

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

HubSpot native reporting + manual Slack post

HubSpot's built-in reports cover pipeline movement well, but stitching in Apollo sequence data, Gmail thread flags, and a plain-English narrative still requires a human to write it — Starch automates that last mile.

Google Sheets pipeline tracker + Zapier

You can automate data pulls into Sheets and trigger a Slack post, but writing the narrative summary and flagging unanswered prospect threads requires logic that Zapier can't express — you'd still be writing the update by hand.

Notion weekly update template (manually filled)

Notion is good for formatting and distribution, but the data still has to be pasted in by a human — Starch connects directly to Notion from its integration catalog and can write to it, but the bigger win is that Starch generates the content, not just stores it.

Gong or Clari for forecast prep

Gong and Clari are excellent for call intelligence and AI-assisted forecasting at scale, but they're priced for larger sales orgs and don't help a 2-person RevOps team write and distribute the weekly narrative digest — they're complementary tools, not substitutes.

On Starch RECOMMENDED

One platform — sales agent crm, founder inbox, project 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

We run on Salesforce, not HubSpot. Does this work?

Yes. Salesforce is available from Starch's integration catalog and queried live when your app or automation runs. You won't get the same scheduled-sync depth as HubSpot (which Starch syncs on a schedule), but for weekly update purposes — pulling deal stage changes, rep activity, and pipeline snapshots — live query is sufficient. Pipedrive works the same way.

Will the update actually read like a human wrote it, or does it look like a data export?

That's on you to specify in the prompt, and it's worth spending 5 minutes on. Tell Starch 'write this in plain English, lead with what moved, close with what needs action, no tables' and it follows those instructions. The first draft is usually 80% of the way there; most teams iterate once on tone and structure in week one, then don't touch it again.

What if a rep's Gmail is where the deal threads live, not a shared inbox?

Starch syncs individual Gmail accounts you connect — so if you connect your own RevOps Gmail, it sees your inbox and sent mail. For rep-owned threads, each rep would need to connect their Gmail, or you'd route deal correspondence through a shared alias. Starch isn't going to access a rep's personal inbox without that connection being set up. This is an honest constraint worth planning around if deal correspondence is fragmented across 30 personal inboxes.

Can Starch post directly to Slack on a schedule, or does someone have to trigger it?

Starch can post to Slack on a schedule with no manual trigger. Connect Slack from Starch's integration catalog, set the automation to run every Friday at a specific time, and it sends to the channel you specify. You can also trigger it manually anytime — useful for mid-week pipeline checks before a board call.

Is this going to replace our weekly forecast call, or just make prep faster?

Just prep faster. The digest surfaces what moved and what's stuck — it doesn't replace the judgment call on how to respond to a stalled $95k deal or whether to pull in an exec on a close. What it does is get you to the forecast call with the facts already organized, so the conversation can be about decisions instead of data retrieval.

We're not SOC 2 certified ourselves — is Starch?

Starch is not currently SOC 2 Type II certified. If your company has a security review process that requires it, that's worth knowing upfront. Most early-stage RevOps teams running on a 2-person staff aren't blocked by this, but it's an honest answer.