Buy judgment, not a seat

Hiring a full-time CTO can feel like the grown-up move. The goal is to put someone in the chair, put the title on the about page, and make the anxiety go away.

Often the result is a salary, a recruiting cycle, and six months of orientation. The business still does not have a decision.

A CTO is not the primary need. The need is someone who will name what not to build.

The job is smaller than the title

Early on, the useful work is narrow. What is the one technical bet that unlocks the next 90 days? What should be refused? Who should write the first version, and who should not be in the room yet?

A strong engineer who has never owned a P&L will optimize for craft. A marketplace CTO who needs a seat will optimize for staying. Neither is automatically wrong. Neither is what a funded founder usually needs in month three.

The spec for the role should be written after the work is known, not before.

Judgment now, a seat later

Fractional leadership is a way to buy judgment without locking the org chart. It provides architecture, a written case for change, and continuity until a search partner runs a process.

If the stack is a pile of local tools held together by the one person who "knows how it works," the problem is not hiring. The problem is visibility. Hire the seat after the choke point is named. Otherwise the new CTO inherits folklore and spends a year redrawing it.

When to hire the seat

A full-time CTO is needed when the work is no longer a sequence of bets. It becomes a function: hiring, vendor leverage, and a roadmap that must survive the founder being on a plane. That is a real job.

Until then, avoid staffing a department that cannot be described. Pay for the decision. Keep the option to hire when the case is obvious.

Titles are cheap. Wrong titles are expensive.