From CTO to solo builder: what I lost and what I gained
The team, the budget, the leverage - all gone. But something else came back.
The first thing I noticed going solo was how loud my own decisions were. As a CTO, decisions get distributed. You set direction, others execute, others review, the system absorbs the variance. Solo, every call is yours and the feedback is immediate.
That's terrifying for about two weeks. Then it's freeing.
What I lost
Leverage, mostly. At Tiki, I could move an initiative forward by aligning three senior engineers. Now I move it forward by writing the code. The scope of what's possible in a week is much smaller.
I also lost the professional social layer - the alignment meetings, the architecture reviews, the sense of being accountable to a team. I didn't expect to miss that. I do, sometimes.
What came back
Taste. The ability to make small aesthetic decisions about a product without running them by anyone. The satisfaction of a clean system that I understand end-to-end because I built it. The joy of being the person closest to the problem, not the person several layers removed from it.
There's a particular kind of clarity that comes from having no one to blame. No team decision to point at, no legacy architecture to excuse. The code is the code and I wrote it.
The honest comparison
CTO work is more impactful in aggregate. More users reached, more engineers helped, more business value created. Solo work is more satisfying per unit of effort. Both are real. I needed to do both to know which one I wanted more.
I'm not trying to grow back into management. I'm trying to build things that last.