Internal Comms & Meetings

How to draft a slack announcement as Foundation and Nonprofit Ops Teams

Internal Comms & MeetingsFor Foundation and Nonprofit Ops Teams2 apps12 steps~24 min to set up

Your four-person ops team sends a lot of Slack announcements: grant cycle opens, board meeting reminders, compliance deadlines, program spend updates, new grantee welcomes. Each one gets drafted by whoever has context that day, usually in a Notes app or a Google Doc, then copy-pasted into Slack. Tone is inconsistent — sometimes formal, sometimes casual — because three different people are writing them. Important details (deadline dates, portal links, DocuSign URLs) get buried or forgotten. There's no record of what went out, no way to audit what staff were told before a 990 filing question comes up, and the drafting itself takes 20-30 minutes for what should be a 5-minute task.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Foundation and Nonprofit Ops Teams2 apps12 steps~24 min to set up

Outcome

What you'll set up

A Starch app that drafts Slack announcements in your foundation's voice, pulling live context from your calendar, QuickBooks, and Salesforce so the right dates and numbers are already in the message

A searchable archive of every announcement you've sent — indexed so you can answer 'what did we tell staff about the Q3 grant cycle?' in seconds

A consistent drafting workflow any team member can run, so the ED isn't the only one who gets the tone right

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

Knowledge Management Meeting Notes

Data sources & config

Google Calendar is a scheduled-sync provider — Starch syncs your calendar data on a schedule, so announcement drafts auto-populate with correct meeting dates and deadlines. Salesforce is connected from Starch's integration catalog; the agent queries it live to pull grantee names and grant amounts when you need them in an announcement. QuickBooks is a scheduled-sync provider — Starch syncs your QuickBooks data on a schedule, so program spend figures in budget-update announcements pull from live actuals. Notion, if your team uses it for internal docs, is also a scheduled-sync provider.

Prompts to copy

Build me a Slack announcement drafting app for our foundation's internal comms. It should let me pick the announcement type (grant cycle open, board meeting reminder, compliance deadline, grantee welcome, program spend update), pull in relevant dates from Google Calendar, and output a draft in a formal-but-approachable tone that I can review and post. Archive every published announcement in a searchable log.

Add a template for grantee welcome announcements that pulls the grantee organization name and grant amount from Salesforce and formats it as a 3-paragraph staff update.

Build a section in our Knowledge Management app that stores every Slack announcement we've sent since January 2025, tagged by type and date, so we can search them during audits or board prep.

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

Walkthrough

Step-by-step

1 Connect Google Calendar as a scheduled-sync provider. Starch syncs your calendar on a schedule so upcoming board meetings, grant deadlines, and compliance dates are always available to pull into announcement drafts.

2 Connect Salesforce from Starch's integration catalog. The agent queries it live when you're drafting a grantee welcome or a grant-cycle open announcement and need accurate grantee names, award amounts, or application counts.

3 Connect QuickBooks as a scheduled-sync provider so Starch has current actuals — when you're drafting a program spend update for staff, the numbers come from your books, not a stale spreadsheet.

4 Open Starch and describe your announcement app in plain language. Tell it the announcement types your foundation sends most often and what data belongs in each one.

5 Starch builds a simple interface: pick announcement type, confirm the auto-populated details (date from calendar, grantee from Salesforce, spend figure from QuickBooks), review the draft.

6 For grant-cycle announcements, the app pulls the application deadline from your calendar event and the total available funding from the relevant QuickBooks budget line. You review, edit the narrative if needed, and copy to Slack.

7 For grantee welcome announcements, the app queries Salesforce live to confirm the organization name and grant amount, then formats a three-paragraph staff update that you can post the same day the agreement is signed.

8 Every published announcement is automatically logged in the Knowledge Management app — tagged by type, date, and relevant grant cycle — so your team has a permanent, searchable record.

9 When a compliance question comes up (a 990 audit, an expenditure responsibility review), search the announcement archive in Knowledge Management to pull exactly what staff were told and when.

10 Meeting Notes captures any discussion from your ops standups or board prep calls about messaging decisions — so if the reason you changed the language on a grantee announcement is ever in question, it's in the meeting record.

11 Any team member — not just the ED — can run the drafting workflow. Tone consistency comes from the app's template logic, not from whoever had bandwidth that morning.

12 Review the announcement log quarterly. If the same announcement type is being edited heavily every time, update the template prompt in Starch to reflect the language your team actually uses.

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

Spring 2026 Grant Cycle Open — Staff Announcement

Sample numbers from a real run

Total available funding (Spring 2026 cycle)	750,000
Number of returning grantees eligible to apply	14
Application portal open date (from Google Calendar)	0
Submission deadline (from Google Calendar)	0
Time to draft without Starch	25
Time to draft with Starch	5

It's the first week of March. Your program officer needs to send a staff-wide Slack announcement that the Spring 2026 grant cycle is open. Without Starch, she opens a blank doc, checks the shared Google Sheet for the funding total ($750,000 across 14 returning grantees), navigates to the Salesforce instance to confirm applicant counts are reset, and looks up the portal URL she bookmarked somewhere in Chrome. She writes the announcement from scratch, copies it to Slack, and 25 minutes have passed. With Starch, she opens the Slack announcement app, selects 'Grant Cycle Open,' and the draft appears: funding total pulled from the QuickBooks budget line for Spring 2026 program grants ($750,000), application window pulled from the two Google Calendar events your ED created last month (March 3 open, April 18 deadline), and a placeholder for the portal link she pastes in herself. She reviews the three-paragraph draft, makes one edit to the opening sentence, and posts. Five minutes. The announcement is automatically logged in Knowledge Management under 'Spring 2026 / Grant Cycle Open / March 3 2026' — findable in seconds when your auditor asks what staff were told about the cycle timeline.

Measurement

How you'll know it's working

Time to draft and post a routine internal announcement (target: under 8 minutes)

Number of announcements with factual errors caught post-posting (grant amounts, dates, portal links)

Percentage of staff announcements that can be traced in the archive during a compliance review

Consistency of tone across announcements written by different team members (qualitative, reviewed quarterly by ED)

Time spent reconstructing internal communications history during board prep or 990 preparation

Comparison

What this replaces

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

Manual drafting in Google Docs + copy-paste to Slack

Free and flexible, but produces inconsistent tone, requires manual data lookup every time, and leaves no searchable archive of what went out.

Slack's own message scheduling and pinning

Good for distribution but does nothing to help draft the message or pull in live data from your calendar, QuickBooks, or Salesforce.

Fluxx or Foundant built-in comms features

These platforms have grant-specific notification tools, but they're scoped to grantee-facing comms, cost six figures for a small ops team, and don't help with internal staff announcements at all.

Notion templates + manual population

Starch actually syncs Notion on a schedule, so you can use both — but a static Notion template still requires someone to look up and type in the dates and dollar figures by hand every cycle.

On Starch RECOMMENDED

One platform — 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

Does Starch post directly to Slack, or does my team still have to copy-paste?

Starch connects to Slack from its integration catalog and can post to channels directly when an automation runs. For announcement drafts you want to review before sending, the standard workflow is: draft in Starch, review, post yourself. You can also build an automation that posts automatically — for example, a weekly program spend update every Monday morning — if the announcement doesn't need a human review step.

We use Salesforce, but it was set up by a consultant three years ago and the schema is a mess. Will Starch still work with it?

Starch connects to Salesforce from its integration catalog and the agent queries it live. It handles nonstandard field names and custom objects — you describe what you need (grantee org name, grant amount, award status) and the agent figures out where that lives in your instance. You don't need a clean Salesforce setup for this to work.

Is our announcement history secure? We sometimes reference grant amounts and grantee names in internal comms.

Starch is not SOC 2 Type II certified today — that's worth knowing if your foundation has strict data security requirements. Data from your scheduled-sync providers (QuickBooks, Google Calendar) lives in Starch's database. If your compliance officer needs SOC 2 Type II before connecting financial data, that's an honest constraint right now.

We already have a Notion wiki. Can Starch pull from it instead of replacing it?

Yes. Starch syncs your Notion data on a schedule — pages, databases, users. The Knowledge Management app can sit on top of your existing Notion content, so your announcement archive and your existing wiki live together in one searchable place. You're not starting over.

What about announcements that reference our QuickBooks budget lines — does Starch have access to the full chart of accounts?

Starch syncs QuickBooks on a schedule and pulls 20+ entity types including invoices, bills, payments, vendors, and journal entries. One current limitation: QuickBooks report views (the pre-built P&L and Transaction List reports) are temporarily unavailable pending a connector fix. Entity-level data syncs normally, so budget-line figures you'd find in journal entries or bills are accessible. If you need a formatted P&L report in the announcement, pull the number from the entity data rather than a QuickBooks report view for now.

Can a program associate run this, or does it require the ED or ops director every time?

That's the point. Once the announcement app is built and the templates are configured, any team member opens it, picks the announcement type, reviews the auto-populated draft, and posts. The ops director or ED sets up the templates once; staff run them ongoing. No one has to be the institutional memory for what tone the foundation uses.