I’m building infrastructure, not a product, and that’s been harder to explain than to build
I shared a build update yesterday and noticed something interesting.
People don’t react to this like a typical product. They react like it’s already operating.
There’s no launch funnel here. No polished onboarding. The system runs whether anyone is watching or not.
That’s made it surprisingly hard to talk about.
It doesn’t sit cleanly in familiar buckets:
Not SaaS (no linear user journey)
Not content (generation isn’t the point)
Not tools (very little configuration)
Not community (yet)
It’s closer to infrastructure you explore than software you adopt. I’m documenting it publicly because I’m still pressure-testing:
how builders describe systems that don’t ask permission to exist
whether “usable” can come before “explainable”
and how others have handled projects that resisted neat categorization
No pitch. No ask. Just sharing the shape of the problem and continuing to ship.
If this resonates, I’m curious how you framed it when you ran into the same wall.
If not - all good. Back to work.
