People & HR

How to set compensation bands as Foundation and Nonprofit Ops Teams

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

Your foundation runs maybe 12-15 staff across programs, grants, and ops. Compensation bands don't exist in writing anywhere — they live in the ED's head, the last salary survey someone bought three years ago, and a locked spreadsheet HR consultants built during a reorg. When you're hiring a new program officer or promoting a grants coordinator, you're pulling numbers from GuideStar peer data, a Chronicle of Philanthropy survey PDF, and whatever Candid publishes, then reconciling them manually against your QuickBooks payroll data to figure out where you actually sit. No dedicated HR staff. No compensation consultant on retainer. Just you, three browser tabs, and a deadline from the board's finance committee.

Build this on Starch → See the apps used

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

Outcome

What you'll set up

A living compensation band framework that maps each role (program officer, grants manager, ops coordinator, ED) to salary ranges anchored to actual peer organization data and your own payroll history from QuickBooks and Paylocity

A repeatable review process that surfaces pay equity gaps, compression issues, and budget impact before you bring anything to the finance committee or full board

A Knowledge Management app that stores your compensation philosophy, band methodology, and annual review decisions so the next time anyone asks 'how did we set this number,' the answer exists somewhere other than a single person's memory

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

Knowledge Management Budgeting

Data sources & config

Starch syncs your QuickBooks data on a schedule — payroll-related entities including bills, payments, and journal entries flow in automatically. Connect Paylocity from Starch's direct connection so employee records, pay statements, and org unit data refresh on a schedule. For peer salary benchmarking data locked behind survey portals (Candid nonprofit compensation survey, AFP benchmarking tool, regional nonprofit association salary reports), Starch automates those sites through your browser — no API needed. The Budgeting app pulls QuickBooks actuals directly to model the total personnel cost impact of any band adjustment before it goes to the board.

Prompts to copy

Build me a compensation band tracker for a 15-person nonprofit foundation. Roles are: Executive Director, Deputy Director, Program Officer (senior and junior), Grants Manager, Grants Coordinator, Operations Manager, Finance Associate, and Executive Assistant. Pull our actual salary and payroll data from QuickBooks and Paylocity. For each role, show current salary, the band minimum, midpoint, and maximum we've set, where each person sits as a compa-ratio, and a flag if anyone is below band minimum or above band maximum.

Build me a knowledge base that stores our compensation philosophy document, band-setting methodology, annual survey sources we use (Candid, GuideStar, AFP), decisions made at each annual review, and any board or finance committee approvals. Make it searchable so any staff member or auditor can find our rationale for any salary decision.

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

Walkthrough

Step-by-step

1 Connect QuickBooks — Starch syncs your chart of accounts, payroll bills, and vendor payments on a schedule so you have a live picture of what you're currently spending on personnel by role.

2 Connect Paylocity — Starch pulls employee records, pay statements, and org unit structure on a schedule, giving you the current salary for every employee mapped to their title and department.

3 Tell Starch to build the compensation band tracker app using the prompt above. Starch reads your current payroll data and scaffolds a table with every role, current salary, and a placeholder band range for you to populate.

4 Pull your external benchmarking sources. Starch automates the Candid nonprofit compensation survey portal and any regional salary benchmark sites through your browser — no API needed — and brings the data into your band tracker so you can see market percentiles alongside your actual numbers.

5 Set your band ranges. Work with your ED or finance committee chair to decide where you want to position relative to market (e.g., target the 50th percentile for program roles, 60th for leadership). Enter those decisions directly into the Starch app.

6 Review the compa-ratio column. The app flags anyone below 0.85 (below-band risk, retention concern) or above 1.15 (above-band, compression issue). In a 15-person foundation, you may find two or three flagged employees — surface these to the finance committee with context, not just numbers.

7 Open the Budgeting app and model the total personnel cost of bringing every below-band employee to the band minimum. Starch pulls your current QuickBooks actuals as the baseline and shows you what the annualized budget impact looks like against your current program and operations budget.

8 Run a pay equity cut. Ask Starch to group your compa-ratios by gender and tenure and show you whether any patterns exist. For a 15-person team this is a straightforward table — but it's the kind of thing your board's DEI committee will ask about.

9 Document the band-setting process and decisions in the Knowledge Management app. Store the survey sources you used, the percentile targeting decision, the finance committee approval date, and any exceptions granted. This is your 990 and audit trail.

10 Set up a scheduled annual review. Tell Starch to remind you each November to re-pull the benchmarking data, refresh the compa-ratio table from current Paylocity records, and generate a summary of what's changed since last year's review.

11 Publish your compensation philosophy document to the Knowledge Management app so any staff member can read how bands are set, what the review cadence is, and who approves exceptions — reducing the number of times you field the same question individually.

12 Before your next finance committee meeting, ask Starch to generate a one-page compensation band summary showing current bands, where every employee sits, and the budget impact of any proposed adjustments — ready to drop into your board packet.

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

Annual Compensation Review — Q1 2026, $50M Community Foundation

Sample numbers from a real run

Program Officer (Senior) — current salary	78,000
Program Officer (Senior) — band midpoint (50th pct, Candid survey)	84,500
Grants Coordinator — current salary	52,000
Grants Coordinator — band minimum	55,000
Total cost to bring 2 below-band employees to minimum	8,200
Total personnel budget (current)	1,240,000
Personnel budget post-adjustment	1,248,200

In January 2026, the ops lead at a $50M community foundation uses Starch to run the annual compensation review ahead of the February finance committee meeting. Starch pulls current salaries from Paylocity (15 employees across 8 roles) and cross-references them against the Candid 2025 Nonprofit Compensation Report, which Starch pulls from the survey portal through browser automation. The band tracker surfaces two issues: the Senior Program Officer is at $78,000 against a market midpoint of $84,500 — a compa-ratio of 0.92, flagged yellow — and the Grants Coordinator is at $52,000, $3,000 below the band minimum of $55,000. The ops lead opens the Budgeting app, which shows total current personnel spend of $1.24M against a $1.3M personnel budget line in QuickBooks. Bringing both employees to their targets costs $8,200 annually — well within the existing budget surplus. The ops lead documents the band methodology (Candid 50th percentile for individual contributor roles, 55th for management) in the Knowledge Management app, records the finance committee approval date, and publishes the compensation philosophy so the ED isn't fielding individual questions about how salaries are set. The whole process — benchmarking, gap analysis, budget modeling, documentation — takes one afternoon instead of two weeks of spreadsheet work.

Measurement

How you'll know it's working

Compa-ratio by role (target range 0.90–1.10 for most positions)

Percentage of staff within their compensation band (goal: 100% by end of fiscal year)

Personnel budget variance — actual payroll spend vs. approved budget line in QuickBooks

Pay equity gap by demographic group (compa-ratio dispersion across gender or tenure cohorts)

Time from annual review kickoff to finance committee approval (target: under 3 weeks)

Comparison

What this replaces

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

Spreadsheet + Candid/GuideStar PDF reports

Free and familiar, but band ranges live in a file that gets stale, doesn't connect to your actual payroll data, and disappears when the person who built it leaves.

Payscale or Radford subscription

Good market data, but costs $5,000–$15,000/year for a nonprofit license and gives you a benchmarking report, not a connected app that knows what you're actually paying in QuickBooks and Paylocity.

HR consultant engagement

Produces a defensible band framework for the board, but typically costs $8,000–$20,000 per engagement, happens once every three to five years, and leaves you with a PDF — not a living system you can update yourself.

Rippling or Gusto (HRIS)

Solid payroll and HR platforms, but compensation band management and peer benchmarking aren't their core feature — you still need to build the analysis layer on top, and the platforms assume a dedicated HR owner.

Fluxx or Foundant (grants management suite)

Purpose-built for grant lifecycle management and board reporting at foundations, but cost six figures, require dedicated grants-management staff to administer, and don't solve the compensation band problem — they solve a different problem entirely.

On Starch RECOMMENDED

One platform — knowledge management, 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 Salesforce for grants management and QuickBooks for financials. Does Starch connect to both?

Yes. Connect Salesforce from Starch's integration catalog — the agent queries it live when your apps need it. Starch syncs your QuickBooks data on a schedule, so payroll bills, payments, and journal entries are always current. The compensation band app can pull from QuickBooks directly; it doesn't need to touch your Salesforce grants data at all.

We use Paylocity. Is that supported?

Yes. Starch connects directly to Paylocity and syncs employee records, payroll runs, and pay statements on a schedule. That's the source of truth for current salaries in your band tracker.

Our salary benchmarking data comes from a Candid survey we log into with a foundation account. Can Starch pull that?

Yes. Starch automates that site through your browser — you give it your credentials, and it navigates the portal, pulls the relevant compensation tables, and brings them into your app. No API needed from Candid's side.

Is Starch SOC 2 Type II certified? We have to answer to our board and auditors about data handling.

Not yet. Starch is not SOC 2 Type II certified today. If your board or auditors require SOC 2 Type II for any vendor touching payroll or HR data, that's a real constraint to weigh. It's on the roadmap.

We're a small team — no dedicated HR person. Who owns the compensation band process in Starch?

Typically the ops lead or ED. The apps are built by describing what you want in plain English — no technical setup required. Once the tracker and Knowledge Management app are live, the annual review process is a matter of refreshing the benchmarking data, reviewing the compa-ratio flags, and documenting the decisions. It's designed for a team where the person running the review has ten other things on their plate.

Can Starch store our board-approved compensation policy so it's findable later?

Yes. The Knowledge Management app is built exactly for this. Store your compensation philosophy document, the band methodology, the survey sources you used, and the finance committee approval date. It's searchable, version-tracked, and accessible to any staff member you give access to — so the answer to 'how did we set this salary' doesn't live only in the ED's inbox.

Our QuickBooks report views are something we rely on heavily. Any issues there?

One honest note: QuickBooks report views like P&L and Transaction List are temporarily unavailable while an upstream connector issue is being fixed. Entity-level data — bills, invoices, payments, vendors, and journal entries — syncs normally. For compensation band work, you're primarily reading payroll bills and payments, which are not affected.

We run on a tight budget. What does this actually cost relative to hiring an HR consultant?

An HR consultant engagement to set compensation bands typically runs $8,000–$20,000 and produces a PDF that goes stale in two years. Starch gives you a connected, living app you can update yourself annually. The benchmarking data pulls from sources you may already pay for (Candid survey) or that Starch can pull through browser automation. The upfront time investment is one afternoon to set up the app; the annual review is a half-day after that.