Marketing & Growth

How to plan a monthly content calendar as Foundation and Nonprofit Ops Teams

Marketing & GrowthFor Foundation and Nonprofit Ops Teams3 apps12 steps~24 min to set up

Your four-person ops team is the communications department, the grants team, and the board relations function rolled into one. Planning a monthly content calendar means someone—usually the same person who pulled the board packet last week—is manually checking what grant cycles are opening, which donor anniversaries are coming up, what program updates need to go out, and when the 990 public disclosure lands. That intelligence lives across a Salesforce instance, a shared Google Sheet, Gmail threads, and one program officer's memory. The result is either a calendar built in a single frantic afternoon or no calendar at all, with content going out reactively. Neither is how you want to represent a $50M foundation to grantees, board members, and the public.

Build this on Starch → See the apps used

Marketing & GrowthFor Foundation and Nonprofit Ops Teams3 apps12 steps~24 min to set up

Outcome

What you'll set up

A monthly content calendar app that pulls open grant cycles, donor touchpoints, and program milestones from Salesforce and Gmail into one prioritized queue — built in natural language, no configuration consultant required

A weekly digest from Growth Analyst that tells you which foundation content (newsletter, annual report landing page, program updates) is actually driving traffic and engagement, so you stop guessing which communications matter

A standing automation that drafts the month's content briefs — donor update letters, grantee announcements, board communication previews — and drops them into your Project Management board as assigned tasks before the first of each month

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

Growth Analyst Project Management Growth Analyst

Data sources & config

Connect Salesforce from Starch's integration catalog — the agent queries it live when the content calendar app runs, pulling contact records, open opportunities, and grant-cycle dates. Starch syncs your Gmail data on a schedule, so the app can read incoming grant notifications, donor replies, and deadline reminders without manual input. Growth Analyst connects to your website analytics via PostHog from Starch's integration catalog. For donor portals or foundation board portals that don't have an API, Starch automates them through your browser — no API needed.

Prompts to copy

Build me a monthly content calendar app that reads our Gmail for upcoming grant cycle deadlines and donor anniversary emails, pulls open opportunities and contact records from Salesforce, and generates a prioritized list of content we need to produce this month — donor letters, grantee announcements, program updates, and board communications — sorted by deadline and relationship tier.

Every Friday at 4pm, draft content briefs for the next month's top five communications based on the content calendar. For each brief, include the audience (board, grantee, donor, public), the key message, the tone guidance (formal for board packets, warm-but-professional for donor letters), and a suggested send date. Create a task in Project Management for each brief, assigned to me, due the following Monday.

Set up Growth Analyst to track our foundation website — specifically which program pages, grant announcement posts, and newsletter archive pages are getting traffic — and email me every Monday morning with a summary of what changed, which content drove the most visits, and where we should focus communications effort this month.

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

Walkthrough

Step-by-step

1 Connect Salesforce from Starch's integration catalog. The agent queries your contact records, open opportunities, and any grant-cycle date fields live — no export, no CSV, no consultant needed to write a report.

2 Starch syncs your Gmail data on a schedule. The content calendar app reads incoming grant deadline notifications, donor thank-you replies, and program update threads to identify time-sensitive communication triggers for the month ahead.

3 Describe the content calendar app in natural language: tell Starch the categories of content your foundation produces (donor letters, grantee announcements, board communications, public program updates), the audiences, and the tone standards for each.

4 Starch builds the app and populates the first month's calendar — a prioritized queue with content type, audience, deadline, and a one-line brief for each item — pulling directly from Salesforce and Gmail rather than asking you to enter data manually.

5 Install Growth Analyst from the Starch App Store. Connect it to PostHog (queried live from Starch's integration catalog) and point it at your foundation website. This takes about ten minutes and requires no analytics expertise.

6 Growth Analyst begins emailing you a weekly digest every Monday: which program pages and grant announcement posts drove the most traffic, what your newsletter open rates look like directionally, and where to focus communications effort this month — in plain language, not a dashboard you have to interpret yourself.

7 Build the monthly automation: 'On the 25th of each month, read the content calendar for next month, draft a one-paragraph brief for each item, create a task in Project Management for each brief assigned to the appropriate team member, and Slack me a summary of what's queued.' Starch assembles this from your description.

8 For donor portals or foundation board portals where you need to check posted grant guidelines or compliance updates, Starch automates those sites through your browser — no API needed. It reads the page and surfaces the relevant dates and requirements into your content calendar app.

9 Review the first auto-generated content queue as a team. Adjust the prioritization logic by telling Starch in natural language: 'Weight donor anniversary letters above general program updates' or 'Flag anything going to board members as high priority and assign it to me directly.'

10 At the start of each month, run the calendar generation manually or let the automation fire. The output is a Project Management board with tasks assigned, briefs attached, and deadlines set — ready for writing, not planning.

11 Use Growth Analyst's weekly digest to close the loop: if a grantee announcement drove unusually high traffic, flag that format for next month's calendar. If a donor letter type is getting low engagement on the website version, adjust the brief template.

12 Publish a shared view of the content calendar as a Starch dashboard for your program officers so they can see what communications are going out about their grants this month — no more 'I didn't know that letter was going to our grantee this week' surprises.

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

April 2026 Content Calendar — Spring Grant Cycle

Sample numbers from a real run

Donor anniversary letters (12 due in April)	12
Spring grant cycle open — 3 new grantee announcements	3
Q1 program update for board packet (due April 18)	1
990 public disclosure notice for website (due April 30)	1
Newsletter — spring grant cohort intro	1

On March 25th, the automation fires. Starch reads Gmail (scheduled sync) and finds 12 donor contact records with April anniversaries flagged in Salesforce (live query from the integration catalog). It also finds three grantee organizations whose grant agreements were signed in Q1, triggering the foundation's standard 60-day public announcement cadence. The content calendar app generates 18 content items for April, prioritized by deadline: the Q1 board communication due April 18th lands at the top, followed by the grantee announcements (April 8, 12, and 19), then the 12 donor letters grouped by relationship tier. The 990 public disclosure notice — a standard compliance communication the team sends every year — is auto-drafted and queued for April 28th with a two-day buffer. Growth Analyst's Monday digest on March 31st shows that last year's spring grant cohort announcement got 340% more website traffic than a typical program update, so the team decides to write the newsletter intro first rather than last. Total planning time: thirty minutes reviewing the queue instead of three hours building it.

Measurement

How you'll know it's working

Donor communications sent on time as a percentage of total donor touchpoints due that month (target: 100% — a missed anniversary letter to a $500K donor is not recoverable)

Content calendar completion rate: tasks drafted, assigned, and completed before send date vs. total items queued

Board communication turnaround time: days between board meeting date and when the program update brief is in draft

Grantee announcement lead time: days between grant agreement execution and public announcement going out

Website traffic to program pages week-over-week, tracked via Growth Analyst's weekly digest

Comparison

What this replaces

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

Fluxx or Foundant (purpose-built grants management)

Built for grants management at scale with a dedicated team; costs $60K–$150K+ annually and assumes a full-time grants manager — not sized for a 4-person foundation ops team that also handles communications, compliance, and board relations.

Asana + manual content calendar in Google Sheets

Works if someone has time to maintain both; in practice, the Sheet goes stale by week two and Asana tasks get created without the Salesforce context that tells you which donor or grantee the communication is actually about.

Mailchimp + in-house editorial calendar

Mailchimp handles the send; it doesn't help you figure out what to send, when, and to whom based on your grant cycles and donor relationships — you still build the calendar by hand.

Hiring a communications coordinator

The right long-term answer for a growing foundation; costs $70K–$90K annually before benefits, and you still need the systems this person will work in — Starch is what you build for them before you can afford them.

On Starch RECOMMENDED

One platform — growth analyst, project management, growth analyst 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

We use Salesforce, but it was set up by a consultant three years ago and the schema is a mess. Will Starch still be able to read our grant cycle dates and donor records?

Yes. When you connect Salesforce from Starch's integration catalog, the agent queries it live and discovers your schema — including custom fields and objects the consultant created. If your grant cycle dates live in a field called 'Cycle_Open_Date__c' instead of a standard field, you tell Starch that when you describe the app ('our grant cycle open dates are in the custom field called Cycle_Open_Date__c') and it reads accordingly. You don't need a clean Salesforce instance, just access to one.

Our donor portal (we use a foundation-specific giving platform) doesn't have a public API. Can Starch still pull deadline and reporting dates from it?

Yes. For portals without an API — including most foundation-specific giving platforms and donor-advised fund portals — Starch automates them through your browser, no API needed. It logs in, navigates to the relevant pages, and extracts the dates and requirements you care about. You tell Starch where to look and what to pull; it handles the navigation.

Is Starch SOC 2 Type II certified? We have a board that asks about data security for any new vendor.

Not yet — Starch is not currently SOC 2 Type II certified. That's worth knowing if your board has hard requirements around certified vendors. Starch can tell you what security practices are in place, but we won't claim a certification that isn't there.

We produce maybe 15–20 pieces of foundation communication per month. Is this overkill for that volume?

For a $50M foundation, the value isn't volume — it's that the right donor letter goes out before the anniversary, the board packet brief is drafted before the program officer is chasing you for it, and the grantee announcement doesn't get forgotten because the grants manager (you) was busy with a 990 question. Fifteen communications where none slip is worth more than fifty sent reactively.

QuickBooks is mentioned — can Starch pull program spend data into the content calendar so we know which programs have budget to announce new grants this month?

Yes. Starch syncs your QuickBooks data on a schedule — bills, invoices, vendors, and journal entries are all available. You can tell the content calendar app to cross-reference program spend against your budget (which lives in a Google Sheet you connect from Starch's integration catalog, queried live) so the queue only surfaces new grant announcements for programs that have remaining committed capital. Note: QuickBooks report views like the full P&L are temporarily unavailable due to an upstream connector issue, but entity-level data including invoices and journal entries syncs normally.

Can the content briefs Starch drafts actually match our foundation's voice? We write in a very specific tone for donors versus grantees versus the public.

You describe the tone guidelines when you build the app — 'donor letters should be warm, personal, and reference the specific program area their gift supports; grantee announcements should be formal and lead with the grant amount and purpose; public program updates should be accessible and avoid jargon.' Starch applies those rules per content type when it drafts each brief. The briefs are starting points, not final copy — your team still writes and approves everything.