Ask any recruitment owner who is responsible for IT inside their business, and you usually get one of three answers. ‘Me, mostly.’ ‘Our supplier, I think.’ Or a longer pause than the question deserves.
None of those are the right answer. They are the symptom of something quieter. IT in most growing recruitment businesses does not have a written owner for each part of it. Responsibility is shared by default, which is the same as not being shared at all. The day something matters, nobody has the full picture.
This blog is about the small, calm exercise that fixes that. Half an hour, a piece of paper, and the right column headings.
Map your IT into eight categories. For each one, write down a single name responsible for it. Not a department. A person.
Strategy and roadmap. Where the IT is going over the next eighteen months. Whose call.
Service desk. The day-to-day ‘something is broken’ line. Whose phone rings.
Security and compliance. MFA, encryption, the audit trail when an insurer or a client asks.
Identity and access. Who has admin rights, who lost them, who should never have had them.
Devices and endpoints. The laptops, phones and tablets your team carry. Encrypted, patched, replaceable.
Data and backup. Where the files live. When the last restore was tested. Whose answer that is.
Vendors and licences. The Microsoft renewal. The CRM contract. The email security add-on nobody can quite remember signing for.
People. Onboarding the new consultant on Monday. Offboarding the leaver on Friday. Who triggers it, who closes it.
Most owners have never written this down. The exercise itself is most of the value. Empty rows are the gaps you have been carrying without naming them.
The pattern we see most often when we audit recruitment businesses is not negligence. It is split ownership. The owner thinks the supplier handles backups. The supplier thinks the owner asked for a specific backup product, and is delivering exactly that. Nobody is actually testing a restore.
The same dynamic plays out across every row of the map. Identity sits between the supplier and the office manager. Vendor renewals sit between finance and whoever last opened the email. Devices sit between the laptop refresh budget and the person handing a machine over to a new starter on a Monday morning.
Each shared row is a row where the work happens by accident, or not at all. Nothing dramatic happens until the day something does. Then, in the hour after a missing laptop or a hijacked mailbox, three people each think it was someone else’s job.
A clean ownership map removes the question. One name per row. The room can move.
Vendor is the right word for someone you hand a problem to and pay for the fix. Boilers, printer toner, vending machines. The relationship is transactional. It works.
It does not work for IT in a growing recruitment business. Too many of the categories on the ownership map sit between rooms. A vendor cannot make those calls because they do not see the desks. They see tickets.
A partner sits closer in. They know the rhythm of your week. They know when payroll runs. They know which consultants are about to onboard. They know what ‘urgent’ means today versus next Tuesday. From that position, they can own rows of the ownership map in a way a transactional supplier never will.
The simplest test for whether you have a partner or a vendor. Could the people who answer your IT call name your top three desks? Could they tell you what kind of week it has been on the placements board? If not, the relationship is a contract. Not a partnership.
The best compliment a client has ever paid us was a recruitment owner saying, almost as a throwaway in a meeting, ‘I forgot you were external.’
That sentence is the bar. It means the IT decisions had stopped feeling like a separate negotiation. The partner had been absorbed into the team’s working week. The owner did not have to switch contexts to bring an IT question into the room. It just got handled.
That is what IT support is supposed to feel like. Not a portal. Not a ticketing system. A name and a face the team knows, who is in the loop on what the business is doing this quarter, and who picks up the rows of the ownership map that should not be the owner’s problem any more.
The vendor relationship makes you the integrator. The partner relationship makes them the integrator. That is the shift.
A 25-person recruitment business does not need an in-house IT director. It does still need someone playing that role. Strategy, roadmap, ownership of every category on the map, the long view across vendors and risk.
The honest framing is that the tools an enterprise uses for this are now sitting inside Microsoft 365 Business Premium. The same toolkit a 5,000-person business has access to is sitting on your tenant. The variable is whether someone with the right posture is configuring it for the way your desks actually work.
That is what ‘enterprise-grade IT, without the enterprise price’ means in practice. Not a discount. A different shape of ownership.
Print the map this week. Eight rows, one name per row.
Where the row reads ‘me, mostly’, the question is whether you want to keep that one or hand it on. Where the row reads ‘I’m not sure’, the question is bigger.
If your IT partner cannot fill in the rows next to you, they are still a vendor.
