← People analytics

People analytics · models & decisions

Employee lifetime value: a scenario model

Explore onboarding, development and retention scenarios without assigning a price to a person.

Practitioner concept associated with Maia Josebachvili; ADM HR costed illustration · 2016-era practitioner development · 2026 illustration · Original editorial explanation
Employee lifetime value: a scenario model — simplified model sketchRecruit & onboard · Build competence · Contribute & develop · Exit / transition. Editorial interpretation, after Practitioner concept associated with Maia Josebachvili; ADM HR costed illustration (2016-era practitioner development · 2026 illustration).Recruit &onboardBuildcompetenceContribute &developExit /transitionScenario assumptions, not a person’s priceADM HR · ORIGINAL INTERPRETATIONPractitioner concept associated with Maia Josebachvili; ADM HR costed illustration · 2016-era practitioner development · 2026 illustration
Original simplified sketch after Practitioner concept associated with Maia Josebachvili; ADM HR costed illustration (2016-era practitioner development · 2026 illustration). Read the explanation for assumptions and limitations. Download SVG ↗

The core idea

Employee lifetime value is a practitioner planning concept for considering contribution and cost across an employment journey. Maia Josebachvili helped popularise it in people-operations discussions. There is no single universally standardised formula. An explicit scenario can include recruitment, ramp-up, ongoing contribution, development and transition costs, with a stated time horizon. It should be treated as a model of assumptions about roles or cohorts, not a monetary judgement of a person’s worth.

Source and attribution [1]

Using it in practice

Choose a planning question, such as whether better onboarding could shorten time to competence. Define contribution carefully and distinguish it from revenue already supported by capital, colleagues and other costs. Set a horizon and test plausible scenarios for retention and development. Keep costs from being counted twice. Present ranges and the assumptions most responsible for the result.

An example, not a reported case

Worked example · illustrative

For an invented role cohort, assume a £2,000 joining cost, net contribution after ongoing employment costs of £500 in each of the first three months, then £1,500 in each of the next nine, and a £1,000 transition cost. The undiscounted 12-month scenario is −2,000 + 1,500 + 13,500 −1,000 = £12,000. It is an illustrative scenario, not an estimate for a real employee or a promise that retention produces this amount.

What to watch for

Contribution is often difficult to isolate in team-based work. Long horizons amplify uncertain assumptions, and retaining someone is not automatically beneficial in every circumstance. Do not use the model to ration fair treatment or predict an individual’s worth. Where long-term cash flows are material, finance should help with timing and discounting; this example deliberately uses a short undiscounted horizon.

Separate assumptions from observations

Mark which inputs come from records and which are estimates. Time to competence might be observed; future contribution may be speculative. Show both rather than letting a spreadsheet’s precision hide the distinction.

Test the intervention mechanism

If the proposal is better onboarding, specify how it changes ramp-up or avoidable rework. Do not simply increase every positive input at once. Compare the intervention with a plausible alternative and include its implementation cost.

Avoid double-counting

If net contribution already subtracts salary and benefits, do not subtract them again. If replacement cost includes lost output, avoid adding the same loss separately. Document the cost boundary so another person can reproduce the calculation.

Use a range and a decision rule

Vary the assumptions that could change the conclusion, such as ramp-up time or retention duration. Ask what evidence would justify proceeding or revising the plan. The useful output is a transparent decision discussion, not a precise-looking valuation assigned to an employee.

Treat the curve as an investment hypothesis

Define the role, time horizon and what contribution means before attaching money to it. Include recruitment, onboarding, development and exit assumptions, but distinguish measured costs from speculative benefits. For many roles, contribution is shared and difficult to separate. The model can help ask whether better onboarding or retention is worthwhile; it should not be used to assign a financial worth to a person or to rank their entitlement to support.

Explore time to competence

An illustrative improvement that shortens supported learning from twelve weeks to ten may create value, but only if competence and quality are maintained. Examine who provides the support and whether their time changes too. Do not count both an assumed productivity gain and the same saved supervision time twice. Use a clear comparison and show the operational evidence behind the assumption rather than drawing a smooth curve with no measured basis.

Use scenarios instead of a single forecast

Compare plausible retention periods, development costs and contribution assumptions. Ask which assumption drives the result and whether a realistic change reverses the conclusion. Include the possibility that the intervention does not work as expected. A range communicates uncertainty more honestly than a precise lifetime estimate. Keep benefits that cannot credibly be monetised visible as separate outcomes rather than inventing a monetary value merely to complete the calculation.

Consider the ethical consequences

An investment model can unintentionally encourage neglect of roles or people assigned a lower estimated return. Establish fair access to development and support independently of such estimates. Review whether the analysis values short-term output while overlooking cooperation, knowledge sharing or service continuity. The practical question is how to design better employment experiences and organisational capability, not how to identify people supposedly worth more than others.

Keep the unit of analysis and assumptions visible

A planning estimate may consider recruitment cost, time to proficiency, expected contribution and likely tenure, but these inputs are uncertain and interdependent. Define whether the analysis concerns a role, a cohort or a programme. Use ranges for ramp-up time and retention rather than one apparently precise number. Distinguish observed data from assumptions and avoid double-counting replacement costs or benefits already included elsewhere in the model.

Use the estimate to compare interventions, not people’s worth

An onboarding improvement might shorten time to competence, while better scheduling might improve retention. Compare plausible scenarios and include the cost of implementation and manager time. Check whether an apparent gain depends on unrealistic retention or contribution assumptions. The concept can support investment planning, but it should not become an individual label or a justification for neglecting people in roles assigned lower financial values. Explain non-financial benefits and uncertainty alongside any monetary estimate.

Take it into your next conversation

Three useful questions.

  1. Which decision will this analysis change?
  2. Are the population, denominator, time period and assumptions explicit?
  3. What alternative explanation or unintended effect must we check?

Related terms

Go to the evidence

Sources & attribution

Further reading: Nadeem Khan and Dave Millner (2023), Introduction to People Analytics: A practical guide to data-driven HR, 2nd edition, PDF pp. 227, 244 and 294–295. Edition & reading notes ↗

[1] Greenhouse: The impact of people operations on employee lifetime value ↗

The core idea is an original summary of the cited work. Application notes, examples and sketches are our interpretations, not quotations or reproductions of the authors’ figures. Publisher records may require access to read the full original work.

Explore People Analytics →

Application guidance expanded on 26 September 2026. These practical suggestions and invented examples are editorial explanations; further-reading sources are not the original authors of the historical models unless expressly identified. Original overview review dates are retained.

Published 2026-09-20 · Reviewed 2026-09-22. Editorial approach

Keep exploring

A little more context.

People analytics · models & decisions01

Human capital ROI: formula and interpretation

Calculate a broad workforce-cost ratio and understand why it is not an individual employee valuation.

Workforce financial-metrics tradition associated with Jac Fitz-enz6 min
People analytics · models & decisions02

Employee-lifecycle analytics

Follow attraction, recruitment, onboarding, development, performance, retention and exit with consistent definitions.

Common HR practice framework6 min