Internal Comms & Meetings

How to run a monthly business review as Foundation and Nonprofit Ops Teams

Internal Comms & MeetingsFor Foundation and Nonprofit Ops Teams3 apps10 steps~20 min to set up

The week before your board meeting, one person on your four-person team disappears into spreadsheets. They're pulling QuickBooks actuals into a shared Google Sheet, manually reconciling program spend against budget lines, copying grant disbursement totals out of Salesforce (which a consultant configured in 2019 and nobody fully trusts), and stitching everything into a slide deck that looks slightly different every quarter. The CFO at a $500M foundation has a finance team that does this. You have Tuesday afternoon and a prayer. The deck is usually done by Thursday night, reviewed Friday morning, and sent to board members who will ask about a number you couldn't verify in time.

Build this on Starch → See the apps used

Internal Comms & MeetingsFor Foundation and Nonprofit Ops Teams3 apps10 steps~20 min to set up

Outcome

What you'll set up

A monthly business review dashboard that pulls QuickBooks actuals, Plaid cash balances, and Salesforce grant-pipeline data into one place — updated on a schedule, not by hand

An auto-drafted board packet narrative that surfaces budget variances, program spend by grantee category, and cash runway in plain language your board chair can read in 10 minutes

A standing automation that runs the first business day of each month, assembles the data, flags anomalies, and sends a draft to your ops lead for review before the meeting

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

Investor Reporting Runway Analysis Scenario Analysis

Data sources & config

Starch syncs your QuickBooks data on a schedule (invoices, bills, journal entries, vendor payments — all 20+ entity types). Starch syncs your Plaid bank feed data on a schedule for real-time cash balances and transaction categorization. Connect Salesforce from Starch's integration catalog; the agent queries it live when your grant-pipeline view or board report needs disbursement and application data. Donor portals and government compliance sites that have no API are automated through your browser — no API needed.

Prompts to copy

Build me a monthly board report that pulls our QuickBooks program expense actuals, compares them to the budget we uploaded, shows grant disbursements by program area, and includes a 12-month cash runway chart from our Plaid bank feeds. Format it as a board packet with an executive summary paragraph at the top.

Show me our current burn rate and cash runway using our Plaid operating account and our Salesforce grant receivables pipeline. Flag any month where projected cash drops below 6 months of operating expenses.

Model three scenarios: (1) we make two additional $500K grants this quarter on schedule, (2) we delay both by 90 days, (3) one LP delays their $2M pledge by a quarter. Show how each scenario changes our runway and year-end cash position.

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

Walkthrough

Step-by-step

1 Connect QuickBooks so Starch syncs your actuals on a schedule — bills, invoices, journal entries, and vendor payments pull automatically. No manual export from QuickBooks Online.

2 Connect your foundation's operating and program bank accounts through Plaid so Starch syncs transaction and balance data on a schedule — this becomes the source of truth for cash runway.

3 Connect Salesforce from Starch's integration catalog so the agent can query grant application status, approved amounts, disbursement dates, and grantee records live when your board report runs.

4 Open the Runway Analysis starter app and describe your foundation's structure: 'Show cash runway using our Plaid operating account, subtract recurring program expenses from QuickBooks, and project 18 months forward.' Starch builds the dashboard; you review and adjust the category labels to match your chart of accounts.

5 Open the Investor Reporting starter app and describe your board packet format: 'Every first Monday of the month, pull QuickBooks actuals vs. budget by program area, Salesforce grant-pipeline totals, and Plaid cash balance. Write an executive summary paragraph, flag any line item more than 10% over budget, and email the draft to me and our board chair.' Starch schedules and drafts it.

6 Tell Starch to include grantee-level disbursement detail: 'Add a section that lists every grant payment made this month from QuickBooks, grouped by program area, with the Salesforce opportunity name next to each one.' This cross-references your accounting system and your grants database without manual VLOOKUP.

7 Use the Scenario Analysis starter app to model the cash impact of grant timing decisions before the board meeting: connect Plaid and describe the scenarios you want — delayed pledges, accelerated disbursements, new multi-year commitments — and see runway under each one.

8 For donor portals that require manual login and don't expose an API — your community foundation's grant reporting portal, state charitable registration dashboards — tell Starch to automate the data pull through your browser: 'Log into [portal], navigate to our grant status page, extract the current balance and next reporting deadline, and add it to my monthly board report.'

9 Set up the automation trigger: 'Run this on the first business day of every month. Assemble the board packet, flag variances, run the scenarios, and Slack me a summary with a link to the draft.' Your ops lead reviews the draft rather than building it.

10 Before the board meeting, tell Starch to update the narrative for anything that changed since the draft ran: 'The $750K pledge from the Smith Family Foundation came in this week — update the cash runway chart and revise the executive summary paragraph.' One prompt, not an afternoon.

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

March 2026 Quarterly Board Packet — Greenfield Community Foundation

Sample numbers from a real run

Education Program grants disbursed (Q1)	487,500
Housing Initiative grants disbursed (Q1)	312,000
Operating expenses (Q1 actuals)	94,200
Q1 budget variance — Housing (over)	38,000
Pending grant receivable — Smith Family Foundation pledge	750,000
Cash balance (Plaid, as of March 31)	4,120,000

It's the Friday before the April board meeting. Starch ran the monthly automation on April 1st and delivered a draft board packet to the ops lead by 8am. The executive summary flagged one variance automatically: the Housing Initiative came in $38,000 over Q1 budget, driven by two emergency grants approved in February that weren't in the original plan. Starch pulled the QuickBooks journal entries for both, found the matching Salesforce opportunity records, and included a one-sentence explanation in the packet without anyone touching a spreadsheet. The cash runway chart showed 14.2 months at current burn using the Plaid balance and QuickBooks expense run rate — down from 16.1 months in February because of the Housing overage. The ops lead ran a Scenario Analysis with one prompt: 'Show what happens if the Smith Family Foundation $750K pledge arrives in April vs. June vs. not at all.' The board chair received a clean PDF on Thursday evening. The question they asked — 'What's the plan if Smith delays?' — was already answered on page 4.

Measurement

How you'll know it's working

Months of operating cash runway (updated monthly from Plaid + QuickBooks actuals)

Program spend actuals vs. budget by program area (pulled from QuickBooks, compared to uploaded budget)

Grant disbursements made vs. committed pipeline (QuickBooks payments vs. Salesforce approved amounts)

Board packet draft-to-send time (target: under 2 hours of human review, down from 2 days of manual assembly)

Budget variance by line item (any program area more than 10% over or under plan flagged automatically)

Comparison

What this replaces

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

Fluxx or Foundant GrantsConnect

Purpose-built for grants management and board reporting, but starts around $30-60K/year and assumes a dedicated grants-management team — overkill for a four-person foundation ops team that needs a board packet, not a full GMS replacement.

Manual QuickBooks export + Google Sheets + Google Slides

Free and familiar, but someone spends two days every month doing the export, reconciliation, and formatting by hand — and the deck looks different every quarter because there's no consistent template enforcing itself.

Blackbaud Financial Edge NXT

Deep nonprofit accounting and reporting functionality, but six-figure implementation cost and designed for organizations with a dedicated finance team, not a lean ops team wearing five hats.

Power BI or Tableau connected to QuickBooks

Powerful dashboards once built, but requires someone with BI skills to build and maintain them — and a four-person ops team usually doesn't have that person, so the dashboards never get built or go stale.

On Starch RECOMMENDED

One platform — investor reporting, runway analysis, scenario planning 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 configured by a consultant and the data quality is inconsistent. Will Starch still work?

Starch connects to Salesforce from its integration catalog and queries your data live — whatever's actually in your instance, including custom fields and objects. If your grant stages or disbursement amounts are inconsistently filled in, Starch will surface that gap rather than hide it. You can tell Starch to flag records where key fields are empty: 'Show me all approved grants in Salesforce where disbursement date is blank.' That's actually a useful artifact of the monthly review process — the board packet doubles as a data-quality audit.

QuickBooks is our accounting system but our program budget lives in a shared Google Sheet. Can Starch use both?

Yes. Starch syncs your QuickBooks data on a schedule (actuals, bills, payments, journal entries). Connect Google Sheets from Starch's integration catalog and the agent queries your budget tab live when the board report runs. You can tell Starch: 'Pull program area actuals from QuickBooks and compare them to the budget in column D of our FY2026 Budget tab in Google Sheets. Calculate the variance for each row.' No manual VLOOKUP required.

We use Xero, not QuickBooks. Does this still work?

Yes — connect Xero from Starch's integration catalog; the agent queries it live when your dashboard or board report needs actuals. The workflow is the same; you'd describe your chart of accounts to Starch in natural language and it builds the variance analysis from whatever Xero returns. The scheduled-sync depth is deeper for QuickBooks, but Xero via the integration catalog is fully functional for the board-packet use case.

Is Starch SOC 2 certified? We have data governance requirements as a foundation.

Starch is not currently SOC 2 Type II certified — that's a real limit worth naming. If your board or legal counsel requires SOC 2 certification before connecting financial or grantee data, that's a legitimate blocker today. It's on the roadmap. In the meantime, you control which data sources you connect and what the automation does with the output.

Our donor portal and state charitable registration site don't have APIs. Can Starch still pull data from them?

Yes — Starch automates those through your browser, no API needed. If you can log in and click through the site yourself, Starch can do the same thing: navigate to your grant status page, pull the current balance and next reporting deadline, and include it in your board packet. This works for government compliance portals, community foundation grant portals, and any other web-based system that doesn't expose a formal API.

We don't want fully automated reports sent to the board without human review. Can we build in an approval step?

Yes. Set up the automation to run and deliver the draft to your ops lead first — not directly to the board. Tell Starch: 'On the first business day of the month, run the board packet and Slack me a link to the draft for review. I'll trigger the send manually after I've reviewed it.' You get the time savings of automated assembly without losing the human checkpoint before anything goes to the board.