@marc hahaha, i wrote eleven because i launched one already in jan(pwnremote.com). @levelsio also, told me that shipping 12 products is a great strategy. But you don't think, if a person is a newbie. They can't ship like 12 products in 12 months. For me the first product took me 2months to build.
I think you can build a product in a month. It's not about working fast, but more about adjusting the scope to the bare minimum so you can finish it within a month.
Yep, focus on the core part that provides value to the customer. Only must-haves, no nice-to-haves. And don't worry about it being scaleable, etc.
For example if you're building a $50/mo SaaS business, you don't need to ship the $50/mo recurring billing system until exactly one month after launch :) (and even then you can probably just charge their card manually, rather than having it fully automated)
Ok, i understand. But can you tell me why I shouldn't be doing that? You don't think a recurring billing system is good? Or you are saying that first check whether the users want to pay for the service or not?
I'm saying to focus on the things that deliver value to the users. Ignore everything else until it becomes a necessity.
The billing system is just an example of something many makers invest a lot of time on upfront when it's not necessary yet. (Because for the first couple dozen customers you can handle it manually.)
@marc hahaha, i wrote eleven because i launched one already in jan(pwnremote.com). @levelsio also, told me that shipping 12 products is a great strategy. But you don't think, if a person is a newbie. They can't ship like 12 products in 12 months. For me the first product took me 2months to build.
I think you can build a product in a month. It's not about working fast, but more about adjusting the scope to the bare minimum so you can finish it within a month.
So,That means not too many features. Make it minimum and simple. Got it. Thanks!
Yep, focus on the core part that provides value to the customer. Only must-haves, no nice-to-haves. And don't worry about it being scaleable, etc.
For example if you're building a $50/mo SaaS business, you don't need to ship the $50/mo recurring billing system until exactly one month after launch :) (and even then you can probably just charge their card manually, rather than having it fully automated)
Ok, i understand. But can you tell me why I shouldn't be doing that? You don't think a recurring billing system is good? Or you are saying that first check whether the users want to pay for the service or not?
I'm saying to focus on the things that deliver value to the users. Ignore everything else until it becomes a necessity.
The billing system is just an example of something many makers invest a lot of time on upfront when it's not necessary yet. (Because for the first couple dozen customers you can handle it manually.)
OK, That sounds right! Thanks for the guidance. Also, ordered traction book as you recommended. Thanks a lot again.