Internal Comms & Meetings

How to write a weekly team update as Foundation and Nonprofit Ops Teams

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

Every Friday afternoon, someone on your four-person ops team spends 90 minutes assembling a weekly update by hand: pulling open Salesforce to count how many grant applications moved stages, checking QuickBooks to see if program spend is tracking to budget, skimming Slack for anything the program officers flagged, and then writing a narrative that sounds coherent to your board chair and your ED at the same time. The update lives in a Google Doc that gets emailed as a PDF. Half the team has stopped reading it because it's always late. The person who wrote it resents writing it. And the numbers in it are already two days stale by the time it lands.

Build this on Starch → See the apps used

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

Outcome

What you'll set up

A weekly update that auto-drafts itself every Friday morning — pulling live grant-pipeline counts from Salesforce, program spend vs. budget from QuickBooks, and any flagged action items from your project tracker — so all you're doing is a 10-minute review before sending.

A single searchable archive of every weekly update, board packet narrative, and team decision, so when your new grants associate asks 'what did we say about the literacy portfolio in Q3?' they find the answer in 30 seconds instead of asking you.

Automated follow-up reminders tied to action items called out in the update, so 'Finance to confirm grant agreement executed by Oct 15' doesn't disappear into the ether after you hit send.

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

Project Management Knowledge Management Email Agent Meeting Notes

Data sources & config

Salesforce connects from Starch's integration catalog — the agent queries it live when the weekly automation runs. Starch syncs your QuickBooks data on a schedule (invoices, bills, payments, journal entries) so spend figures are ready without a manual export. Notion connects from Starch's integration catalog if your team documentation lives there; alternatively, Starch's built-in Knowledge Management app stores updates natively. Google Calendar syncs directly so the automation can reference what meetings happened that week.

Prompts to copy

Every Friday at 8am, pull open grant applications from our Salesforce pipeline (stages: Inquiry, LOI, Full Proposal, Due Diligence, Approved, Declined), count by stage and compare to last week, pull QuickBooks program spend against our Q4 budget categories, summarize any tasks that closed or are overdue in Project Management, and draft a weekly update in our standard format: pipeline summary, spend summary, decisions made this week, open items for next week.

Add this week's update to Knowledge Management under 'Weekly Updates / 2026' and tag it with any grant names mentioned.

Extract all action items from this week's update, create tasks in Project Management with owners and due dates as specified, and send me a reminder on Tuesday if any are still open.

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 will query your grant pipeline live — stages, application counts, movement week-over-week — each time the automation runs. No manual Salesforce report export required.

2 Starch syncs your QuickBooks data on a schedule. Map your program budget categories (e.g., Education Initiative, Capacity Building, Operations) to the QuickBooks classes or accounts you actually use, so spend comparisons reflect your chart of accounts, not a generic template.

3 Install the Project Management app and migrate your open-item log into it — or just tell Starch to create tasks from whatever your team currently tracks in a shared doc. Voice or prompt task creation means your program officers can add items without a login tutorial.

4 Install the Meeting Notes app and run it on your weekly team call. After the call, it produces a summary with decisions and action items. The weekly update automation can pull from this summary directly instead of requiring anyone to re-type what was discussed.

5 Describe your weekly update format to Starch in plain language: what sections it needs, whose names appear as owners, what tone is appropriate for your ED vs. your board chair. Starch builds a draft template from your description.

6 Set the automation to run every Friday at 8am. It pulls Salesforce pipeline counts, QuickBooks spend vs. budget, closed and overdue tasks from Project Management, and the Meeting Notes summary from your weekly call, then assembles a draft in your format.

7 Review the Friday draft — your job is approving numbers and adjusting the narrative tone, not assembling the underlying data. Budget 10 minutes instead of 90.

8 Tell the Email Agent to send the approved update to your distribution list (ED, board chair, program leads) and file a copy to Knowledge Management under the correct folder and tags.

9 After send, the automation extracts action items from the update, creates tasks in Project Management with named owners and due dates, and sets Tuesday follow-up reminders for any that are still open mid-week.

10 At the start of each quarter, ask Knowledge Management: 'Summarize the decisions made about the literacy portfolio across all weekly updates in Q3.' It returns a synthesized answer from archived updates — useful for 990 narrative sections, grant reports, and board packet context.

11 When a new grants associate joins, point them to Knowledge Management. Onboarding paths are built from your archived updates and decisions, so institutional knowledge doesn't require a two-hour download from you.

12 For board meeting prep, ask Starch to pull the last 12 weekly updates and generate a quarterly narrative with spend trends, pipeline conversion rates, and open items that carried across multiple weeks. This is the foundation of your board packet, not a blank doc.

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

October 2026 Weekly Update — Week of Oct 13

Sample numbers from a real run

Salesforce pipeline — Full Proposal stage	7
Salesforce pipeline — LOI stage	12
QuickBooks: Education Initiative spend YTD	1,240,000
QuickBooks: Education Initiative budget YTD	1,350,000
QuickBooks: Capacity Building spend YTD	410,000
QuickBooks: Capacity Building budget YTD	375,000
Open action items carried from prior week	3
New action items from Oct 13 team call	5

On Friday October 17 at 8:05am, Starch's automation queried Salesforce and found 7 applications at Full Proposal stage (up from 5 the prior week — two LOIs converted) and 12 at LOI stage. It pulled QuickBooks spend for the week and surfaced that Capacity Building is running $35,000 over YTD budget, a variance that hadn't been flagged yet because it only became visible when program spend and the Google Sheet budget were reconciled in the same surface. The draft weekly update called this out with the line: 'Capacity Building is $35k over YTD budget as of Oct 17 — recommend review before the Nov grant cycle opens.' Your ops director reviewed the draft at 8:20am, adjusted the tone on the Capacity Building flag so it didn't read as alarming to the board chair, and approved. The Email Agent sent it at 8:35am. Three action items were extracted automatically: (1) Finance to pull Capacity Building invoice detail by Oct 22, (2) Program lead to confirm two newly converted Full Proposals have signed grant agreements in DocuSign, (3) ED to review updated 990 expenditure responsibility memo before Oct 31. All three appeared as tasks in Project Management with owners and due dates before 9am. The ops associate who used to spend Friday afternoons on this update spent that time instead reviewing two grant agreements.

Measurement

How you'll know it's working

Time to send weekly update from data-pull to send (target: under 20 minutes, from a prior 90-minute baseline)

Grant applications advanced by stage week-over-week (pipeline velocity by stage: Inquiry → LOI → Full Proposal → Approved)

Program spend vs. budget variance by initiative category, flagged when any category exceeds 5% over or under YTD budget

Open action items older than 7 days (update quality metric — high carryover means the update isn't driving closure)

Board packet assembly time ahead of quarterly board meetings (goal: first draft in under 2 hours from archived weekly updates)

Comparison

What this replaces

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

Manual Google Doc + Salesforce report export + QuickBooks export

Costs 90 minutes of skilled ops staff time every week and produces a document that's already stale — Starch queries the same data sources automatically and drafts the narrative.

Fluxx or Foundant (purpose-built grants management)

Six-figure annual cost, assumes a dedicated grants-management team, and still doesn't write the internal update — Starch connects to your existing Salesforce instance and builds the surfaces on top of it.

Notion weekly template + manual fill

Good for storing updates but someone still has to pull the numbers from Salesforce and QuickBooks manually each week — Starch automates the data pull and the draft, Notion just stores the result.

ChatGPT or Claude with manual copy-paste

Good at polishing prose once you've assembled the numbers, but you're still doing the assembly — Starch connects directly to your data sources so no copy-paste step exists.

On Starch RECOMMENDED

One platform — project management, knowledge management, email agent 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 understand our custom objects?

When you connect Salesforce from Starch's integration catalog, the agent queries it live and can work with whatever field names and custom objects exist in your instance. You describe what you want in plain language ('count applications where Stage equals Full Proposal') and Starch figures out the mapping. If a field name is ambiguous, it will ask you to clarify once and remember your answer.

Our QuickBooks program categories don't match our grant budget line items exactly. How does the spend comparison work?

Starch syncs your QuickBooks data on a schedule — bills, invoices, payments, journal entries — and you describe the mapping in natural language when you build the automation ('map QuickBooks class Education Initiative to budget line 3.1 in our annual budget'). You're not locked into QuickBooks' category structure for the surface Starch builds on top. That said, if you need a live reconciliation against a Google Sheet budget, Starch can query Google Sheets from its integration catalog at the same time.

Is this secure enough for donor data and grant applicant information?

Starch is not SOC 2 Type II certified yet — that's worth knowing upfront. For a foundation handling donor information and grant applicant PII, you should evaluate that against your data governance requirements. Starch doesn't store data pulled from live-queried integrations like Salesforce beyond what's needed to run the automation; QuickBooks data syncs to Starch's database on a schedule. If your foundation has a policy requiring SOC 2 Type II for any SaaS touching program data, that's an honest constraint today.

What if we want to include donor portal updates (e.g., application status from a funder's portal) in the weekly update?

If the donor portal has no API, Starch can automate it through your browser — no API needed. You'd describe what to look for ('log into the Luminate portal, check the status of our three pending applications, and include the results in the Friday update'), and Starch's browser automation handles the navigation and data extraction. This works for most foundation and government grant portals.

We already have a Notion workspace where we store team documentation. Can the weekly updates go there instead of Starch's Knowledge Management app?

Yes. Notion connects from Starch's integration catalog, so the automation can write each weekly update to your existing Notion database after it's approved. You don't have to migrate documentation. Starch's built-in Knowledge Management app is an option if you want AI-powered search across updates without maintaining the Notion structure, but it's not required.

The QuickBooks report views like the P&L are mentioned in the capability catalog — can we use those in the weekly update?

Honest answer: QuickBooks report views (P&L, Transaction List, Vendor Expenses) are temporarily disabled in Starch pending a connector fix. Entity-level data — bills, invoices, payments, vendors, journal entries — syncs normally and is available today. For most weekly update use cases (spend vs. budget by category, open payables) the entity-level data is enough. If you need the formatted P&L view specifically, that's a limitation to be aware of right now.