Headcount Planning Tool

Model headcount scenarios and their cost the moment a team lead asks. Joy reads your current roster and comp data read-only and returns each scenario's roles, fully-loaded annual cost, and budget impact in the same conversation.

For Finance & FP&A Partners HR Business Partners People Ops Leaders Department Heads
Sample prompt to Joy's Assistant

Using our current roster and comp data, model [a few headcount scenarios] for [our team] next year: for each, show the roles added, the fully-loaded annual cost, when they'd start, and the budget impact.

What it can look like

An illustrative example. Your output will reflect your own sources, data, and prompts.

Using our current roster and comp data, model three headcount scenarios for our Customer Success team next year: for each, show the roles added, the fully-loaded annual cost, when they'd start, and the budget impact.

I read your current Customer Success roster and comp bands read-only, then modeled three ways to grow the team next year against those numbers. Each scenario below shows the roles added, the fully-loaded annual cost, and what it does to the team budget.

Customer Success headcount scenarios: next year

Reading your current Customer Success roster and comp bands, the team is 24 people at roughly $3.5M of fully-loaded cost today. I modeled three ways to grow it next year. The middle scenario, five hires phased across the year, is the one that matches the account growth in your plan, so its headline numbers are up top.

5 roles
Added in Scenario B
+$700k
Incremental annual cost
20%
Of the team's budget

Here is how the three scenarios compare on total incremental cost for the year.

Incremental annual cost by scenario

A · Hold & specialize$280k
B · Scale for growth$700k
C · Scale + leadership$1.19M

The full model, with the roles and timing behind each number, is below. Fully-loaded costs come from your comp bands: about $140k for a CSM, $150k for a support engineer, $130k for a CS ops analyst, and $185k for a team lead.

ScenarioRoles addedFully-loaded costTimingBudget impact
A · Hold & specialize2 CSMs$280kBoth by Q2+8%
B · Scale for growth3 CSMs, 1 support engineer, 1 CS ops analyst$700kPhased Q1–Q4+20%
C · Scale + leadership5 CSMs, 2 support engineers, 1 team lead$1.19MPhased Q1–Q4+34%

Budget impact. Scenario B adds $700k, taking the team's fully-loaded cost from $3.5M to $4.2M, a 20% increase. Scenario A is the safe hold at +8%, and Scenario C's +34% only pencils out if the enterprise pipeline in your plan lands in full.

Break-even. At your current load of roughly 12 accounts per CSM, Scenario B's five hires give the team room for about 60 more accounts, which covers the new-logo growth your revenue plan adds next year. If net retention holds where it landed last year, that added book offsets the $700k inside the first three quarters; below that retention line, payback slips into the following year.

This is a model read from your current roster and comp data, not a change to anything, nothing here touches the HRIS or moves a requisition. Tell me to shift the mix, move a start date, or add a fourth scenario and I will re-run the costs so the totals stay tied out.

Want me to phase Scenario B across the four quarters, or model a fourth scenario that caps the increase at 15% of budget?

From a hiring idea to a costed model

Headcount Planning Tool turns your roster and comp data into an on-demand scenario model. This isn't a dashboard you keep running. Each time you ask, the JoySuite assistant Joy reads the current roster and comp bands read-only, applies your loading rates, and shows each scenario's added roles, fully-loaded annual cost, and what it does to the team budget.

  1. Connect your roster and comp data

    Link your HRIS and comp source once. Joy reads them read-only, and only when you ask: current headcount by team, salary bands, and the benefits, tax, and overhead rates that make a number fully loaded.

  2. Describe the scenarios

    Tell Joy the team and the options to model: how many roles, which levels, and roughly when they'd start. Add constraints up front if you have them, like a budget ceiling or a fixed start quarter.

  3. Review the model

    Get each scenario side by side with the roles added, the fully-loaded annual cost, the timing, and the percentage it adds to the team budget, plus a short read on break-even.

  4. Use it where you work

    Ask follow-ups like "phase the middle scenario by quarter" or "cap the increase at 15%," then copy the model into a budget review or a planning doc. Joy never changes headcount or writes to the HRIS.

  5. Make it one click for your team

    Save this ask as a custom command on the assistant your team already uses, so anyone can run it in one step.

Make it yours

Fully-Loaded Costing

Every role is priced with salary, benefits, tax, and overhead from your own loading rates, so the number is the real number, not just base pay.

Scenario Comparison

See two, three, or more options side by side on cost, timing, and budget impact, so the trade-off is obvious before anyone commits.

Budget-Anchored

Each scenario is shown as a percentage of the team's current budget, so you know what it does to the plan, not just what it costs in isolation.

Instant Re-Model

Change the mix, a level, or a start date and Joy re-runs the fully-loaded cost and the totals in the same chat.

Phase by Quarter

Spread a scenario's hires across the year to see how the cost lands quarter by quarter instead of as one annual figure.

Cost of Delay

Model what pushing a hire a quarter later saves now and what the delayed coverage costs the team.

Attrition-Adjusted

Net expected departures against the plan so the model shows the true change in headcount, not just the gross adds.

Cap to Budget

Set a ceiling and ask for the strongest hiring mix that fits inside it, ranked by impact.

Frequently Asked Questions

How does the tool calculate fully-loaded cost?

It starts from the base salary in your comp bands, then applies your own benefits, tax, and overhead rates to reach a fully-loaded figure. Because the multipliers are yours, the number reflects what a role actually costs your organization, not a generic industry markup.

Does JoySuite change our headcount or HRIS?

No. Joy reads your roster and comp data read-only and models the scenarios in the conversation. It never opens a requisition, changes headcount, or writes anything back. You review the model and act in your own systems.

Where do the cost figures come from?

From the roster and comp data your organization connects to JoySuite. Joy reads current headcount and salary bands at the moment you ask, so the model reflects the figures as they stand today rather than a saved snapshot.

Can I model my own scenarios?

Yes. Describe the roles, levels, and rough start dates you want to compare, and Joy builds each scenario. Change the mix or a constraint as a follow-up and it re-runs the fully-loaded cost and budget impact in the same chat.

Is this a dashboard I have to keep running?

No. There is nothing running in the background. Each time you ask, Joy reads the latest roster and comp data and returns the model on demand, so there is no dashboard to build, refresh, or maintain.

Ready to cost the plan before it's approved?

Join the waitlist and be first to try this workflow when JoySuite launches.