Should I Hire a CTO or Find a Technical Cofounder?

The question founders almost always ask me is the wrong question. They ask: should I hire a CTO or find a technical cofounder? What they mean is: how do I get technical talent into this company? But the real question is different: what kind of technical relationship does this company actually need to do what I cannot do?

I was not a software engineer. I could not write code. But I understood, better than most engineers I worked with, what the product needed to feel like, what problem it was solving, and what compromises were unacceptable. What I needed from Wozniak was not someone who would take my requirements and implement them. I needed someone who saw the problem the same way I did and had the obsession and the capability to solve it in a way I could not. That is a different relationship from a CTO.

A CTO is a role. A technical cofounder is a person who shares the problem with you. The distinction matters enormously. A CTO will ask: what do you want me to build? A technical cofounder will ask: are we solving the right problem? The second question is the more valuable question, and it requires a fundamentally different kind of trust — a trust that goes in both directions, that tolerates disagreement, and that does not reduce to reporting relationships.

The founders who hire a CTO when they need a technical cofounder tend to discover the gap at the worst possible moment: when the company needs to make a hard technical decision that will determine its architecture for the next five years, and the CTO defers to the founder's business judgment rather than asserting the technical reality that would change the business decision. A CTO who is an employee does not own that moment. A cofounder does.

My counsel is direct: if the technical problem is hard enough that the right answer to it is genuinely uncertain — if building the product requires someone who will feel personally responsible for the outcome, who will lose sleep over a wrong architectural decision, who cannot walk away when it gets hard — then you need a cofounder, not a CTO. If the technical problem is well-understood and the challenge is execution rather than invention, a talented CTO can lead it. The distinction is between invention and execution. Know which one you are doing.

Jobs has described the ideal. I will describe the constraint. You are not choosing between a cofounder and a CTO in the abstract. You are choosing within the limits of who will agree to each arrangement and at what cost. This is a political problem, not a philosophical one.

The technical cofounder arrangement is fundamentally a power-sharing agreement. You are offering ownership — typically significant equity, potentially equal to your own — in exchange for commitment and shared risk. The person you are asking to take this arrangement must believe, as you believe, that the company will be valuable enough that the equity is worth forgoing salary, stability, and alternative opportunities. This is a strong belief to ask of a stranger, and it is not always available at the moment you need it.

Here is what founders do not examine carefully enough: the cofounder relationship is an arrangement that is very difficult to exit gracefully. A CTO who is not working out can be managed out of the company with legal and emotional difficulty but without destroying the company's ownership structure. A cofounder who is not working out is a crisis. You have given them equity in a cliff and a vesting schedule, and whatever your legal documents say, removing them from the company is a negotiation that will consume attention you cannot afford at a moment you cannot predict.

This is not an argument against finding a cofounder. It is an argument for being honest about what the arrangement costs when it works and what it costs when it fails. A cofounder is right when you are at the beginning of something genuinely uncertain, when the technical problem is central enough to the company's identity that ownership is the only arrangement that aligns incentives correctly, and when you have enough mutual trust — established through real work together, not through enthusiasm and good intentions — to make the decision together rather than one of you following the other.

A CTO is right when the technical challenge is real but the architecture is sufficiently understood that a highly skilled executive can lead it without co-owning the company's direction. A CTO is also right when you have not yet found the person who has both the technical skill and the personal alignment to be a genuine cofounder, and waiting is costing you more than moving forward with a strong employee would cost.

My test is power and trust: who controls which decisions, and do you have the specific evidence of trust — not the hope of trust — to share the decisions that the cofounder arrangement implies?

Both my colleagues have described the qualitative dimensions of this decision — Jobs on the nature of the relationship, Machiavelli on its political risks. Neither has asked the question that should come first: what does the evidence say about your company's specific technical needs, and which arrangement actually serves those needs?

I am not interested in generalizations about cofounders versus CTOs. I am interested in what is specifically true about this company, at this stage, with this technical problem. Let me be precise about the evidence I would want to see before recommending one arrangement over the other.

First: what is the actual nature of the technical challenge? There is a categorical difference between a company whose competitive advantage is a proprietary technical insight — a novel algorithm, a new approach to a hard problem, a technical capability that no one else has — and a company whose competitive advantage is execution on a known technical approach. The first kind of company needs a technical cofounder because the technical insight is the company's core asset and must be owned by someone who treats it as such. The second kind of company may be well-served by a strong CTO.

Second: what does the evidence say about the talent pool available for each role? The supply of people willing to take the technical cofounder arrangement at your specific company is real and finite. The supply of strong CTOs is also real and finite but has a different structure. For many companies, the honest evidence is that the people who would make great cofounders are not available at the stage and terms the company can offer, and the people who would make great CTOs are more accessible. This is a real constraint that the evidence reveals if you look for it.

Third: what does the evidence say about your own operating style with technical partners? Have you worked closely with technical people before? Do you know from experience whether you tend to complement technical judgment or override it? This matters because the cofounder arrangement requires you to genuinely share authority over decisions that will feel like product decisions but are actually technical ones. If the evidence from your own experience suggests you struggle with that kind of shared authority, the cofounder arrangement will create conflict that the CTO arrangement would contain more manageably.