Live data from Hacker News

Lessons learned from my failed startup after 2 years, 300 users and 0 revenue

sergioschuler.com

11–20 of 161 posts

Re: Lessons learned from my failed startup after 2 years, 300 users and 0 revenue

#11
There are a lot of things I'm interested in but would not pay for online, but good failed startup stories like this is not one of them.

Seriously, if somebody could cull 2 or 3 of these a day and deliver in a weekly or monthly format? It'd be worth a subscription.

Thanks for the article!

Re: Lessons learned from my failed startup after 2 years, 300 users and 0 revenue

#12
post #7

Lesson N+1: Hacker News can break your blog's webserver. That's one you only learn through experience. [ETA: which is sad, because I want to read it!]

Damn Bluehost, hehe. I wish I knew how to fix it, but a few refreshes seems to go through.

The only solution is to throw money at it until it gets better, isn't it? Or to wait it out. I remember when the word "Slashdot" became a verb, back when "Reddit" was a joke about a frog and a library book and DOS was what Windows ran on. The problem hasn't improved, as far as I know. So no biggie; it's not your fault. Ride it out and you'll be fine. Meanwhile, I'm mostly commenting so I can find your article again later and get to actually read it!

Re: Lessons learned from my failed startup after 2 years, 300 users and 0 revenue

#13
I think for first time bootstrappers, investing some time in a quality blog on a particular field you would like to build products for is really really useful. Apart from having a good audience to launch your first product, it helps you interact with people before you have something to sell to them. You learn more about their problems, the existing market, competition and so on.

Re: Lessons learned from my failed startup after 2 years, 300 users and 0 revenue

#15
post #5

This is a fantastic writeup (and like nearly all worthwhile writing on the subject, I don't necessarily agree with all of it). Two elaborations: 1) General advice to non-technical founders, not specific to this post: If sales is one of your primary skill sets, and you cannot sell one developer on working for you, you may want to have a brief heart-to-heart with yourself on whether you are sufficiently skilled at sell…

> 1) General advice to non-technical founders, not specific to this post: If sales is one of your primary skill sets, and you cannot sell one developer on working for you, you may want to have a brief heart-to-heart with yourself on whether you are sufficiently skilled at selling to build a company which will live or die based on your sales ability. But I think "selling" the product to a developer is a difficult sell…

Cash or no cash, I believe the key for a developer is working on an interesting problem + having impact. If you have real companies offering real money for a product that don't even exist, at least the developer can be convinced that his/her work will have impact.

Re: Lessons learned from my failed startup after 2 years, 300 users and 0 revenue

#16
post #14

OP, your biggest mistake is not taking the time out to learn how to code yourself. You said it went on for 2 years, that was plenty of time.

INDEED! In fact I started. Did One Month Rails (a couple of months ago). My github (please don't laugh, but do give out advice): https://github.com/sergioschuler/

Re: Lessons learned from my failed startup after 2 years, 300 users and 0 revenue

#17
post #5

This is a fantastic writeup (and like nearly all worthwhile writing on the subject, I don't necessarily agree with all of it). Two elaborations: 1) General advice to non-technical founders, not specific to this post: If sales is one of your primary skill sets, and you cannot sell one developer on working for you, you may want to have a brief heart-to-heart with yourself on whether you are sufficiently skilled at sell…

You are absolutely right on both comments! And additional comments: 1) I am not a developer, but I believe having an idea -> finding a developer is the wrong flow. It should be like this: 1. Have the idea. 2. Get customers who give you real money to build this idea. 3. Get a developer by telling "I already have paying customers". 2) Absolutely agree. When I say "I should build that", in fact what I wanted to say was…

To me it seems like recruiting of a developer worth anything, from scratch and without an existing team to help you to recruit or lure, must be much more difficult than getting an amazing idea or selling said amazing idea. Is that just because I never tried selling anything?

Does anybody have examples of successful startups that proceeded in the way Sergio describes and became successful -- starting out with a business person/team, selling the goods first, then manage to find developer(s) to build it? (It's not rhetorical, I'd love to hear such examples -- the usual stories seem to be revolving around a gang of programmers, or at least a programmer co-founder.)

Re: Lessons learned from my failed startup after 2 years, 300 users and 0 revenue

#18
post #7

Lesson N+1: Hacker News can break your blog's webserver. That's one you only learn through experience. [ETA: which is sad, because I want to read it!]

Damn Bluehost, hehe. I wish I knew how to fix it, but a few refreshes seems to go through.

I wouldn't blame your host, actually. It's WordPress. It's a shame it's so often given a free pass on these issues when it really isn't good at handling peaks in traffic.

Re: Lessons learned from my failed startup after 2 years, 300 users and 0 revenue

#19

Earlier quoted context omitted.

> 1) General advice to non-technical founders, not specific to this post: If sales is one of your primary skill sets, and you cannot sell one developer on working for you, you may want to have a brief heart-to-heart with yourself on whether you are sufficiently skilled at selling to build a company which will live or die based on your sales ability. But I think "selling" the product to a developer is a difficult sell…

Cash or no cash, I believe the key for a developer is working on an interesting problem + having impact. If you have real companies offering real money for a product that don't even exist, at least the developer can be convinced that his/her work will have impact.

But I think a strong trend will be that less experienced and less skilled (and over-confident) developers will be more easily lured. How do you counter this trend when recruiting, and filter for the one that is skilled enough but still can be lured? You can't just take any developer to be solo developer for a startup (much harder than team development), especially to work on somebody else's idea.

Re: Lessons learned from my failed startup after 2 years, 300 users and 0 revenue

#20
Do people find it really ok to have video and a website spelling "try it free" and then have only an email input form ? I know that testing if demand exists is important, but doesn't it have adverse effect on your reputation to somehow lie to your prospects ?
Post reply on HN