“We already have an MSP, why would we need an IT Director too?”
It’s one of the most common questions I get from founders and operations leaders in the 10-100 employee range, and it comes from a reasonable place. Both roles involve “IT.” Both show up in conversations about servers, software, and support tickets. It’s easy to assume they’re the same job wearing different hats.
They’re not. And the businesses that understand the difference early tend to make better technology decisions, spend less on IT overall, and avoid the slow drift into vendor-driven decision-making that quietly costs SMBs a lot of money over time.
What an MSP actually does
A Managed Service Provider delivers and supports your IT. Helpdesk tickets, patching, backups, network monitoring, hardware procurement, maybe some cloud administration. A good MSP does this reliably and keeps the lights on.
That’s the job. It’s a delivery function, and it’s a valuable one. But an MSP’s incentives are built around delivery, not direction. They’re not paid to ask whether your business needs a different platform strategy in 18 months, or whether the three overlapping tools you’re paying for should be consolidated into one. They’re paid to keep what exists running, and often, to sell you more of what they offer.
What an IT Director actually does
An IT Director sits above the delivery layer. The role is about direction, not tickets: setting the technology roadmap, deciding what the MSP (or internal team) should actually be prioritising, reviewing whether delivery is meeting the business’s needs, managing vendor contracts and renewals, and making sure technology decisions get made in the context of where the business is actually heading, not in isolation.
Crucially, an IT Director holds the delivery function accountable. Someone has to ask “is this MSP relationship actually working for us, or have we just gotten used to it?” That’s not a question an MSP can objectively ask about itself.
Why the confusion is expensive
When a business doesn’t distinguish between delivery and direction, one of two things usually happens.
The first is that the MSP ends up setting direction by default, because nobody else is. Decisions get made based on what’s easiest to sell or support, not what’s best for the business. Spend creeps up. Nobody notices because there’s no one whose job is to notice.
The second is that the owner or a senior operator becomes the accidental IT Director, on top of their actual job. Technology decisions land on their desk reactively: a renewal notice here, a vendor push there, a security incident that forces a decision nobody was ready to make. There’s no roadmap, just a series of reactions.
Both patterns are common in founder-led businesses between 10 and 100 people. Neither is anyone’s fault. It’s simply a structural gap: delivery is covered, direction isn’t.
You don’t need to choose one or the other
This is the part that surprises people: bringing in IT Director-level direction doesn’t mean replacing your MSP. In most engagements, the MSP relationship stays exactly where it is. What changes is that someone is now setting their priorities, reviewing their performance against the business’s actual needs, and making the vendor and budget calls that nobody else in the business is positioned to make impartially.
Think of it the way you’d think about your accountant and your audit committee. Both deal with “the numbers,” but one delivers the bookkeeping and the other provides oversight. You wouldn’t expect the same person or firm to do both objectively. IT works the same way.
How to tell if this gap exists in your business
A few signs are worth watching for:
- Technology decisions keep landing on the owner’s or a senior leader’s desk, usually at the worst possible time
- Nobody can clearly explain the IT roadmap for the next 12-18 months
- Software renewals happen on autopilot without anyone reviewing whether the tool is still needed
- IT spend has grown steadily but nobody’s mapped it against business outcomes
- The MSP relationship has never really been reviewed or benchmarked since it started
If two or more of these sound familiar, there’s a reasonable chance your business has delivery covered and direction missing.
The fractional model
Full-time IT Directors are typically out of reach for businesses at this size, both in cost and in the reality that most 10-100 person businesses don’t need five days a week of strategic IT leadership. A fractional arrangement, a few days a month, embedded in the leadership team, closes the direction gap without the overhead of a full-time executive hire.
If this distinction is resonating with your own setup, it’s worth a conversation.