Internal Comms & Meetings

How to draft a slack announcement as Professional Services Founders

Internal Comms & MeetingsFor Professional Services Founders3 apps11 steps~22 min to set up

You need to tell your 12-person team about a new client win, a scope change, a billing policy update, or a retainer renewal — and you're composing it from scratch in Slack while juggling three other things. The message either comes out too long (nobody reads it), too short (people ask follow-up questions all afternoon), or lands at the wrong time when half the team is on client calls. You don't have a comms person. You have a Google Calendar, a HubSpot deal, a thread in Gmail, and fifteen minutes between calls. The announcement gets written in a hurry, lacks the right context, and spawns a thread that takes longer to manage than the original message would have taken to write properly.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Professional Services Founders3 apps11 steps~22 min to set up

Outcome

What you'll set up

A Starch workflow that pulls context from your live HubSpot deal, Gmail thread, or meeting notes and drafts a Slack announcement with the right tone, length, and audience targeting — so you stop writing from scratch every time

A repeatable template library for your most common announcement types — new client won, engagement kicked off, retainer renewed, team policy updated — each pre-wired to the data source that makes it relevant

An approval step where the draft lands in your inbox or a private Slack channel first, so you review once and post with confidence instead of second-guessing your own copy

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

Email Agent Knowledge Management Meeting Notes

Data sources & config

Starch connects directly to HubSpot (scheduled-sync provider) so deal names, contract values, and close dates are available without manual lookups. Gmail is a scheduled-sync provider, so thread context from client conversations feeds drafts automatically. Google Calendar is a scheduled-sync provider, giving Starch visibility into meeting timing so announcements go out at the right moment. Notion is a scheduled-sync provider used by the Knowledge Management app to keep prior announcements and policy docs accessible as reference. Slack is connected from Starch's integration catalog; the agent queries it live to post drafts or send to a review channel before publishing.

Prompts to copy

Draft a Slack announcement for #general telling the team we just signed Aldridge & Partners as a new retainer client. Pull the deal name, contract value, and kick-off date from HubSpot. Keep it under 150 words, celebratory but professional. Tag the project lead.

Write a Slack message for #operations announcing that our timesheet submission deadline is moving from Friday 5pm to Friday noon starting next Monday. Pull any prior policy announcements from Knowledge Management so this message stays consistent with our existing tone.

After today's client kick-off call with Meridian Group, draft a Slack post for the project channel summarizing what was agreed — scope, timeline, first deliverable, and who owns what. Use the Meeting Notes transcript from this afternoon's call.

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

Walkthrough

Step-by-step

1 Connect HubSpot as a scheduled-sync provider in Starch — deal stage, client name, contract value, and kick-off date will be available to any announcement workflow you build.

2 Connect Gmail and Google Calendar as scheduled-sync providers so Starch can pull thread context and meeting timing when it drafts announcements tied to specific client interactions.

3 Connect Notion as a scheduled-sync provider through the Knowledge Management app — store your prior all-hands posts, policy updates, and announcement templates there so Starch drafts stay consistent with your existing voice.

4 Connect Slack from Starch's integration catalog — the agent will query it live to post finished announcements or send drafts to a private review channel first.

5 Open the Meeting Notes app in Starch and configure it to capture your internal kick-off calls and deal-close debrief meetings — transcripts and action items from those sessions become source material for project-launch announcements.

6 Tell Starch: 'Draft a Slack announcement for #general whenever a HubSpot deal moves to Closed Won. Include the client name, engagement value, project lead, and kick-off date. Keep it under 150 words and post a draft to #founder-review first.' Starch builds this as a triggered automation.

7 Build a second automation for policy and operational updates: 'When I describe a policy change, draft a Slack message for #operations that references any prior related announcements in our Knowledge Management wiki so the language stays consistent. Send me the draft before posting.'

8 For post-meeting announcements, use the Meeting Notes app after each client kick-off call: Starch transcribes the call, extracts decisions and owners, and you tell it 'Turn the action items from today's Meridian call into a Slack post for #meridian-project.'

9 Review every draft in your private Starch review channel or the Email Agent app — each draft arrives with a one-line summary of what it says and why it was written that way, so you can approve in 30 seconds or edit before it goes live.

10 Set a weekly automation: 'Every Monday at 8am, check HubSpot for any deals that moved stages last week and draft a brief team update Slack message summarizing pipeline movement — wins, proposals sent, renewals coming up — and send it to #leadership.' This replaces the pipeline update you currently write by memory.

11 Publish your final announcement templates to the Knowledge Management wiki so future team members (or a future ops hire) can see the standard format and rationale without asking you.

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

Aldridge & Partners Retainer Win — April 2026

Sample numbers from a real run

HubSpot deal: Aldridge & Partners	84,000
Contract term (months)	12
Monthly retainer value	7,000
Kick-off date	20,260,428
Project lead assigned	1

It's Tuesday afternoon. You close the Aldridge & Partners deal in HubSpot — $7,000/month, 12-month retainer, kicking off April 28th. Normally you'd tab over to Slack, type something, realize you forgot the kick-off date, go back to HubSpot, copy it, paste it in, post it, and then spend the next hour answering 'who's the project lead?' in the thread. Instead, Starch detects the HubSpot deal moving to Closed Won, pulls the deal name, contract value, kick-off date, and the project lead you assigned in the deal record, and drops a draft into your #founder-review Slack channel: 'Big news — we just signed Aldridge & Partners on a 12-month retainer starting April 28th. Monthly value: $7k. Jamie is leading the engagement. More details at kick-off sync Thursday. 🎉' You read it in 10 seconds, hit approve, and it posts to #general. Your team sees it while it's still fresh, the thread stays clean because the message answered the obvious questions upfront, and you're back on the phone by 3:15pm.

Measurement

How you'll know it's working

Time from deal close to team-wide announcement (target: under 30 minutes without founder writing time)

Thread reply volume per announcement (fewer follow-up questions = better-written original message)

Percentage of standard announcement types covered by Starch automations vs. written from scratch

Retainer renewal announcements sent before vs. after renewal date (a late announcement means the team finds out from the client, not from you)

Consistency score — whether new policy announcements contradict prior ones (tracked by reviewing Knowledge Management docs against new drafts)

Comparison

What this replaces

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

Writing it yourself in Slack

Zero setup cost, but every message competes with everything else on your plate — context gets dropped, tone varies, and the team learns to read your announcement quality as a proxy for how stressed you are.

Notion + Slack manual workflow

You can maintain a template library in Notion and copy-paste, but you still have to pull numbers from HubSpot manually, and nothing reminds you to post until someone asks why they haven't heard about the new client yet.

Zapier (HubSpot → Slack)

Zapier can trigger a static Slack message when a deal closes, but the message is a template with merged fields — no context from Gmail threads or meeting notes, no tone adjustment, no draft-for-review step before it posts to the whole team.

Dedicated comms or EA hire

Solves the problem at scale, but at a 12-person consultancy you're not there yet — and the hire doesn't fix the underlying data fragmentation across HubSpot, Gmail, and Calendar.

On Starch RECOMMENDED

One platform — email agent, knowledge management, meeting notes 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

Will Starch post announcements automatically, or can I review them first?

Your call. You can configure any automation to post directly to a Slack channel, or to send the draft to a private review channel first. For anything going to #general or a client-facing channel, most founders set up the review step so there's a human in the loop before it goes live. The review adds about 30 seconds — Starch surfaces the draft with a one-line summary of what triggered it.

What if my deal data lives in a Google Sheet instead of HubSpot?

Connect Google Sheets from Starch's integration catalog; the agent queries it live when the announcement automation runs. You'd tell Starch which columns map to client name, contract value, and kick-off date. It's a slightly looser structure than HubSpot's typed schema, but it works.

Can Starch draft announcements in different tones for different channels — #general vs. #operations vs. a client-project channel?

Yes. When you describe the automation or type a prompt, you specify the channel and tone. 'Draft something celebratory for #general' produces a different output than 'write a factual project-update post for #meridian-project.' You can save these as separate automations, one per announcement type.

Is Slack data stored in Starch?

Slack is connected from Starch's integration catalog and queried live — meaning Starch sends messages to Slack and can read channel/user data when needed, but your Slack history isn't stored or synced into Starch's database. If you want past announcements archived as reference material, the right place for that is your Notion Knowledge Management wiki, which does sync on a schedule.

What if a team member posts a question in the Slack thread after the announcement goes live? Does Starch handle replies?

Not automatically — Starch drafts and posts the announcement, but it doesn't monitor threads for replies. If you find you're getting the same three questions every time, that's a signal to add those answers to the original announcement template. The Knowledge Management app is useful here — store a FAQ per announcement type and Starch can pull from it when drafting.

Is Starch SOC 2 certified? We sometimes announce sensitive deal terms internally.

Not yet — Starch is not SOC 2 Type II certified today. If your firm has strict data compliance requirements, that's worth factoring in. For deal announcements that contain sensitive contract values, you can keep the automation scoped to internal Slack channels and use the draft-review step so nothing posts without your explicit approval.