In-House IT or an IT Partner? What Actually Fits a Small A&E Firm

The moment a firm’s technology starts to hurt, the instinct is to hire someone to own it. A capable IT person, on staff, who finally makes the problems go away. It is a reasonable instinct. For most firms under fifty people, it also solves the wrong problem.

Architecture and engineering firms tend to reach this point the same way. Projects grow, tools multiply, the server everyone forgot about starts causing problems, and the partners are tired of being the help desk. So the firm hires an IT person, or leans harder on the one contractor who has been around for years.

For a while, it works. Tickets get answered. Things stop breaking as often. But two problems tend to surface, and neither is about technical skill.

The gap is usually strategy, not support

Most IT professionals are exactly that: technical professionals. They are good at keeping systems running, and that is a real skill. What they are usually not hired or trained to do is connect technology decisions to how the firm actually makes money.

That is the difference between a technician and a strategist. A technician keeps the lights on. A strategist asks whether the lights should be on at all, what the firm is trying to achieve over the next two years, and which technology investments move it there. Most firms end up with the first and quietly assume they are also getting the second.

You can have every technical box checked and still be losing time and margin, because no one is treating technology as a business decision rather than a tool list.

The person who fixes everything is also your biggest risk

The second problem is quieter and more dangerous. When one person understands how everything is wired together, that person becomes a single point of failure.

The documentation is usually thin, because the person who would write it is the same person too busy fixing things to write it. When they take a month off, or leave, the firm discovers how much lived only in one head. We have seen firms unable to make a simple change to their own website or billing system because the one person who understood it was unavailable.

Concentrated knowledge feels efficient. It is actually a risk sitting on your balance sheet, and it grows the longer it goes undocumented.

Accountability is harder than it looks

There is a management problem too. When the rest of a firm is non-technical, holding a technical person accountable is genuinely difficult. Every concern can be met with a technical answer that leadership has no easy way to evaluate, so good intentions on both sides can still end in a standoff.

This is not a knock on in-house people. It is a structural mismatch: you are asking non-technical leaders to manage, evaluate, and set direction for a discipline they were never meant to be experts in.

What a partner actually changes

The alternative is not simply outsourcing the same job to save a little money. Done well, a partner changes the shape of the problem.

• You get both layers. Day-to-day support (the fix-my-laptop, keep-the-servers-running work) and a strategic layer above it: a Fractional CIO who owns technology as a business decision and answers to outcomes, not tickets.
• You get a team, not a person. Coverage does not vanish when one individual is on leave, and knowledge is documented as a matter of course rather than left in someone’s head.
• You get a single point of accountability. One relationship that manages your vendors, projects, and roadmap, so leadership can say what the business needs and let someone else source it, price it, and run it.

The honest version: a good partner should make itself accountable in a way a single hire structurally cannot.

What if you already have someone

None of this means letting your in-house person go. For a lot of firms the better answer is co-managed IT: your person stays and gets a team behind them. They keep the institutional knowledge and the internal relationships, and they gain the layer above them, a Fractional CIO setting direction, documented systems, coverage when they are out, and senior backup on the projects and incidents that are too big for one set of hands. The single point of failure quietly goes away, and your in-house person gets to spend their time on the interesting work instead of the endless ticket queue.

What this means for your firm

If your firm is weighing an in-house hire, the useful question is not “in-house or outsourced.” It is: who owns technology as a business decision here, and what happens to us if the one person who understands our systems is gone next week?

If the answer to the first is “no one, really,” and the answer to the second makes you wince, the gap you are trying to fill is not another technician. It is the strategic seat that sits empty in most firms your size.

That is exactly what a Strategic Technology Assessment is built to surface: where your technology stands today, where the real risks are, and a plan and budget to close them. It is the conversation we have with firm leaders every week, and it is the honest place to start before you hire anyone.