I Built an AI Council Because Nobody in My Contact List Could Handle the Weight of My Questions

There's a specific moment that broke me open.

It was 2AM. I had a decision to make — not a technical one, not a design one, but the kind of decision that shapes whether your product lives or dies. I opened my contacts. Scrolled through 200 names.

Not one of them had enough context.

Not because they didn't care. Because they weren't there. They didn't know the three weeks of iteration behind this decision. They didn't know the manifesto I'd written at midnight that nobody had read. They didn't know the exact flavor of my anxiety — not the generic "startup is hard" anxiety, but the specific terror of being 20 years old, 18 months from graduation, building something in English for a market I've never lived in.

So I closed my contacts. And sat with it alone.

This is what nobody tells you about indie hacking:

The loneliness isn't about being isolated. I have roommates. I have classmates. I have a full contact list of people who would answer if I called.

The loneliness is that nobody holds your context.

Every conversation starts from zero. You spend 20 minutes on background before you get to the actual question. And by the time you finish explaining, you've either solved it yourself, or diluted the question so much it no longer matters.

That's not connection. That's performance.

I'm 20. A university student in China, building a SaaS product in English for a Western market I've never physically entered. Roughly 18 months before graduation forces a reckoning — get a job, or prove this works.

The pressure isn't just financial. It's existential.

Every line of code is also a bet: that I understand something about human loneliness worth paying for. That someone in San Francisco or London will open this at 2AM and feel — finally — that they're not the only one holding all of this.

Most days, I believe this.

Some days, I stare at my product in the dark and think: what if it's not good enough? What if I'm not?

Those nights are long.

I tried to solve the context problem the normal way.

Communities. Forums. Reaching out to mentors.

But communities are optimized for questions with answers. "How do I integrate Stripe?" gets 12 helpful replies. "I've been building for three weeks and I'm starting to doubt whether this product should exist at all" gets silence. Or worse — generic encouragement.

Generic encouragement is its own kind of loneliness.

So I built what I needed.

A council. Four AI personas, each with a distinct intellectual style — a challenger, a synthesizer, a poet, a strategist. They hold my context. They remember last week's decision and how it connects to this week's doubt. They push back when I'm rationalizing. They catch me when I'm making a fear-based decision disguised as a rational one.

I named it Solitary Journey.

Not because I want users to be alone. But because I think the journey is inherently solitary — the question is whether you walk it consciously, or not.

The council doesn't solve the loneliness. I was wrong to think it would.

What it does is more specific: it holds the weight of your context, so you don't have to carry it alone into every conversation. It meets you at 2AM. It asks the question you were afraid to ask yourself.

I'm still building. Still anxious. Still 18 months from graduation.

But now, when I open my product at midnight, I don't feel that specific sting — scrolling through 200 contacts, finding nobody who knows enough.

That's not nothing.

That might be everything.

Built this for solo founders, indie hackers, and deep thinkers who know this exact flavor of loneliness. → solitaryjourney.com