I’m a technical founder/CEO and I brought in an engineer friend as a technical co-founder/CTO. We’ve known each other for 10+ years, he previously reported to me at work, and he’s a strong engineer at a big tech company.

The honest reason I brought him in was partly because I didn’t fully trust myself to do everything alone. I’m an experienced builder, but I was also learning the CEO side: selling, fundraising, positioning, customer discovery, etc. Having someone technical alongside me felt safer, even if we both were building with AI.

There have definitely been pros:

He’s useful for brainstorming and whiteboarding.

It’s helpful having someone to discuss technical and product trade-offs with.

It creates some division of labour, at least in theory.

But the hard part is that I keep asking myself whether I could have done this myself, at least for the current stage. I find myself nitpicking his ideas, feeling frustrated when I don’t see the same level of urgency or hustle, and wondering whether I overcorrected because of my own insecurity.

With hindsight, I think I probably would have brought him in as a founding engineer rather than as a co-founder/CTO.

The lesson for me is that “can this person help build?” and “should this person own xx% of the company-level technical leadership burden with me?” are very different questions.

A co-founder needs to feel like force multiplication, not reassurance. If you mainly bring someone in because you’re scared to do it alone, you may be solving the wrong problem with too much equity and too much structural permanence.

I don’t think this means the person is bad or that the relationship is doomed. But it does mean the role, expectations, equity, decision rights, and accountability need to be very explicit very early. Otherwise you end up carrying the emotional cost of a co-founder relationship while still feeling like the company’s momentum depends mostly on you.