39
24 Comments

Reflections from an unsuccessful indie hacker in 2023: failure, hope, and YC

As the year draws to a close, I find myself reflecting on my indie hacker journey so far. I’m sharing mine from this year, in the hopes that it will resonate with others and highlight that we're all in different parts of the journey.


It started with a goal

I’ve been thinking about starting a side business for a long time. I’m getting older, having kids is on the horizon, and soon I may not have all the free time I have now. I set goals every year, and this year wanted to take the business goal seriously. Here was my goal, verbatim how I wrote it.

Goal: Tinker and start a business

  1. Measure: test at least 1 idea (find place where customers congregate, talk to 10 of them, try landing page + marketing)
  2. Measure: learn to make a web app (ex. Go through Node book or similar iOS etc.).
  3. Measure: I’ve started building something (Github repo, AI tinkering etc., 10 blog posts with views)

Re-learning to code (thanks ChatGPT)

I’ve been working as a product manager for years. I have a technical background and education but hadn’t coded in 7+ years. So, I didn’t even know that I could figure it out. I didn’t know that I’d be able to figure out hosting, deployment, all that jazz.

Early in the year, I started going through tutorial books. At some point I realized ChatGPT could code for me and teach me, so I immediately dropped the books and went that route. It wasn’t easy, but WAY easier with ChatGPT. Fast forward to the end of the year and I’m a semi-competent React/node JS developer. Learning is way easier with a goal in mind.

Building a product

I picked an idea based off of my experience and desire to mess around with ChatGPT APIs. I figured everyone was building blog writers, but I could focus on the niche of UX writing/copy. My prior job was focused on building tools for this. In retrospect, this was fun, but I didn't validate the idea enough.

I had such a strong desire to re-learn to code and build something, that I focused on that part rather than talking to customers and thinking about product market fit, marketing, distribution, or community. It’s like I had to prove to myself that I could execute on it before focusing on the other parts.

By the end of the summer, it was almost ready.

Launching, sort of

Once it was in MVP status, I deployed it (stringbot.ai). I realized I didn’t have a launch or distribution plan, so I went to google ads. They’ve largely been unsuccessful. ~40 people have signed up, but none have really engaged with the product the way I’d hoped.

I also started talking to potential customers (Ex-colleague writers). It was clear they didn’t really see a need for this themselves, but suggested maybe others who didn’t like to write may use it.

I also saw competitors popping up, and OpenAI announcing the GPT store, which could do something very similar (I even made a GPT for it). I lost hope that this is an important enough problem for people.

Indie Hacker peer group

Near the time I deployed, I saw Indie Hackers starting up a peer group program, so I applied and joined.

It’s been a good experience so far (no, IH didn’t ask me to post this). It’s been a great place to get honest feedback and meet others on different journeys. It’s made me feel more connected to the IH community, and hopefully more likely to continue. It wasn't their intention, but talking to the IH group made me take a moment to reflect and hit pause on stringbot.

Taking a break, applying to Y Combinator

After a little break, I had a cool idea. I’m not ready to share it yet, but I figured it was one that I’d want some help on – so I applied to YC with it, very late. I didn’t get in, but in the rejection was told that it was a top idea:

“We do have some good news, though - of the late applications we read this batch, yours was one of the strongest, and we would have preferred to interview if only we had capacity. We encourage all late apps to reapply for the next batch, but we want to particularly encourage you.”

While I know this is no guarantee, it does help with idea validation. I’ll probably apply again. I know this isn't very "Indie Hacker"-y, but if nothing else it gives me some validation going into 2024.

Lessons learned and the path forward

In 2023, I’m proud of:

  • Re-learning and gaining confidence coding.
  • Finding an indie hacker community.
  • Applying to YC.
  • Reaching my goals.

I learned:

  • To never make a complete product without talking to customers or trying a low-code/non-scalable MVP first, without a really good reason. This is advice repeated over and over again in the community. It’s so important to internalize this.
  • To get more comfortable sharing on the internet. I’ve never been one to post/comment, but that needs to change. Feedback and support from folks on the internet is invaluable.
  • Life needs balance. This year, I was sometimes so obsessed with building that I let some other things slide out of place (wasn’t as present with friends/family, skipped hobbies that I love). This isn’t sustainable for me. I need to find a more balanced path, even if its just a state of mind.
  • Think big on goals! I hit my goals, which means I wasn't thinking big enough.

What was your biggest takeaway in 2023?

I’m still noodling on my 2024 goals but will share those soon. If you want to follow my journey, follow me on twitter/x (which I plan to actually start using in 2024, link to account) - I'm happy to follow back.

posted to Icon for group Lessons learned
Lessons learned
on December 27, 2023
  1. 3

    “I’m getting older, having kids is on the horizon, and soon I may not have all the free time I have now.” - damn this really hits home, I’m in the same mindset atm. But I’m currently too scared and picky to execute an idea because I’ve spend months on something that I thought was amazing but turned out to be utter shit haha

    1. 2

      It’s a balance on planning vs just diving in and executing for sure. Sounds like we’re in similar situations - if you ever want to bounce ideas off of someone feel free to DM me on twitter/x.

    2. 1

      One of his key takeaways is „never complete a product without talking to users“. This prevents building things that are utter shit :D

      1. 1

        even though "taking to users" sounds like very obvious suggestion I wouldn't rely on it 100% for building the first MVP.

        we spent 8 months talking to all type of potential customers. based on their feedback it felts like we are hitting a home-run.

        but when the product was ready no one wanted to pay for it.

        one we had a product the conversation with users become so much different. we could see who is using it and who is not and dive deep into their use cases.

  2. 1

    I think there is some contention in your last two bullet points: "Life needs balance [...]" and "I hit my goals, which means I wasn't thinking big enough." It's the kind of thing that's easy for me to miss in my thought processes, so I think it's worth pointing out. It might be helpful for you to focus on setting meaningful, resilient goals that can be achieved quickly rather than setting "big" goals. That'll make it easier to pivot successfully. In general, we tend not to stop and look around until we've "finished something," and that's almost always an error; it's easier to ensure that that doesn't happen when you set your sights on baby steps.

  3. 1

    How to best focus on customers?

  4. 1

    Thank you for sharing your experiences, I resonated a lot with this line: "I had such a strong desire to re-learn to code and build something, that I focused on that part rather than talking to customers and thinking about product market fit, marketing, distribution, or community."

    Your post is a good wake up call to not get sucked into learning and doing what's comfortable, and instead work on the bigger picture. For me, coding and building feels more comfortable than talking to customers and thinking about product market fit because it's what I'm used to.

    One of my biggest takeaways in 2023 was to set my life up for success. I used to live with many other roommates in order to save on some living costs. I thought I could use the extra savings towards my business ideas. But actually, living with so many other roommates put a drain on my daily mental capacity and that cost me more. So I decided to find an affordable apartment to rent by myself. Even though I am paying twice as much, I am now taking more action and making more tangible steps towards my goals.

  5. 1

    I wonder if you could make a better use of your time by hiring no-code devs to develop your mvp. If you have to do the find idea prpcess, polish business model, development, marketing… it gets very difficult.

    A dev is expensive, but what about no-code “devs”?

  6. 1

    Thank you for sharing this! After a lot of thinking I'm just starting to work on personal side projects and this post really encouraged me to keep working, specially on the "sharing things on the internet" part haha I also don't post/comment much so I'm working on that. Thanks again for sharing and best of lucks in your next projects!

  7. 1

    Great insights and story.
    So relatable, as a fellow Product Manager trying new ideas.

    Thanks for the honest and transparent feedback.
    And congrats on having the guts to share publicly

  8. 1

    we always hear success stories because of the survivorship bias, this was a really good read! best of luck for 2024!

  9. 1

    "Never make a complete product without talking to customer"

  10. 1

    "Despite setbacks as an indie hacker in 2023, failure taught resilience. Hope persists; aiming for YC, embracing lessons learned. The journey continues."

  11. 1

    Well i can say that there are a lot of good things you have done and made a lot of progress here

  12. 1

    Good luck in 2024!

  13. 1

    That's an interesting perspective! 2024 is right around the corner, time to start planning for the future now! :)

  14. 1

    Commendable effort - despite setbacks, you pushed boundaries by relearning coding, connecting with the IH community, validating ideas, applying to YC, and achieving personal growth

    The lessons learned will surely guide you to future success.

  15. 1

    Your 2023 adventure is really motivating, filled with both highs and insightful lessons. My lesson is to embrace iterative validation and to pursue ambitious goals without sacrificing life's balance.

  16. 1

    Good progress I must say. However' I applied to IH peer group too a month ago, haven't heard anything yet.

    1. 1

      We are the pilot group, I think. I’m sure you’ll hear back eventually.

  17. 1

    Seems like a good progress! How many users are enough for YC to take notice?

    1. 1

      In this case, zero :)

Trending on Indie Hackers
From building client websites to launching my own SaaS — and why I stopped trusting GA4! User Avatar 76 comments I built a tool that turns CSV exports into shareable dashboards User Avatar 70 comments $0 to $10K MRR in 12 Months: 3 Things That Actually Moved the Needle for My Design Agency User Avatar 66 comments The “Open → Do → Close” rule changed how I build tools User Avatar 48 comments I lost €50K to non-paying clients... so I built an AI contract tool. Now at 300 users, 0 MRR. User Avatar 44 comments A tweet about my AI dev tool hit 250K views. I didn't even have a product yet. User Avatar 40 comments