Indie Hackers — what commenting there actually gave us

We spent time commenting on Indie Hackers. Here’s the honest return.

Not leads. Not signups. Not revenue. And we’re not treating it as market validation.

What we did get was better product evidence.

In one thread, a builder took a suggestion to add a deliberately failing fixture and implemented it. That exposed a real problem: the checker was not reading the external fixture at all. They fixed the path and added an assertion that the test must fail for the intended rule.

That turned a comment into a concrete reliability improvement.

The useful lesson for us was not “comment more.” It was this:

A green test only means something if you can show the exact bad case it catches.

That sharpened the questions we now ask about reliable AI-assisted systems:

• Can every important rule be challenged by a known-bad control?
• Can we keep “verified” separate from “accepted”?
• When a requirement changes, can we show which previous checks became stale?
• Can uncertainty carry a reason and a next action instead of a cosmetic confidence score?

The sample is small and not representative. These conversations do not prove demand or willingness to pay.

But they are more useful than a pile of reactions. A comment becomes valuable when another builder can use it, test it, and report what changed.

So far, that is what commenting on Indie Hackers has given us: fewer vague assumptions, one clear adoption signal, and better product tests to run next.