And I am out of ideas on how can I get feedbacks from our customers on this
What is your objective in launching this MVP? Is it to attract these users, learn more about what users want? For example, we're offering early access to some users to refine our platform.
Will your users be the buyers or do you plan to charge administrators/managers, etc?
You might want to look at GitLab's pricing model[0].
The goal of freemium is to get as many users as possible to test out our service. There is much to explain through Ads so the best option is to get them testing the service themselves.
I've too many ideas on my mind on which features should I limit or how should I, but I don't have any data or past experience with freemium models. also an idea that came to mind is to A/B test different models but I am not expecting much traffic at the beginning of our launching based on our budget.
and Yes users will be the buyers.
The hard part of asking for money is that most people will say "no." The easy part of "freemimum" is that you can pretend people will buy it later and rationalize continuing to work on the project.
Or to put it another way, the simplest thing that might work from a business perspective is charging money. And right now, you are thrashing around blindly with freemium which is harder to get to right, less informative, and produces less revenue.
If you don't know what people might pay for, then you don't know what problem you are solving. If you know what problem you are solving then you know what people might pay for and charging money gets you direct conversion of the might to a will or won't.
- You will offer a freemium model
- You don't have early users
- You want to get users to test your product and offer feedback
Lauching does not seem to be blocked with the pricing model given that you're offering a freemium, so I'd say don't worry about this for now: launch and learn. One assumption I'm making is that you can support many users as in the effect of an additional user is marginal. Why does it matter? It is not our case, since our product enables users to do compute intensive machine learning jobs through collaborative notebooks with automatic model tracking and deployment. This is why we're going with an "early access" type of offering and Slack channels to stay in touch with users and help them.
If an additional user doesn't imply a hefty price in compute/storage and you don't have to worry about Poisson distribution, then I'd say just launch it.
Again, this is my input given a set of hypotheses I'm making about what your product does. I may be wrong and you're welcome to correct.
