Sizing Device Needs When a Team Grows Quickly

Fast-growing organisations face two equally expensive mistakes. Too few devices leaves new hires idle in their first week, while too many means paying for units nobody uses for months.

This article covers how to size between the two, using an approach that works without lengthy historical data.

Start from the Hiring Plan, Not Current Headcount

Device requirements follow employee start dates rather than current headcount. So the starting point is the hiring plan by month, not a total figure.

What must be added to that plan is procurement lead time. If devices need several days to be ready for use, the requirement must be met before the start date rather than on it.

Account too for the fact that hiring plans are rarely exact. Some roles fill later, some earlier, and some are cancelled. This is why contracts allowing incremental additions suit growing organisations better than procuring everything upfront.

Sizing a Sensible Buffer

Beyond per-person requirements sits a buffer requirement that frequently escapes the calculation.

Buffer for replacement when units fail. Without it, every fault means one person stops working until a replacement arrives.

Buffer for sudden needs: new hires starting earlier than planned, short-term consultants, or training sessions requiring several units at once.

Buffer for turnover. Employees leaving and joining rarely coincide, creating periods of idle units and periods of shortage.

How large a buffer is sensible depends on fleet size and how quickly replacements can arrive. That discussion sits in our spare units article.

Separating Permanent from Temporary Needs

A common mistake is treating every requirement with one contract type.

Permanent needs are devices for standing roles that will continue to exist. These suit longer contracts where the monthly rate is lower.

Temporary needs are devices for fixed-duration projects, consultants, seasonal interns, or training. Forcing a long contract onto these means paying for units that sit idle once the need ends.

Separating the two from the outset is usually cheaper than standardising everything, even though per-unit rates on short contracts are higher.

Building a Simple Forecast

For the next three months, calculate requirements with fairly tight increments following the hiring plan, since this range is usually reasonably certain.

For the following three to twelve months, use a range rather than a single figure. A lower estimate for near-certain needs, an upper estimate for the fastest growth scenario.

Share that range with your provider when structuring the contract. A provider aware of your growth plan can prepare unit availability in a consistent configuration, and that consistency is what keeps fleet management simple.

Maintaining Consistency While Adding

Adding units incrementally carries a risk that is rarely recognised: additional units arriving in a different configuration from the original fleet.

That difference adds preparation work, complicates support, and sometimes renders accessories incompatible. State from the outset that additional units must follow the same configuration, and confirm availability across the growth period you are planning for.

Accounting for Lead Time That Gets Forgotten

Device requirements do not appear on an employee's start date but several days earlier, and that gap is frequently omitted from planning.

Several stages consume time before a unit is ready. The unit must arrive from the provider. Standard company configuration must be installed. Network and management system enrolment must complete. The user account must be prepared.

For organisations using a standard system image, the configuration stage moves quickly. For those building every unit from scratch, this stage can take considerably longer and is the primary reason new hires sit idle in their first week.

Count backwards from the start date rather than forwards from the order date. That approach immediately shows when ordering must happen.

For hiring whose schedule frequently shifts, ordering against the lower estimate and adding incrementally is safer than ordering against the most optimistic scenario.

Maintaining Consistency as the Fleet Grows

Adding units incrementally carries a risk only felt months later: additional units arriving in a configuration not precisely matching the original fleet.

These small differences generate repeated work. System images need retesting, troubleshooting procedures branch, and accessories sometimes no longer fit.

State during contract negotiation that additional units must follow the same configuration, and confirm availability across the entire growth period you are planning. This is a primary reason to choose lines with long availability cycles.

If a provider cannot guarantee identical configuration over a long period, it is better to know at the outset and plan two configuration tiers deliberately than to find the fleet fragmented by accident. This is covered in our uniform system image article.

Reviewing Forecasts Periodically

A requirement forecast built once at the start of the year will miss, and that is normal. What matters is how often it is reviewed.

Compare forecast against actual every few months. If hiring consistently runs slower than planned, adjust the next forecast rather than continuing with the original figure.

Watch turnover too, not only additions. Units returning from departing employees can be reissued to new hires, reducing the need for additional units.

Review whether configuration mapping still fits. Teams whose working patterns have shifted may need a different configuration tier from the one originally planned.

Share these reviews with your provider. A provider aware of your growth direction can prepare unit availability far better than one receiving only sudden orders.

Frequently Asked Questions

Is it better to rent everything at once or incrementally?

For confirmed requirements, all at once usually secures better rates. For requirements dependent on a hiring plan, incremental avoids paying for idle units.

What if growth runs slower than planned?

A contract permitting incremental additions keeps that risk small, because you only add when the need is real.

Does fleet configuration need to be uniform?

Strongly recommended, with at most two configuration tiers. Beyond that, preparation and support become difficult without proportionate benefit.

In Short

A useful forecast need not be accurate, only early enough and honest about its uncertainty. What matters most is separating permanent from temporary needs, and ensuring additional units stay consistent with the existing fleet.

References & Sources

The asset records behind any headcount-based calculation follow CIS Control 1: Inventory and Control of Enterprise Assets (accessed 24 September 2026). For keeping configuration uniform as the fleet grows, see the CIS Benchmarks (accessed 24 September 2026).