Solving other people's problems, part II

Ask, and you shall receive.

So ask I did:

I actually feel more excited coding for the startups I’m freelancing for than my own products… Am I f**ked

And Twitter gave and I received more than I can ever ask for.

I have more clarity into why now:

• Nice setup – I guess it’s just the combo of factors like alignment of values, I like the team, I enjoy the work, I am providing value, contributing… (but all of which are similar for indie hacking)
• Money motivates – The money definitely helps! (versus say, my own products which isn’t making as much as I wish). I think that’s definitely one aspect of it and a big one! Always easier to feel more motivated by where the money is coming.
• Feedback loops – I’ve never worked harder, expected more and got back less for my own products. But hardest for me I think it’s the variable rewards, if ever. Not having tighter feedback loops, not seeing cause-effect, is difficult for me to move purposefully. The direct feedback loop from code to useful features ship to being paid money in bank account every 2 weeks is also easier to feel excited for. the do X, get $Y linear path definitely helps. Oftentimes with products, we’re building into a void. Plus my current products aren’t super engaging for me…
• That one idea – Or maybe I just haven’t really found an idea that truly engages. A higher bar for ideas might be needed.
• No more honeymoon – I feel like I could do with a new idea, or change how I’m approaching my current ones. my current projects aren’t super engaging. Maybe need to inject fun, or learning new interesting things. Key is keeping yourself interested, consistently. But also not realistic to stay in honeymoon mode forever.
• Build less – I could definitely do with more business focus on my own products and less building.
• Discomfort – There’s definitely more at stake w.r.t. my own products, not just money but expectations, social, emotional, identity. With products, it gets uncomfortable pushing my own limiters. With work, it’s less complicated that way.
• Learning new things – I enjoy learning and experiencing new things, this could be why I find the new startup freelance work exciting (I’m just 3 months into it).
• Need for distance – “You’re excited because it’s new & it’s not in your focus area. Context switching is good for your products as it takes your mind off the task for a bit. Having your product in the back burner lets it simmer so when it’s time to focus on it, you get more done.” Could be a sign I need some distance, and recharge from my own projects. Or need to have some active rest, like having fun.
• Less risk to bear – “Startups have long term visions and goals all set. Also they are taking most of the risk, so it makes it more fun!”
• Opportunity cost – “Finding/recognizing strong startup opportunities isn’t evenly distributed: it’s skill & luck. Sometimes it’s better (and more interesting) to jump on someone else’s bandwagon b/c it’s hitched to a much bigger opportunity.”
• Hero mode – “You can’t get demotivated as quickly as your customer will ask for progress and also come around with new ideas that being new motivation. For me it gives a better feeling of “someone actually needs what I’m doing”.”
• Consistency still rules – “Pretty normal that excitement about this or that project would ebb and flow, but staying consistent in the long term is really what gets us to places worth going. So I wouldn’t worry too much about it and just keep going.”

Last but not least… best reply award goes to:

Batman wouldn’t exist without Robin – @pavelkosyrev

I always assumed working on own products is more interesting, so was surprised to experience otherwise. Still observing myself on this one, and trying to keep an open mind and not get fixated with either indie hacking or working in a startup.

Thank you, guys.