Integrations

One card per source category, data flows in from anywhere.

View all integrations →

The Agentic Layer

The governed foundation — platform capabilities.

Reporting & Analysis

Business performance tracking, variance, and analytical insight.

See all →

Planning & Modeling

A comprehensive look at forward-looking corporate financial strategy.

See all →

Consolidation & Close

The entire financial close and data management cycle, at a high level.

See all →
Planning & modeling

Headcount planning tied to the P&L.

Plan every role, start date, and fully loaded cost in one governed model. Your HRIS, payroll, and GL reconcile automatically, department heads work in their own view, and every figure traces to the employee record behind it.

HRISEmployees
RecruitingOpen roles
ERP / GLActuals
BenefitsRate +4%
CubeHeadcount forecast
260 people+12 net new hires
Engineering142 → 150
Sales64 → 68
G&A42 → 42
Open roles, start dates Jul–Sep
ActualsForecast →
Behind every role
Headcount=Base salary $12.35M+ Benefits $1.22M+ Payroll taxes $0.71M+ Equipment $0.46M
Thousands of finance professionals, in every industry, run on Cube
The problem

The headcount plan is never the same in HR and finance.

HR tracks roles in the HRIS, finance tracks cost in a spreadsheet, and every month someone reconciles the two by hand while open roles go unbudgeted.

Headcount_plan_v7_HR_edits.xlsxHRIS export from three weeks agoPayroll ≠ plan by $312K

Systems disagree

Roles live in the HRIS, cost lives in payroll and the GL, and the employee counts drift apart every month.

The roster is stale

The plan rests on an HRIS export that missed this month’s hires, exits, and transfers.

Cost is understated

Salary goes in the plan, but benefits, taxes, and equipment are estimated, so the real cost of a hire lands as a variance.

The solution

One headcount plan for HR and finance.

Cube connects the HRIS to the plan, so the roster, open roles, and fully loaded cost stay current for both teams.

Systems disagree

One roster, both teams

HRIS data syncs into Cube, so HR and finance plan from the same list.

The roster is stale

Updates on their own

New hires, exits, and transfers flow in on a schedule.

Cost is understated

Fully loaded cost

Benefits, taxes, and ramp apply by role, so cost reflects reality.

Why teams choose Cube

One headcount number HR and finance both trust.

HR and finance agree

The HRIS, payroll, and the GL map to one governed model, so counts and cost reconcile every month.

Timing that adds up

Start dates, ramp, and attrition drive cost by month, so a delayed hire shows up in the plan right away.

Fully loaded, every time

Salary, benefits, taxes, and equipment roll up per role, with an audit trail on every change.

Every headcount number opens.

A department head asks why their cost is over plan. In Cube, every figure traces to the roles, start dates, and payroll lines behind it.

A glass revenue bar opening into threads that lead to individual transactions
Drilldown
Engineering cost · March$1,215.0K
Existing employees$612.0K
New hires$398.0K
Jul 06Senior engineer · started Mar 3$184.0K
Jul 08Product designer · started Mar 17$96.5K
Jul 09Data analyst · offer accepted$72.0K
+ 9 more roles · Workday
Source: Workday, ADP
Workflows

Where teams put the headcount plan to work.

Hiring plan by department

Every role, start date, and cost, owned by the leader who needs it.

Department budgets

Each leader’s roles and cost, rolled up to the company plan.

Board headcount reporting

Headcount and cost per department in the deck, from the governed model.

Hiring scenarios

A freeze or an acceleration, recalculated across the P&L and cash.

Sales capacity planning

Rep headcount, ramp, and quota tied to the bookings target.

Compensation planning

Merit increases, bonuses, and commissions modeled by role and cycle.

One connection

Headcount planning on live actuals.

Cube connects your HRIS, payroll, and GL, three of the hundreds of source systems it speaks to, so HR and finance plan from the same roster.

Your sources
Where it shows up
NetSuite
Payroll actuals in the GL
HRIS
Open roles and offers
Workday
Employees and comp
ADP
Payroll, taxes and benefits
Hiring plan
Roles, timing and cost
Department budgets
Owned by each leader
Board deck
One headcount number

One governed model that turns workforce signals into operating intelligence. Roles, comp, and payroll are mapped once, reconciled, and traced to the employee record.

Mapped onceReconciled to the GL

The headcount plan that updates itself.

Employees land from Workday, payroll from ADP, and actuals from NetSuite. Cube runs the governed formulas behind every cell, and the plan publishes back to the model.

Behind every cellGoverned formula
Fully loaded cost =
Base salaryWorkday HCM
+ BenefitsPlan rates · Workday, ADP
+ Payroll taxesEmployer tax rates · ADP
+ EquipmentPer-hire policy · Cube model
Monthly cost = Σ roles × (salary + benefits + taxes) × months active from start date
See a headcount plan using your numbers
Bring one department’s hiring plan. On the demo, we load it live and trace one cost to the role behind it.
Where you work

One headcount plan, on every surface.

Cube connects the systems where your data lives to the tools where decisions happen. When a number changes in Cube, it updates in the spreadsheet, the board deck, the dashboard, and the answer in Slack or Claude. Everyone keeps their own view and permissions, and every figure traces back to the transaction.

See it on your numbers.
On the demo, we connect a source, publish a number once, and show it land in a spreadsheet, a deck, and chat.
AI Agents

Your digital finance team works while you sleep.

Four FP&Agents handle the always-on work across your data, reports, plans and business partners. Agents scale finance's capacity, while the people remain in control.

Before your first coffee
6:00 AM Actuals synced into your Excel model.
6:04 AM March bookings variance explained in #sales-leads.
6:10 AM Board deck refreshed with the latest numbers.
6:15 AM Q3 forecast rerun on new pipeline data.
9:00 AM CEO asks in Teams what changed. Answered.
Security & governance

Board-ready means audit-ready.

Delivering numbers everywhere only works if access travels with them. In Cube it does, enforced in the layer rather than in each tool.

Security & compliance
Every export, governed.

Every AI feature respects your permissions, and every edit, sync, and publish lands in one audit trail.

SOC 1 & 2
Type 2
Certified
HIPAA
Compliant
Certified
Every edit
Tracked
To the source
Role-based access
CFO, VP and auditor views from one source.
CFO
VP Sales
Permissions on every view
User-level access wherever your numbers show up.
Viewing as David
Marketing$1.24M
Sales
Full audit trail
Who, what, when, before and after.
Maya edited Q3 rent2:14 PM
David approved forecast2:31 PM
SSO
Okta, Microsoft Entra, Google.
Single sign-on enabled

See a headcount plan using your numbers.

Turn workforce signals into action. Bring one department: we connect the sources, build the plan live, and trace a cost to the role behind it.

FAQs

Headcount planning questions, answered.

What is headcount planning?

Headcount planning is the process of deciding how many people the business needs, in which roles, when they start, and what they cost. In Cube, the plan connects to your HRIS, payroll, and GL, so every role carries its fully loaded cost into the P&L.

What is the difference between headcount planning and workforce planning?

Headcount planning focuses on the number of roles, their timing, and their cost. Workforce planning is broader and also covers skills, structure, and long-term talent needs. Cube handles the financial side of both in one governed model tied to the P&L.

How do you automate headcount planning?

Connect the plan directly to your HRIS, ATS, and payroll so hires, exits, and comp changes load on a schedule instead of through exports. Cube calculates fully loaded cost by role and month, and recalculates as soon as actuals land.

What is the best headcount planning software?

The best headcount planning software connects HRIS, payroll, and GL data in one model, calculates fully loaded cost by role and start date, supports hiring scenarios, controls access to salary data, and traces every figure to the employee record. Cube does this as the Agentic FP&A Platform, in the spreadsheets, decks, and chat tools your team already uses. 

What should you look for in headcount planning software?

Look for live connections to your HRIS, ATS, payroll, and ERP; fully loaded cost by role; start-date and ramp modeling; hiring scenarios; approval workflows for new roles; field-level access so salary data stays private; and audited security such as SOC 1 and SOC 2. Also check whether department heads can work in Excel or Google Sheets, since that decides adoption. 

How do you reconcile the HRIS with payroll and the GL?

Map employees, departments, and cost centers to one shared structure, then compare planned cost to payroll and GL actuals each month. Cube maps the HRIS, payroll, and the GL into one governed model, so a gap shows up with the roles that explain it.

What is fully loaded employee cost?

Fully loaded cost is the total cost of an employee: base salary plus benefits, employer payroll taxes, bonuses, commissions, equipment, and software. Cube calculates it per role and month, so every hire lands in the plan at its real cost.

What data do you need for headcount planning?

You need current employees and comp from the HRIS, open roles and offers from the ATS, payroll and benefits costs, and GL actuals by department. Cube connects to hundreds of source systems, including Workday, ADP, Greenhouse, and NetSuite.

How do you plan for attrition?

Apply an expected attrition rate by department, based on history, and plan backfills with realistic time to hire. In Cube, attrition is a visible driver you can adjust by scenario, and its effect flows through headcount, cost, and cash.

How often should a headcount plan be updated?

Most teams update headcount monthly, after payroll closes, and review hiring plans quarterly. With Cube, the HRIS and payroll sync on the schedule you set, the plan recalculates as soon as they land, and FP&Agents flag material changes overnight.

Can department heads see their own headcount plans?

Yes. Cube uses role-based permissions, so department heads see their own roles and totals while salary detail stays with HR and finance. They can check numbers in Cube Web, Excel, Google Sheets, Slack, or Teams, from the same governed source.

Does headcount planning software replace the HRIS?

No. Your HRIS and payroll remain the systems of record, and Cube works alongside them. Teams keep working in Excel or Google Sheets, with live, governed numbers from Cube flowing into their spreadsheets and edits publishing back to the model.

Is headcount planning software secure?

It should be audited and access-controlled. Cube is SOC 1 and SOC 2 Type 2 audited, with SSO and SAML support, role-based permissions, encryption in transit and at rest, and a full audit trail on every driver, mapping, and plan change.

Still have questions? See it on your own headcount data.
Start here

What is headcount planning?

Headcount planning decides how many people the business needs, in which roles and departments, when they start, and what they cost. It is usually the largest line in the operating budget.

HR owns the people and finance owns the cost, so the plan only works when both read from the same roster. Cube connects the HRIS, payroll, and GL in one governed model.

Top-down

Budget-based headcount planning

Start from a cost envelope and allocate roles to departments.

Bottom-up

Role-by-role planning

Each leader lists roles, start dates, and levels.

Rolling

Monthly headcount updates

Actual hires and exits replace the plan as they happen.

Scenario

Hiring scenarios

A freeze, an acceleration, or a reorg, modeled side by side.

Why headcount planning matters

People are most of the cost base, and hiring decisions are slow to reverse. A plan that captures fully loaded cost and real start dates shows the effect of every hire on the P&L and cash before the offer goes out, so leaders can hire with confidence.

How to build a headcount plan

The same five steps apply whether the plan lives in a spreadsheet or in Cube.

  1. 1.
    Start from the current roster. Load employees, departments, and comp from the HRIS, reconciled to payroll.
  2. 2.
    Set cost assumptions. Define benefits, taxes, equipment, and merit rates so every role is fully loaded.
  3. 3.
    Plan new roles. Have each leader add roles with level, location, and target start date.
  4. 4.
    Apply attrition and backfills. Use historical attrition by department and realistic time to hire.
  5. 5.
    Compare to actuals and roll forward. Each month, replace planned hires with actual ones, explain the variance, and extend the horizon.

Key headcount planning metrics

Fully loaded cost
Salary plus benefits, taxes, equipment, and variable pay.
Revenue per employee
Annual revenue divided by average headcount.
Attrition rate
The share of employees who leave in a period.
Time to hire
The days from opening a role to the start date.
Open roles
Approved positions not yet filled.
Span of control
The average number of direct reports per manager.

Headcount planning in a spreadsheet vs. Cube

Spreadsheet Cube
Answers Is this number current? Yes, synced from the HRIS and payroll.
Built from Exports pasted from the HRIS. Live connections to the HRIS, ATS, and payroll.
Cadence Manual, when someone has time. On the schedule you set.
Accuracy depends on Shared files and hidden tabs. Role-based permissions on salary data.
Numbers used Salary only, estimated extras. Fully loaded, by role and month.