New to WIP?
We're a group of makers shipping together. We help each other stay accountable and reach our goals.
Apply for access
Other questions
Back
Question
How to be more consistence, and ship the products?
Hi everyone,
I'm new, and I want to learn more about building and shipping the products.
How to learn things and ship everyday, if I'm starting, should I do 11month, 11 product challenge?
Also, How to do marketing for the product for the organic user?
Shazeb
I'm new, and I want to learn more about building and shipping the products.
How to learn things and ship everyday, if I'm starting, should I do 11month, 11 product challenge?
Also, How to do marketing for the product for the organic user?
Shazeb
👋 Join WIP to participate
Shipping "12 products in 12 months" (or eleven haha) is a great way to both build a shipping muscle (learn how to get a product out the door), and try out many different ideas to see which ones get traction.
Because the truth is, it's hard to predict which idea will work. So you'll just have to try a bunch and see what happens.
So yes, I think launching a lot of products is definitely a viable strategy. You can do the same for marketing. Try out 12 ways of marketing your product in 12 weeks. See what works, and double down on that.
@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.
I commit code every single day and build a streak. It doesn't matter how big the commit is - but it needs to happen every day. I like this approach because I'm constantly thinking subconsciously about what I'm going to do next. So, when I sit down to do the work - it's really easy to jump straight into building because my conscious memory already has context.
@philipithomas Yes, this is happening to me nowadays after using Wip. I don't want to break the streak. Thanks!