People & HR

How to track open roles as Small Finance Teams

People & HRFor Small Finance Teams2 apps10 steps~20 min to set up

Your 3-person finance team doesn't own hiring, but you feel every open role in the P&L. Each unfilled seat is a cost center assumption that's already wrong: the headcount plan you built in your 13-week cash model assumes a February start date that HR quietly pushed to April. Nobody told you. You find out when payroll comes in $18K lighter than projected and the variance looks like a mistake. Open roles live in a spreadsheet someone in HR maintains, job postings scatter across Greenhouse and LinkedIn, and your headcount-to-forecast reconciliation happens manually every time someone thinks to ping you. There's no clean feed from any of these tools into NetSuite or QuickBooks, so your budget-vs-actual headcount table is always stale.

Build this on Starch → See the apps used

People & HRFor Small Finance Teams2 apps10 steps~20 min to set up

Outcome

What you'll set up

A live open-roles tracker that pulls from your HR systems and shows headcount gaps against your approved budget by department, so your cash model reflects reality and not a six-week-old spreadsheet

An automated weekly digest that flags newly opened roles, roles that slipped their target start date, and roles that closed — delivered to your inbox before you rebuild the forecast on Friday

A headcount reconciliation view that maps open and filled roles to their NetSuite or QuickBooks cost center so budget-vs-actual variance on payroll lines has an explanation attached

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

Data sources & config

Starch syncs your Paylocity data on a schedule (employees, payroll runs, time-off records) so the filled-role side of your headcount table is always current. For open roles in Greenhouse or Lever, connect them from Starch's integration catalog — the agent queries them live when your tracker refreshes. NetSuite cost center and department data syncs on a schedule so every open role maps to the right budget bucket without manual lookup. Slack and Gmail are both available: Starch syncs Gmail on a schedule and connects Slack from the integration catalog so your weekly digest lands wherever you already read things.

Prompts to copy

Build me an open roles tracker that shows every open headcount, the department it sits in, the approved budget for that role, the target start date, and current status. Pull from Paylocity for filled and active roles so I can see the delta against our approved headcount plan. Flag any role where the target start date has passed and the role is still open.

Create a headcount knowledge base that stores the approved headcount plan by department, links each open role to its NetSuite cost center code, and lets me search 'who owns engineering hiring this quarter' without asking the CEO.

Set up a weekly automation: every Thursday at 4pm, compare current open roles against last week's snapshot, summarize what changed — newly opened, closed, or start-date-slipped — and send me the diff as a Slack message and a Gmail summary so I have it before I rebuild the cash forecast on Friday.

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

Walkthrough

Step-by-step

1 Connect Paylocity (scheduled sync) so Starch has a live feed of every active employee, their department, cost center, and start date — this becomes the 'filled' side of your headcount reconciliation.

2 Connect Greenhouse or Lever from Starch's integration catalog so open requisitions, job stage, and target start dates are queryable whenever your tracker runs.

3 Connect NetSuite (scheduled sync) so Starch can pull department and cost center codes and match every open role to the correct P&L line — no more manually cross-referencing a second spreadsheet.

4 Start from the Project Management app and tell Starch: 'Build me an open roles tracker where each card is a headcount req, with fields for department, cost center, approved salary band, target start date, current stage, and days open.' Starch builds the board; you review and adjust field names to match how your team talks about roles.

5 Add a reconciliation column that compares approved headcount (from your plan, imported as a reference table) to current filled + open count by department, so the gap is visible without a VLOOKUP.

6 Set up the Knowledge Management app to store your approved headcount plan as a living document — department by department, approved FTEs, salary budget, and the cost center each role rolls into. Tell Starch: 'Create a headcount plan knowledge base that HR and finance can both search, and flag me when any entry hasn't been updated in 30 days.'

7 Build the Thursday automation: 'Every Thursday at 4pm, pull the current open roles from Greenhouse and compare to last Thursday's snapshot. List roles that opened this week, roles that closed or were filled, and any role where the target start date is now in the past but the role is still open. Send the summary to my Gmail and post it in #finance on Slack.'

8 Add a cash-model impact field to each open role card: when a role's start date slips, Starch calculates the monthly payroll savings against your budget assumption and surfaces the number so you can update your 13-week model with one copy-paste instead of a manual recalculation.

9 Set a second automation for month-end: 'On the last business day of each month, generate a headcount variance report comparing approved headcount budget to actual payroll cost by department from QuickBooks, and list every open role that contributed to the favorable variance.' This becomes your month-end headcount footnote without manual assembly.

10 Share a filtered view of the open-roles tracker with the hiring manager for each department — they see only their roles, update status notes directly, and Starch writes those updates back into the master tracker so you're not chasing five people over Slack to get current status.

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

Q1 2026 Headcount Close — March 31

Sample numbers from a real run

Engineering — approved headcount	12
Engineering — filled (Paylocity active)	9
Engineering — open reqs (Greenhouse)	3
Monthly payroll budget (Engineering)	187,500
Actual March payroll (QuickBooks sync)	141,200
Favorable variance — 3 open seats	46,300
Q1 cumulative headcount underrun	112,400

Going into March close, your 13-week cash model had assumed all 12 engineering headcount would be filled by February 1. Starch's Thursday digest flagged on February 6 that three senior engineer reqs slipped their start dates — two pushed to April, one to May. Because Starch had already mapped those reqs to the Engineering cost center in NetSuite, you updated your cash model the same day: $46,300 favorable variance in March alone, $112,400 cumulative in Q1. When the CFO asked in the board prep call why payroll was $112K under budget, you had the headcount reconciliation ready: three open reqs, specific role titles, specific slip dates, specific cost center. No scramble to reconcile Greenhouse against QuickBooks manually. The month-end automation had already built the footnote.

Measurement

How you'll know it's working

Days-to-fill by department vs. approved headcount plan target

Monthly payroll budget variance attributable to open headcount (favorable or unfavorable)

Number of roles where actual start date slipped vs. modeled start date in the cash forecast

Headcount-budget-to-actual by cost center at month-end close

Open-role aging: reqs open more than 60 days as a share of total open reqs

Comparison

What this replaces

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

Greenhouse + a headcount Google Sheet

Greenhouse tracks recruiting pipeline well but has no native link to your financial cost centers or cash model, so the reconciliation between open reqs and budget variance is always a manual export-and-VLOOKUP exercise that breaks the moment someone renames a department.

Workday or BambooHR with a built-in headcount module

Full HRIS platforms have headcount planning features but they're built for HR and require separate exports to get the data into NetSuite or QuickBooks in a format finance can use for variance analysis; Starch connects both sides so finance and HR read from the same source.

A shared Notion or Confluence headcount doc

Works fine for a single source of truth in a static moment, but Notion doesn't pull live from Paylocity or Greenhouse, so the doc is stale within a week and someone (usually you) has to manually update it before close.

Rippling or Deel with headcount analytics

Strong if your company is already on Rippling, but the headcount analytics don't map to your NetSuite cost center structure or your 13-week cash model without a custom integration that your 3-person team doesn't have time to build or maintain.

On Starch RECOMMENDED

One platform — project management, knowledge management 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 Greenhouse for recruiting and Paylocity for payroll. Will Starch actually pull from both?

Yes. Starch syncs Paylocity on a schedule — employees, start dates, pay data — so your filled-headcount side is always current. Greenhouse is reachable from Starch's integration catalog of 3,000+ apps; the agent queries it live when your open-roles tracker runs. You connect both in Starch and describe what you want to see; Starch handles the data routing.

Our headcount plan lives in a Google Sheet. Can Starch use that as the baseline for budget-vs-actual?

Yes. Connect Google Sheets from Starch's integration catalog and the agent queries it live. You'd tell Starch something like: 'Use the Approved Headcount tab in this sheet as the budget baseline, and compare it to current Paylocity active employees plus Greenhouse open reqs by department.' Starch builds the reconciliation view on top of both sources.

Does Starch store all of this HR data? We have some sensitivity around employee records.

For Paylocity (a scheduled-sync provider), Starch does sync and store the data it needs to power your apps — that's how the weekly Thursday digest can compare this week's snapshot to last week's without running a live query both times. Starch is not SOC 2 Type II certified today, which is worth knowing if your company has a vendor security review process. For teams where that matters, it's an honest limitation.

We don't have a formal headcount plan — just a rough number the CEO tracks in his head. Can Starch still help?

Yes, and it's actually a good forcing function. Start by telling Starch: 'Create a headcount plan template for a 200-person company, organized by department, with fields for approved FTEs, salary band, cost center, and target start date.' Starch builds the template; you fill in what you know. Even a rough plan stored in Starch is better than nothing when the CFO asks why payroll is $46K under budget in March.

Will this replace our ATS or HRIS?

No. Starch reads from Greenhouse and Paylocity — it doesn't replace them. Recruiters still work in Greenhouse; HR still manages employee records in Paylocity. What Starch adds is the finance-facing surface: a tracker that maps open reqs to cost centers, flags start-date slippage, and feeds your cash model — the layer that neither your ATS nor your HRIS was built to provide.

QuickBooks report views aren't working — will my cost center data be affected?

The QuickBooks issue is limited to report-style views (P&L summary, Transaction List, Vendor Expenses). Entity-level data — including journal entries and department-level data that maps to cost centers — syncs normally. Your headcount-to-cost-center reconciliation will work. If you rely on a QuickBooks P&L pull for the payroll variance comparison, use the NetSuite scheduled sync instead, or pull the payroll actuals from Paylocity directly.