Martin Gulp

I think many tech product builders, including myself, can easily fall into tunnel vision, whereby I am overly convinced that the feature we re working on is clearly justified. With vibe-coding tools, the cost of building new features has also dropped dramatically. But lower development costs didn't seem to translate to product growth in my organization. Many newly launched features still receive little adoption, or have a hard time "syncing" with the rest of the product.

So I m curious: how do you decide when a feature is actually worth building? Do you wait for repeated user requests, test a lightweight version first, trust your product instinct, or rely on behavioral data before committing?

A big part of my week is spent talking to early-stage founders about how they handle login, access, and identity, and there is a pattern I keep noticing that I want to understand better.

Almost everyone puts auth off at the start, which honestly makes sense when you are still trying to prove the product matters at all.

we just officially crossed 100+ signups. <3