Live data from Hacker News

My experience releasing failed SaaS products

mmartinfahy.medium.com

21–30 of 104 posts

Re: My experience releasing failed SaaS products

#21
Am I wrong to think that this post needs a couple of revisions? It feels like it is all over the place. I don't know if it's just me but the structure and organization feels so off...

The tone of the article makes it seem like the maker is not interested in solving the problem, but more interested in getting paid and that's all that matters.

It's also hard for the reader to contextualize anything if the author leaves out the details of his 3 failed SaaS projects.

Re: My experience releasing failed SaaS products

#22
post #8

Much of this seems like useful lessons learned, but this particular section jumped out at me: > To my credit at this time I would learn and do anything to get more users to my site, to the point where I was getting banned from multiple forums for posting after people told me to get lost. How is this "to your credit"? If, as you say, the success of your product depends on getting niche users to buy in and trust that y…

I knew a company that did this (their marketing person would constantly make accounts on Reddit, get banned, and then try again all day) and asked them about it. They said that only the regulars who post and comment get mad, not the lurkers. It might only be the mods getting mad if posts only lasted 15 minutes or so. So in their view it didn't matter that the mods were seething with rage as that didn't get passed on…

This seems like the product of a person who shouldn’t be in a marketing position and a ceo who can’t hire marketers.

Barring a direct measurement to the contrary it’s highly likely this marketer was damaging the companies brand. The comments and bans from moderators are surely now the top results on google when one searches reviews. If this was a viable marketing strategy every forum on the internet would be full of such posts driven by automated bots.

Re: My experience releasing failed SaaS products

#23

A rather painful reading experience. The author needs to learn how to edit their thoughts and use punctuation/grammar properly.

A brief exercise in shipping an MVP and seeing if it gets traction before refining the feature set =). Thanks for reading my ramblings despite the lack of proofreading hopefully its a bit better for others now.

Haha I appreciate this response.

Re: My experience releasing failed SaaS products

#24
post #8

Much of this seems like useful lessons learned, but this particular section jumped out at me: > To my credit at this time I would learn and do anything to get more users to my site, to the point where I was getting banned from multiple forums for posting after people told me to get lost. How is this "to your credit"? If, as you say, the success of your product depends on getting niche users to buy in and trust that y…

This is growth hacking at it's finest. Eeking out .5% gains anywhere just to get some form of validation. Most think that they are able to infiltrate niche forums/sites and act the part but ultimately the 2nd message is always 'wow, I've just been using this tool for X and I got Y!'.

Re: My experience releasing failed SaaS products

#26
Maybe this isn't helpful advice, but don't take product failures so personally. They are experiments and learning exercises, and most companies fail by default. Of course it depends greatly on your life situation, i.e. do you have a job that can support you while working on stuff as a side-project? Or are you attempting to launch something as your full-time day job with limited savings or income? (10x more stressful)

People don't have personal investment or insight into your particular project. Most people assume there is a huge company behind every product they use, and wont hesitate to bash it on social media not realizing it may be a solo founder or tiny team with limited resources. Extreme reactions also get faster responses from big companies, so people have been trained to viscerally bash apps when reviewing them rather than posting more measured empathetic feedback. I think you will find that chatting with users 1:1 yields much higher quality feedback than reading reviews.

3-4 months also strikes me as a very short time to build, launch, monetize, and then declare a project a failure. In my experience, successful companies take years to build, or at least 5-6 months to start iterating on the initial feedback and building a reasonable userbase.

Just my 2c.

Re: My experience releasing failed SaaS products

#28
That was a painful read, sorry.

My advice for the author is to take a moment and look at the things they pay actual money for. Goods, services, Etc. And how they discriminate between vendors of those goods. (Why buy brand X when brand Y is cheaper, when you need a widget how do you find where to get one? How do you decide which one to get? Things like that.)

It is a big "ask" to ask people for money in exchange for access to or to use your app. When is the last time you bought an app for your phone? What put you over the edge into buying something? What things about that purchase made you feel better about buying it, and more importantly what things made you feel worse about buying it?

In none of the anecdotes presented, is there a discussion about how you played the role of being a customer for your own product. How did you feel about the "value" of the product given the price asked? How did the installation process go?

It can be hard to step out of your own context sometimes and that is where it can be helpful for a trusted friend, who will give you honest advice, can be the stand in for the customer and tell you the answers to these questions.

Lastly, in all three anecdotes the author is laser focused on money, money, money. All of their metrics around success or failure are based on money. The problem here is that money is the first derivative of customer satisfaction not the metric. Focus on delighting customers and they will happily hand over money.

Re: My experience releasing failed SaaS products

#29

I have been building and failing multiple websites/mobile apps since 2006. To this day, I don't think I could ever be in that situation of creating something that somehow takes off. Theres gotta be a place for failed web/mobile app developers to get together and figure out a way to make it, anyone know of such a place?

Surround yourself with winners if you want to succeed, not the opposite

Re: My experience releasing failed SaaS products

#30
As someone who’s created a few mildly successful products in my life, I noticed a few things missing.

- dogfooding isn’t that important, but if you’re not you need to test. Even just a few smoke tests on multiple devices will go a long way.

- allow customers to leave you feedback in the app and make it easy, don’t even look at your reviews except to respond with “this has been fixed.” It should be easy to communicate with your customers and have a conversation. I’ve always had a few good customers that will email me about things and leave suggestions as I go. These people are valuable to your success.

- negative feedback is positive feedback by people who don’t care. In the post, they mentioned a lack of trust. That’s some good feedback! Make it so a sign up isn’t required until it’s actually necessary. Demos, trials, etc can go a long way here.

Post reply on HN