Here is a decision most owner-led businesses make several times a year without noticing they're making it: who decides which technology we use?
Not in the abstract. Specifically. Who evaluated the CRM before you signed the three-year contract? Who decided the new scheduling tool would integrate with the old billing system — and who noticed when it didn't? Who's deciding right now whether to build the client portal or buy one? Who owns the AI strategy your board, your partners, or your own curiosity keep asking about?
In a lot of companies, the honest answer is: the owner, in between everything else. Or the office manager who's "good with computers." Or the vendor, who has a clear opinion and an obvious interest.
That's not a criticism. Companies in the size range we work with rarely need a full-time technology executive, and hiring one would be hard to justify. But the decisions a CTO would make are still being made. They're just being made by someone without the time, the background, or the independence to make them well.
The decisions that compound
Most technology choices are small and reversible. A few are neither, and those are the ones that deserve senior attention.
Architecture. How your systems connect, where your data lives, and what talks to what. Get this wrong and every future project costs more, because everything has to work around the original mistake.
Vendor selection. The platform you choose today shapes your process, your costs, and your options for years. We made the case for scrutinizing that choice in Own the Platform, Not the Subscription.
Build versus buy. The three-door decision from Buy, Build, or Bother, made case by case, by someone who has seen both kinds of projects go right and wrong.
Security and compliance. Who has access to what, how data is protected, and what happens if something goes wrong. Easy to defer until the day it isn't.
AI strategy. Where AI actually helps your business, what order to do things in, and what to leave alone. This one is newer, moving faster, and surrounded by more sales pressure than any of the others.
What a fractional CTO actually does
A fractional CTO is a senior technology leader who joins your leadership team part-time and owns those compounding decisions. At Solve, that's typically four to twenty hours a week, over engagements that run a few months to a year.
In practice, the work looks like this:
- Sitting in on the decisions that shape the technology — before contracts are signed, not after.
- Evaluating vendors and proposals with no stake in the outcome.
- Setting a roadmap that sequences projects so each one makes the next one easier.
- Overseeing builds, whether they're done by an internal team, a contractor, or us.
- Owning the systems after launch, so there's always someone accountable — the gap we described in What Happens After Go-Live.
- Hiring, when the business is ready for its own technical staff.
When it's worth it
A fractional CTO earns their keep when a business is making technology decisions with real consequences and nobody senior is accountable for them. Some signs:
- You're about to sign a significant software contract and nobody on staff can evaluate it independently.
- You have several systems that don't talk to each other, and the workarounds are becoming someone's full-time job.
- You're considering a custom build and don't have anyone to oversee it.
- Your team is experimenting with AI and you'd like it to add up to something.
- Every technology decision still lands on the owner's desk — the bottleneck we wrote about in The Owner Is the Bottleneck.
When it isn't
If your technology is simple, standard, and working, you probably don't need one. A small firm running good off-the-shelf tools with no custom systems and no major decisions ahead should spend the money elsewhere.
And a fractional CTO isn't a substitute for doing the math. Every project they recommend should still clear the same bar as anything else: price the problem, price the fix, and only build if the return is clearly there. We hold our own work to a guaranteed 2× return; technology leadership should be held to the same standard.
Where to start
Write down the last five technology decisions your business made — purchases, builds, integrations, anything with a contract or a real cost. Next to each one, write who made it and how. If the answers are mostly "the owner, quickly" or "the vendor recommended it," that's a signal.
Our Fractional CTO page covers how the engagements work. If you'd like a quicker read on where technology could actually move the needle in your business, the AI Automation Scorecard takes a few minutes and gives you a ranked list of candidates.
You may not need a CTO. But the decisions a CTO would make are already on your desk. It's worth deciding who's going to make them.