The hardest part of being a solo founder wasn’t what I thought

The hardest part of running a one-person company is not the workload. It is choosing the right work.

What I expected

When I started, I assumed the hard part would be wearing every hat. CEO. CTO. CMO. VP Product. Four jobs in one chair, no one to delegate to, no one to escalate to.

All of that while working full time as a lecturer and researcher at a college.

The workload is real. It is not the bottleneck.

What is actually hard

A solo founder is one person, and that person has a default mode. Mine is building. I want to ship features, fix bugs, and tighten infrastructure until it hums.

Building feels productive. It is measurable. It is satisfying. At the end of a coding day the diff is real, the bug list is shorter, the system is leaner.

The work that pays the bills feels like distraction

Sales conversations. Watching the market. Learning what customers actually need. Talking to people instead of typing into a terminal.

This work has no diff at the end of the day. No ticket closed, no graph that moves on a dashboard you control. It feels soft, slow, like you are getting away with something.

It is also the work that decides whether the product survives.

The real lesson

A perfectly built product nobody wants is worse than a half-built one customers are pulling out of your hands.

The hardest part of being solo was not doing everything. It was resisting the role I am best at when another role needed me more.

Building is the comfortable seat. Talking to customers is the uncomfortable one. The discipline is to spend more time in the uncomfortable seat than feels natural.

A small weekly check

Each Friday I ask one question: did I spend more time this week with code or with customers?

If the answer is always code, that is the bug to fix.