Why a 30-person company shouldn't hire a full-time IT director yet

Somewhere around 25 or 30 employees, the conversation starts. The systems are getting complicated. Vendors are multiplying. Someone forwarded the owner an article about AI, and now there is a vague sense that nobody on the team is actually in charge of any of this. The instinct is to fix it the way you fix every other capability gap: hire someone full-time and make it their job.

I want to talk you out of that — or at least out of doing it this year. Not because technology leadership doesn't matter at your size. It matters more at your size than it ever has. I want to talk you out of it because of how the math actually works, and because the full-time hire is almost never the cleanest way to get the thing you're trying to buy.

Run the real number. A competent IT director who can both set strategy and lead execution is not a $120,000 salary. By the time you load it — base, payroll taxes, benefits, the recruiter fee to find them, the equipment and software they'll need, the ramp time before they're productive — you are well north of $200,000 a year in true cost for one person. And a single person, no matter how good, has exactly one background, one set of blind spots, and one bad week that can stall everything. You are buying a point of failure and calling it leadership.

Here is the part nobody says out loud at 30 people: the role you actually need isn't full. You need director-level judgment on the decisions that matter — what to build versus buy, which vendor contract is quietly bleeding you, whether the stack you chose in 2021 is the stack for the next five years, what to do about the fact that your whole team is already pasting client data into ChatGPT with no policy. Those are real decisions with real consequences. But they don't take forty hours a week. They take the right person, present at the right altitude, on a regular cadence — plus a team that actually does the work the decisions create.

That is the gap a fractional technology director fills, and it's a genuinely different product from the two things most owners compare it to. It is not a fractional-CIO consultancy that hands you a polished roadmap and a final invoice and disappears before anything gets implemented. It is not an MSP that executes tickets with no strategic context and no opinion about where you should be going. It is the director who sets the direction and leads the team that makes it real — one accountability line, no handoff between the person who decided and the people who do.

The honest objection is ownership. Doesn't a full-time hire care more, sit in your building, belong to you in a way an outside firm never will? Sometimes. But proximity is not the same as accountability, and a salaried employee whose work nobody senior can evaluate is not actually accountable to anyone — they're just close by. The arrangement I'd defend is the one structured so you could end it cleanly and choose not to: your documentation in your possession, your vendor relationships in your name, the relationship built so leaving is easy and staying is the obvious call.

There is a point where the full-time hire is right. It usually arrives later than the anxiety does — when the technology function is large enough that director-level work genuinely fills the week, when there's a team to manage day to day, when the strategic load is constant rather than episodic. A good fractional director will tell you when you've crossed that line, because that is the relationship working correctly, not the relationship ending badly. The mistake isn't hiring a technology director eventually. It's hiring one before the work is shaped like a full-time job, and paying $200,000 to find that out.