By Andreas Pettersson, Founder, Leaders ADAPT
Nobody wakes up and decides to hire a CTO. What happens is smaller. A vendor sends a renewal that is 40 thousand dollars higher than last year and you sign it because you cannot tell whether the alternative is better. Your insurer sends a security questionnaire and you forward it to the one person who knows the passwords. Your head of sales has started pasting customer emails into an AI tool, and you are not sure whether that is clever or a problem. None of these is a crisis. Together they are a pattern, and the pattern has a name. You are the technology department, and you are not qualified for the job.
I know the feeling from the other side. At Arcules I held the CEO, CFO and CTO seats at once for a stretch, in a company that sold technology. Even there, the hardest technology calls were not technical. They were about money, risk and who owns what. In a company that does not sell software, that is even more true, and the owner is usually the last person to notice the seat is empty.
The right time to hire a CTO is when technology decisions begin to carry real money or real risk and nobody in the company is qualified to make them. The right kind of CTO depends on how often those decisions arrive.
Quick answer: Hire technology leadership when platform, vendor, security, data or AI decisions start carrying real money or risk and nobody inside can judge them. Pick the shape by frequency. Daily tickets need an IT manager or provider. A few big decisions a quarter need a CTO advisor. Weekly decisions with nobody in the seat need a fractional CTO. Daily strategy and an engineering team need a full time CTO.
Leaders ADAPT places technology leaders from its own bench and stays accountable for the engagement, priced as a fixed fee quoted after the first call. Every outside figure on this page belongs to its publisher, is linked, and was read in October 2026. If their page has changed since, their page wins. Nobody named here pays us.
The question is not whether, it is which seat
Most owners ask "do I need a CTO" as a yes or no question. It is the wrong frame, and it leads to two expensive mistakes.
The first mistake is hiring too much. An owner reads that every growing company needs a chief technology officer, recruits one at a full executive salary, and discovers six months later that there are four real decisions a quarter and the new CTO is rewriting the intranet to stay busy. Good people leave seats like that.
The second mistake is hiring too little. The owner promotes the IT manager, or extends the managed service contract, and calls it technology leadership. The tickets get answered. The strategy never arrives, because nobody was hired to provide it.
Here is the frame I use instead. Technology work in a non tech company comes in two kinds. There is keeping things running, which is frequent, operational and measurable. And there is deciding what the systems should be, which is less frequent, expensive when wrong and hard to measure. The first is an IT job. The second is a CTO job. Your question is how much of the second kind you have, and how often it shows up.
Eight signs a non tech company needs technology leadership
These are the signs I listen for when an owner describes their week. Count how many are true for you.
1. You sign technology contracts you cannot evaluate. Renewals, new platforms, the ERP upgrade. You compare price because price is the only column you understand. The vendor knows this.
2. One person holds the keys. The domain, the cloud account, the admin passwords and the backup schedule live with one employee or one contractor. If that person left on Friday, Monday would be ugly. Our page on key person risk explains why a buyer later treats this as a price question.
3. Security questions arrive and nobody owns the answer. Cyber insurance forms, customer questionnaires, a bank asking about controls. Verizon's 2025 Data Breach Investigations Report found ransomware in 44 out of every 100 breaches it studied, a median ransom payment of $115,000, and third party involvement in breaches doubling to 30 out of 100. Those are not big company numbers. They are supply chain and small company numbers.
4. Departments are buying their own tools. Sales has one CRM, service has a ticket system, operations has spreadsheets, and nobody can produce a customer list everyone agrees on. Every tool was a reasonable choice. The sum of them is not.
5. An AI project has no owner. Someone ran a pilot, it looked good in a demo, and it has not turned into anything. Or worse, nobody ran a pilot and staff are using whatever they found.
6. Your reporting depends on one heroic spreadsheet. The numbers you run the company on are assembled by hand each month by someone who would rather be doing their real job.
7. A buyer, lender or board member asked a technology question you could not answer. Who owns the code? Where does customer data live? What happens if the main system goes down? If the honest answer was "let me find out," that is a sign.
8. You are spending more of your own week on technology than on customers. This is the one owners notice last. It is also the most expensive, because your hours are the scarcest resource in the company.
One or two of these is normal life in a $10M company. Three or four means decisions are being made by default. Five or more means the technology seat is empty, and you are sitting in it.
Which kind of technology leader: four shapes
Once you know the seat is empty, the next question is the shape. There are four, and they solve different problems.
| Shape | What it solves | How often you need it | Who it fits |
|---|---|---|---|
| IT manager or managed service provider | Laptops, network, email, tickets, backups, patches | Every day | Every company, regardless of strategy |
| CTO advisor | A few large decisions a quarter, judged by someone who has made them before | One to two hours a week | A company with a capable person in the seat, or an owner who decides well with good input |
| Fractional CTO | Weekly decisions, vendors and a roadmap with nobody owning them | One to three days a week | A company with no technology leader and a growing decision load |
| Full time CTO | Daily strategy, an engineering team, technology as part of the product | Every day | A company whose product or delivery runs on software it builds |
A few notes on reading this.
The IT manager does not go away. Every shape above it still needs someone keeping the lights on. A fractional CTO who spends the day resetting passwords is a very expensive help desk. Fix the operational layer first if it is broken.
The advisor shape is underused. Many owners can make good technology decisions if someone with real experience sits next to them for an hour before they sign. That is the CTO advisor shape, and it is often the right first step for a company with fewer than four or five real decisions a quarter.
The fractional shape fits the empty seat. When decisions pile up weekly and nobody owns the vendors, the data or the roadmap between meetings, an hour of advice has nowhere to land. Someone has to be in the building. Our fractional CTO page covers what that seat owns, and the fractional CTO cost page covers what the market charges for it.
Full time is for companies where technology is the work. If you build and ship software to customers, or your delivery depends on systems your own engineers write, you need a technology executive every day. Most manufacturers, distributors and service firms between $5M and $50M do not, at least not yet.
The general version of this choice, across every executive seat, is on the fractional vs interim vs advisory page, and the full menu of shapes we work in is on Fractional Executives and Advisory.
What a full time CTO costs, and why the hire is hard
The full time seat is not cheap, and it is not easy to fill well.
The US Bureau of Labor Statistics lists chief technology officer as one of the titles in its computer and information systems managers group. It puts the median annual wage for that group at $175,140 in May 2025, projects employment to grow 16 out of every 100 jobs from 2025 to 2035, much faster than average, and lists five years or more of related experience as typical. That group includes IT directors at large firms, so treat the wage as a floor for an executive seat, before benefits, bonus, payroll tax and the months it takes to find the person.
The cost is not the main risk. The main risk is hiring the wrong profile. A software CTO from a venture backed startup and a technology leader for a 200 person distributor are different people. One builds product. The other chooses, integrates and governs systems someone else builds. Owners who have never held the seat tend to hire the impressive resume rather than the right one.
The pattern I have seen most often in companies this size is a mismatch rather than a bad person. The owner hires for the title, the new leader arrives with a playbook from a different kind of company, and a year later both sides are frustrated. A technology leader who has worked inside an owner led company knows that most of the job is choosing and governing, not building.
My rule: do not write a full time CTO job description until someone who has held the seat has spent a quarter inside your company. You will write a much better one, and you may discover you do not need it yet.
Where AI fits in the decision to hire a CTO
In 2026, AI is the trigger for about half the technology leadership conversations I have with owners. The pattern is consistent. A few tools are on trial, a vendor is pitching a platform, staff are experimenting on their own, and nobody can say which of these is worth money.
The adoption is real. McKinsey's 2025 survey on the state of AI, with 1,993 participants, found that 88 out of every 100 respondents said their organizations use AI, while only 7 out of 100 said it had been fully scaled across the organization. Almost everyone is trying. Very few are getting it into the way the company actually runs.
That gap is a leadership gap more than a tool gap, and it changes how you should read the eight signs above. If AI is the main reason you are thinking about a CTO, ask three questions before you hire anyone.
First, is the data ready? If customer, pricing and operations data sit in six systems with no owner, an AI hire will spend a year on plumbing. That is still CTO work, but you should hire for it knowingly.
Second, who decides what data goes into which tool? Someone has to write that rule before the next customer list ends up in a public chat window. That is a security decision as much as an AI one, and the FTC's cybersecurity basics for small business still apply underneath it: automatic updates, multi factor authentication, a plan for the day something goes wrong, and staff who know why it matters.
Third, what stays with people? Decisions about who you hire, which customers you keep and what you promise do not go to a model. I wrote the longer list on what not to delegate to AI. If your company runs on EOS, the AI for EOS companies guide shows where the tools attach to the scorecard and meeting rhythm. And the free AI readiness assessment on this site will tell you in a few minutes whether your gap is data, people or leadership.
When the honest answer is that the AI work needs building, not just deciding, it often belongs with a technology leader who can do both. At Leaders ADAPT that work runs through the Fractional AI Executive offer, delivered partly with technical partners from the bench.
What hiring a CTO does not fix
I tell owners this before they spend a dollar on the seat.
Hiring a CTO does not fix an owner who will not let go of technology decisions. If every vendor choice still needs your signature after a week of second guessing, you have hired an expensive advisor to a bottleneck. The two things owners most often tell me when they book a call are that they hate one on ones and that delegation boomerangs back. Both show up the day a technology leader starts.
It does not fix a leadership team that disagrees on priorities. If sales wants one thing, operations wants another and finance wants to spend nothing, the new CTO spends their week refereeing. That is leadership team development work, and it comes first.
It does not fix a broken operational layer. If the help desk is failing, the backups are untested and the laptops are five years old, fix that with an IT manager or a better provider. A strategist on top of a broken foundation produces strategy nobody can act on.
And it does not fix a business model problem. If the company is losing money on its core work, no system will save it. A good technology leader will tell you that in the first month, which is one way to know you hired a good one.
Who is on the bench for this
Leaders ADAPT is the CEO's bench. I build the leader, and when the leader needs a technology seat filled, in whichever of the four shapes fits, I bring someone from the bench and stay in the room.
Sergey Dmitriev is the fractional CTO and AI systems partner on the bench. Sergey builds and runs the AI and data work Leaders ADAPT delivers, including digital twin and company knowledge systems, and trains leadership teams on AI tools with me. In the hiring decision, Sergey is the person who reads your systems, your vendors and your AI experiments and tells you, plainly, whether you need an advisor, a fractional seat or a full time hire, and what the job description should say if it is the last one.
Thor Legvold is the leadership psychologist on the bench. When the question is whether your strong IT person can grow into the seat, or whether a candidate will fit the way your leadership team actually works, Thor runs the assessment before anyone signs an offer.
Every engagement runs through Leaders ADAPT. I take the first call, I match the partner, and I stay accountable for the outcome.
When to hire a CTO FAQ
When should a non tech company hire a CTO?
When technology decisions start to carry real money or real risk and nobody inside the company is qualified to make them. Typical triggers are a platform contract you cannot evaluate, systems that live in one person's head, a security or insurance question you cannot answer, an AI project with no owner, or a buyer asking about technology. The kind of leader depends on how often those decisions arrive.
Do I need a CTO or an IT manager?
An IT manager keeps today's systems running. A CTO decides what the systems should be next year and why. If your problems are tickets, laptops and backups, hire or contract an IT manager. If your problems are platform choices, data, vendors, security posture and AI, you need CTO judgment, which may come from an advisor or a fractional CTO before a full time hire.
Can a small company afford a CTO?
Most companies between $5M and $50M in revenue cannot justify a full time CTO, and do not need one unless the product is software. They can afford CTO judgment in smaller shapes, an advisor for one to two hours a week or a fractional CTO for one to three days a week. The question is how often decisions arrive, not the size of the title.
What are the signs a company has outgrown its IT provider?
The provider answers tickets well but nobody tells you what to stop buying. Renewals arrive and you sign them because nobody can compare options. Your sales or operations leader picks tools without anyone checking the data. Security questions from insurers or customers go unanswered. When the provider is your strategy by default, the company has outgrown that arrangement as its only technology voice.
Should my first technology leader be fractional or full time?
For most owner led companies outside software, fractional or advisory first. You learn what the seat needs before you write a job description, and you get senior judgment while the decision load is still light. Move to full time when technology decisions arrive daily, when you have a team of engineers to lead, or when the part time fee nears a full salary for the same scope.
Is promoting my best IT person to CTO a good idea?
Sometimes. The person who built your systems knows them better than anyone, but running systems and deciding strategy are different jobs. Test it before you change the title. Give them one real decision with an outside advisor next to them, watch how they handle vendors and the leadership team, and decide after a quarter. A clear no is kinder than a failed promotion.
What does a CTO do in a company that does not sell software?
In a manufacturer, distributor or service business, the CTO owns the systems map, vendor and platform decisions, data and reporting, security basics, the technical side of AI adoption and key person risk in IT. The job is less about writing code and more about making sure the technology the company buys actually serves the way it makes money.
Does a business buyer care whether I have a CTO?
A buyer cares less about the title and more about what it covers. They check who owns the code, accounts and data, whether two people can run every critical system, whether basic security controls are in place, and what AI tools touch customer data. A company with no technology leader often has no answers to those questions, and unanswered questions tend to lower an offer.
Count the decisions before you choose the title
The title is the last thing to decide. Start with the decisions.
Tomorrow morning, take a sheet of paper and list every technology decision you made, delayed or avoided in the last 90 days. Contracts, tools, security questions, AI requests, data problems, people. Next to each one, write how much money or risk it carried and who in the company could have made it without you. If the list is short and the stakes are low, you need a better IT provider. If the list is short and the stakes are high, you need an advisor. If the list is long and nobody but you can own it, you need a technology leader in the building, at least part of the week.
What the first conversation looks like
It is a 30 minute call with me, not a sales rep. Bring your list of technology decisions from the last quarter and a rough picture of your systems and vendors, in whatever state they are in. I will tell you which of the four shapes fits, whether that is an IT fix, an advisor, a fractional CTO or a full time search, and if the honest answer is a better managed service provider, I will say so.
If a seat from the bench is the right move, Sergey joins the second call, we agree the scope and the three outcomes we write down, and the fee is fixed and quoted after that call. I stay in the room for the length of the engagement.
Your step for tomorrow morning: take the free assessments so I can see how much of the company still runs through you, then book a fit conversation. Hiring a CTO is the easy part. Knowing which kind is what the call is for.
