💬 I often get Q’s like these:

How did you get your first customers for WIP? How did you grow BetaList’s traffic? Etc.

Makers are looking to reverse-engineer success. I see it everywhere.

I don’t think it works that way and the answers to those questions are mostly useless. 💥

I have built dozens of different products over the last couple of years. The vast majority failed. 😭

Surely if I know the answers to these questions, but still fail over and over again, these answers aren’t that useful. 🤷‍♀️

So what’s a better question to ask? 🤔
99.9% of the questions I receive are about the products that did well. In a way that makes sense, because we quickly forget about those that didn’t succeed.

🧠 This is known as survivorship bias.

Focusing on what survived, while ignoring what made it survive in the first place.
The real question, what you really want to know, is this:

What makes @WIP, @BetaList, and to some extent @AllStartupJobs succeed where my countless other attempts failed?

What separates a failed product 👎 from a successful product 👍?
Honestly, I don’t know. I wish I did.

It’s like Steve Jobs said “I’ll know it when I see it.” 👀

Same is true when we make products. We don’t know upfront what will work. But once we see an inkling of a product that does have potential, it’s not that hard to spot.
🚫 The wrong idea requires you to push and push until you’re tired and can’t take it anymore.

👌 The right idea will pull you forwards.
🚫 The wrong product will have you begging people for feedback. You’ll cling to any comment remotely positive. (“Wouldn’t use, but nice idea!”)

👌 The right product will attract people wanting to use it. People will give feedback without you asking for it.
🚫 The wrong product will have you focused on the technology, fine-tuning the design, tweaking the copy.

👌 The right product will give you the confidence to ship something embarrassing, because you know despite all its shortcoming it’s useful.
So keep shipping. Assuming your current product will fail and you need to try a bunch more before you’ve found the metaphorical spaghetti that sticks to the wall. 🍝
This means you need to keep your initial products small. If it takes 10 tries to find something that works, you can’t afford to spend more than month trying out an idea. 💡⏳
Persistence is not about sticking with what doesn’t work. Persistence is continuously experimenting until you’ve found something that goes work. ♻️💪
Happy shipping! 🚢✨

—
Inspired by conversations in 🚧 @WIP

https://t.co/J4IDFyoUgD
Grammar mistakes, stupid ideas, etc courtesy of tweeting at 6am in morning (that’s before I go to sleep, not after waking up). Bye! 😴
Oh, and when I talk about successful products and refer to my own, I mean that in the context of what’s successful for me personally. I prefer speaking from personal experience hence referring to my own products.

More from Startups

I shipped all these apps in 2020. Most of them generated $0.

🎬 https://t.co/JAhXqsuu6h $0
🌍 https://t.co/BrNUAhfiIT $0
💡 https://t.co/ZWcLfOH4aI $0
🐞 https://t.co/aghOxYEcPI $1.99
👍 https://t.co/2JhJLe27pW $3,025 in 10 days.

But that's ok, just keep shipping! My stories👇

🎬
https://t.co/wuiBp1XsYD is the first thing I created. It's a community for indie makers. The different thing is we post updates in videos. I created it for fun as I think the world doesn't need one more text-based forum, so I make a video one. No monetization plan so far.

🌍 https://t.co/fiwjgCWho5 is a social app. The idea is from Linktree, an app to share your social links. I thought it would be cool to add more visuals to it, and meanwhile we can explore others around. I also have no monetization plan for it. Make it for fun too.

💡 https://t.co/fZfL45uvVX is a platform to connect influencers with their fans. People says it's like @superpeer. But the only difference is it's all sync. Influencers don't need to commit their time to fixed slot. Fans pay to ask questions, influencers can answer at anytime.

Continuing Influenswer... I think the product has its potential. But for now maybe I didn't find the right niche to serve. Will re-evaluate it in future.
There are a *lot* of software shops in the world that would far rather have one more technical dependency than they'd like to pay for one of their 20 engineers to become the company's SPOF expert on the joys of e.g. HTTP file uploads, CSV parsing bugs, PDF generation, etc.


Every year at MicroConf I get surprised-not-surprised by the number of people I meet who are running "Does one thing reasonably well, ranks well for it, pulls down a full-time dev salary" out of a fun side project which obviates a frequent 1~5 engineer-day sprint horizontally.

"Who is the prototypical client here?"

A consulting shop delivering a $X00k engagement for an internal system, a SaaS company doing something custom for a large client or internally facing or deeply non-core to their business, etc.

(I feel like many of these businesses are good answers to the "how would you monetize OSS to make it sustainable?" fashion, since they often wrap a core OSS offering in the assorted infrastructure which makes it easily consumable.)

"But don't the customers get subscription fatigue?"

I think subscription fatigue is far more reported by people who are embarrassed to charge money for software than it is experienced by for-profit businesses, who don't seem to have gotten pay-biweekly-for-services fatigue.

You May Also Like