People & HR

How to plan headcount as Foundation and Nonprofit Ops Teams

People & HRFor Foundation and Nonprofit Ops Teams3 apps12 steps~24 min to set up

Your foundation runs headcount planning out of a QuickBooks payroll export dropped into a Google Sheet that three people have edited since the last board meeting. When program leadership wants to add a half-time grants coordinator in Q3, you're manually reconciling salary, benefits load, and restricted-fund allocations across tabs that don't talk to each other. Paylocity or ADP has the actual headcount data; QuickBooks has the budget actuals; the strategic plan lives in a Notion doc. None of these surfaces speak to each other, so every headcount conversation requires a manual data-pull the day before it matters.

Build this on Starch → See the apps used

People & HRFor Foundation and Nonprofit Ops Teams3 apps12 steps~24 min to set up

Outcome

What you'll set up

A live headcount model that pulls actual salary and benefits data from your payroll system and compares it against program budget allocations by restricted fund, so you always know your true personnel cost before a board meeting.

A scenario-comparison view showing what adding a 0.5 FTE grants coordinator in Q3 does to your runway and fund balances, built on your actual Stripe restricted-gift revenue and Plaid bank data — not a spreadsheet assumption.

An automated headcount snapshot delivered to your Slack channel before each board meeting, pulling from QuickBooks actuals and your payroll system so the ops team isn't manually assembling numbers the week of.

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 Runway Analysis Budgeting

Data sources & config

Starch syncs your QuickBooks data on a schedule (invoices, bills, payments, journal entries, vendors) and your Paylocity data on a schedule (employees, payroll runs, benefits, time-off balances). Stripe is also synced on a schedule to bring in restricted gift revenue. Salesforce is connected from Starch's integration catalog and queried live when the headcount app needs to cross-reference open grant commitments against personnel allocations. Notion is synced on a schedule to pull in your strategic hiring plan. Any donor portal or government compliance site that doesn't have an API is automated through your browser — no API needed.

Prompts to copy

Build me a headcount planning model that pulls our current staff salaries and benefits from Paylocity, maps each role to a program budget line from QuickBooks, and shows me how adding a 0.5 FTE grants coordinator in Q3 affects our total personnel spend and restricted-fund balances through year-end.

Show me three scenarios side by side: (1) headcount flat, (2) add 0.5 FTE grants coordinator in July, (3) add 1.0 FTE grants coordinator in July — with runway and net burn for each, using our actual Stripe gift revenue and Plaid bank feeds as the baseline.

Build me a quarterly budget tracker that breaks down personnel costs by program area — Education, Climate, General Operations — comparing budgeted versus actual spend from QuickBooks, with a pace indicator for each restricted fund.

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

Walkthrough

Step-by-step

1 Connect QuickBooks via Starch's scheduled sync — this pulls your chart of accounts, payroll journal entries, and vendor bills on a recurring schedule so headcount costs are always current, not last month's close.

2 Connect Paylocity via Starch's scheduled sync to bring in your live employee roster, salary bands, benefits elections, and payroll run history — so your headcount model reflects actual comp, not budget placeholders.

3 Connect Stripe via Starch's scheduled sync to pull in restricted and unrestricted gift revenue; this becomes the revenue baseline in your scenario models so runway projections reflect real cash in, not grant commitments.

4 Connect Salesforce from Starch's integration catalog — the agent queries it live when your headcount app needs to see open grant commitments or program budgets tied to specific roles, flagging any position whose funding source closes before the hire's projected end date.

5 Connect Notion via Starch's scheduled sync to bring in your strategic hiring plan document — Starch reads the planned roles, timelines, and program assignments so the model knows what you intend to hire, not just what you've hired.

6 Start from the Scenario Analysis app — tell Starch 'use our Stripe gift revenue and Plaid bank feeds as the baseline, then model flat headcount, +0.5 FTE in July, and +1.0 FTE in July as three scenarios showing runway and net burn through December 2026.' Starch builds the comparison view from your actual data.

7 Fork the Runway Analysis app and tell Starch 'break down burn by personnel versus program expenses, and flag any month where personnel costs exceed 65% of total operating spend' — a threshold your board tracks against your program-efficiency ratio.

8 Build a custom headcount allocation table by telling Starch 'show me each staff role, their salary plus benefits load from Paylocity, their assigned program area, and the restricted fund covering them from QuickBooks — flagged red if the fund balance covers less than six months of that role's cost.'

9 Use the Budgeting app to set quarterly personnel budgets by program area, compare them against actual payroll from QuickBooks, and see pace indicators so you know by February whether Education is tracking to blow its personnel line before the grant period ends.

10 Set up an automation: 'Every Friday at 9am, pull current headcount from Paylocity, total personnel spend month-to-date from QuickBooks, and remaining restricted-fund balances from QuickBooks, and post a summary to the #ops-team Slack channel.' Starch schedules and runs it — no manual pull required.

11 Before each board meeting, tell Starch 'generate a one-page headcount summary showing current FTE count by program, open positions, Q3 hiring plan, and total projected personnel spend through year-end under each scenario' — export it or hand it directly to the Presentation Agent when it launches.

12 When a program director asks about adding a role, tell Starch 'model adding a 1.0 FTE Program Officer at $90K salary plus 28% benefits load, funded from the Climate Resilience restricted fund, starting October 1 — show me how that affects the fund balance and our overall runway.' Get the answer in seconds, not a spreadsheet session.

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

Q2 2026 Headcount Review — Climate Program Expansion

Sample numbers from a real run

Climate Program — Personnel (current)	187,000
Climate Program — Personnel (proposed +1.0 FTE Program Officer)	302,600
Climate Resilience Restricted Fund Balance	410,000
Months of Climate personnel covered at proposed headcount	16
General Operations — Personnel (current)	143,000
Total Foundation Personnel Spend (current annualized)	498,000
Total Foundation Personnel Spend (proposed annualized)	613,600

Your Climate program director wants to add a full-time Program Officer by October 1. Normally this triggers a week of back-and-forth: someone exports the Paylocity roster to confirm current Climate headcount, someone else checks QuickBooks to find the Climate Resilience fund balance, and a third person builds a new tab in the shared spreadsheet to model the impact. With Starch, you type: 'Model adding a 1.0 FTE Program Officer at $90K salary plus 28% benefits load to the Climate program, funded from the Climate Resilience restricted fund, starting October 1 — show me fund balance through June 2027 and flag any shortfall.' Starch pulls the current Climate personnel cost ($187,000 annualized, confirmed from Paylocity) and the Climate Resilience fund balance ($410,000 from QuickBooks). The proposed hire adds $115,600 annually ($90K + 28% benefits), bringing Climate personnel to $302,600. The model shows the fund covers 16 months of proposed Climate personnel from October — meaning you hit a shortfall in January 2028, six months before your next Climate grant renewal closes. That's the conversation you need to have with your program director before approving the hire, and it takes ten minutes instead of a week.

Measurement

How you'll know it's working

Personnel cost as a percentage of total operating expenses, by program area and in aggregate — your board tracks this against your stated program-efficiency ratio

Restricted fund runway per role: how many months each restricted fund covers the personnel costs assigned to it, surfaced before any hire decision

Headcount variance to plan: budgeted FTEs versus actual FTEs by quarter, broken out by program and general operations

Benefits load accuracy: actual benefits spend per employee from Paylocity versus the 28% (or whatever your assumed load is) baked into budget models

Time from headcount request to board-approved model: currently measured in days of spreadsheet work; target is same-day scenario delivery

Comparison

What this replaces

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

Fluxx or Foundant

Purpose-built for grants management but costs six figures, assumes a dedicated grants-management team, and doesn't solve the headcount planning problem — you'd still need a separate HR and finance workflow on top of it.

QuickBooks + Paylocity + Google Sheets (your current stack)

You already own these tools, but the connections between them are manual exports and copy-paste — every headcount model is already stale by the time it reaches the board.

Workday or ADP Workforce Now

Robust headcount planning modules, but enterprise pricing and implementation timelines that a 4-person ops team can't justify for a $50M foundation's scale.

Adaptive Planning (Workday Adaptive)

Excellent scenario modeling, but requires a finance hire to maintain it, takes months to implement, and costs far more than the ops budget a lean foundation team controls.

Custom Google Sheets model

Free and flexible, but every scenario is a new tab, every board meeting requires a manual data pull, and the model breaks the moment someone edits a formula — which happens every time.

On Starch RECOMMENDED

One platform — scenario planning, runway analysis, quarterly budgeting 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 Paylocity for payroll — can Starch actually pull live salary and benefits data from it?

Yes. Paylocity is one of Starch's scheduled-sync providers, meaning Starch syncs your employee roster, payroll runs, benefits elections, and time-off balances on a recurring schedule. The data lives in Starch's database so your headcount model doesn't require a manual export every time you run a scenario.

Our grants database is in Salesforce — a custom instance someone configured three consultants ago. Will Starch connect to it?

Salesforce is available from Starch's integration catalog and queried live when your app runs. Starch won't replace your Salesforce instance or restructure it — it reads the data you already have there and surfaces it in whatever headcount or grant-pipeline view you describe.

We track program budgets against restricted funds in QuickBooks. Can Starch show personnel costs mapped to specific restricted funds?

Yes. QuickBooks entity-level data — invoices, bills, journal entries, vendors, payments — syncs on a schedule. You can tell Starch 'show me personnel costs mapped to each restricted fund from QuickBooks, flagged if the fund balance covers less than six months of the assigned role's cost' and it builds that view from your actual chart of accounts. One current note: QuickBooks P&L and Transaction List report views are temporarily disabled pending a fix, but entity-level data syncs normally.

We're not SOC 2 certified — is Starch?

Starch is not SOC 2 Type II certified today. If your foundation's data-governance policy or a major funder requires SOC 2 certification before connecting payroll or financial data, that's worth flagging before you get started. It's on the roadmap.

Can Starch automate the headcount summary that goes to our board — without us building it manually every quarter?

That's exactly the kind of automation Starch is built for. You describe it in plain language — 'every quarter, two weeks before the board meeting, pull current FTE count from Paylocity, personnel spend by program from QuickBooks, and our three headcount scenarios, and post a summary to Slack with a link to the full model' — and Starch sets up the scheduled run. You're not writing any code; you're describing the outcome.

We use a donor portal and a government compliance site that don't have APIs. Can Starch touch those?

If you can log in and navigate it in a browser, Starch can automate it through browser automation — no API needed. That covers donor portals, 990-filing portals, expenditure-responsibility tracking sites, and similar tools that have no integration catalog entry.

Will Starch replace our grants-management system — Salesforce, or eventually a tool like Fluxx?

No, and it's worth being direct about this: Starch is not a grants-management system. It connects to the systems you already have — Salesforce, QuickBooks, Paylocity — and lets you build the surfaces in between: the headcount model, the board dashboard, the fund-balance alert. Your grants database stays where it is.