What is or was your transition from developer to founder/indie hacker like?
I'm a developer and currently doing a PhD. Most times I'm working on technical things, and when I don't, sometimes without even realising, I'm finding my way into writing some code.
I am really interested and excited about building AND launching and running products and I want to get to the point where I launch products that make money. But most times when I think of some idea instead of digging deeper on how to test it and launch it fast (some of them are really testable without custom tech) I just start building things. Sometimes I stop myself and think of how to test it, come up with a low-tech idea (like a landing page and a form) and while making that I somehow go back to "but it won't take long to build" (yeah, right, a 2-3 weeks later I think maybe the landing page was a good idea again). And I'm very aware of this but my instinct still drags me back to making products as opposed to developing and testing the business idea.
Developers on indie hackers, especially those who have successfully launched a product, how was your transition form the developer mindset to "indiehacker" mindset?
I'm not necessarily looking for advice, I guess what worked for someone doesn't work for everyone. I'm interested in your stories and if you felt this kind of struggle coming from your tech background?
Before starting Indie Hackers I did remote contract work for a couple years. It was a hiatus from the grind of being a founder, which had burned me out years earlier. It was also an easy way to save up money.
I began dabbling on a side project, my previous business Taskforce. I did it more for coding practice and to learn new frameworks than anything else, and so it didn't progress much as a business. In hindsight, I did it that way because I was afraid of the business side of things.
When the last company I was contracting for went under, I took the opportunity to quit contracting cold turkey and become a full-time founder. At that point, I had just over a year of runway saved.
I burned through my first 4 months of savings doing all the wrong things. I wasn't working very hard. I didn't set firm deadlines and reduce the scope of my projects to fit. I spent a few months dabbling on Taskforce before I accepted that I wasn't ever going to be motivated to work on the growth/business side of things. The turning point was watching people launch and grow successful projects in just a few months, and realizing that I'd be more likely to do the same than to stick with my current project. Dropping Taskforce meant eating years of sunk costs. That was painful.
My next project was some app that I'd always wanted for myself. It was a bad idea. It was more of a feature than a business, and it would've taken me forever to code. About 2 months into it, I was still writing code with no end in sight, and wasting time playing around with the latest frameworks. Then I realized I had no plan for growth whatsoever. I was just doing what I'd always done. I think I was motivated by the story of the Mint guy who spent months coding in isolation, then released his product, and BOOM the rest was history. Not a good story to learn from.
(This was before Indie Hackers existed, so good stories were hard to find. 😇)
Then I decided to get serious, switch gears, and go into hardcore analysis mode. I realized that I knew the right things to do, but my challenge was finding the discipline to do them.
So I made a validation checklist of requirements that my next idea would need to hit, and #1 on that list was something like "must not be code intensive." I wanted something I could build and launch in less than a month. The rest of the list was similar. It was full of reactions to my past mistakes.
I checked my idea notebook I'd been keeping for years, and none of the 50+ ideas passed muster, so I started brainstorming from scratch. A few days later I had three ideas that scored fairly highly on my checklist. The best one by far was Indie Hackers, so I did that.
(It's worth noting that I almost chose one of the other ideas, because they involved more code and seemed more fun. Discipline is hard.)
Building Indie Hackers was relatively easy. I got distracted, I decided to build it from scratch, and I made sure to learn/play with new tech, but I still went from idea to launch in three weeks. I made my first $500 in revenue a couple weeks after that.
Thanks so much for sharing that story @csallen! I’m curious, what was the rest of your validation checklist? 😊
I'm slightly hesitant to share my validation checklist. It was useful for me at the time, because it dealt with things that I personally needed to be more disciplined about. I doubt it's a good list for people who are not me. In fact, it's not even a good list for me anymore, two years later. Nevertheless, here it is:
cc @chvid
Thanks a lot for this. I think it is very cool.
For all of us who don't have a profitable side business; this type of thinking seems to be critical and I think it is a lot more constructive to read about this than seeing an Elon Musk video on sending a rocket to Mars.
Thank you @csallen! Some of the things you mentioned in your checklist (e.g. "can I personally do a good job marketing and distributing it?") are great reminders of things that I need to be more critical about and add to my own checklist.
Though being an Indie Hacker is often a very personal ("independent" some might say) journey, I think a lot of the lessons we've all learned can be applied broadly!
Can you share the notes / checklist / scoring mechanism that caused you to start indiehackers?
Thank you for your answer. Really appreciate it. I now know why the indiehackers forum is custom build :).
I liked the part where you went as far as choosing the idea that doesn’t require much coding. I think I’m also getting that part wrong. I choose ideas that seem exiting to build; actually I think I even make features that are cool to build seem important when they actually are just nice to haves.
Yeah if that's your challenge, consider picking ideas that are fun/cool to market. Imagine your ideal set of customers and the distribution channels they pay attention to, then imagine strategizing on how to interact with them through those channels all day. If that doesn't sound fun, maybe pick another idea.
If you like coding, trust me, you'll probably come to enjoy the coding part on any idea you pick. You don't need to optimize for that upfront.