Internal Comms & Meetings

How to draft a slack announcement as Small RevOps Teams

Internal Comms & MeetingsFor Small RevOps Teams2 apps11 steps~22 min to set up

You're two people supporting 30 reps, and somehow you're also the internal communications team. Every time territory changes, quota resets, or a new sequence launches in Apollo, you're writing a Slack announcement from scratch — pulling numbers from HubSpot, cross-referencing the Google Calendar for timing, and trying to remember what you said last quarter so this one is consistent. You draft it in a Google Doc, paste it into Slack, realize you forgot the SFDC link, edit it three times, and post it at 4pm on a Friday because that's when you finally had five uninterrupted minutes. The reps read 40% of it. The CRO asks why they didn't know about the territory change.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Small RevOps Teams2 apps11 steps~22 min to set up

Outcome

What you'll set up

A Starch app that pulls live pipeline context from HubSpot and Apollo and drafts a structured Slack announcement whenever you describe what changed — no blank-page starting point

A consistent announcement format your reps actually parse: what changed, who it affects, what action is required, and by when — auto-populated from your connected data

A reusable workflow so the next time quota resets or a new sequence goes live, you describe it in a sentence and get a draft in under two minutes

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 Email Agent

Data sources & config

Starch syncs your HubSpot data on a schedule — contacts, companies, deals, and owners — and connects to Apollo.io on a schedule for contacts, accounts, and sequence data. Notion is connected from Starch's integration catalog and queried live when an announcement needs to link to a specific doc or territory map. Slack is connected from Starch's integration catalog so the drafted announcement can be pushed directly to the right channel.

Prompts to copy

Draft a Slack announcement for the sales team about this week's territory reassignment. Pull the affected rep names and their current deal counts from HubSpot. Format it as: what changed, who's affected, what they need to do in HubSpot by EOD Friday, and a direct link to the updated territory doc in Notion.

We're launching a new Apollo sequence targeting Series B SaaS companies next Monday. Draft a Slack post for the #sales channel that explains the sequence name, the ICP, which reps are enrolled, the first touch timing, and what they should do if a prospect responds before the sequence finishes. Pull the enrolled rep list from Apollo.

Write a forecast-week Slack announcement for Monday morning. Pull this week's open opportunities by stage from HubSpot, flag any deals that haven't had activity in 10+ days, and remind reps to update their close dates and next steps before the 2pm pipeline review.

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

Walkthrough

Step-by-step

1 Connect HubSpot as a scheduled-sync source in Starch. Deal stage, owner, activity date, and close date will refresh automatically so your announcements reflect current pipeline without manual exports.

2 Connect Apollo.io as a scheduled-sync source. Enrolled contacts, active sequences, and account data sync on a schedule — so when you reference who's in a sequence, you're working from live data, not a CSV you pulled yesterday.

3 Connect Notion from Starch's integration catalog. When an announcement references a territory map, quota doc, or playbook, the agent queries the right page live and includes the correct link.

4 Connect Slack from Starch's integration catalog so completed drafts can be sent or staged to the right channel directly from Starch — no copy-paste step.

5 Open the Sales Agent CRM app (built on HubSpot and Apollo) and describe the announcement in plain language: what changed, who it affects, and what action you need from reps. The more specific you are about the trigger, the tighter the draft.

6 Starch pulls the relevant HubSpot deal and owner data for the affected reps, cross-references Apollo for sequence enrollment if relevant, and drafts a structured announcement with the standard sections your team has agreed on.

7 Review the draft in Starch. If deal counts or rep names need a correction, tell Starch in a follow-up message — 'rep Jordan Smith isn't on this territory anymore, replace with Casey Lee' — and it rewrites the relevant section.

8 Starch formats the final announcement for Slack: clean enough to read on mobile, with a bullet summary at the top for reps who won't read past the first three lines.

9 Send or stage the announcement to the right Slack channel directly from Starch. If you want to schedule it for Monday 9am instead of now, describe that and Starch queues it.

10 After the announcement goes out, tell Starch to set a reminder: 'if the HubSpot deals for the reps in this announcement haven't been updated by Thursday EOD, draft me a follow-up nudge for the same channel.' It tracks the state and drafts the follow-up if the condition is met.

11 Save the prompt you used as a reusable template in Starch. Next territory change, quota reset, or sequence launch, you open the template, swap in the new specifics, and get a draft in under two minutes instead of starting from a blank doc.

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

Q2 2026 Territory Rebalance — April 7 Announcement

Sample numbers from a real run

Reps affected by rebalance	8
Open deals requiring re-assignment in HubSpot	23
Deals with no activity in past 10 days (flagged in draft)	6
Time from prompt to reviewed draft	4
Reps who updated HubSpot by EOD Friday (after nudge)	7

On April 7, the CRO finalized a territory rebalance affecting 8 of the 30 reps — three new hires absorbing accounts from two senior reps who moved to enterprise. You had 45 minutes before the Monday standup. You opened Starch and typed: 'Draft a Slack announcement for #sales about today's territory rebalance. Pull the 8 affected reps from HubSpot and list their current deal counts by stage. Flag the 6 deals with no activity in the last 10 days as needing immediate owner re-confirmation. Include the Notion link to the updated territory map and tell reps to update deal owners in HubSpot before EOD Friday.' Starch pulled 23 open deals across the 8 reps from the HubSpot scheduled sync, flagged the 6 stale ones by activity date, grabbed the Notion territory-map link via live query, and returned a draft in under four minutes. You edited one rep name, approved it, and posted it to #sales at 9:02am — before the standup. On Thursday you ran a follow-up: 'Which of the 8 reps from Monday's announcement haven't updated their deal owners in HubSpot yet?' Starch pulled current ownership data, found one rep hadn't touched it, and drafted a direct Slack message to that rep. 7 of 8 reps were updated by EOD Friday without a second all-hands announcement.

Measurement

How you'll know it's working

Time from 'something changed' to announcement posted in Slack (target: under 10 minutes)

Percentage of reps who take required CRM action within 48 hours of an announcement

Number of follow-up 'did you see my message?' DMs sent by RevOps per announcement cycle

HubSpot data accuracy rate on deal owner and stage in the week following a territory change

Announcements drafted per week vs. hours spent on internal comms

Comparison

What this replaces

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

Google Docs + manual Slack paste

You're writing from scratch every time with no live data — rep names, deal counts, and stage breakdowns have to be looked up and typed in manually, which is where errors and stale numbers come from.

Notion templates

Good for storing the format, bad for populating it — Notion doesn't query HubSpot or Apollo, so you're still doing the data-gathering step yourself before you even start writing.

ChatGPT or Claude with a pasted CSV

Gets you a draft fast, but you have to export the HubSpot data, paste it in, and then manually post to Slack — three steps that Starch collapses into one connected workflow.

HubSpot native Slack integration

Surfaces individual deal notifications in Slack but can't draft a structured, human-readable team announcement that synthesizes territory changes, deal counts, required actions, and Notion links in one message.

On Starch RECOMMENDED

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

We use Salesforce, not HubSpot. Can Starch still pull our deal and rep data for announcements?

Yes. Connect Salesforce from Starch's integration catalog and the agent queries your deals, owners, and stage data live when it drafts an announcement. The workflow is the same — you describe what changed, Starch pulls the current Salesforce data, and builds the draft around real numbers.

Can Starch actually post to Slack, or does it just give me a draft I have to copy?

Connect Slack from Starch's integration catalog and it can push the announcement directly to the channel you specify. If you want to stage it and post manually, you can do that too — but the copy-paste step is optional, not required.

What if the draft pulls a deal count that's wrong because a rep updated HubSpot an hour ago?

HubSpot syncs on a schedule in Starch, so there's a short lag between a rep updating a deal and that update being reflected. For most announcement use cases — territory changes, quota resets, sequence launches — this doesn't matter. If you need real-time deal counts, tell Starch to note the data-as-of timestamp in the announcement so reps know the context.

We don't have a standard announcement format yet. Can Starch help us build one?

Yes. Tell Starch: 'Draft a reusable Slack announcement template for RevOps to use whenever territory or quota changes. It should have sections for: what changed, who's affected, required action and deadline, and a link to supporting documentation.' Starch will draft the template, and once you approve it, you can reference it in every future announcement prompt.

Is Starch SOC 2 certified? We have to be careful about what we connect to HubSpot and Salesforce.

Starch is not SOC 2 Type II certified today. If your security policy requires SOC 2 before connecting a CRM, that's a real constraint worth knowing upfront. It's on the roadmap.

Can we use this for external announcements too, or just internal Slack posts?

The workflow is built around internal Slack announcements, but you can describe any output format. If you want a customer-facing email draft based on the same HubSpot data — say, notifying accounts that their rep changed — the Email Triage app handles outbound drafting and can connect to Gmail or Outlook to send it.