Ankit Pandit

When I'm trying a new SaaS tool, I'm much more interested in signing up if I've already seen what it can actually do. Being asked to fill out a form before seeing any real value can make me leave before giving the product a chance.

I get why founders ask people to sign up upfront, though. It helps them save their work, personalize the experience, and understand who's using the product. And some tools need a bit of setup before they can show useful results.

Personally, I like the idea of letting someone try one small part of the product first, then asking them to create an account when they want to save their work or go further. But I'm not sure that approach makes sense for every type of SaaS.

I'm trying to get better at competitor research for SaaS products, but there's one thing I keep struggling with: knowing which updates are actually worth paying attention to.

A competitor might change their pricing, launch a new feature, redesign their website, or announce an integration. It's interesting to see all these changes, but I don't think every update should influence what you build.

My current thinking is that a change matters when it affects how a product is positioned or what customers can do with it. I'm still figuring out how to separate those signals from the noise.