3 ms·
Skip team features until a customer (or somebody ready to pay) is asking for it. In our B2B SaaS we have Fortune 100 companies as customers and even they are so
by mtmail 4y ago
Skip team features until a customer (or somebody ready to pay) is asking for it. In our B2B SaaS we have Fortune 100 companies as customers and even they are so far fine with individual accounts. We implemented two-factor-auth after customer requests but it's shocking how few of our users actually switch it on, definitely not relevant to grow or get more sales.
I can't answer it for B2C, that growth might work different.
Start with a framework that includes authentication. It will save weeks of work. https://github.com/smirnov-am/awesome-saas-boilerplates https://github.com/smirnov-am/awesome-saas-boilerplates
Good luck for your MVP/launch.
- PaulHoule 4y agoMy hot take is that collaborative features make your marketing problem worse. If your product is single user then a user who buys in gets the full value of the product. If it is multiple user then you have to make much bigger sales or attract more users overall to unlock the value. That said, sometimes collaboration is a killer feature. Lately I have developed a content-based recommendation system which works OK but probably the collaborative recommendation systems that are more widespread would be seen as better by most people.
- simaogdias 4y agointeresting. This is a new take and it makes sense. We need to sit down and assess if collaboration is critical or a dealbreaker to get the value out
- simaogdias 4y agothe way you showcase the scenario, makes lot of sense! We are torn so this definitely helps Thanks for the insights and the boilerplate repo, gold