In an industrial company of this size, IT is usually one or two people. They do their job well: they set up users, fix the shipping printer, bring email back when it goes down and call the ERP vendor when something breaks. Without them the company does not open on Monday.
Now make a different list. Over the past year someone decided whether to renew the ERP contract for three more years, which vendor would build the portal, whether to buy Windows extended updates, how to answer the customer who sent a security questionnaire and whether the team could use an AI tool with customer data.
Who made those decisions? Almost always one of two people: the general manager, on the recommendation of the vendor who was going to bill for it, or the IT lead, without the authority or the time to do it well.
Two jobs with the same name
“IT” names two jobs that look nothing alike.
Running means everything works today: machines, accounts, network, backups, the call to the vendor. It is urgent, visible, and somebody does it, because otherwise the plant stops.
Directing means deciding what the company will have three years from now, with whom and for how much. It is almost never urgent and nobody sees it, so nobody does it. Or the vendor does.
The problem is not that the IT lead does not know. It is that their day is full of urgent work, nobody gave them the job of directing, and when they weigh in, they carry less weight than a salesperson with a slide deck. Asking one person to do both is the most common way to get neither done well.
The decisions being made with nobody in charge
These are the ones that cost the most when they are made blind, and all of them arrive sooner or later:
- Signing or renewing a long contract. Who owns the code, what happens to your data if you leave, how much the price goes up at renewal. We covered it in what to check before you sign with a software vendor.
- The order of projects. When everything is urgent, the one from the latest meeting wins unless there is a written rule for deciding what goes first.
- The annual budget. Separating what is required from what is wanted, which in 2027 already comes with due dates.
- Which data leaves the company. What can be sent to an AI model and what cannot, agreed in writing before everyone decides on their own.
- What happens when the person who knows leaves. A system only one person understands is a risk nobody owns, until somebody inherits it.
None of these is a hard technical problem. They are business decisions with technical consequences, and they need someone who understands both sides and sits in the meeting.
Why not hire a full-time director
Sometimes that is the right call. But in a company this size, technology leadership decisions do not fill forty hours a week. They fill a handful a month, bunched around the budget, renewals and projects.
That leaves two bad options. Hire someone experienced and pay for a role that does not have enough work: they get bored, leave, or invent projects to justify the job. Or hire someone inexperienced so the salary fits, and the big decisions are still made by the vendor.
The third option is paying for the hours that are actually needed. That is what a fractional CTO is: the same experienced person, a few hours a month, with a fixed seat in the meetings where decisions are made.
What it looks like in practice
It is not a consultant who sends a report. If they are not in the meeting where the decision is made, it does not work. Concretely:
They are part of the decisions. A standing monthly meeting with leadership, and available when a proposal, a contract or a customer with a new requirement shows up.
They review before anything is signed. Proposals, contracts and renewals go past someone who knows what to ask and does not get paid on the sale.
They back the IT lead, they do not replace them. They provide judgment, take away the decisions that are not the IT lead’s to make and back them in front of vendors. The point is for the person running IT to carry more weight, not less.
They write decisions down. What was decided, on what criteria and what would change it. A year from now, when someone asks why that system was chosen, the answer is on one page and not in someone’s memory.
When you do not need one
It is worth saying, because it happens:
- If nothing important will change in the next two years: no big contracts, no new system, no customers asking for something different.
- If leadership already has the judgment, because someone there comes from technology and has the time to use it.
- If everything you use comes from one vendor, works, and the contract is reasonable. Reviewing the renewal when it comes is enough.
What to ask for
From whoever you hire for this, ask for three things from day one:
- That they tell you whether they have something to sell you. Someone who directs and also builds or resells has a built-in conflict of interest. It does not disqualify them, but it must be stated, and every recommendation must come with its alternative.
- That everything is written down and in your name. Inventories, decisions and admin passwords belong to the company, not to whoever put them together.
- That they start by finding out what you have. Nobody can direct what they do not know. That is why the first month is almost always a technology audit: an inventory with judgment of what runs, what is at risk and what comes first.
How to tell whether it is working
Six months in, you should be able to answer yes to these:
- Is there a list of what runs in the company, with an owner for each item?
- Were this half’s contracts reviewed before they were signed?
- Does the IT budget separate what is required from what is wanted?
- Is the IT lead putting out fewer fires than before?
If all four are still no, the problem is not the lack of a technology director. It is that the one you have is not directing.
A warning about us
We also build software, so we have exactly the conflict of interest from point one. When we act as fractional CTO, every recommendation to build something comes with the alternative of buying it or not doing it, and everything we write is yours to take to another vendor.
Where we come in
Fractional technology leadership is part of our technology consulting. We have worked with companies on the border for more than fifteen years, in Spanish and English, fifteen minutes from El Paso. If you want to see whether it fits, book a call; if you would rather start on your own, Chira asks the questions and tells you in writing what to fix first.