Internal Comms & Meetings

How to draft a slack announcement as Small Customer Success Teams

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

You're a three-person CS team covering 250 B2B accounts. When something important happens — a major customer goes live, a renewal closes, a bug is causing churn across a segment — you need to get a Slack message out fast. Right now that means someone on the team manually pulls the account data from HubSpot, pastes usage numbers from whatever dashboard you have open, writes the announcement from scratch, and then forgets to @ the right channel or attach the right context. The whole thing takes 20 minutes you don't have, and half the time the announcement goes out late or with stale numbers. There's no template, no automation, and no institutional memory for what a good CS Slack announcement even looks like.

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

A Starch app that drafts Slack announcements pre-populated with live HubSpot account data, so your team isn't copying and pasting deal fields by hand

A trigger-based workflow that detects renewal closes, new customer kickoffs, or health-score drops and queues a draft announcement for your review before it posts

A reusable template library inside Starch so every announcement — expansion win, churn alert, QBR reminder — has a consistent structure your team can send 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 Knowledge Management

Data sources & config

Starch syncs your HubSpot data on a schedule (contacts, companies, deals, and owners), so account names, ARR, CSM assignments, and deal stages are always current. Gmail is also synced on a schedule so the email agent can cross-reference thread context when drafting. Intercom is connected from Starch's integration catalog and queried live when the workflow needs recent support ticket context to add to an announcement. Slack itself is reachable via Starch's integration catalog so the final post can be sent directly from the automation once you approve the draft.

Prompts to copy

When a deal in HubSpot moves to Closed Won, draft a Slack announcement for #customer-success with the account name, ARR, CSM owner, kickoff date, and a one-sentence summary of what they're using us for. Use a celebratory but professional tone.

Every Friday at 4pm, pull all HubSpot accounts whose health score dropped below 60 this week and draft a Slack message for #cs-team summarizing who's at risk, the ARR at stake, and which CSM owns each account.

Build me a knowledge base of our standard Slack announcement templates — new customer live, renewal closed, churn risk flagged, QBR scheduled — so anyone on the team can find the right template and fill it in without starting from scratch.

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

Walkthrough

Step-by-step

1 Connect HubSpot to Starch — Starch syncs your contacts, companies, deals, and deal owners on a schedule so every announcement pulls from current data, not whatever you last exported.

2 Connect Intercom from Starch's integration catalog so the agent can query recent support tickets live if you want to add support context to a churn-risk or renewal announcement.

3 Connect Slack from Starch's integration catalog so approved drafts can post directly to the right channel without you copy-pasting.

4 Open the Sales Agent CRM starter app in Starch and fork it to add a 'draft Slack announcement' action — describe in plain language what deal stage changes should trigger a draft and what the announcement should include.

5 Tell Starch: 'When a HubSpot deal moves to Closed Won, draft a Slack announcement for #customer-success with account name, ARR, CSM owner, kickoff date, and a one-sentence use-case summary. Hold it for my approval before posting.'

6 Set up a second automation for churn risk: 'Every Friday, pull HubSpot accounts whose health score field dropped this week and draft a #cs-team Slack message listing the accounts, ARR at risk, and owning CSM. Send it to me for review at 4pm.'

7 Use the Knowledge Management starter app to store your approved announcement templates — new customer live, expansion closed, QBR scheduled, churn alert — so any team member can find the right format instantly instead of writing from memory.

8 Add a Gmail sync step so the email agent can pull relevant thread context (recent emails with the account) and include a one-line summary in the Slack draft when relevant, giving channel readers enough background to act without clicking into HubSpot.

9 Review the draft queue each morning — Starch surfaces everything pending your approval in one place, so you're not hunting across tabs to find what's ready to post.

10 Approve or edit the draft with one click; Starch posts to the designated Slack channel and logs the announcement in the knowledge base for future reference.

11 Once the pattern is working, tell Starch to add a 'kickoff scheduled' trigger: 'When a new customer's kickoff call is added to Google Calendar, draft a #customer-success announcement with the account name, CSM, kickoff time, and a link to the account in HubSpot.' Starch syncs your Google Calendar on a schedule so this just works.

12 Share the Slack Announcement app with the rest of your CS team inside Starch so anyone on the team — not just the person who built it — can trigger a draft when something account-level happens.

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

Meridian Analytics renewal + expansion — April 2026

Sample numbers from a real run

Meridian Analytics	48,000
Expansion ARR added	12,000
New contract total	60,000
CSM owner	0

On April 14, Meridian Analytics closed their renewal in HubSpot at $48k ARR and added a $12k expansion seat package in the same deal, bringing their contract to $60k. The moment the deal stage flipped to Closed Won, Starch detected the change via the scheduled HubSpot sync, pulled the account name, the new ARR, the CSM (Sarah), and the expansion product line, then drafted a Slack announcement for #customer-success: 'Meridian Analytics just renewed and expanded — $60k ARR (+$12k for the analytics add-on). Huge win. Sarah owns the account; kickoff for the new seats is April 22. Thanks to the whole team for the support handoffs this quarter.' The draft sat in Starch's approval queue for three minutes before Sarah approved it. Total time from deal close to Slack post: four minutes. Previously that announcement would have happened the next morning, after someone remembered to write it, after pulling the numbers from HubSpot manually. The #customer-success channel had 18 reactions inside 10 minutes — which matters, because team visibility into wins is one of the things a three-person CS team loses when it's heads-down all day.

Measurement

How you'll know it's working

Time from trigger event (deal close, health drop, kickoff booked) to Slack announcement posted — target under 5 minutes

Percentage of CS announcements that go out the same day as the triggering event vs. next day or later

Number of announcement drafts approved without edits — a proxy for whether Starch's data pull and template are accurate

Slack channel engagement on CS announcements (reactions, thread replies) — a rough signal that the team is actually reading them

CSM time spent per week on internal communications vs. customer-facing work

Comparison

What this replaces

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

Writing it manually from HubSpot

Free and always an option, but takes 15-20 minutes per announcement and relies on whoever happens to notice the deal closed — which on a three-person team means it often happens the next morning or not at all.

Gainsight or ChurnZero Slack integrations

Both have native Slack alerting, but they cost six figures, require a CS-ops person to configure, and give you alerts — not drafted announcements with context — so you're still writing the message yourself.

Zapier + HubSpot + Slack

Can send a templated Slack notification when a deal closes, but the message is a static template with field substitutions — it won't summarize account context, pull in support ticket history from Intercom, or hold the draft for your review before posting.

Notion + copy-paste

Some CS teams keep announcement templates in Notion and fill them in manually — better than nothing, but still requires someone to notice the trigger event, find the template, fill it in, and post it, which is the exact three-step chain that breaks down at 5pm on a Friday.

On Starch RECOMMENDED

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

Does Starch actually post to Slack automatically, or do I have to copy the draft and paste it myself?

Starch can post directly to Slack through Starch's integration catalog connection — you connect Slack once and the automation posts to whichever channel you specify. The default setup holds drafts for your approval first, so you're not worrying about a draft going out with a wrong number. Once you trust the pattern, you can set certain announcement types (like a new customer kickoff) to auto-post without review.

What if the HubSpot data Starch pulls is wrong — like the ARR field hasn't been updated yet?

Starch pulls from whatever's in HubSpot at the time of the sync. If your team is inconsistent about updating deal fields before closing, the announcement will reflect that inconsistency. The approval step is specifically for this — you review the draft before it posts, catch any bad data, and the act of reviewing the draft often surfaces data hygiene issues in HubSpot that you'd want to fix anyway.

Can Starch pull usage data from our product analytics tool to include in the announcement?

Depends on the tool. If you're using PostHog, the Growth Analyst starter app in Starch already connects to it — you can describe a workflow that pulls product usage data alongside the HubSpot deal data and includes a usage summary in the announcement. For other analytics tools, connect them from Starch's integration catalog if they're listed there; the agent queries them live when the automation runs. If your tool isn't in the catalog, Starch can automate your browser to pull data from the dashboard directly — no API needed.

We use Intercom for support tickets. Can Starch include recent ticket context in a churn-risk announcement?

Yes. Connect Intercom from Starch's integration catalog and tell Starch to query it when drafting churn-risk announcements. The agent will pull recent open or resolved tickets for the account and include a summary — something like 'three tickets opened in the last 14 days, all around the reporting module' — so the Slack message gives your team actual context, not just a health score number.

Is Starch SOC 2 certified? We handle sensitive customer data and our security team will ask.

Starch is not SOC 2 Type II certified today. That's a real limitation worth naming. If your security team requires SOC 2 Type II before any new tool can connect to HubSpot or Intercom, Starch isn't the right fit right now. If they're comfortable with the current posture — and many small-team CS orgs are — it works fine for this workflow.

We're three people. Is this going to take weeks to set up?

The core workflow — HubSpot sync, a trigger automation, a Slack draft — takes an afternoon the first time. You describe what you want in plain language, Starch builds the app, and you test it against a real deal. The Knowledge Management piece (storing templates so the whole team can find them) is another hour. Most teams are running their first automated announcement within the same day they start.