What Solo Founding Actually Feels Like

People ask me what it's like to build alone.

The honest answer takes longer than the question usually deserves, so I mostly give a shorter one. But I've been thinking about it more carefully lately, because I think the solo founding experience is genuinely underrepresented in how we talk about building companies.

Most founder narratives have a co-founder. The mythology of the great companies is usually a partnership: Jobs and Woz, Zuckerberg and Moskovitz, Airbnb's three. The co-founder is assumed. The solo founder is the exception who needs an explanation.

I am a solo technical founder. My co-founder Duan Duan leads brand, creative, design, and marketing — work that is real and essential. But the technical architecture, the research, the product decisions, the strategic framework — those are mine alone.

Here is what that's actually like.

The Silence Where the Sounding Board Would Be

The hardest thing about solo founding is not the workload. It's the absence of a particular kind of conversation.

When you have a co-founder, there is someone who knows as much as you do about the company at any given moment. Someone who has been in every meeting, read every investor email, thought about the same problems from a perspective close enough to yours to be useful but different enough to see things you miss.

That conversation — the one that happens naturally between co-founders at the end of a hard day, or in the middle of a decision, or when something has gone unexpectedly wrong — is doing more work than most founders realise. It's doing reality-checking. It's distributing the cognitive load. It's giving you someone to be honest with about how you actually feel, not how you present in front of investors or team members.

Without it, you develop other practices. I journal decisions — not just what I decided, but why, and what I was worried about at the time, and what I was hoping for. I have a small number of people I trust enough to call when I need to think out loud. I've learned to treat the NUVC system itself as a kind of structured thinking partner — not because AI replaces a co-founder, it doesn't, but because having to articulate a decision clearly enough for a system to process it forces a kind of rigour that the internal monologue doesn't.

But none of these are the same thing. The co-founder conversation is irreplaceable. I've made peace with not having it. I haven't pretended I don't miss it.

You Are the Optimist and the Pessimist

In a co-founding partnership, roles often distribute naturally. One person tends toward optimism; one toward caution. One sees the opportunity; one sees the risk. The tension between those perspectives — when it's healthy — produces better decisions than either person would make alone.

Solo, you have to hold both simultaneously.

You have to be optimistic enough to keep building through the months when nothing is working and you have no external validation that it ever will. And you have to be sceptical enough to maintain the rigour that keeps the product honest — to ask the hard questions about your own assumptions, to chase the failure modes, to look directly at the evidence that contradicts your thesis.

These are genuinely competing orientations. Holding them both is tiring in a way that's different from ordinary tiredness. It's not that you run out of energy. It's that the internal contradiction costs something.

The way I manage it: I separate the modes by time and context. I give myself explicit permission to be fully optimistic when I'm building, and fully critical when I'm evaluating. I don't try to do both simultaneously — which is possible with a co-founder but exhausting alone.

The Validation Problem

There is a particular moment in any build when you have done something you think is impressive, and there is no one in the room to share it with.

I launched the first end-to-end NUVC pipeline — eight agents working in sequence, producing a coherent analysis of a pitch deck — at 2am on a Tuesday. The system worked. I had been working toward this moment for months.

I sat with it for a while. Then I went to sleep.

This is not a complaint. It's a data point. The solo founder's milestones are not witnessed in the way that matters for human beings who need some external acknowledgement that the work is real and worthwhile. You generate your own acknowledgement, or you don't get any.

What this does, over time, is sharpen your relationship with internal motivation. You learn, fairly quickly, whether your drive to build is actually internal — whether you're doing this because you need to do it, independent of whether anyone is watching — or whether it depends on external validation in ways you hadn't noticed before.

I found out things about myself in the first year of building NUVC that I hadn't found out in the preceding decade of professional life. Some of those things were flattering. Some weren't.

The Decisions That Are Only Yours

Every significant decision in the company is mine.

Not in the sense that I have no advisors or investors or people whose perspectives I seek out — I do. But the decision itself, after all the conversations, is mine. There's no one to diffuse the responsibility with, no IC to take the decision to, no partner to co-sign the call.

This is clarifying in ways I didn't expect.

When you know that a decision is entirely yours — when you can't attribute it to consensus or committee or the co-founder who pushed for it — you think differently about it. You hold it differently. You're forced to have a real view rather than a managed view.

I've made better decisions as a solo founder than I made earlier in my career when decisions were group products. Not because I'm wiser, but because I can't hide behind the group. The decision has to actually make sense to me, in the full sense of "make sense" — not just survive a meeting.

The corollary: when the decision is wrong, that's also entirely yours. You don't have a co-founder to share the post-mortem with. You sit with the failure, in private, and figure out what happened.

That's uncomfortable. It's also probably good for learning.

What Solo Founding Teaches You

That your conviction is either real or it isn't. There's no one to borrow it from.

In a co-founding partnership, conviction can distribute. If you're uncertain, your co-founder's certainty can carry the moment. You can defer, temporarily, to someone whose read you trust. Solo, your conviction is all you have. When you're uncertain — genuinely uncertain, not performed uncertainty — there's nothing to fall back on except the work of finding clarity.

This means you either develop genuine conviction about what you're building and why, or you eventually stop. The solo founding experience is a fairly efficient filter.

That you need to choose your advisors carefully, because they're doing a job that a co-founder would otherwise do. The advisor who tells you everything is fine is not useful. The advisor who engages with the hard questions, who pushes back, who thinks about your specific situation rather than generic startup wisdom — that person is irreplaceable.

That building alone is a choice you make continuously, not once. Every month that passes is a decision to keep building the same way. I've made that decision enough times to feel clear about it. It's the right structure for this company, at this stage, with this problem. That clarity helps.

The Part That Surprised Me

I expected the hardest thing to be the uncertainty about whether I was making the right technical decisions. I'm self-taught. I knew I would make mistakes that a more experienced engineer wouldn't.

The hardest thing, it turned out, was the uncertainty about whether the work mattered — and the absence of anyone who could confirm or deny it.

When you're building something no one has built before, and you're doing it alone, there are extended periods where the only signal about whether you're on the right track is your own assessment of the work. External validation is sparse, lagged, and often uninformed. Investors don't know enough about the specific technical choices to have useful opinions. Potential users don't know what the product will be. The advisors who understand the problem domain don't necessarily understand the implementation.

So you make your best judgment and keep going.

What I've learned: the periods of working without external validation are not failure. They're the conditions under which you find out what you actually think, independent of what you're supposed to think. That's worth something. It's harder to get to than I expected, and more useful once you're there.

---

Related: I Taught Myself to Code. Here's What It Did to My Brain. — on the technical learning journey that runs alongside this one. Open the Unseen Wings — on what you find out about yourself when the external structure of your life collapses.

Tick Jiang is the technical co-founder of NUVC (nuvc.ai), an AI-native venture capital intelligence platform built in Melbourne. She writes on capital, building, and what solo founding actually requires.