Live data from Hacker News

Ask HN: Show your failed projects and share a lesson you learned

news.ycombinator.com

131–140 of 285 posts

Re: Ask HN: Show your failed projects and share a lesson you learned

#131
post #120
post #40

Had several: last minute airline seat bidding app with an interested airline. Fishing competition app with paying users. Housing valuation app for a city council, with the actual city council interested and opening up their API to us. The city council also wanted a parking app and water billing app. A telco requested a reloading app that was basically CRUD but offered 6 digits for a few days of work. There was a diet…

Have you considered that you’re a common denominator in your half dozen examples? How could they all fail the same way with different people to blame?

There are plenty of other experiments.

One failed because nobody wanted to fund it, right during a crypto boom. It might be a bad idea too. Who knows? But everyone moved on to better projects.

One failed because we tried to clone Blue Apron but local logistics and payment infra wasn't mature enough.

One failed because of scope creep.

One failed because the CEO was bullshitting investors and they pulled out. It may not be related but probably is.

Some failed because I was the lazy one who didn't feel good about committing.

All of those did not fail from lack of hard work. But they're less interesting. Laziness is the one I'm really pissed about. It's also possible they'd fail later, but they did not get that far.

There's successes too, but that's off topic.

Re: Ask HN: Show your failed projects and share a lesson you learned

#132
post #78

Earlier quoted context omitted.

Do you think offering some kind of onboarding/deployment service would have helped? Helping them migrate all their data and workflows into this new tool?

It likely would have helped on the margin, but honestly it seemed like we were selling a much better experience to patients, and only marginally better experience to doctors. We really needed to nail the doctor experience, but there is some nuance there. Generally, PTs have front office people who spend their day in these tools, while doctors have fairly limited exposure. The shortcomings of the existing tools aren't…

“ In other fields, tools that affect our customers customers are very successful IF that drives more sales, or can affect the bottom line in some way.”

Very insightful - whatever solution you have must actually drive enough $ for someone to really want to give it a try. Which is a huge ask if someone’s business isn’t really tech oriented and they don’t really believe the optimization is worth breaking through existing ways of doing things.

Re: Ask HN: Show your failed projects and share a lesson you learned

#135

Spent about $200000 on developing a real-time massive multiplayer online strategy game just to run out of money then fail our Kickstarter: https://www.kickstarter.com/projects/breadboard/terra-mango-... We already had 4000+ people sign up to play once it hit beta, and even had local news cover us: https://www.fox35orlando.com/news/terra-mango-could-be-the-n... We vastly underestimated our ability to market the game a…

Can I ask where the capital came from? Did you all pool together to fund it? It's a lot of dedication for something that sadly didn't ship.

Re: Ask HN: Show your failed projects and share a lesson you learned

#136
https://www.CocktailLove.com I built last year on my paternity leave and haven’t had significant time to work on it since. I tried to monetize by selling Nick & Nora glasses on the site but didn’t know how to market it (or just no one wanted them).

It still gets a sign-up or so a week and 1.5k visitors a month from Google but it’s far from where I wanted it to be.

I think the biggest learning is that trying to work full time at a new job (moved from FAANG to a scale up), raise a young kid, maintain a relationship with your partner, workout occasionally, and work on a side project all at the same time is near impossible. At least for me :)

Re: Ask HN: Show your failed projects and share a lesson you learned

#137
Testedrecruits.com - I built a recruiting software in-house that has helped me hire hundreds of people. I tried to turn it into a software as a service and never got anywhere and never got anywhere.

RomyLMS.com - same thing here, I built training software that I use to run University level courses for my employees. Employees. I converted it to software as a service, and no one used it.

My lesson from both is that if you are not going to be putting full-time marketing and sales effort into a software as a service, you'll have a very hard time beating established competitors.

I think that the software as a service area now has started to become saturated as people view it as easy money. I think the true easy money right now is actually in the construction trades and manufacturing. Building skills in each of those areas will reap long-term rewards for those who do so.

Re: Ask HN: Show your failed projects and share a lesson you learned

#138

As I was known to drink a lot of Diet Dr. Pepper and had people who timed my code production in 'cans per hour' :-) I thought it would be fun to convert an old 47" Fresnel lens that came from an old big screen TV into an aluminum can melter. The project consisted of a frame on an alt/az base to hold the lens, arms from teh frame to position it's focal point on can that had been crushed vertically and then slid down a…

Please tell me your Dr Pepper consumption could not be measured "cans per hour".

Re: Ask HN: Show your failed projects and share a lesson you learned

#139
http://liveworks.app

An app that would let hospitality workers pick up any shift from any venue at any time. The problem with that is, since its a platform I needed a lot of supply (restaurants) to encourage the demand (workers) side. We even decided to pivot to a 3 staged launch (stage 1, we'd let restaurants come on board for free, stage 2, we'd let them pay their own workers through the app, stage 3 we open the flood gates and let the workers pick up shifts from places other then their own restaurant)

What did I learn?

- Don't work on problems that you are not 100% passionate about. I met the other co-founder through a work/equity deal where my agency would take some $ plus percentage equity to finish the app.

- Before trying to solve a problem, ask if the problem is worth solving or not (product design), being a technical person, its easy to jump straight into the bells & whistles of a product without thinking about _who_ is going to use it, and if there is even a need for it? We can pick the shiniest tools and the best tech, but if no one is going to use the product, none of that matters.

- We ignored competition, thinking was since we are not _just_ a scheduling app, we can ignore the biggest competitor in the space and still make a scheduling app. Turns out the competition just rolled out a new feature that lets venues handle the HR side of their business as well.

http://shareablekitchen.com

A platform that would let kitchen owners rent out their un-used kitchen space for some $$ on the side. Kind of like Airbnb, but for kitchens (I know that should have run alarm bells). I joined the project after it was already started by the 2 previous co-founders (both non-technical). Idea was to let new business owners that were just starting out, easily rent kitchens from other people for a couple of hours, days, weeks at a time.

What did I learn?

- Market research is important, don't skimp over it. I realized a couple months into the work that most restaurant owners don't want to deal with renting their kitchens anyways. There are specific ghost kitchens in almost every city now so it's cheaper/easier for people looking to start their culinary experience to go through them instead of renting a given person's kitchen.

- After doing some back of the napkin calculations, ghost kitchens on their own was a small industry to be in (don't remember the exact numbers, but it was peaking out around 1 million / year)

- You can not steamroll health/safety restrictions, and every state, city, county has their own permits for renting kitchens to handling food. This often times requires the person seeking to rent a kitchen to have their own business permits, to keep track of all those things and enforce them was too much to handle.

- Competition already exists out there, and its mainly catered towards community kitchens. - Don't become partners with people that are not going to have skin in the game. Although I will digress going into details here, but if they don't have skin in the game (even as non-technical co-founders), they will treat it as a side project.

Main takeaway: - Trust your gut, vet ideas, vet people

- An mvp glued together is better than a highly scalable/distributed/serverless/${new_shiny_tech}

Re: Ask HN: Show your failed projects and share a lesson you learned

#140

About 12 or so years ago I created a competitor to eBay in Australia with a few friends. TradeCity. We had a slick clean UX, no stupid bid sniping, $1 listing fee only if you make a sale. In 1 week of launching we got around 5000 registered users, 1000s of items listed, and steady flow of traffic. Made the mistake of using a VPS provider in Australia, a week after launch… bam servers died. Went to restore the backup…

That's a big lesson to learn about backups.
Post reply on HN