Internal Comms & Meetings

How to draft a slack announcement as Solo Media and Creator Founders

Internal Comms & MeetingsFor Solo Media and Creator Founders2 apps12 steps~24 min to set up

You record a podcast episode, wrap a sponsor deal, and then realize you never told your co-host or VA the recording link, the sponsor talking points, or the publish date — because your 'announcement' was a Slack message you typed at 11pm and never sent, or three separate DMs that contradicted each other. When you're running a newsletter or podcast solo or with one part-time contractor, there's no comms rhythm. Slack announcements happen ad hoc or not at all. Sponsors get confused about deliverables. Episode launches go sideways because nobody synced on timing. You're not forgetting things because you're disorganized — you're forgetting because you're also the talent, the editor, and the sales rep.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Solo Media and Creator Founders2 apps12 steps~24 min to set up

Outcome

What you'll set up

A Starch app that drafts structured Slack announcements for episode launches, sponsor activations, and newsletter sends — pulling from your Notion editorial calendar and Gmail sponsor threads so the draft already has the right dates, links, and deliverables

An email-to-Slack pipeline that converts sponsor confirmation emails into a formatted Slack message your VA or co-host can act on without asking you follow-up questions

A recurring weekly announcement automation that summarizes what's live, what's coming, and what's overdue — posted to Slack on a schedule so your small team stays aligned without a Monday standup

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

Data sources & config

Starch syncs your Gmail data on a schedule so the email agent reads incoming sponsor confirmations and partnership briefs without you forwarding anything manually. Starch connects directly to Notion so your editorial calendar entries are available when building weekly Slack drafts. Slack is connected from Starch's integration catalog; the agent queries it live when posting or drafting announcements. No code, no Zapier chain — you describe what the announcement should contain and Starch assembles it.

Prompts to copy

Watch my Gmail for emails with subject lines containing sponsor name or 'confirmed' and draft a Slack announcement that includes the sponsor name, deliverable dates, talking points from the email body, and the episode or issue number. Post the draft to the #ops channel for my review.

Every Monday at 8am, pull this week's Notion editorial calendar entries and draft a Slack message summarizing: what publishes this week, which sponsor slots are confirmed vs. pending, and any action items tagged to my VA. Post it to #weekly-sync.

When I forward you a brand partnership email, extract the campaign name, deliverable dates, payment amount, and any spec requirements, then draft a Slack message I can send to my co-host or editor with all the details formatted clearly.

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

Walkthrough

Step-by-step

1 Connect Gmail in Starch — Starch syncs your inbox on a schedule and the email agent starts reading incoming sponsor and partnership threads.

2 Connect Notion from Starch's integration catalog so the agent can query your editorial calendar live when it builds weekly announcements.

3 Connect Slack from Starch's integration catalog; the agent will post drafts to whatever channel you specify — #ops, #launches, #team, whatever you actually use.

4 Open the Email Agent app and type: 'Watch for sponsor confirmation emails and draft a Slack message for my #ops channel with the sponsor name, deliverable dates, talking points, and episode or issue number.'

5 Test it by forwarding a real sponsor email to see the draft output — edit the template prompt if the format isn't right for how your team reads Slack.

6 In the Knowledge Management app, create a short doc that defines your standard episode launch checklist — recording link, sponsor mention timing, publish date, thumbnail status. Starch can reference this when building announcements so nothing structural gets dropped.

7 Set up the Monday morning automation: 'Every Monday at 8am, query this week's Notion editorial calendar, check Gmail for any unresolved sponsor threads, and post a Slack summary to #weekly-sync with what's live, what's coming, and what's pending.'

8 Add a second automation for episode launch day: 'When an episode publish date on my Notion calendar matches today, draft a Slack announcement for #team with the episode title, guest name, sponsor mention, and YouTube or podcast link — pull the link from the Notion entry.'

9 Wire up a sponsor activation alert: 'When a new email arrives from a confirmed sponsor domain, draft a Slack message for my editor with the campaign specs and due date so they can plan the recording or newsletter slot.'

10 Review the first week of auto-drafted announcements and adjust the prompt wording for anything that consistently comes out wrong — the agent updates its behavior from plain-English corrections.

11 Use the Knowledge Management app to store your sponsor brief template and episode format guide so the agent has standing context when drafting — no need to re-explain your format every time.

12 Once the rhythm is stable, add a Friday recap automation: 'Every Friday at 4pm, summarize what published this week, which sponsors were mentioned, and any follow-up emails still outstanding — post to #recap and flag anything that needs my attention before the weekend.'

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

May 2026 Episode Launch — Sponsor Activation Week

Sample numbers from a real run

Sponsor deal confirmed (email thread)	2,500
Episode publish date (Notion calendar)	0
Talking points buried in email chain	0
VA hours spent chasing details	90

It's Wednesday. You just got a confirmation email from a $2,500 sponsor for your Thursday episode. Normally you'd forward it to your VA with a half-written note about what they need to do, then answer three follow-up Slack questions from them over the next four hours. With Starch, the email agent reads the confirmation, extracts the sponsor name (Riverside), the agreed talking points, the deliverable (60-second mid-roll mention), and the payment amount, then drafts a Slack message to #ops: 'Riverside confirmed for Ep. 84 — publishes Thursday May 14. Mid-roll at ~32min. Talking points: [extracted from email]. Invoice sent, payment due May 21. No additional assets required.' Your VA sees it, replies with a thumbs up, and you never typed a word. The Monday automation already had the episode on the weekly-sync summary because it pulled from your Notion calendar. No phone tag, no missing context, no $90 worth of back-and-forth to communicate what was already written in an email.

Measurement

How you'll know it's working

Time from sponsor confirmation email to VA-ready Slack announcement (target: under 5 minutes, was previously 2-4 hours)

Number of launch-day Slack messages you personally wrote vs. auto-drafted (track weekly)

Sponsor deliverable miss rate — how often a talking point, date, or asset requirement was missed at time of recording

VA follow-up questions per episode launch (a proxy for announcement clarity)

Weekly editorial calendar coverage — percentage of scheduled episodes that had a Slack summary posted before publish day

Comparison

What this replaces

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

Zapier + Slack

Can forward emails to Slack, but can't read the email content intelligently, extract structured fields, or adapt the announcement format to your editorial calendar context — you end up with a raw email dump instead of a usable team brief.

Notion + manual Slack posts

Works fine if you actually write the Slack message every time, but the bottleneck is you — this stack has no way to auto-draft from your inbox or calendar without you initiating every action.

Beehiiv or Substack internal tools

Solve the publishing layer well but have no outbound Slack integration, no sponsor workflow, and no way to pull from your Gmail threads to build internal team communications.

A part-time EA or OBM

A human will always write a better Slack message than any AI right now, but at $40-60/hr for 4-6 hours of sponsor ops coordination per month, you're spending $200-360/mo on tasks that are 80% information extraction and formatting — the part Starch handles.

On Starch RECOMMENDED

One platform — email agent, 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 read my Gmail, or do I have to forward emails manually?

Starch syncs your Gmail data on a schedule — it reads your inbox automatically. You don't forward anything. One honest note: the Gmail OAuth consent screen currently shows the name of Starch's underlying email connector, not 'Starch' itself. That's a cosmetic issue on the roadmap to fix, not a functional one. The data sync works normally.

My editorial calendar is in Notion — can Starch actually read it?

Yes. Connect Notion from Starch's integration catalog and the agent queries your pages and databases live when building announcements. If your calendar is a Notion database with date, episode title, and guest fields, Starch can read all of it.

What if my sponsor emails don't follow a consistent format?

That's the normal case. The email agent uses AI to extract the relevant fields — sponsor name, dates, deliverables, amounts — from however the email is actually written. You can also tell it 'if the email doesn't mention a talking point, flag the draft for my review before posting' so nothing goes to your VA half-baked.

I use ConvertKit, not Gmail — does this work with my email setup?

The email agent and scheduled inbox sync are built around Gmail and Outlook. ConvertKit is reachable from Starch's integration catalog for querying subscriber and campaign data, but if your sponsor correspondence lives in a ConvertKit inbox rather than Gmail, you'd want to route that to Gmail first. Most creator founders keep sponsor DMs in Gmail even if they send newsletters from ConvertKit.

Is Starch SOC 2 certified? I'm giving it access to my inbox and a Slack workspace.

Not yet — Starch is not SOC 2 Type II certified today. That's an honest limit worth knowing before you connect sensitive inboxes. If SOC 2 is a hard requirement for your situation, that's a real constraint. Most solo and small-team creator founders aren't blocked by this, but you should make the call with full information.

Can I post the announcement directly to Slack, or does it always need my approval first?

Your choice. You can configure the automation to post directly to a channel, post as a draft to a review channel first, or send you a DM to approve before anything goes live. Most people start with a review step and then switch to direct posting once they trust the output quality.