IT procurement strategy: how mid-market companies stop buying reactively

Most mid-market IT teams don't have a procurement strategy. They have a credit card and an IT supplier account.

Someone needs a laptop, the IT lead orders one. A team grows by five people, someone buys five machines on short notice. An employee breaks a screen, the replacement comes from whichever supplier responds first.

It works. Until the company hits 200 people and suddenly you're spending significant amounts on hardware annually with no visibility into what's been ordered, by whom, or whether anyone compared prices.

Based on 130+ conversations with IT teams at mid-market companies, reactive purchasing is one of the most common cost complaints. The frustration is not that nobody planned for it, but that equipment is expensive.

What reactive purchasing actually costs

The direct cost is obvious: you pay more per unit when you buy one at a time instead of in planned batches. But the indirect costs add up faster.

IT time. Every ad hoc order takes time: comparing options, getting approval, placing the order, tracking delivery, registering the asset. When one person handles all of this manually, those minutes add up to hours every month.

Budget surprises. When purchasing happens reactively, costs are impossible to forecast. Finance asks "what will we spend on IT hardware next quarter?" and the honest answer is "I don't know yet."

Inconsistency. Without a standard catalogue, employees end up with different models, different specs, and different accessories depending on when they joined and who ordered their equipment.

‍

What a procurement strategy looks like at mid-market scale

You don't need a procurement team. You need four things:

1. A standard catalogue. Define which devices are approved for which roles. Three laptop options, two phone options, a standard accessory kit. Employees choose within the catalogue, you control what's available.
2. Budget per employee. Set a hardware budget and let people order within it. If they want something above budget, they can pay the difference. This removes IT as the bottleneck while keeping spend controlled.
3. Approval workflows. Not every order needs the CTO's sign-off. Low-risk, within-budget orders auto-approve. Over-budget or non-standard requests go through a manager.
4. Supplier integration. Connect your supplier directly to your ordering system so orders route automatically. No manual emails, no copy-pasting serial numbers, no tracking spreadsheets.

How this works in practice

A new hire starts in two weeks. Their manager opens the Store, selects a laptop from the approved catalogue, and checks out. The order routes to the integrated supplier (Dustin, Ingram Micro, or whoever you work with). The device ships directly to the employee. When it arrives and enrolls in MDM, it appears in the asset register automatically.

No emails to IT, no manual registration and no scrambling on the Friday before a Monday start date.

For the IT team, this means fewer tickets, predictable spend, and a complete audit trail of what was bought, for whom, and when. For finance, it means actual data to forecast against instead of quarterly surprises.

Start with visibility, then add structure

If you're not ready to overhaul procurement overnight, start with visibility. Know what you're spending, on what, and for whom. When you can answer "what did we spend on hardware last quarter?" in five seconds, the rest follows naturally.

The companies that get this right tend to start small: one supplier connected, one approval workflow, a basic catalogue, and expand from there. The goal isn't perfection. It's getting out of reactive mode.

See how Velory's Store handles procurement for mid-market IT teams, try the interactive demo.

‍

‍
FAQ

What is an IT procurement strategy?

An IT procurement strategy is a structured approach to purchasing hardware, software, and services for your organisation. Instead of buying reactively when someone needs something, you define approved devices, set budgets, create approval workflows, and integrate with suppliers so orders route automatically.

How is IT procurement different from general procurement?

IT procurement deals specifically with technology assets: laptops, phones, software licenses, mobile subscriptions, and peripherals. It intersects with MDM enrollment, asset lifecycle management, and IT security in ways that general procurement doesn't.

What tools help with IT procurement at mid-market scale?

Look for tools that combine a device catalogue, budget controls, approval workflows, and direct supplier integration. The goal is to remove IT as the bottleneck while keeping spend visible and controlled. Velory's Store is built specifically for this.

How do I reduce reactive IT purchasing?

Start with visibility: know what you're spending, on what, and for whom. Then add structure: a standard catalogue, per-employee budgets, and approval workflows. Connect at least one supplier directly so orders flow without manual emails.