Seasonal / Surge Cash Requirement

Why this comes up

Retail, agriculture, and light-industrial clients often need a predictable seasonal headcount spike, and the cash exposure that comes with staffing it up isn't at the peak headcount period, it's earlier, while payroll for a ramping crew is going out before collections have caught up. This engine finds the actual tightest point across the full ramp-up, peak, and ramp-down cycle.

How we calculated this

Headcount ramps linearly up over your ramp-up weeks, holds flat at peak headcount for your peak weeks, then ramps back down. Each week's payroll and billings scale with that week's headcount, then the same cash-timeline simulation used elsewhere on this site walks the cumulative position to find the trough.

Worked example: 2-week ramp-up to 20 peak workers, 8 weeks at peak, 2-week ramp-down, $800/head weekly payroll, $1,000/head weekly billings, a 3-week collection delay.

Week 0 (10 workers ramping): payroll $8,000, no receipts yet, cumulative -$8,000
Week 1 (20 workers, full peak): payroll $16,000, cumulative -$24,000
Week 2 (still ramping cash-wise): cumulative -$40,000
Week 3: first receipts arrive ($10,000 from week 0's billings), cumulative -$46,000 (the trough)
Weeks 4 onward: receipts catch up to the steady $20,000/week peak billings, cumulative recovers

Peak funding requirement: $46,000, at week 3, not at the headcount peak itself.

What this means

• The cash trough typically lands during the ramp-up or early peak, not at maximum headcount, because that's when payroll has grown but receipts from the earliest ramp weeks are still working through the collection delay.
• A longer collection delay pushes the trough deeper and later, since more weeks of payroll accumulate before the first receipt arrives.
• This funding requirement is temporary by nature, unlike steady-state working capital, but sizing it wrong at the peak is exactly as risky as sizing steady-state float wrong.

Common mistakes

• Sizing seasonal funding to peak headcount payroll alone, missing that the actual cash trough usually occurs earlier in the ramp, before receipts have caught up.
• Using a steady-state working capital estimate for what is actually a ramping, temporary surge with its own distinct cash profile.
• Not accounting for ramp-down properly; cash needs don't end the moment peak headcount is reached, receipts from the peak period still need to clear the collection delay after headcount starts winding down.

Frequently asked questions

Why does the trough happen before peak headcount?

Because payroll for a growing crew accumulates faster than receipts, which lag by the full collection delay. By the time headcount peaks, several weeks of payroll obligation have built up while only a few weeks of receipts have started arriving.

How is this different from a general working capital calculation?

General working capital (Payroll Float / Working Capital) assumes a steady state. This engine models a specific ramp-up, hold, ramp-down shape, which produces a different, usually deeper, trough during the transition periods.

What if my seasonal ramp isn't linear?

This engine assumes linear ramp-up and ramp-down. If your actual ramp shape is meaningfully different, use New Contract Cash Requirement's free-form period entry instead to model the exact shape.

Limitations

Assumes linear ramp-up and ramp-down and uniform per-head payroll and billings throughout; a seasonal surge with variable rates or a non-linear ramp shape needs a custom period-by-period model instead.

Next decision

• Compare against your steady-state working capital baseline

Learn more

Why Staffing Agencies Need So Much Working Capital — working capital in staffing is structural, and a seasonal surge is a sharper version of the same problem.