The weeks nobody posts about — what solo building actually feels like in the middle

I follow a lot of indie hackers online.

I see launch posts. MRR updates. "We hit X users" posts.

What I almost never see is what it looks and feels like in the middle.

Between the launch and the milestone. Between the idea and the first user. Between the rewrite and the re-launch.

So here's what the middle actually looks like for me.

The code weeks

These are the weeks where I'm deep in the codebase. Not shipping. Not talking to users. Just building.

These weeks feel productive in the moment. But they're also the weeks I'm most at risk of building in the wrong direction without noticing.

I've learned to force myself out of pure build mode once a week — even just to write down "what problem am I solving this week and is it still the right problem?"

The flat weeks

These are the weeks where I ship something, share it, and... nothing.

No signups. No feedback. Flat analytics.

These are the weeks where most people quit. And I understand why. The silence is genuinely demoralising.

What I've learned: flat doesn't mean wrong. It often just means you haven't found the right distribution yet. The product isn't the only variable.

The rabbit hole weeks

These are the weeks I disappear into a technical problem that isn't actually the most important thing to solve.

"I need to optimise this query before it becomes a problem" — for a product with 12 users.

"I should set up proper logging infrastructure before going further."

These feel like productive weeks. They're often procrastination wearing a technical hat.

I now try to ask: "Is this the most important thing for the product right now, or is this the most comfortable thing?"

The doubt weeks

These happen after the flat weeks, usually.

"Is this worth doing?"
"Should I build something different?"
"Is there something structurally wrong with the idea?"

These weeks are useful if you engage with the doubt honestly instead of suppressing it. Sometimes the doubt is pointing at something real. Sometimes it's just the natural trough that comes before momentum builds.

The hard part is telling the difference.

What I've found that helps: write the doubt down. Make it specific. "I'm worried that the market is too small" is more useful than a vague feeling that something is wrong.

A specific worry can be tested. A vague feeling just eats at you.

What nobody tells you about building:

The middle is the actual work. Launches are moments. The middle is months.

Learning to build through the middle — through the flat weeks, the doubt weeks, the rabbit hole weeks — is the actual skill of indie hacking.

The technical skills get you started. The middle is where persistence and self-awareness matter more.

If you're in the middle right now — what's it looking like? I'm genuinely curious.