How to draft a slack announcement on Starch

A Slack announcement sounds simple — you're just telling your team something. But the drafts that actually land are the ones that answer the right questions upfront (what changed, why now, what you need from people), use a consistent format the team recognizes, and go out at the right moment. The ones that don't land sit in #announcements unread, get followed by a flood of clarifying questions in DMs, or worse, create confusion because the context was buried in paragraph four.

What this looks like in practice varies: a product launch message reads differently than a policy change, a fundraise announcement has different stakes than a sprint retrospective summary, and what your team needs to hear after a rough quarter is structured nothing like a routine ops update. The format, tone, and level of detail shift depending on what you're announcing and to whom.

On Starch, you end up with a drafted announcement ready to review and post — pulled from the actual source material. If the announcement follows a board meeting, it draws from your meeting notes. If it's a weekly company update, it pulls from whatever live data you've connected: deals closed, revenue numbers, milestones hit. You're not rewriting summaries from scratch or copying numbers out of a spreadsheet. You get a draft in your Slack channel or your clipboard, built from real context, that you edit and send — not one you write from a blank page.