This article is not about which computer to buy. It is about who requests it, who approves it, who registers it, and who is accountable when the equipment didn't arrive on time.
Many of the companies that contact us arrive with the same situation: they manage their team's computers on their own and, at some point, the process gets stuck. Often, the problem isn't the computer. It's that three departments make three different decisions without speaking to one another.
People closed a hire with a start date. IT found out days later. Finance received an invoice for an emergency purchase that wasn't in any budget. Each department did its part well, and yet the outcome went wrong.
In companies with distributed teams, this happens more often, because every new hire adds a country, a deadline, and a vendor to the equation. The question “who buys the computers?” ceases to have a single answer and starts having three.
In this article, I review where that friction arises, what is needed to eliminate it, and how we solve it at First Plug, so that each department gets what it needs without adding meetings or bureaucracy.
Who decides on computer purchases in a company?
In a company with a distributed team, the purchase of computers is not decided by a single person. Three departments are involved: IT defines what is purchased and how it is configured, Finance defines how much is spent and with what predictability, and People defines when the equipment is needed. The three objectives are compatible. The conflict appears when each department resolves things on its own, without shared rules.
This is not exclusive to hardware. A Gartner survey of B2B buyers found that 74% of buying decision teams experience conflict that the firm classifies as unhealthy. Gartner describes it as a situation in which members pursue conflicting goals, disagree on how to move forward, or end up overruled by other decision-makers. The same study was based on 632 buyers surveyed between August and September 2024, and showed that groups that reach an agreement are 2.5 times more likely to rate their purchase as high quality. Gartner Sales Survey Finds 74% of B2B Buyer Teams Demonstrate "Unhealthy Conflict" During The Decision Process +2
The practical takeaway is not to remove departments from the decision, but to eliminate the handoffs where information gets lost: ensuring that all three work under the same rules and on the same record.
What do IT, Finance, and People care about when purchasing equipment?
Each department looks at the same purchase from a different angle. IT thinks of the device as an asset that it needs to be able to support and manage. Finance thinks of it as a cost per seat that it needs to be able to forecast. People thinks of it as a prerequisite for the employee to start working on the agreed date. None of the three criteria is sufficient on its own.
Department | What it decides | What it measures | Pain points when the process fails |
|---|---|---|---|
IT | Approved configurations by profile, security, and remote management | Registered devices, fleet standards, support tickets | Non-standard devices, unregistered devices, or devices that must be configured remotely |
Finance | Budget per seat and purchasing terms | Cost per seat, budget variances, number of vendors | Ad hoc purchases, varying prices by country, paid equipment that is not returned |
People | Date when the employee needs the equipment | Ensuring the person has everything ready on day one | A first day without equipment, or with installations handled over a video call |
Read from start to finish, the table highlights the blind spot: each department sees only part of the cycle, and no one sees the whole picture. IT knows what equipment exists, Finance knows how much it cost, and People knows who joins and who leaves. If that information is not cross-referenced, problems arise during handoffs.
At what points does the cross-departmental process break down?
When a company manages its hardware on its own, the process breaks down at the handoffs, not within each department. There are four moments where this happens most frequently: onboarding a new employee, urgent purchases, replacing faulty equipment, and offboarding someone who leaves the company. In all four, the problem is the same: one department finds out too late about something another has already decided.
1. Onboarding: when IT finds out too late
People closes a hire with a start date. IT gets notified when the timeline for purchasing, configuring, and shipping no longer fits into the schedule. The usual workaround is to buy whatever is available, wherever it's available.
If you want to see how to organize this stage from end to end, we break it down in how to equip a new remote employee step by step.
2. Urgent purchases and reimbursements
An urgent purchase from a local store solves day one, but it creates three problems. It breaks the fleet standard because a model arrives that IT didn't plan to support. It is usually more expensive because it is bought without negotiating or comparing. And it almost never gets logged in the inventory with its assigned owner.
A frequent variation is asking the employee to buy their own computer and then reimbursing them. That leaves the device in ownership limbo: does it belong to the company or the individual? The question only surfaces when that person leaves. Furthermore, the labor and tax treatment of that reimbursement varies by country.
3. Replacement due to failure
A laptop breaks mid-year. IT confirms it needs to be replaced, Finance hadn't budgeted for that expense, and People gets the complaint from the employee who can't work. If no one defined who approves a replacement, the decision gets stuck while the person waits.
We explain how to resolve this moment in laptop replacement for remote teams.
4. Offboarding: when the equipment doesn't return
People confirms a departure. IT revokes access that same day, but the laptop remains at the home of the person who left. If no one coordinates the retrieval, the device is lost.
It's not just a financial cost, and we break it down in what happens to the laptop when a remote employee leaves the company.
What does an equipment policy need to include?
An equipment policy is a short document that sets the rules for purchasing, assigning, and returning equipment. It doesn't need to be long: with six written definitions, most requests no longer require cross-departmental negotiation.
Catalog by role. IT defines two or three approved configurations based on the role type. People chooses from the catalog and does not specify hardware.
Minimum notice period by country. People reports each onboarding with the advance notice required by the employee's country. In LATAM, this timeframe is not the same across all markets because import regulations, customs, and local availability vary; we explain this in how to send a laptop to another LATAM country. The important thing is that People has the timeframe on hand when closing the hire.
Approval threshold. Finance approves the budget per position once a year and only reviews exceptions. If you want to plan for it, how to execute the IT budget before year-end might be helpful.
Whose name the equipment is registered under. Always the company's. This is the requirement to be able to demand its return later, as we explain in the acquisition stage.
What is signed upon onboarding. An acknowledgment of receipt and the commitment to return the equipment upon termination of employment.
How an exception is handled. Who requests it, who validates it, and who approves it, so that an off-catalog request doesn't turn into an endless message thread.
Writing these rules is the first step. What is hardest, when the company manages it on its own, is sustaining them with employees across several countries, each with their own timelines, customs, and availability. That is where a single vendor changes the outcome.
What changes when all three areas work with a single provider?
A single provider for the entire lifecycle gives all three areas the same information at the same time. IT, Finance, and People no longer need to reconstruct the status of each device from different spreadsheets. Instead, they look at the same single record, updated by whoever purchases, delivers, and recovers the equipment. Here is how we do it at First Plug:
For IT, the change is traceability. The ISO/IEC 27001:2022 standard, in control 5.9, requires building and maintaining an inventory of information and associated assets, along with their owners. On the First Plug platform, that inventory maintains itself: each device is logged with its owner, country, and status. In addition, computers purchased through us include MDM enrollment, so they arrive ready to be managed remotely.
For Finance, the change is predictability. Purchasing, configuration, shipping, support, and recovery all come from the same provider.
For People, the change is meeting deadlines. Equipment ships configured and ready to use, so the employee's first day doesn't depend on someone installing software over a video call.
There is a key factor that ensures country-specific delivery deadlines can be met: in LATAM, we have our own operations. The timeline People works with doesn't rely on a third party that subcontracts delivery. We manage it ourselves, with direct knowledge of how each country operates.
Recovery completes the cycle. People notifies us of an offboarding, we coordinate the pickup, and the equipment is returned. IT sees the updated asset, and Finance avoids an unnecessary replacement purchase.
Frequently Asked Questions
Who should own the computer procurement process?
It is best to distribute it rather than concentrate it. IT owns the equipment standard and inventory. People owns the order trigger, because they are the department that knows first when someone joins or leaves. Finance approves the annual budget per role and reviews only exceptions, not every transaction.
How far in advance should equipment be requested for a remote hire?
It depends on the destination country. Within LATAM, importation, customs, and local availability vary by market, so there is no single timeframe. The key is to establish a minimum lead time per country and make sure People has it on hand when closing each hire.
Should employees be reimbursed for purchasing their own computers?
It solves the immediate need for day one, but it breaks the standard and complicates retrieval. The equipment enters a gray area of ownership that only surfaces when the person leaves the company. In addition, the labor and tax treatment of reimbursements varies by country, so it is best to review it locally before adopting it as a policy.
How can out-of-budget, rush purchases be avoided?
With three rules: a catalog of configurations by role, a minimum advance notice period per country, and an annual budget per position approved beforehand. If you also work with a single provider covering all countries where you hire, the workflow becomes predictable and emergencies decrease.
Is a procurement committee needed to make hardware decisions?
In most cases, no. A concise equipment policy that defines the catalog, notice periods per country, and who approves exceptions, along with an equipment inventory log that all three departments can consult, is sufficient. Bringing the three areas together makes sense for establishing the annual framework and major exceptions, not for every individual order.
Conclusion
Streamlining computer procurement isn't achieved by designating a single owner. It is achieved by agreeing on what each department decides and putting it in writing before the next new hire arrives.
When IT owns the standard, People owns the trigger, and Finance owns the framework, every team gets what it needs: controlled equipment, predictable expenses, and employees who start working on the agreed date. Interdepartmental conflict doesn't disappear because everyone has less to say, but because each person knows beforehand where their responsibility ends.
If you'd like to see how this workflow would look with your team and your countries, you can request a quote and we will review it together.
You might also be interested in…
















