How to make technology decisions without a CTO

A surprising number of companies face their biggest technology decisions with no CTO in the room. The CTO left and the search is running. The founder is commercial, not technical. The board has deep financial experience and no engineering experience. The decision still has to be made.

I see the same failure mode in each case: the decision gets made on confidence rather than evidence. The most assured voice wins — often a supplier, sometimes the loudest engineer, sometimes a deck. The cost of being wrong arrives a year later, when it is hard to undo.

You do not need a CTO to avoid this. You need a method.

Write the decision down

One page. What are we deciding? By when? What happens if we do nothing? Most technology arguments blur three or four decisions together — a platform choice, a hiring question, a budget question. Separate them. Some will turn out not to be urgent at all.

Price the downside, not just the upside

Every proposal you receive will describe the benefits. Ask instead: if this goes wrong, what does it cost to unwind? A tool you can drop in a month is a different class of decision from a platform migration or a five-year contract. Spend your scrutiny in proportion to the cost of reversing.

Demand evidence, not opinions

For any claim that matters, ask what evidence sits behind it. "The platform won't scale" — says who, based on what measurement? "We must rebuild" — what specifically fails today? Engineers, like everyone else, hold opinions with more confidence than the data supports. The question is not hostile. It is the job.

Get an independent view for the big ones

Suppliers are selling. Internal teams have preferences and careers. For a decision that is hard to reverse — a rebuild, a replatform, a major contract, an acquisition — pay someone with no stake in the outcome to examine the evidence and give you a written opinion. It is a small cost against the size of the mistake it prevents. That independent view is most of what I do as technology advisory.

Agree the exit before you commit

Whatever you choose — a supplier, a build, an interim leader — agree upfront what done looks like and when you will review it. Decisions without review dates become permanent by default.

When to borrow leadership instead

Sometimes the honest answer is that the company needs technical leadership, not another one-off decision. That does not have to mean a full-time hire before you are ready. A fractional CTO — a few days a month, defined outcomes, an agreed end — can hold the technical line through a search, a growth phase, or a recovery, and help you hire the permanent person properly.

The common thread in all of it: technology decisions reward the same discipline you already apply to financial ones. Write them down. Price the downside. Follow the evidence.