How to plan headcount with AI

People & HR3 AI tools7 steps6 friction points

Headcount planning is the process of mapping your people needs — current roles, open reqs, planned hires, and associated costs — against your business timeline. For most operators, it lives at the intersection of finance and people ops: you're trying to answer 'who do we need, when do we need them, and can we actually afford it?' It's not a once-a-year exercise; it gets revisited every time runway shifts, a key person leaves, or you're preparing a board update.

The reason AI feels like a natural fit here is that the workflow is heavy on synthesis and structuring judgment, not raw computation. You're pulling together salary benchmarks, role timelines, department priorities, and cash projections — then assembling them into a coherent plan that other people can act on. That's exactly the kind of messy, context-dependent work where a good language model can cut hours off the process by generating structure, surfacing tradeoffs, and drafting the narrative layer.

ChatGPT, Claude, and Gemini can genuinely help with headcount planning today — especially the thinking and structuring work. They're good at generating role-by-role cost breakdowns from data you paste in, drafting hiring timelines, stress-testing assumptions you describe in prose, and producing board-ready summaries. The limitation isn't intelligence; it's that none of them have access to your actual payroll data, bank balances, or existing org chart without you first exporting and pasting it in.

People & HR3 AI tools7 steps6 friction points
AI walkthrough

How to do it with AI today

A practical walkthrough using ChatGPT, Claude, and other off-the-shelf LLMs — what they're good at, what you'll have to do by hand.

Tools that work for this
ClaudeChatGPTGemini
Step-by-step
1 Export your current headcount from your HR system (Paylocity, ADP, Gusto, or even a spreadsheet) and your latest cash balance and monthly burn from your bank or accounting tool. This is your input layer — the models have no live connection to these systems, so you're starting with a manual pull.
2 Paste your current headcount data into Claude or ChatGPT with a prompt that asks it to calculate fully-loaded cost per role, total people spend, and cost as a percent of runway. Give it your current cash balance and net burn so it can do the math.
3 Describe your planned hires for the next 12 months — role title, target start quarter, estimated salary range, and which department. Ask the model to build a month-by-month headcount cost projection and flag which hires most materially affect runway.
4 Run a scenario comparison: ask the model to show you what headcount cost looks like if you hire to plan versus a 90-day-delayed version. Paste in both outputs so you can compare them side by side in a doc or spreadsheet.
5 Ask the model to draft the headcount section of a board update or all-hands memo — summarizing current team size, planned growth, cost trajectory, and any open risks. Claude tends to produce cleaner prose here; ChatGPT is useful for iterating on structure quickly.
6 Copy the model's outputs into a Google Sheet or Notion doc manually. There's no automatic handoff — you're doing the formatting, version control, and distribution yourself.
7 Next quarter, repeat from step one. Nothing from this session carries forward automatically; the model has no memory of last quarter's plan unless you paste it back in.
Prompts you can copy
Here is our current headcount by role and salary: [paste data]. We have $2.1M in the bank and $180K monthly net burn. Calculate total people spend, fully-loaded cost per role assuming 1.2x salary for benefits and taxes, and how many months of runway are consumed by payroll alone.
We plan to hire a Head of Engineering at $180K in Q2, two senior engineers at $150K each in Q3, and an account executive at $110K plus $50K OTE in Q4. Model our month-by-month headcount cost through end of year and flag which hire most compresses runway.
Compare two scenarios: Scenario A is hiring to the plan above. Scenario B delays all hires by one quarter. Show total headcount cost, runway consumed, and team size at the end of each quarter for both scenarios.
Draft the headcount section of a Series A board update. We have 12 FTEs, plan to reach 18 by year-end, people spend is 62% of total burn, and our next hire is a Head of Sales in Q2. Keep it to 150 words; lead with the strategic rationale for each planned role.
Here is our headcount plan from last quarter: [paste]. We ended up not hiring the two engineers we planned. Revise the model for the remaining three quarters assuming we hire them one quarter later than originally planned and salaries came in 8% higher than our estimate.
Reality check

Where this gets hard

The walkthrough above works — until your numbers change, the LLM hallucinates, or you have to re-paste everything next month.

No live connection to payroll or cash data — every run starts with a manual export and paste, which means your plan is already slightly stale before the model touches it.
Scenario comparisons don't persist — you get two blocks of text you have to manually format and place side by side; there's no living model that updates when your burn changes.
The model has no memory between sessions — next quarter you're re-pasting the entire context from scratch, including last quarter's plan, actuals, and any adjustments you agreed to.
Salary benchmarks are based on training data, not live market rates; if you're hiring in a competitive market or niche role, the model's estimates may be materially off without external sourcing.
Output format drifts across sessions — the clean table structure you prompted carefully in February looks different in May if you don't paste your exact formatting instructions back in every time.
There's no connection between your headcount model and your financial projections — if burn changes in your accounting system, the headcount plan doesn't update; you reconcile manually.

Tired of the friction?

Starch runs the whole workflow on live data — no copy-paste, no hallucinated numbers, no re-prompting next month.

See the Starch version →
Starch alternative

The same workflow on Starch

Starch is an agentic operating system — an agent builds the persistent software your headcount planning actually runs on, connected to your live payroll, banking, and financial data, so the plan reflects what's true today, not what you exported last week.

Connect Paylocity or ADP once — Starch syncs your employee roster, pay statements, and org units on a schedule, so your headcount cost figures reflect actual payroll data rather than a number you estimated from a spreadsheet.
The Runway Analysis app combines live Stripe revenue and Plaid bank feeds to show real net burn and cash projection — tell Starch to layer your planned hires on top and see exactly how each role affects your months of runway.
Use Scenario Analysis to model competing headcount plans side by side — hire to plan versus a delayed version, or a leaner org versus a fully staffed one — with your actual baseline revenue and burn already built in, not a number you typed.
Describe the headcount dashboard you want in plain English — 'show me current FTE count by department, monthly people spend, and a 12-month hire timeline against runway' — and the agent builds it as a persistent app that stays current as data refreshes.
Connect your accounting data from QuickBooks or NetSuite from Starch's integration catalog so your headcount model sits alongside your full P&L — no manual reconciliation between your people plan and your financial projections.
When it's time to present your headcount plan to the board, the Presentation Agent (coming soon) will build a polished slide deck directly from the data your Starch apps are already tracking — no Sunday night reformatting required.
Get closed-beta access →
Toolkit

Starch apps for this workflow

Pick your role

See this workflow by operator

Run plan headcount on Starch

You're on the list! We'll be in touch soon.