How this calculator works
The classic workforce forecasting question — "how many agents do we need?" — has a deceptively simple math at the core. The complication isn't the formula. It's that most teams pick numbers out of the air for the inputs and then defend the forecast politically rather than analytically.
This calculator forces explicit inputs across the five drivers that actually matter:
Real-world impact
Illustrative scenarios drawn from operator practice. Numbers are realistic order-of-magnitude estimates, not measurements from any specific deployment.
Case 1: Finance asking for next year headcount in 5 days
SetupHead of Ops at a regional fintech needs to justify a 2026 plan covering 4 case types (KYC, fraud review, ATO, disputes) with different complexity and volume curves.
ProblemExisting spreadsheet model was 14 tabs of stale assumptions, last touched 8 months ago, produced a single headcount number with no scenario range, putting roughly $1.8M in payroll asks at risk of being slashed.
Tool surfacedMulti-case-type calculator separated AHT and volume per type, layered shrinkage (22% real vs 15% assumed) and peak month uplift, produced in-house vs vendor split economics side by side.
OutcomePlan went in with three scenarios (lean, base, peak-ready) and finance approved base case at 31 FTE plus 8 vendor seats, vs the original ask of 38 FTE that would have been rejected.
Case 2: 60% vendor-heavy footprint that was bleeding cost
SetupCOO at a high-growth ecommerce platform had 24 in-house and 36 vendor reviewers across two sites, locked into a per-case vendor rate set 3 years prior.
ProblemVendor cost per case had crept to roughly $4.20 vs in-house fully loaded $3.10 once productivity and shrinkage were applied honestly; the platform was spending an extra $360K per year on the worse option.
Tool surfacedVendor split scenario showed crossover point at 45% vendor, not 60%, given current AHT and shrinkage; rebalancing recovered the spread without losing peak flexibility.
Outcome12 cases per day shifted in-house, vendor headcount renegotiated to a smaller flex pool, net savings around $230K annualized in year one with peak coverage preserved.
The formula
total_minutes = Σ (volume_i × handle_time_i) // sum across case types
productive_min = productive_hours × 60 // per agent per day
base_FTE = total_minutes / productive_min
after_shrink = base_FTE / (1 − shrinkage) // PTO, training, sickness
after_peak = after_shrink × peak_ratio // peak vs avg day
final_HC = after_peak × (1 + sl_buffer) // service level cushion
What each input means
- Daily volume per case type — your forecasted demand. Different case types should be separate rows because they have different handle times. Aggregating to "total cases" hides the complexity mix that drives staffing.
- Avg handle time — minutes per case from open to close, including post-call wrap-up. Measure from your actual data, not the SLA target.
- Productive hours per agent — an 8-hour shift becomes ~6.5h after breaks, meetings, system time. This is the time an agent is actually available to take cases.
- Shrinkage — % of paid time agents aren't producing. Typical 25-30% for shift-based ops accounting for PTO, sick, training, attrition gaps.
- Peak / average ratio — your worst day vs average day. Staff for peak or your service level collapses on peak days. Typical 1.3-1.6 for steady-state operations, higher for event-driven ones.
- Service level buffer — extra capacity for forecast variance and ramp-up time on new hires. Typical 10-20%.
The vendor split decision
For most operations, a hybrid in-house/vendor model is more cost-efficient than pure in-house, but only for the right case types. The general rule:
- High-volume, low-complexity cases (clear approvals, clear declines, simple resolutions) → vendor handles end-to-end with defined SLA
- Gray-zone, judgment-heavy cases → in-house team owns
- High-stakes / regulatory escalation cases → in-house, often senior tier
The split calculator above assumes 60% of total volume can go to vendor at the vendor cost rate, and 40% needs in-house. Adjust those assumptions to your operation — they vary a lot by industry, case type, and your vendor capabilities.
What this calculator is NOT
- It's not a substitute for an actual workforce management (WFM) system. Real WFM platforms (Verint, NICE, Calabrio) model intraday scheduling, skill-based routing, real-time adherence. This is the spreadsheet-level capacity calculation that feeds into WFM, not WFM itself.
- It doesn't model attrition, hiring lead time, training time for new hires, or seasonality beyond the peak ratio. For multi-quarter planning, those matter.
- It assumes linear productivity. In reality, agents get more efficient with tenure (and less efficient if overworked). Real-world variance is wider than the buffer accounts for.