EIGENN.
docsguidesapichangelogpricingsign in
EIGENN.

Headcount Planning

Plan hires and salaries month by month, and see the payroll and overhead costs that follow.

This guide builds a monthly headcount plan in Scenario planning. At the end, you know how many people you employ each month, what they cost, and how the cost changes when you hire. The guide is for founders, finance leads, and department heads who own a hiring budget.

Time: about 15 minutes

Headcount Planning: create a Headcount plan from a template, enter hires, and open Scenarios to test a delay

Before you start

  • Use an Owner or Member role. A Viewer can open models but cannot change them.
  • Collect your current headcount, your planned hires by month, and the salaries.
  • Know your rate for payroll taxes, benefits, and overheads, as a percentage of salary.

Choose the template that matches the detail you need:

TemplateUse it whenBreakdown
Headcount planOne hiring rate and one average salary are enough.None
Headcount by DepartmentEach team hires and pays at a different level.Department: Engineering, Sales, Marketing, G&A
Advanced HeadcountYou plan person by person, with raises and bonuses.Employee: Alice, Bob, Carol, Dana

All three templates start with example figures. Replace them with your own.

1. Create the model

  1. Go to Scenario planning → click New model. You can also click Quick start.
  2. In the Create model search box, type headcount. The Templates group shows the matching templates.
  3. Select a headcount template and press Enter.

Eigenn creates the model, gives it the template name, and opens the grid. The model has 12 monthly periods. The first period is the current month.

The Create model window with headcount in the search box. Templates lists Headcount + Hiring Plan marked Coming soon, then Headcount plan, Headcount by Department, and Advanced Headcount.

2. Read the formulas

Each template puts the assumptions in the Inputs section. The formulas below the inputs calculate the cost. Read them before you change a value.

Headcount plan has three inputs: Starting headcount, Monthly hires, and Average annual salary. The Plan section calculates:

VariableFormula
Headcountif Headcount[previous] = blank then Starting headcount + Monthly hires else Headcount[previous] + Monthly hires
Monthly payroll costHeadcount * Average annual salary / 12

The first period has no previous value, so it starts from Starting headcount. With the example inputs (10 people, 2 hires, 120,000 salary), month 1 has 12 people and costs 120,000. Month 12 has 34 people and costs 340,000.

Headcount by Department has the inputs Headcount, Average annual salary, and Taxes and overheads. The Payroll section calculates Base payroll as Headcount * Average annual salary / 12. Then it calculates Fully-loaded payroll as Base payroll * (1 + Taxes and overheads). Each department calculates its own payroll, and the total row adds the departments. With the example figures and 25% overheads, one month looks like this:

DepartmentHeadcountAverage annual salaryFully-loaded payroll
Engineering12150,000187,500
Sales8120,000100,000
Marketing5110,00057,292
G&A4130,00054,167
Total29127,500398,958

The total row of Average annual salary shows the average of the departments, not the sum. Cost per head in the Summary section divides the total Fully-loaded payroll by the total Headcount. In this example, the result is about 13,757.

Advanced Headcount gives each employee an Annual salary and an Annual bonus. Annual raise and Taxes and overheads apply to the whole company. The Payroll and Summary sections calculate:

VariableFormula
Monthly salaryAnnual salary * (1 + Annual raise * timestep / 12) / 12
Fully-loaded cost(Monthly salary + Annual bonus / 12) * (1 + Taxes and overheads)
Annual run rateFully-loaded cost * 12

timestep counts the periods from 0. The salary goes up a little each month. In month 12, timestep is 11. The monthly salary is then higher than the start value by 11/12 of the annual raise.

3. Enter your own figures

  1. Click Expand all in the grid header. Each variable with a breakdown shows one row per department or employee.
  2. Select a cell in an input row.
  3. Type the value and press Enter.

Each period holds its own value. To plan hires in a given month, enter the number in that month of Monthly hires. Enter 0 in the months without hires. In Headcount by Department, enter the planned headcount of each department for each month.

After you change one input, make sure that Monthly payroll cost, Fully-loaded payroll, or Fully-loaded cost moves in the expected direction.

4. Add a department or an employee

  1. In the model toolbar, click More → Dimensions.
  2. Select Department or Employee.
  3. Under Items, type the name in Add an item.
  4. Click the + button (Add dimension item).

Each name must be unique in the dimension. Eigenn adds a row for the new item under each variable that uses the dimension. Enter the values for the new item in those rows.

To rename an example item, such as Alice, type the new name in its row. Then click its save (pencil) button.

5. Test a hiring delay

  1. In the model toolbar, click Scenarios.
  2. Click the + button (Create scenario).
  3. Type a Scenario name, such as Hiring delayed to Q2.
  4. Click Save scenario.
  5. Open Scenarios and select the new scenario.
  6. Set Monthly hires to 0 in the months that you delay.

The change applies to the scenario only. The base plan does not change. To compare the two cases, click Model settings → Scenarios. In Compare scenarios, select a Period and read the difference in payroll cost.

Model settings Scenarios panel. Compare scenarios shows Base and a Revenue decline 20% scenario for the Aug '27 period.

A Headcount plan model with the Scenarios menu open. The menu shows the + button and the Base scenario marked Default. The grid shows Headcount 12, 14, and 16 and Monthly payroll cost 120,000, 140,000, and 160,000 from Oct '26.

6. Use the payroll in another model

A headcount model can supply the payroll cost to an operating plan.

  1. Open the operating plan model.
  2. Click More → Linking.
  3. In Select a model, choose the headcount model.
  4. Click Add source.

Then reference the payroll variable as Model.Variable in Formula Explorer.

Related

  • Dimensions
  • Formulas
  • Scenarios
  • Planning Models and Formulas
  • Compare and Share Planning Scenarios
  • Stress Tests: the Headcount change lever on the cash forecast
  • Consolidation

First Cash Review

Check cash inputs, triage the finance overview, and test one decision about the future.

Invoice Collection Workflow

Move from a receivables signal to a checked invoice action, a recovery sequence, and an updated cash expectation.

On this page

Before you start1. Create the model2. Read the formulas3. Enter your own figures4. Add a department or an employee5. Test a hiring delay6. Use the payroll in another modelRelated

Eigenn docs

current product

Overview
Overview
OverviewAccount PreferencesApproval PoliciesAssistant AutomationAssistant Command CenterAssistant Workspace and Saved WorkBank ConnectionsBilling and UsageBudgets and ForecastCommand CenterCustomer FieldsCustomer LifecycleCustomer RecordsCustomersDeveloper PlatformDocument Processing and ExtractionFiles and Document VaultFinancial Analytics and ReportsFinancial OverviewInbox and ApprovalsInvoice InsightsInvoice ProductsInvoicesMarketplace IntegrationsNotifications and BrandingOnboarding and SupportOverviewPlanning Data and DimensionsPlanning Models and FormulasPlanning Time and ActualsPlanning UncertaintyPlanning Versions and CollaborationPlanning Views and ExportsPlans and AdjustmentsReceivablesReceivables AnalyticsReceivables ControlsRolling Budget CloseScenario PlanningSecurity and AccessSettings OverviewStress TestsTeams and OrganizationsTone Profiles and ExperimentsTransaction Categories and RulesTransaction CodingTransactionsWeekly Finance RitualWorkflow ExecutionsWorkflow OutcomesWorkflow PausesWorkflows
OverviewBudget vs. ActualsBuild a Driver-Based Planning ModelBuild and Review a ForecastBuild Your First WorkflowCollaborate on a Planning ModelCompare and Share Planning ScenariosConfigure Approval PoliciesConfigure Assistant OperationsConfigure Customer FieldsConfigure Notifications and BrandingConfigure Planning Time and ActualsConfigure Receivables ControlsConnect Planning Data and ActualsConnect Transaction RecordsConsolidationCreate and Manage CustomersCreate and Send InvoicesCreate Your First Planning ModelDeveloper API SetupFirst Cash ReviewHeadcount PlanningInvoice Collection WorkflowMaintain Transaction RulesManage Security and BillingManage Team AccessManage the Invoice LifecycleMCP WorkflowsMonitor and Recover WorkflowsOrganize and Share DocumentsProcess Inbox ItemsReconcile and Categorize TransactionsRevenue ForecastingReview a Customer Finance RecordReview, Restore, and Export a Planning ModelRun a Finance Operating ReviewRun a Receivables Tone ExperimentRun a Runway Stress TestRun Planning Uncertainty AnalysisRun Your First Command Center ReviewSave and Share Assistant WorkSet Up a WorkspaceTroubleshoot Account AccessWebhook DeliveryWeekly CFO Review
Overview

Concepts

DataDimensionsFormulasScenarios

Variables

VariablesChange an input over timeCreate a variableFormat a variableOrganize variablesTime totalsUse a variable from another modelVariable types

Time

TimeLast actual dateRoll the model forwardTime granularityTime settings

Formulas

FormulasBlanks and helpersCommon formulas: cash and balance sheetCommon formulas: cohortsCommon formulas: currency and multiple entitiesCommon formulas: headcount and payrollCommon formulas: SaaS metricsCommon formulas: seasonalityConditionalsDimension referencesFormula syntaxFunctionsTime referencesTroubleshoot formulasValues with uncertaintyWrite a formula

Charts and Dashboards

Charts and dashboardsCompare scenarios and versionsCreate a chartExport and shareTablesTime aggregation in charts

Dimensions

DimensionsApply a dimensionCreate a dimensionDimension examplesDimension totalsThe Dimensions page

Data

DataChoose cash or accrual for XeroConnect a data sourceLink a variable to dataRefresh and check actualsUse transaction categories as actuals

Data Integrations

Data integrationsBank transactionsCSV importFortnoxQuickBooksStripeXero

Views

ViewsCreate and edit a viewFilter a viewShare a view

Versions

VersionsCompare versionsRestore a versionSave a version

Scenarios

ScenariosCompare scenariosCreate a scenarioPlans and adjustmentsStress tests and shocks

Collaboration

CollaborationComment on a modelShare a model and set accessTeam roles and planning access

Managing Models

Managing modelsDuplicate a modelExport a modelModel limits and performanceStart from a templateThe models home and foldersTrash, restore, and delete a model
OverviewIntegrationsMCPSDKsWebhooks
OverviewAuthenticationBank Accounts APICustomers APIErrorsForecasts and Stress Tests APIInvoice Payments APIInvoices APIPaginationRate LimitsRemote Tracker API StatusTracker Categories APITracker Entries and Timers APITracker Projects APITransactions APIWebhooks API StatusWorkflows API
Overview
Overview