For us that was finding the first testers and building models from scratch that will outperform the available ones out there.
Now, our next challenge is breaking the 200 users mark and starting to charge users.
@ayhan_dzhemalov I see many teams make a portion of their software as open source to get more attention and SaaS with a pricing
So those who needs free will use open source others will buy from SaaS. This mostly done for developer tools
@ashmil_hussain I see, yea thats an option, however, we are not struggling that much… there are pros and cons of having an open source project.
With us, we are trying to be the first in the world to build one of our solutions and it just doesn’t make sense to have an open source project.
Seems to be a theme here in the comments... Moving from building --> acquisition.
Many times that's a result of staying in our comfort zone of 'building'. Carve out time in your calendar, 1 hour per day, shut everything off except for acquisition activities.
Developing a product that adopts and gets shaped based on users' needs.
It is quite easy to get lost in the details of perfecting what a pipeline created months if not years ago when it comes to feature/functionality release/improvements. However, responding to actual needs and trends by providing a solution at the right time is quite challenging without cannibalizing your product.
Promotional marketing is so important, I once developed a product in just 1 week and I had no idea how to promote it, but it did end up getting 1000 natural growth users!
The most challenging aspect of building our SaaS was finding the right balance between customer needs and technical constraints. We wanted to create a product that was both powerful and easy to use, but that proved to be a difficult task. In the end, we had to learn to compromise and prioritize certain features over others.
Onepane