Strategy & Planning

How to run annual planning as Foundation and Nonprofit Ops Teams

Strategy & PlanningFor Foundation and Nonprofit Ops Teams4 apps11 steps~22 min to set up

Your foundation's annual planning cycle is a four-week slog that happens mostly in email threads. The program budget lives in a Google Sheet that three people have edited since last March, the actual spend is in QuickBooks, and reconciling the two takes a full day before anyone can even talk about next year's allocations. Board members want a planning deck by October 1. You're pulling grant pipeline data manually from Salesforce, copy-pasting actuals from QuickBooks, and trying to write a narrative that makes $50M of grantmaking look coherent. The consultants who set up your systems are long gone. Fluxx or Foundant would solve some of this, but they cost six figures and assume a dedicated grants-management team you don't have.

Build this on Starch → See the apps used

Strategy & PlanningFor Foundation and Nonprofit Ops Teams4 apps11 steps~22 min to set up

Outcome

What you'll set up

A live annual planning dashboard that pulls actuals from QuickBooks, grant commitments from Salesforce, and program-area budgets from your existing data — so the numbers in your planning deck match the numbers in your systems

A scenario analysis workspace where you can model next year's grantmaking at different funding levels and see the impact on reserves, operating costs, and program spend before the board asks

A board planning packet that assembles itself from your connected data — grant pipeline, spend-vs-budget by program area, and a narrative summary — so the week before your October board meeting isn't an all-hands scramble

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

Scenario Analysis Budgeting Investor Reporting Presentation Agent

Data sources & config

Starch syncs your QuickBooks data on a schedule — invoices, bills, payments, journal entries, and vendor records refresh automatically, so your planning surfaces always reflect current actuals. Salesforce connects from Starch's integration catalog; the agent queries it live when your grant pipeline view runs. Donor portals and any foundation-specific web dashboards that don't have APIs are automated through your browser — no API needed. Google Sheets with your legacy budget model can be connected from Starch's integration catalog and queried live alongside your accounting data.

Prompts to copy

Build me a scenario analysis that uses our QuickBooks actuals as the baseline and lets me model three versions of next year: flat grantmaking budget, 15% increase in program spend, and a reduced-operations year if our endowment return comes in below 5%. Show reserves, operating cost coverage, and program payout ratio for each.

Create a budgeting dashboard that compares our current-year actuals from QuickBooks against the program-area budgets in our annual plan, broken down by Education, Health Equity, and Economic Mobility. Flag any category that's more than 10% over or under pace.

Build me a board planning packet for our October meeting: grant pipeline summary from Salesforce, spend-vs-budget by program area from QuickBooks, year-end reserves projection, and a 150-word narrative framing our grantmaking posture for next year.

Assemble a 12-slide annual planning presentation. Slide 1: mission context. Slides 2-4: this year's grantmaking by program area with actuals vs. plan. Slides 5-7: three scenarios for next year's budget with runway and payout ratio. Slides 8-10: grants pipeline and commitments. Slides 11-12: proposed allocations and open questions for the board.

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

Walkthrough

Step-by-step

1 Connect QuickBooks to Starch. Starch syncs your chart of accounts, transactions, journal entries, and vendor records on a schedule. This becomes the single source of actuals for every planning surface you build.

2 Connect Salesforce from Starch's integration catalog. The agent queries it live to pull current grant pipeline — applications received, commitments made, grants paid, and grants pending — by program area.

3 If your current-year budget still lives in a Google Sheet, connect it from Starch's integration catalog so the agent can query both the plan and the actuals in the same workflow.

4 Start with the Budgeting app. Describe your program areas and ask Starch to compare actuals from QuickBooks against the plan from your sheet, broken down by Education, Health Equity, Economic Mobility, or whatever categories your board uses. Starch surfaces variance by category without you touching a formula.

5 Open Scenario Analysis and connect Plaid or describe your reserves position. Build three planning scenarios: a baseline using current-year actuals, an increased-grantmaking case, and a conservative case tied to endowment return assumptions. Each scenario shows program payout ratio, operating expense coverage, and year-end reserves.

6 Use the scenario outputs to draft your proposed annual allocations. Ask Starch to generate a one-paragraph narrative for each scenario that you can drop into board materials without rewriting.

7 For any data that lives on grantee portals, government databases, or foundation-specific sites without APIs — 990 data, compliance filings, funder peer benchmarks — Starch automates those sites through your browser with no API needed. Ask Starch to pull the data and surface it alongside your internal numbers.

8 Build your board planning packet. Ask Starch to assemble a summary view: grant pipeline by program area, spend-vs-budget by category, year-end reserves projection, and the scenario comparison. This is the document your ED reviews before the board meeting, not the document you spend a week building.

9 Use the Presentation Agent to turn the planning packet into a board deck. Describe the structure — program narrative, actuals vs. plan, scenario comparison, proposed allocations, open questions — and Starch assembles the slides. Iterate on individual slides with follow-up prompts rather than rebuilding from scratch.

10 Save the planning workflow as a recurring automation. Next year, the same surfaces rebuild themselves from fresh data. You describe any changes to program areas or budget categories and Starch updates the structure without starting over.

11 After the board approves allocations, use Starch to build a grant commitment tracker that pulls from Salesforce live and shows commitments-vs-approved-budget by program area throughout the year — so you're not waiting until next October to find out you overcommitted the Health Equity program in Q2.

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 2025 Annual Planning Cycle — $50M Foundation, 4-Person Ops Team

Sample numbers from a real run

Education Program — approved grantmaking budget	18,500,000
Health Equity Program — approved grantmaking budget	14,000,000
Economic Mobility Program — approved grantmaking budget	12,000,000
Operating expenses (staff, facilities, admin)	3,200,000
Grants paid YTD (QuickBooks actuals through Sept 30)	36,400,000
Grants committed but unpaid (Salesforce pipeline)	5,100,000
Year-end reserves projection (baseline scenario)	6,800,000

By late September, your ops director has connected QuickBooks and Salesforce and described the planning layout to Starch. The budgeting dashboard shows $36.4M paid against $44.5M in approved grantmaking budgets — roughly 82% pace across all programs, with Health Equity running 6% over pace ($8.6M paid against a $14M budget) and Economic Mobility running 11% under ($9.8M paid against $12M). The Salesforce live query surfaces $5.1M in committed but unpaid grants, mostly multi-year awards with payment schedules in Q4 and Q1. The scenario analysis runs three versions of the FY2026 plan: a flat $44.5M grantmaking budget that preserves $6.8M in reserves assuming a 5.5% endowment return; a 15% increase to $51.2M that draws reserves to $3.1M and requires a strong market; and a conservative $38M budget that rebuilds reserves to $9.4M if the endowment return lands at 3.8%. Each scenario shows program payout ratio (the IRS 5% minimum is the floor the ED cares about), operating cost coverage, and the reserve balance at year-end. The board deck assembles from those outputs in about 20 minutes of iteration — 12 slides, real numbers, scenario narratives the ED edits rather than writes. The week before the October board meeting, nobody is manually pulling data from three systems.

Measurement

How you'll know it's working

Program payout ratio by area (grants paid ÷ endowment assets, tracked against 5% IRS floor)

Spend-vs-budget variance by program area at each quarter-end

Grant commitments as a percentage of next year's approved budget (pipeline coverage)

Operating expense ratio (operating costs ÷ total grantmaking, target typically under 15% for a foundation this size)

Reserves coverage in months of operating expenses (board-level solvency metric)

Comparison

What this replaces

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

Fluxx or Foundant GLM

Purpose-built for grants management with built-in workflow and compliance features, but six-figure licensing assumes a dedicated grants-management team and doesn't help you build planning surfaces on top of your financial data.

Excel or Google Sheets (manual annual planning)

Free and familiar, but your plan and your actuals live in different systems and someone has to reconcile them by hand every time you want a current picture — which is most of the time.

Adaptive Insights or Pigment (FP&A tools)

Serious scenario modeling and budget consolidation, but designed for finance teams with a dedicated FP&A analyst; setup and maintenance overhead is high for a 4-person ops team without a CFO.

Salesforce + QuickBooks + a manual board deck

You already have these systems — the problem is that building planning surfaces on top of them requires someone to export, reconcile, and format data every single cycle, which is the work Starch eliminates.

On Starch RECOMMENDED

One platform — scenario planning, quarterly budgeting, investor reporting 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 for our grants database. Can Starch actually read our grant pipeline data, or does it only work with financial systems?

Salesforce connects from Starch's integration catalog; the agent queries it live when your grant pipeline views run. That means you can build planning surfaces that pull grant applications, commitments, payment schedules, and program-area breakdowns from Salesforce alongside actuals from QuickBooks — without any manual export.

Our QuickBooks instance has a somewhat unusual chart of accounts that a consultant set up. Will Starch know how to read it?

Starch syncs your QuickBooks entity-level data on a schedule — invoices, bills, payments, vendors, journal entries — and your chart of accounts structure comes with it. When you describe the planning dashboard you want, you tell Starch which accounts map to which program areas, and the agent builds the view against your actual account structure. You're not fitting your data into a predefined template.

One thing worth knowing: QuickBooks report views — the pre-built P&L, Transaction List, and Vendor Expense reports — are temporarily unavailable due to an upstream issue. Entity-level data (the invoices, bills, payments, and journal entries that make up those reports) syncs normally. So you can build a program-area spend view from underlying transaction data; you just can't pull the formatted QuickBooks P&L report directly right now.

This is a known limit. The entity-level data is what matters for planning surfaces — the pre-built QuickBooks report views are cosmetic wrappers around the same numbers. Starch builds your views from the underlying data, not from the formatted reports.

We need to pull some data from our state's philanthropic reporting portal and from GuideStar for peer benchmarking. Those sites don't have APIs.

Starch automates those sites through your browser — no API needed. Any website you can log into and click through, Starch can navigate. That includes government reporting portals, GuideStar, grantee financial portals, and any other foundation-specific site that predates modern APIs.

Is Starch SOC 2 certified? Our board has questions about data security given that we'd be connecting our QuickBooks and Salesforce accounts.

Starch is not SOC 2 Type II certified yet. That's an honest limit worth naming. If your board requires SOC 2 Type II as a condition of connecting financial systems, that's a real constraint right now. It's on the roadmap.

We already pay for a grants management system. Starch isn't replacing that, right?

Correct. Starch connects to your grants database and your accounting system and lets you build the surfaces in between — the planning dashboard, the scenario model, the board packet. It doesn't replace Salesforce, QuickBooks, or whatever grants management system you're using. Think of it as the layer that makes those systems talk to each other and produce outputs you can actually use.

The Presentation Agent and Budgeting app both sound useful for our board deck and annual planning. Are those live today?

Budgeting and Presentation Agent are both currently in development — you can request beta access to get notified when they launch. In the meantime, you can build custom planning dashboards and scenario analyses in Starch today using the Scenario Analysis app (which is live) and natural-language app authoring for custom views on top of your QuickBooks and Salesforce data.