Building with no audience, no signal, and no external pressure

Building with no audience, no signal, and no external pressure. What that’s actually like.

There’s a version of this post that’s about discipline and systems and how I stay productive. That’s not this post.

This post is about what it’s actually like to build something in deliberate obscurity — no users yet, no external validation, and no forcing function except the one you made up for yourself.

It’s strange. I’ll say that first.

The silence is the point, until it isn’t

The blog-first approach I’m running is intentional. Don’t announce until the work is there. Build the runway before you reveal the plane. Let the content accumulate domain authority before the LinkedIn post lands. The constraint is a strategy.

But strategy doesn’t change what the silence feels like. You ship a product and nothing happens. Not negative feedback. Not positive feedback. Just the indifferent silence of the internet, which has no idea you exist.

In a normal product launch, the silence is a failure signal. Here it’s expected — I’ve deliberately not told anyone. So the silence is correct. But the nervous system doesn’t know that. It just registers: you shipped something and nobody noticed.

You have to keep building anyway. Not because you’re sure it’s working, but because the alternative — waiting for external validation before continuing — is a slower way to fail.

The specific cost of building alongside a full-time job

Building a product portfolio while employed full-time is a split-attention problem that doesn’t resolve cleanly. The job has real demands. The products have real demands. Neither set of demands pauses while you service the other.

What this creates in practice is a specific kind of cognitive overhead: the context-switching cost between two completely different problem spaces, running in parallel, with no clean boundary between them. It’s not unmanageable. But it’s also not free.

The tradeoff I made is deliberate. Staying employed removes financial pressure from the product decisions. I’m not building under desperation. I can make rational calls about what to keep and what to kill without the distortion of needing any of it to work immediately.

That’s the deal. The overhead is real. The optionality it buys is also real.

Five products with no marketing and no users

Here’s what’s true right now: Gestalt is live. Protocol is live. Neon Oracle is nearly live. Sila is built. None of them have been marketed. None of them have meaningful user numbers.

This is not a failure state. It’s a deliberate sequencing decision — build the content runway first, establish methodology credibility, then surface the products as proof of what the methodology enables.

That logic is sound. It is also uncomfortable to sit inside when you’re the one who built the products and you’d like to know if anyone finds them useful.

The thing I keep returning to: the products exist. They work. They’re solving real problems — problems I had, which means problems other people have. The question is whether I can reach those people with the right framing before the kill criteria clock runs out.

Three months post-launch with no paying customers is my pre-committed exit condition for any product. The timeline is running. The marketing hasn’t started yet.

That’s the honest state of things.

View all active products