27
16 Comments

Failure to launch after going full-time on a project — learnings from Craig Campbell of Eurotripr

Reading success stories is great, but sometimes it's helpful to learn from someone else's failure.

"Failure" might be too strong of a word, considering everything Craig Campbell (@scotalia) of Eurotripr took away from his experience. He tried to go full-time on his trip-planning product, added feature after feature instead of launching, reluctantly admitted defeat, and eventually went back to full-time employment… for now.

I'll share more about what happened, but here are takeaways for

  1. Take your time.
  2. Build smaller projects.
  3. Keep an eye on your mental health.

Slow down

We often hear that first-mover advantage is the end-all-be-all of entrepreneurship. If you don't launch now, someone else will launch first and take home all the spoils, right? But that's a self-sabotaging lie — at least according to Craig. And it’s the reason he may have quit his job a little prematurely.

Craig: I kept thinking that with the COVID lockdowns coming to an end and the 2022 summer travel season coming up, March 2022 was the optimal time to launch Eurotripr. Everything hinged on that. I got more and more anxious. And when March came and went I felt I missed the boat and was really disappointed in myself.

But people travel to Europe every year and will probably continue to do so. So I didn't miss anything.

The point is, we all get the idea that "If I don't launch NOW, I've missed my opportunity." While this could be true for some very specific niche things, for most projects, it is just another lie we tell ourselves. Whether it is to give ourselves extra motivation to launch or an out in the event we fail… either way it is not true.

Launch whenever you are ready, the market will still be there.

Depending on where your product is right now, that might mean hanging onto your dayjob just a little longer.

Craig: Your project is going to take you X number of hours to complete. What the number is doesn't matter - it's going to take you a specific amount of time to complete. You don't have to quit your job to rush through those hours to get it done 'immediately'. It is much less stressful and just as possible to work on your projects with a full-time job.

The key is you have to be disciplined with your time so you can carve out a few hours per day or week to work on your project. If you can do this, you will cross the finish line.

I knew this, but I completely ignored it. In doing so, I took on completely unnecessary stress for myself, my wife, and my family.

Get validated

But of course, it's a balance. And validation is the most important thing in the equation of when to take the leap… that and runway.

Craig: That being said, I think we can all agree that MVPs are the way to go. You don't need to stress yourself to launch, but you don't want to build a bloated, over-engineered product either. That's a waste of time, and can detract from the product.

Looking back, I bit off way more than I could do by myself in such a small period of time. I kept adding more and more features because I thought visitors wouldn't stay if I didn't have user accounts. I thought travelers would like to meet others on the road and would want to create meetups. And on and on…

All these features sounded great as I was building, but not one of them was asked for by a single user because I didn't yet have any users. I spent all my time building for 'what-if' and ignored the advice I had personally given to so many people.

He had some runway, but he was missing validation. And feedback from real users. Here's the piece of advice that stuck out to me:

Craig: Help one person with one feature, then build from there. In other words, start with the tiniest MVP and see if anyone even cares. If they do, ask them what to build next and so on. Anything else — and specifically what I did — is procrastination or fear.

Don't fail due to fear of failure

Sometimes, you've just gotta put something out. Anything.

Craig: In retrospect, I can definitely say I was afraid of putting something out there in case it bombed. But in the end, by NOT putting something out there I simply failed quietly. I can 100% say I'd rather have failed by putting something out that no one wanted than never finishing and never actually knowing if someone would have wanted Eurotripr.

Take care of your mental health

So going full-time didn't work out for Craig this time around, and it took a toll. It started early…

Craig: After a couple of months of coding, reality set in and doubts started to creep into my head. Lots of negative self-talk, and no one really supporting me through it. No one wants to hear the guy that just left a good job talk about his doubts.

It felt really lonely. I shared some moments on Indie Hackers, which was helpful. I also tried building in public and that was exciting at first, but it soon felt like adding more stress and work to an already difficult project.

The worst part was the stress of watching my savings being depleted and not knowing when or if I was going to launch and earn money from it. And then there was the fear that I would look like and feel like a complete failure.

Eventually, he threw in the towel, and that was even harder.

Craig: Admitting to myself that I was not good enough to create the thing I'd been dreaming about for years, yet watching so many other people do it every day was soul-crushing. But I'm responsible to people other than just myself, and that means I have to make hard decisions. Going back to work was a hard decision.

I'm not sure I've even recovered from this feeling, even six months after going back to work. I felt, and still feel, very low due to my failure to finish. And for a time, it did defeat me. As a man, husband, and father I had this image of what I should be and what I should be able to do.

But now, I see it as just a low POINT in the journey. It wasn't meant to be at that time. But I still firmly believe Eurotripr can be a useful product.

Try to create a support structure of loved ones, friends, other indie hackers, you name it. And share the "why" of your journey with them so they can get on board.

Craig: In the end, if you don't have a support group that understands why you are doing this and what the ups and downs are going to be, it can be very difficult to see it through to the other side.

Here's an article on the topic of mental health in indie hackers, in case it's helpful.

Get back up

So he went back to work, and I think maybe that's the biggest lesson Craig shared. You've got to be humble enough to admit when you've failed. And then, you've gotta get back on the horse.

Craig: My full-time job and freelance gigs are very quickly replacing the money I burned through while I was working on Eurotripr. My goal is to add a bit more to my savings than where I was before, and then slow down or eliminate my freelance gig and replace the time I spend on that now with working on Eurotripr. I should be able to do that by November.

  1. 3

    I'm tired of reading success stories, which are 1/100 of real life stories.
    I think honest common stories like these, offer a LOT to learn from, and ultimately help to succeed.

  2. 3

    Why does Eurotripr look suspiciously like NomadList? I mean, the layout is basically the same, and the categories when you hover are the same. When you click on a country, it's also almost the same...

    1. 1

      Hi satvioendem! I'm the builder of Eurotripr and subject of this post. I've been dreaming of starting a Europe-centric travel site/app for longer than than I'd like to admit. I don't consider myself a designer and when I came across @levelsio NomadList I decide to use the design and layout to build my Europe-only version as a way to more quickly get it to done. Sadly I never got it to done, but Pieter Levels definitely built a UI that works with travels / nomads, and I knew I couldn't build a better one, so I directly lifted it. I don't think there is any shame in that.

      1. 1

        I mean, there kinda is shame in that. I'm not a designer either but I don't lift other people's designs right off the page. I design my own, however best I can, with my own unique ideas.

        1. 1

          Even Pieter Levels skinned Nomad List to mirror Product Hunt 1:1 in one of his early versions.

          @csallen admitted his earliest version was ripped from an early version of NomadList.

          "Good Artists copy, better artists steal" or something like that.

          I'm not trying to directly compete with NomadList. I'm not ripping off PieterLevels' data and rebranding it as my own. And if I ever finished Eurotripr and got a message from Pieter saying "Bro stop copying me" I'd be happy to change to look. But taking the design out of my mind and using something that looks nice and presents the info in a convenient way doesn't seem like a problem to me. YMMV.

  3. 2

    "Don't fail due to fear of failure" I'll save that! ( for a friend lol )

    Thanks for sharing.

  4. 1

    I can relate so much to this.

  5. 1

    Thank you for sharing this story. Many great nuggets of insight and practical advice.

    One thing I'm not sure I agree with: Build one feature for one user. Users don't come for features, they come for problems. Plus, almost every product has competition. So why would they stick with something inferior?

    I think the V in MVP stands for valuable. What that means will differ from niche to niche, and it's still important to start small, but it also needs to be enough to solve the users problem elegantly/differently than other solutions.

    1. 1

      Hi ChiefRocker. I'm the builder of Eurotripr and the subject of this article. When I say 'build one feature for one customer', I am saying it is important to validate what you are doing as early as possible. Make sure you can actually help at least one person so you know you are not wasting your time.

      You do not need more than one solid feature to test an MVP.

      Also, you say that users don't come / stay for features, they come / stay to have their problems solved. That's 100% correct. And that is exactly what your one feature should do. If it is not solving their problem, or if you are building too many features to solve too many problems that you haven't even confirmed real people have, then you could end up like me spending too much time coding in a vacuum and never getting your project live.

      In my comments in the article "Feature" => "Solution to a users Problem".

    2. 1

      Yeah, a product isn't "viable" unless it provides some value. It's just a question of balance... but it's riskier to put out a product too late than it is to put it out too early IMO. If you put out a product that isn't good enough, you can improve it and relaunch. If you keep adding features to match competitors, on the other hand, you may never launch at all — it's a slippery slope. Just my two cents :)

  6. 1

    @IndieJames Everyone facing the same situation who is in struggles. We also faced hurdles for our project https://churnfree.com/ but now it's live and working, and we are helping the business to grow.

    if you want to succeed, you need to be consistent and continue working this will gives the result!

    Our Product helps business owners to reduce their business churn rate which helps them to increase their revenue and reduce their membership cancellation requests.

  7. 1

    I don't know about the "slow down" advice. I think there's something to be said about moving quickly. Which is why I couldn't agree more with the "build smaller" advice. I guess the trick is to find the right balance for your product.

  8. 1

    Man, that part about failure hits home hard. My own failures have really made me take a look at who I am as a person and as a man. Super hard, but I found that letting go of ideas about who I was allowed me to get to know the real me better, so that's cool. Gotta say, indie hacking really is one of the best roads to self-development 😅

    Props for navigating that difficult space and coming out the other side @scotalia.

Trending on Indie Hackers
Here's how we got our first 200 users 30 comments Reaching $100k MRR Organically in 12 months 29 comments What you can learn from Marc Lou 20 comments Software Developers Can Build Beautiful Software 13 comments Worst Hire - my lessons 11 comments How to Secure #1 on Product Hunt: DO’s and DON'Ts / Experience from PitchBob – AI Pitch Deck Generator & Founders Co-Pilot 10 comments