19
21 Comments

We failed before we even launched. Reflection time.

We're about to officially Launch Notifire and we've got to be honest, we've failed before we even launched. Let me explain who we are and how we screwed up in following sections.

TL;DR

Let's be honest, when you see a wall of text, most of the time you don't read it (at least I don't). So here's the gist. Feel free to read below to get the full scoop of learnings.

  • We wanted to launch a project quickly but failed to do so
  • We wanted to make something useful but failed to properly validate
  • We've adapted our process to fit what we've learned

Who we are

We're Niche Mates, a group of longtime Friends that want to build sustainable projects & companies that solve problems that we have ourselves, or our Friends have.

Why did we build Notifire?

In the beginning we wanted to build Notifire to scratch our own itch. If you're a full-time employee that builds side projects, you probably have this problem too. We constantly struggled with being focused on the right things. For example, if I visited Github, I would see all the notifications for my main job AND my side projects all scrambled together. I always want that notification badge to go away, so I'd go through all of them together at the same time. Even though it probably wasn't the right moment to be looking at side projects. Or during the night wasn't the best time to worry about work.

Another problem (that I'm sure you also have) was keeping up with all the services I used for work. For my main job, I mainly use Github, Notion and Slack and Figma. For our projects, we use Github and Figma, but also Google docs.

Just to complicate things, I also have some advisory positions where I get pinged on Slack, Github, Gitlab and Trello. Hence the idea to build a place for all your notifications that you can easily sort by context was born. This was heavily influenced by Hey and their features. Like sorting into multiple spaces, Imbox, Feed and Paper Trail. But in Notifire you're basically segmenting your notifications by whatever you want.

You can make a space that fits your needs. I separate my work by the following: Work, Side Hustle, Advisory Positions and within the side Hustle I segment by Projects. We also have a book club we run using Github projects and that goes into Miscellaneous. You get the idea.

More or less we went and successfully scratched our own itch. But we still failed. Why? That can be summarized in 3 points:

  1. We needed 6 months instead of 2 to build this → Things take at least twice as long and then some more
  2. Failure to properly validate in the beginning → Validation is crucial
  3. Failure to fully focus on the project → Focus is the most important thing

I'll go into more detail on those points in the next section

Why did we fail?

We wanted to launch this project within a 2 month timespan. We started chipping away on it in October and it took us until now to get it to a point where we consider to have built our MVP.

As a philosophy for our company, Niche Mates, we set out to launch 12 projects in 12 months but as you can see working for one project for 8 months will not make it very likely to get there 🙂

Let's examine the core things we did wrong, why it happened and what actions we've taken going forward to be better.

Things take at least twice as long and then some more

Why?

This is imo because you have low energy when you work on your side project during the nights and weekends. You seldom get a good block of focus time, especially while still building Notifire I struggled with the notification overload I described above.

We estimated the effort for this based on some vague estimate of how much time we would have each week. But life seldom works that way, I for example adopted a dog a month after starting to work on this project and while it was one of the best things I ever did, it definitely derailed my productivity.

When things move slow you tend to get dragged down (at least I do) by the lack of progress. What you could ship in a week going full time... takes 4 weeks as a side hustle. That makes me think I'm incapable of moving fast, which is one of the things I pride myself on and something that is crucial imo. It's one of the major advantages over bigger companies and/or competitors. This led me to spend more on another project that we're running together and improve that, instead of chipping away on this project. Leading to even longer delays and less progress. You could say it becomes a vicious cycle.

Learnings?

  • Be less optimistic in your planning
  • Adjust buffer for weeks that you have low energy or life gets in the way
  • Try to batch hours together when working on a project to get into flow

Actions taken

  • We now plan with a 3x of what things would take going full time, add some down time and factor in a week of no hours at all per month
  • Time-block your focus blocks in your calendar, and instead of working 1 hour every night, try to work just 2 times per week. Put in a solid 2-3 hour block of time.

Validation is crucial

Why?

In the beginning of this project we did some initial validation but definitely not enough. We were too fooled by the narrative that we have this problem so others are probably likely to have it too.

This lead us to believe that it's fine to just go ahead and build this after talking to a couple friends that all said it was a good idea (Mom test anyone? 🤔)

We did do some outreach to people outside our circle and are also running a campaign on ship to collect emails to gear up for launch, but I still don't feel like we've validated it enough.

Learnings

  • Start validation earlier
  • Don't fall down the rabbit hole of thinking just because it's your problem you don't need to validate

Actions taken

  • Our goal used to be to launch 12 projects in 12 months but we have shifted our focus to validate one project every month and only go forward with it if we hit certain goals that we set for that project.
  • While we only actively build one project, we're validating a bunch mostly via landing pages that take like a day to set up and Matt our product guy works on driving some traffic and talking to customers. Examples for this include making cheap and cost effective transcripts for youtube and picking anyones brain for a small fee

Focus is the most important thing

Why?

As touched on in the previous point we started our side project company with the goal to launch a bunch of projects in 12 months (12 to be exact) and we already launched one before that we put kind of in maintenance mode.

So when we started Notifire we split our focus on 1. Maintaining and extending the first project and 2. Building Notifire.

We did this by putting one person on Notifire as the lead and one other person on the old project as the lead but what we should have done instead is extend the old project and hand it over to Matt to grow then both shift over to Notifire as the next big project fully focusing on that to build some momentum.

When dragged down by the lack of progress, I even went ahead and tackled another project on the side scratching my own itch to show myself that I can ship stuff fast and that watered my focus down even more as I shipped it to myself and a couple friends and then had to maintain it.

In case you're interested it's a weekly planner called "Roles" that we're validating on Product Hunt ship in order to see if it's justified to put in more time. This helped me forget about it for now and focus on the other things at hand.

Learnings

  • Momentum requires focus
  • Only do one thing at a time (Ironically, that's what Notifire is for, yet we failed to do this ourselves 🤔. But we're only human and we make mistakes. We're trying our best to learn from them though, I promise 😁)

Actions Taken

  • One project gets all our attention in what we call an "active build stage", we might be passively validating a couple more but one gets all the developer attention (we're 2 devs + one non dev)
  • Shift towards validation focus (This helps putting some thought into all the million other ideas we have but can't build. We can easily see what people think with low effort and get the ideas out of our head. Making more space for our "One thing")

Conclusion

Let's be real, none of this stuff is new.

I've read about those mistakes plenty of times, especially not focusing on validation enough. I guess that makes us fools (if you believe what Bismarck is saying) but maybe that's what we are and where we stand and that is just a fact. I think failure is not inherently a bad thing, failure to learn however, is bad. And in my opinion we're trying our best to be better and we've already taken the first couple steps. First, to be self-aware. Secondly, to implement those learnings.

If any of the problems we're trying to solve with Notifire resonate with you, you can sign up for early access here

If you want to stay informed with where we're headed, you can subscribe to our (irregular) newsletter here.

If you want to get more insight into our process or anything else that we're doing, feel free to ping me. I may or may not ask you for $500 for my 12 step program to failure as described in this article. I also sell that as a course on Tiktok 💪😁🤙

  1. 1

    La soberbia es la que no empuja a defender nuestra "razón" antes que a hacer dinero.

  2. 3

    I often find problems that no one else really has. 😂

  3. 2

    I can certainly relate to the "be less optimistic in your planning". Developing my app took roughly 6x of my most pessimistic estimate :D

    1. 1

      Hehe. Maybe we should 2x our 3x 😁

      1. 1

        Lol :D Hopefully not 😁 - I did take an insanely complicated project, so I do think that has something to do with my estimates being completely wrong.

        I usually am very accurate with my estimates, as long as there's no UI involved. When there's UI involved, everything goes out the window -- usually what's in your head needs fine tuning when you actually see it on the screen, even more fine tuning when you get user feedback, and so on :D

        1. 2

          Haha, yeah css used to be my worst enemy until tailwind so I get what you mean 😁

  4. 1

    Thanks so much for this sharing, it certainly helps to highlight potential pitfalls to aspiring indies like me.

    Curious to hear more about how you changed your approach to validate the project ideas?

    Are you measuring certain actions on the landing pages? How do you differentiate between a validated idea vs a non-validated idea?

    1. 1

      We're mostly talking more to people. (Mom Tests, not asking "would you buy this").

      We also changed our approach to work more with established authorities in a given space that are a sounding board for the product and will deliver early sales.

      That way the feedback loop is much tighter.

      For example, we're building a niche financial planning tool with restructuring consultants that know other people like themselves (that have similar behavior)

      One other project, we charged people upfront.

      Different ways to do this.

  5. 1

    make sense and I subscribed, curious where you're are going.
    our start-up came from frustration in finding a new gig/assignment, scouting all the platforms, marketing and selling your skills, and again and again filling in forms at platforms with your education, skills and portfolio. We are starting the validation of our first mvp very soon: https://www.aforceof.one/

    1. 1

      Thanks for reading and thanks for signing up :)

      We'll keep you posted and if you need some feedback once you have something to look at let me know 🤙

      I do some freelance stuff on the side from time to time when I have some capacity (not a lot lel.)

  6. 1

    Let me tell you one thing straight - Launching 12 project in 12 months. You will end up in launching but not billing anything. I will instead suggest to focus on 3 or 4 ideas which are validated and work one by one. But simultaneously any of you should focus on one so that it may not get derailed.
    Everyone say to ship ship ship, but i will say don't ship a half baked product instead make it usable and ship it when you are confident.
    2 months to build a product is too optimistic. Userflows, Design, Development and testing can be much more than you think.

    1. 1

      True.

      I think we've come around to forget about that for the same reasons but it sounded like a cool goal in the beginning :p

    2. 1

      Agreed 100%.

      All these "12 projects in 12 months" is just something to get you going. But realistically, you can't gauge true validation in 1 month.

      As far as I know, there's no one who actually completed "12 projects in 12 months" -- either you find one that works, or give up at some point altogether.

      1. 2

        I think we don't have an issue to double down on one project if we have one that's a clear winner but yeah you're right that most of these 12 in 12 don't lead to great results.

  7. 2

    This comment was deleted 3 years ago.

    1. 1

      Have you read about Mom Te...

      Yes but only recently (way after we started this product)

      There were some strong assumptions in the post

      Yeah you're right but I think from the feedback we've gotten (we did do user testing) people that are in our position can resonate with most of what we're saying whereas people that don't have any side gigs see it more as a vitamin than a pain killer, just like you're saying.

      We're concentrating on this Niche of people first that get the full value out of it and then will explore people that just want all their notifications grouped in one place (this is a bigger pain for more people) but from how I'm describing the product here isn't immediately obvious that it solves this as well and maybe we need to tweak the messaging.

      One thing that's more worrying about this specific product is that we haven't figured out distribution for this yet, we have some other projects and they all have very obvious paths for that but we will see how it goes. (Probably another mistake that should be in the article haha)

      I'm not fully familiar with GitHub but I believe they group notifications and there might be ways to go around with separating organizations or having separate accounts if notifications are such a big problem for people.

      Yeah but that view is not great, it's definitely not a first class citizen in Github i spend all day in there trust me 😁. Also the notification badge never goes away in the top right corner. It shouldn't trigger me but it does more often than not and I find myself waisting time. This goes more towards setting your environment up for success

      One thing some people do is that they have different accounts for both and or just get email notifications that they group with folders/tags and ignore the ones on the site this is probably what we're competing against the most at that somewhat mirrors what we've built but it's also much easier to navigate through your notifications and check them all out, before going back to focus time with our app. Something else I haven't really touched up on above.

      About validation I've seen your name here on the comments section a lot but I had no idea what you were working on.

      Posting here once and again but never reached trending so there was barely and views on the posts but yeah we could have done more I agree

      I'd only recommend to have one or two solid ideas, while working on them release some entertaining, potential to go viral products with low effort. Which should help to get you some spotlights, with a sole purpose to build your audience, let them ready when your "killer" products are available.

      Yeah makes sense we've more or less settled on this approach and we have a couple small things we're launching to drive traffic to the other ideas.

      1. 1

        This comment was deleted 3 years ago.

        1. 1

          Thanks mate and thanks for taking the time to read and give some thoughtful feedback 🤙

  8. 2

    This comment was deleted a year ago.

    1. 1

      We all trip up on the fundamentals sometimes. It seems though, that you had a perfect storm of extremely basic mistakes.

      I think partly it's because we went into this not really knowing what we've gotten ourselves into doing this on the side for the first time, you're right we're all somewhat experienced people and we should have known better but the more time passes the more disciplined you need to be to catch yourself eating your own bs and I think we've just not done that or at least not enough

      12 projects in 12 months

      Why??

      I think we wanted to contrast our day to day jobs where we focus on one big thing all the time and we just wanted some variation, build something quick and move on to the next thing.

      I like to go to Hackathons for example for that reason specifically and maybe we've also bought into the hype a bit at the time.

      Those probably wouldn't have become business but could have been cool projects but this is not what we wanted to go for so clearly it was a mistake.

      Hope that makes sense 🤔

Trending on Indie Hackers
How I grew a side project to 100k Unique Visitors in 7 days with 0 audience 49 comments Competing with Product Hunt: a month later 33 comments Why do you hate marketing? 29 comments My Top 20 Free Tools That I Use Everyday as an Indie Hacker 16 comments $15k revenues in <4 months as a solopreneur 14 comments Use Your Product 13 comments