Budgeting for Equipment When Headcount Is Uncertain: A Practical Guide for HR Teams Asked for a Number They Cannot Know

By [Author Name] · [Date] · [X] min read · [Table of Contents]

TL;DR

• Equipment budgeting under uncertain headcount is the problem of pricing something whose quantity nobody knows.
• The mistake is giving a total. A total is wrong immediately and then defended for a year.
• Give a rate per hire instead, plus a separate figure for refresh, plus a stated assumption about leavers.
• Three approaches: a fixed total, a per-head rate, and a committed subscription.
• Choose based on how wide the hiring range is, not on how large the company is.
• Done well, hiring twenty people instead of twelve is an arithmetic update rather than a budget crisis.

Finance asks for next year's equipment budget in October. The hiring plan says somewhere between twelve and thirty-five people depending on funding, which closes in March. The honest answer is a range of about three times, and a range is not what the spreadsheet accepts, so somebody picks a middle number. In June, hiring runs ahead of plan, the equipment line is exhausted, and a new starter's laptop becomes a conversation about budget variance.

The same thing happens in reverse. A company budgets for forty hires, makes eleven, and carries an unspent equipment line that gets cut next year on the evidence that it wasn't needed, which is exactly the wrong lesson.

Recommended Tools

Best tools for HR Operations

B BambooHR HR management system R Rippling HR & IT automation W Workday Enterprise HRIS

View all recommended tools

Other versions: a company with a fixed total discovers that refresh and new hires compete for the same money, so the laptops of existing staff quietly get older to pay for new starters. Another budgets per head and forgets that leavers return devices, so it buys machines it already owns.

The real issue isn't the uncertainty. It's that equipment is budgeted as a total when it's naturally a rate, and a total forces a prediction nobody can make.

When You Don't Actually Need a Different Approach

Stage one: hiring is predictable. A company adding six to eight people a year knows roughly what that costs, and a total works fine. The variance is small enough to absorb and nobody needs a model.

Stage two: friction appears. The hiring range widens, or refresh starts competing with new hires for the same line, and the budget becomes a monthly negotiation. Nothing has broken and somebody is now spending time on it every month.

Stage three: it's a liability. The equipment line runs out mid-year and new starters are affected, or refresh is deferred repeatedly to fund hiring, which produces an ageing estate that fails all at once about two years later.

Stage four: the edge case. Several entities, several currencies, hiring plans that differ by market, and a refresh cycle at a different stage in each. That needs a model rather than a figure.

What HR Teams Actually Need to Give Finance

> "What is the number?" > Give a rate and an assumption, not a total. > A rate survives a change in hiring. A total is wrong the moment the plan moves.

> "What does one person cost?" > Device plus peripherals plus shipping plus the retrieval you will eventually pay for. > Most equipment budgets include the first and forget the other three, which understates by a meaningful margin.

> "Is refresh in the same line?" > It should not be, and this is the most valuable separation available. > Refresh and new hires competing for one pot means the existing estate loses every time.

> "What about leavers?" > State the assumption explicitly, because returned devices reduce what you need to buy. > A company with real attrition and good retrieval buys materially fewer machines than its hiring plan implies.

> "What happens if hiring doubles?" > With a rate, the answer is arithmetic. With a total, the answer is a conversation with finance in June.

A sixth question is worth raising if your hiring is genuinely volatile: what is the lead time cost of being wrong? Being under-budgeted doesn't just cost money, it costs the week it takes to get the money approved before anything can be ordered.

The Three Approaches and What Each One Costs

Fixed total. What it is: one number for the year, derived from the hiring plan. When it's right: when hiring is predictable within about twenty per cent, and when the refresh cycle is quiet. When it fails: whenever the plan moves. And it always moves, which means the budget is either exhausted early or underspent and then cut.

Per-head rate. What it is: a stated cost per new hire, multiplied by actual hires, plus a separate refresh figure. When it's right: almost always, and especially when the hiring range is wide. When it fails: when the rate is set too low, because it was calculated from device cost alone and omitted shipping, peripherals and retrieval. Then every hire is a small overrun and the pattern isn't visible until year end.

Committed subscription. What it is: a per-device or per-period arrangement with a vendor, so the cost is contractual rather than purchased. When it's right: when predictability matters more than total cost, and when the commitment level is below your realistic floor. When it fails: when you commit above your floor. A subscription sized for the optimistic hiring plan costs you for machines you never needed, which is worse than a total because you can't underspend it.

Per-head rate is the recommendation for most companies, because it converts the uncertainty from a forecasting problem into an arithmetic one. The rate is knowable. The headcount isn't, and nobody is asking you to know it.

How to Build the Number: Five Questions

What does one new hire actually cost? Build it up rather than estimating. Device, peripherals, shipping to their market, and a provision for the retrieval you'll pay for when they leave. The last one is the item everybody omits, and across a year of hiring into several markets it is not a small number.

How wide is the hiring range? If the plan is twelve to thirty-five, a total is meaningless and you should say so plainly rather than picking a midpoint that will be wrong in both directions.

How many devices reach refresh age this year? This is knowable from the register, assuming the register is accurate, and it's the half of the budget that doesn't depend on any forecast. Calculate it precisely because it's the part you can.

What is your actual attrition? Leavers return devices, and a returned machine in good condition covers a new hire. With real attrition and working retrieval, the number of machines you buy is considerably lower than the number of people you hire.

What is your floor? The number of hires you're confident of even in the worst case. That's the only figure safe to commit to contractually, and in a company with any funding uncertainty it sits well below the published plan.

Six Platforms Worth Knowing

RemoAsset Best for: companies that want a published figure to budget against rather than a quote that arrives after the budget is due. Why companies choose it: procurement and retrieval across 80+ countries with published pricing from $1,499 a year on the Subscription tier for companies with 50 to 5,000+ employees, including a 60 per cent reduction on retrieval charges. For a budgeting exercise specifically, a published number is worth more than it sounds: you can put it in the spreadsheet in October without waiting for a sales process. It's our own product, so weigh that accordingly. Where it struggles: no network discovery, so the device count you budget from comes from your own register rather than from observation, and an inaccurate register produces an inaccurate refresh figure. No software licence management, which is often the larger per-head cost and sits in a different budget. And only the Subscription tier publishes a figure, with pay-as-you-go quoted, so half the commercial picture still needs a conversation.

Electric AI Best for: smaller companies that want a predictable per-user cost they can model directly. Why companies choose it: it publishes prices, which is unusual here: $10 per user per month on Essentials and $25 on Pro, with a free tier. Where it struggles: the per-user basis means cost tracks headcount rather than devices, which is simpler to budget and less accurate if your device count differs from your headcount. It's an IT management product rather than a logistics one.

Workwize Best for: companies wanting stock held against a hiring plan that may not materialise. Why companies choose it: own warehouses. Where it struggles: publishes no rate card, so it cannot be put into a budget without a sales conversation first. The figures on its pricing page are savings claims rather than prices. Live domain is goworkwize.com.

Firstbase Best for: subscription-shaped equipping at volume. Why companies choose it: clean subscription model, strong supply side. Where it struggles: publishes nothing on price, and retrieval is the weaker half, which matters because retrieval is the budget item people forget.

allwhere Best for: converting equipment into a managed service cost. Why companies choose it: low internal lift. Where it struggles: publishes nothing, so budgeting requires a quote.

Deel IT Best for: companies whose employment costs already run through Deel and want one line. Why companies choose it: hardware alongside employment, MDM and support included. Where it struggles: publishes no price for IT, and its own page states both 130+ and 150+ countries without reconciling them.

The Decision Table: What Actually Needs Deciding

Rows two and three are where most companies actually are.

Give a Rate, Not a Total

This is the recommendation and the reason it works is that it moves the uncertainty to the person who owns it.

A total requires you to predict headcount. You cannot, and neither can the person asking, which is why the hiring plan is a range. When you provide a total built on a midpoint, you have silently accepted responsibility for a forecast that belongs to someone else, and when hiring differs from the midpoint the variance appears on your line.

A rate requires you to know what one hire costs, which is entirely knowable. Then the total is a multiplication performed by whoever owns the headcount number, and it updates automatically when they update it.

So the submission looks like this: equipment costs a stated amount per new hire in our main markets and a higher stated amount in markets we ship to less often. Refresh is a separate figure covering the devices reaching end of life this year, which is a known count. We expect a stated proportion of leavers' devices to be redeployable, reducing purchases accordingly. Then two totals. At the low end of the hiring plan it comes to this; at the high end, this.

That submission is harder to argue with than a single number, because every component is either knowable or explicitly flagged as somebody else's assumption. It also survives the plan changing, which is the main thing a budget needs to do.

The resistance you'll get is that finance wants one number for the model. The answer is to give them the midpoint total as the headline and the rate as the mechanism, so the model has its figure and the conversation in June is arithmetic rather than a variance discussion.

Build the Per-Head Rate Properly

Most per-head equipment figures are too low because they're the device price, and the device is between two-thirds and three-quarters of the real cost.

Four components. The device itself, at your standard build price for the relevant role. Peripherals, which for a home-based worker means monitor, dock, keyboard, mouse and often a chair allowance, and which collectively can approach the device cost. Shipping to their market, which varies enormously and is near zero domestically and substantial for a first shipment into a new country. And a provision for retrieval, because that person will eventually leave and somebody will pay to collect the device.

That last one is the item that's always missing. Retrieval is a real cost, it's incurred on a delay of two or three years, and because it happens in a different budget period from the purchase it never gets attached to the hire that caused it. Including a provision at the point of hiring is the honest treatment and it changes the rate noticeably.

Two refinements worth adding. Differentiate by market rather than using one rate, because a hire in a market you ship to weekly costs materially less to equip than a first hire in a new country, and averaging hides a cost that lands unevenly. And differentiate by role if your standard builds differ significantly, because an engineering build and a general build can differ by a factor that matters at volume.

Then state the rate with its components visible. A rate presented as a single figure invites negotiation on the figure. A rate presented as four components invites a conversation about which component to change, which is a better conversation and occasionally produces a real saving.

Separate Refresh From New Hires

This is the structural fix and it's worth more over three years than getting the rate exactly right.

When refresh and new hires share one budget line, new hires win every time, and they win for a good reason: a new starter without a laptop is a visible, dated, urgent problem, while a three-year-old machine that still works is none of those things. So in any month where the line is tight, the refresh is the thing that slips.

Done once, that's fine. Done repeatedly, which is what happens when the line is permanently tight, the estate ages uniformly and then fails in a cluster. A company that defers refresh for two consecutive years has a large number of four-year-old machines reaching failure at roughly the same time, and the cost arrives all at once alongside the support burden.

Two lines fixes it. One for new hires, expressed as a rate, which varies with hiring. One for refresh, expressed as a count of devices reaching end of life this year multiplied by the build cost, which is knowable from the register and doesn't depend on any forecast.

The refresh figure carries its own argument. Make it explicitly. These devices are at end of life, here's the count, here's what happens if we don't replace them, which is a rising failure rate and a support cost that doesn't appear on this line. That framing holds up better than a general case for keeping hardware current.

And it protects the estate, which is the point. A separate refresh line means a hiring surge doesn't quietly age everybody's laptop, and a hiring shortfall doesn't make the refresh look like money nobody needed.

Account for Leavers, Because They Fund Hires

The last component and the one that makes the arithmetic land differently than people expect.

When somebody leaves, their device comes back. If it's in good condition and not too old, it equips the next hire, which means you didn't buy a machine. At any meaningful attrition rate that's a substantial proportion of your hiring need met from stock.

The arithmetic matters. A company hiring thirty people with attrition that returns twelve usable devices buys eighteen machines, not thirty. Budgeting for thirty overstates the need by a third, and consistently overstating is how an equipment line gets cut in the year after you needed it.

Three conditions have to hold. Retrieval has to actually work, because a device that doesn't come back funds nothing. The machines have to be young enough to redeploy, which means your refresh cycle and your attrition rate interact. And somebody has to track the returned pool, because a redeployable device nobody has recorded is functionally lost and gets replaced by a purchase at full price.

That third condition is where this usually fails, and it's a register problem rather than a budget one. Returned devices sitting unrecorded are functionally lost, and the company buys new ones while owning perfectly good stock.

So state the assumption in the budget explicitly: we expect a stated number of devices to return in usable condition and reduce purchases by that amount. Making it explicit does two things. It reduces the ask, which is good for the submission. And it creates a reason for somebody to actually track the returned pool, because the budget now depends on it.

Where Jurisdiction Comes In

Short section, because almost nothing here is jurisdictional.

What's worth flagging is that equipment cost per hire differs by market for reasons beyond shipping: what you're expected to provide, what obligations attach to somebody's working environment, and what any of it means contractually all differ by jurisdiction. A single per-head rate applied globally will be wrong in both directions, and the markets where it's wrong are the ones you ship to least.

Anything raised on health or accessibility grounds should be funded separately rather than from a standard per-head rate, and should go to whoever handles that rather than through an equipment budget. A rate that has to absorb those requests will either be inflated for everybody or will put somebody in the position of arguing for something they need against a budget line.

Everything else on this page is portable. Give a rate rather than a total. Build the rate from four components including retrieval. Separate refresh from new hires. State the leaver assumption. Commit only at your floor. None of that depends on where you are, which is unusual for anything in this area and worth taking advantage of.

Working a Rate Through, With Real Numbers

The page says build the rate from four components. Here's one worked through, because the arithmetic is where the understatement usually hides and an abstract instruction doesn't surface it.

Take a company hiring into two kinds of market: ones it ships to regularly, and occasional ones.

For a regular market, a general-purpose build at $1,400, peripherals at $600 covering a monitor, dock, keyboard, mouse and a chair allowance, shipping at $60, and a retrieval provision at $150. That totals $2,210 per hire. The device alone was $1,400. So the device is about sixty-three per cent of the real cost, which is why a budget built on the device price alone is short by a third and nobody notices until mid-year.

For an occasional market, the same build and peripherals, shipping at $280 because it's a first shipment crossing a customs boundary, and a retrieval provision at $400 because collecting from a market you rarely serve costs more and succeeds less often. That totals $2,680, about twenty per cent higher.

Now the refresh side, which is separate and knowable. Thirty devices reaching end of life this year, at the $1,400 build cost, is $42,000. No forecast involved: that number comes from the register and it's the half of the budget you can state with confidence.

Then leavers. Hiring thirty, attrition of eighteen per cent on two hundred and twenty people returns about forty devices, of which perhaps half are young enough and in good enough condition to redeploy. Twenty redeployable machines against thirty hires means buying ten devices, not thirty, which changes the new-hire line by two-thirds.

I'd present it exactly like that, as five rows rather than one figure. I've watched a finance director accept a 21 per cent higher rate for occasional markets in about ninety seconds, once the shipping and retrieval lines were visible separately.

Put together: new hires at a rate rather than a total, refresh at $42,000 as a fixed and defensible figure, and a stated assumption that twenty returned devices offset purchases. The submission is three lines and every number in it is either knowable or explicitly somebody else's assumption.

Run your own version of this with your own build prices before the budget conversation. The twenty minutes it takes is the difference between a figure you can defend line by line and one you picked.

The Retrieval Provision, and Why It Keeps Getting Dropped

Worth its own section because it's the component that's always missing and the reasons it's missing are structural rather than careless.

Three things conspire against it. It's incurred two or three years after the hire, in a different budget period, so nothing connects it to the person who caused it. It's small per instance, usually a few hundred at most, so it never triggers attention individually. And in many companies it's paid from a different line entirely, often an operations or facilities budget, so the people building the equipment number never see it.

The result is an equipment cost per head that's understated by between five and fifteen per cent depending on your markets, consistently, every year.

Including it does two useful things beyond accuracy. It makes the full cost of hiring into a distant market visible at the point of the decision, which is when it's useful rather than three years later. And it creates a budget line that retrieval can actually be paid from, which removes one of the common reasons retrieval doesn't happen: that nobody's budget wants to absorb it.

How to size it: take what you've actually paid for collections in the last year, divide by the number of collections, and use that per market or per market group. If you've never paid for one, that's itself a finding, because it probably means retrieval isn't happening rather than that it's free.

One nuance. The provision isn't a reserve you hold, it's an allocation in the per-head rate so that the aggregate budget covers the collections that will happen that year. Those collections are for people hired two or three years ago, which means in a growing company the provision collected this year exceeds the collections needed this year. That's correct rather than an error, and it's worth explaining to finance before somebody notices the apparent mismatch.

Presenting a Range Without Losing the Argument

The practical difficulty with everything above is that finance asked for a number and you're proposing a method. That conversation has a shape that works.

Lead with the number they asked for. Give the midpoint total first, clearly, as a single figure. Withholding it in favour of explaining a methodology reads as evasion, however good the methodology is, and you spend the rest of the conversation recovering.

Then give the mechanism in one sentence: that figure is thirty hires at a stated rate plus a known refresh count, less twenty redeployed devices, and it moves with hiring rather than being fixed.

Then give the two ends. At twelve hires the total is this; at thirty-five it's this. Both calculated, both shown. The range is not a hedge, it's the information finance actually needs to understand the shape of the exposure, and presenting it as arithmetic rather than uncertainty changes how it's received.

Then name what you need from them, which is usually one of two things: either agreement that the line flexes with actual hiring, or a stated figure you should plan to and a commitment that exceeding it is a hiring decision rather than an equipment overrun. Either is workable. What isn't workable is a fixed total with an unfixed hiring plan, which is the arrangement that produces the June conversation.

One tactical point. Bring the refresh number separately and make it the firm part of the ask. It's the most defensible figure you have, it doesn't depend on any forecast, and it's the one most likely to be cut if it's bundled with something uncertain. Presenting it as a separate, known, non-negotiable count is what protects it.

And if the answer is a fixed total anyway, which happens, write down the hiring number it corresponds to and send it in the same email. That one sentence converts a future overrun from your problem into a shared record of what was agreed.

Keep that email somewhere you can find it in nine months. It is the only thing that distinguishes a budget that was wrong from a hiring plan that changed after it was set.

Mid-Year, When the Plan Has Moved

The whole point of a rate is that the June conversation becomes arithmetic. Worth describing what that conversation actually looks like, because having the right structure does not automatically make it easy.

Hiring is running ahead. The equipment line, as a total in somebody's model, is tracking toward exhaustion. Somebody notices and raises it as a variance, usually in a monthly review, and usually framed as an equipment problem rather than a hiring one.

With a rate, your answer is three sentences. We budgeted at a stated rate per hire against a plan of thirty. We have made twenty-two hires in the first half rather than the fifteen implied by that plan. At the same rate the full-year total is higher by a calculable amount, and that figure is a hiring consequence rather than an equipment overrun.

That reframing is the entire value of the method. The spend is not over budget; the headcount is over plan, and the equipment cost followed it exactly as designed. Whether to continue hiring at that rate is a decision for whoever owns the hiring plan, with the equipment cost as one input.

Two things make the conversation go better. Flag it yourself, before anybody asks, at the point you can see the trend rather than when the line runs out. A variance raised by the person who owns it reads as management; the same variance raised by finance reads as a problem. And bring the per-hire rate alongside it, unchanged, because the fact that the rate held is the evidence that the method worked.

The opposite case needs the same treatment. It gets forgotten. If hiring is running behind, say so and release the money rather than letting it sit. An unspent line discovered at year end is cut the following year; an unspent line surrendered in September is remembered as something else entirely.

And keep the refresh line out of both conversations. It did not move, it does not depend on hiring, and allowing it to be discussed alongside a hiring variance is how it ends up funding the gap.

The Cost of Getting This Wrong

The visible cost of an exhausted equipment line is a delay, and it's worse than it sounds. A new starter without a machine while a budget variance is approved loses a week, and the approval itself takes longer than the procurement would have.

The second cost follows an underspend. It is the cut. A company that budgets for forty hires and makes eleven carries an obviously unspent line, and the following year that line is reduced on the evidence that it wasn't needed. Then hiring recovers and the budget is structurally too small for reasons that have nothing to do with equipment.

Third is the deferred refresh, which is the expensive one and arrives late. Two years of refresh losing to hiring produces a cluster of ageing devices that fail together, with a support cost and a replacement cost landing in the same period, and the total is considerably higher than if the refresh had run on schedule.

Fourth is the unrecorded return pool. Devices coming back and not being tracked means buying machines you already own, continuously, at whatever rate your attrition runs at. Nobody ever sees this cost because the purchases all look individually justified.

And fifth is over-commitment. A subscription sized for the optimistic hiring plan is a contractual obligation for devices you never needed, and unlike a budget you cannot simply underspend it.

So the question worth asking isn't what the equipment budget should be. It's whether you've been asked for a total when the honest answer is a rate.

When You're Ready to Move Beyond Picking a Midpoint

The signal is the second year in a row that the equipment line was materially wrong in either direction.

What replaces it fits on half a page. A per-head rate, built from device, peripherals, shipping and a retrieval provision, stated separately for your main markets and your occasional ones. A refresh figure, derived from the count of devices reaching end of life, on its own line. A stated leaver assumption reducing purchases. A floor figure, being the hiring number you're confident of, which is the only number safe to commit contractually. And the midpoint total as a headline so the financial model has its figure.

Five components, one afternoon, and it means the June conversation is a multiplication rather than a negotiation.

RemoAsset is our own product, so weigh this accordingly. The relevant point for budgeting specifically is that a published figure can go into the spreadsheet when the budget is due rather than after a sales process, and most vendors in this category publish nothing. Ours is $1,499 a year on the Subscription tier. It has no network discovery, so your refresh count comes from your own register and an inaccurate register produces an inaccurate figure, and no software licence management, which is often the bigger per-head number.

If you're building next year's number now, the most useful thing you can do is price one hire properly, including the retrieval. That figure is the whole budget.

Frequently Asked Questions

Price one hire properly and the budget takes care of itself.