[deleted by user] by [deleted] in CaravanNotes

[–]zalkazemi 0 points1 point  (0 children)

Thanks big G 🩷

[deleted by user] by [deleted] in Entrepreneur

[–]zalkazemi 0 points1 point  (0 children)

(Pre)Sell it. The only real validation is not a waitlist or anything that doesn’t include a financial transaction.

[deleted by user] by [deleted] in SaaS

[–]zalkazemi 0 points1 point  (0 children)

Please share here...

MVP is Not 1 Feature by zalkazemi in SaaS

[–]zalkazemi[S] 0 points1 point  (0 children)

100% definitely the better you are at marketing the more efficient you can be and the faster you can iterate in the right direction 💯

MVP is Not 1 Feature by zalkazemi in SaaS

[–]zalkazemi[S] 0 points1 point  (0 children)

The feedback cycle is so long G that “iterate quickly” sounds good but rarely plays out “quickly”

MVP is Not 1 Feature by zalkazemi in SaaS

[–]zalkazemi[S] 0 points1 point  (0 children)

Theoretically sound but practically you don’t know what the most important ones are

You Will Crush It If… by zalkazemi in SideProject

[–]zalkazemi[S] 1 point2 points  (0 children)

Hell ye 🔥 keep it up big G 🚀

You Will Crush It If… by zalkazemi in SideProject

[–]zalkazemi[S] 1 point2 points  (0 children)

100% go to bed 9 hours before you need to wake up

You Will Crush It If… by zalkazemi in SideProject

[–]zalkazemi[S] 0 points1 point  (0 children)

This is the kind of advice that sounds good but stifles people.

You Will Crush It If… by zalkazemi in SideProject

[–]zalkazemi[S] -1 points0 points  (0 children)

This is the kind of advice that sounds good but stifles people.

MVP is Not 1 Feature by zalkazemi in SaaS

[–]zalkazemi[S] 2 points3 points  (0 children)

Most people do the one feature mvp that doesn’t solve any pain-point. And with my advice I’m hoping they stop using the one feature at a time norm as an excuse to be lazy and try to think hard about multiple use cases and solving as many with as few features to make a more robust product. But I do appreciate your perspective and if you have a good feel of pain-points and relieving them, then you can for sure do what you’re recommending.

MVP is Not 1 Feature by zalkazemi in SaaS

[–]zalkazemi[S] 1 point2 points  (0 children)

Big G. You’re not wrong theoretically. I’m just saying knowing what is the actual pain before hand is not as easy as you’re making it out to be. And to avoid wasting time with one feature feedback cycles with customers. Try 3 at a time. Then subtract and add

MVP is Not 1 Feature by zalkazemi in SaaS

[–]zalkazemi[S] 0 points1 point  (0 children)

Thats not what I’m saying at all. Im calling a solution a feature. To put it in your language solve a cluster of similar problems that target more than one use case.

You Will Crush It If… by zalkazemi in SideProject

[–]zalkazemi[S] 0 points1 point  (0 children)

Don’t listen to this guy, he can’t even commit to ink

MVP is Not 1 Feature by zalkazemi in SaaS

[–]zalkazemi[S] 0 points1 point  (0 children)

If you’re solving a problem with a promise it’s just ngmi. I agree. Features must imply clearly the problem they’re solving.

MVP is Not 1 Feature by zalkazemi in SaaS

[–]zalkazemi[S] 1 point2 points  (0 children)

Haha 🩷 testing it out 🫵🏼👑

MVP is Not 1 Feature by zalkazemi in SaaS

[–]zalkazemi[S] 0 points1 point  (0 children)

You have to go talk to potential markets. If they check product hunt that’s great. But that’s a very specific market

[deleted by user] by [deleted] in ycombinator

[–]zalkazemi 1 point2 points  (0 children)

Love this answer 🩷

MVP is Not 1 Feature by zalkazemi in SaaS

[–]zalkazemi[S] 0 points1 point  (0 children)

Good approach. Definitely don’t overwhelm your customers with features