Live data from Hacker News

Building a Web Application that makes $500 a Month – Part I

tbbuck.com

111–119 of 119 posts

Re: Building a Web Application that makes $500 a Month – Part I

#111
Love how he cited the crappy design as the main reason why the app sucks ... Then proceeds to put the minimum effort into design to adress the problem. Give a designer a chance to work for you, you will end up with a result that is better but more importantly unique.

Re: Building a Web Application that makes $500 a Month – Part I

#112

Hey guys, not sure if anyone has realized, but for SaaS projects the Extended version of the theme is required. So $1000 is what he should have paid for the admin panel... I hope no one involved with ThemeForest finds out :)

Further evidence why hiring a real designer is better and can be cheaper than buying a pre-baked theme.

Re: Building a Web Application that makes $500 a Month – Part I

#113
post #72

Thanks for writing this up! We're currently going through a similar experience. The good news is that we went from 1 signup a month to quite a few per day (with a few days at over 100 new signups) -- mostly by following things that we've learned here on HN. A few weeks ago, my co-founder was getting pretty bummed out and was starting to look like throwing in the towel...then we managed to get covered in a few places…

Sounds like your hard work paid off indeed! Care to elaborate on how you gained users? Did you only email editors, or did you have other strategies as well? What were your pitches like? I'd love to hear!

I'm working on a blog post that'll probably provide some more (and different details) but here's our story:

Well, since we launched only a few months before, we were still a little scared as to how the site and service would scale (and how much our server bill would jump). So we wanted to grow kinda slowly so we could manage it effectively.

Our strategy then was to reach out to editors or writers of smaller sites that seemed like they were in our milieu, and see if any of them showed any interest. I think we contacted...30 or 40 editors.

We actually didn't get any coverage at all, which was really disheartening. But we kept plugging away on the site and the app, adding a couple additional features. In the meanwhile I kept sending out emails, filling out forms. Users kept trickling in.

We also started using our own app ourselves, sending out Momentomails to our friends and to each other. Making sure the service was live and validating the idea...building up expected user patterns, establishing acceptable levels of service quality...etc.

One thing we found slightly disturbing, was the large number of sites that offer different levels of review prioritization depending on if you email them and expect some free coverage, or if you pay them. And I suppose I can see how that could be an interesting revenue channel, but if I wanted to pay somebody to cover me, I'd probably just buy ad space...so it felt kinda scammish and we decided not to do that. Our service should either be interesting and useful on its own, or we should keep working on it until it is.

On a whim, I decided to send out a contact to some bigger sites, Lifehacker being one of them. Still nothing.

About two weeks after submitting to Lifehacker, this happened: http://lifehacker.com/#!5787941/momentomail-sends-messages-f...

I'm not sure how much getting covered on Apr 1st hurt us or not (we answered a few user contacts answering if we were real or not). But we had a massive spike in new traffic. Massive. We couldn't even see some of our previous spikes on the graph it was so huge. We floated around the top 10 hot sites on LH for two or three days so the spike extended out for awhile.

So far, LH has been the only major site to cover us, but it's let us observe how things spread on the internet. If you search for Momentomail in google, you'll find dozens of pages where we show up, almost all reposts or links to LH's story. A few tweets bounced around the tweetosphere...(or whatever it's called)...and very interesting -- foreign translations of the LH post, showing up a few days later, sent us echos of the initial spike.

Suddenly a rush of Italian users, or Turkish users, or Indonesian users. We haven't gotten the metrics yet, but anecdotally, it looks like about 20% of our new signups are now coming from Spanish language countries...which is pretty exciting.

It's definitely slowed down, and we're still kind of processing all this new traffic, but there's a steady stream of new signups everyday. We've found a few bugs were squashing. Once we add a couple planned (and highly requested features) we'll probably go around and recontact many of the sites that we contacted before...but also the sites that carried our story from the initial Lifehacker story.

In case anybody is interested, some fun notes: we run on GAE, and we had our quota set to a cap of about $5/day, before the LH story, we'd barely even showed up on the quota data (we'd only been using the free service). The week of the LH story, the quotas showed some activity, but we never broke Google's free quota. So our hosting fees so far on GAE are $0. It's definitely a cost effective way to bootstrap a new product. (though secretly we hope to have to "good problem" of having to increase our quota cap).

Re: Building a Web Application that makes $500 a Month – Part I

#114
post #76

Earlier quoted context omitted.

> I recently had to make changes to my own service because the Twitter API policy team didn't like me telling people who unfollowed them. Just curious: which section of the Twitter API ToS do you read as restricting notifying them of people that unfollowed them? I know that the API policy explicitly prohibits automated unfollowing and restricts automated following, but haven't ever seen anything that addresses notifi…

They referenced Section II.4.B, namely since native Twitter apps don't "organically display" unfollows, you should not as well. > Respect the features and functionality embedded with or included in Twitter Content or the Twitter API. Do not attempt to interfere with, intercept, disrupt, filter, or disable any features of the Twitter API or Twitter service, and you should only surface actions that are organically disp…

Ah, that does seem to follow from the quoted section. Thanks for referencing it, I appreciate it.

It's a big bummer as a potential Twitter-hacker, too. I can see why they wouldn't want clients & add-ons to surface unfollows, but it blankets quite a bit of functionality, and then it comes down to an issue of selective enforcement. Sigh.

Re: Building a Web Application that makes $500 a Month – Part I

#115
Thanks, an interesting read that puts a lot of the other "I'm so amazing because my rails app makes me and my uni buddies £50k a month" into perspective.

But I'd echo the comments above - would be good to see the next posts go up soon in particular to what you actually started doing differently that saw it increase. Maybe others here will be able to build on that to give some advice to turn that $500 into $5k :)

Re: Building a Web Application that makes $500 a Month – Part I

#116
post #113

Earlier quoted context omitted.

Sounds like your hard work paid off indeed! Care to elaborate on how you gained users? Did you only email editors, or did you have other strategies as well? What were your pitches like? I'd love to hear!

I'm working on a blog post that'll probably provide some more (and different details) but here's our story: Well, since we launched only a few months before, we were still a little scared as to how the site and service would scale (and how much our server bill would jump). So we wanted to grow kinda slowly so we could manage it effectively. Our strategy then was to reach out to editors or writers of smaller sites tha…

Wow, great! Thanks for all of the details. Really helps to put things into perspective. Sounds like you're doing all the right things and hustling away.

The reason I'm curious is because I "launched" my first web app a few months ago. In actuality it was just a feeler to see how the product faired in the wild - core functionality was there, but greatly lacking features. The only place I shared was HN and it was received tremendously well. It hung out on the front page for the majority of the day, resulted in thousands of hits and hundreds of signups, with more trickling in during the weeks following. At the time, I was reluctant to promote anywhere else before incorporating a few new features. Unfortunately, I was pulled away by more demanding projects, so I haven't had time to make all of the changes and features I had planned on (or marketing), resulting in significantly decreased traffic.

Now that my other projects are winding down, I can focus more time on building and promoting this app. Stories like yours help a bunch, so I appreciate the details.

Could I get your e-mail address? I'd love to stay in touch, but I don't see it anywhere in your profile.

Re: Building a Web Application that makes $500 a Month – Part I

#117

The fact that this article is so popular is sort of sad.That shows that a lot of people on HN are not making $500 a month from their web apps .We should have higher goals than this.

I agree, kinda. I'm glad for the author's success so far (and, as another HNer said, that the word "lifestyle" has not yet reared its head in discussion). On the other hand,back in October, about how my products had brought in $216,000 in revenue in 2010 to date (from $0 in 2008), and I got maybe 30 votes on HN, barely made it onto the front page: http://unicornfree.com/2010/i-made-216668-from-products/ Which leads t…

For me, I prefer the OP's article as it's very much from the perspective of someone still "in the trenches", whereas your artcle seems to be approaching it from the angle of already being through the trenches and reflecting on how awesome it went.

I suppose it's like comparing watching Rocky to watching 2 hours of Lennox Lewis in his prime, you want to see the progression happening, not necessarily look back.

That would be the main point from my perspective and it's simply a matter of preference.

Re: Building a Web Application that makes $500 a Month – Part I

#118
post #113

Earlier quoted context omitted.

I'm working on a blog post that'll probably provide some more (and different details) but here's our story: Well, since we launched only a few months before, we were still a little scared as to how the site and service would scale (and how much our server bill would jump). So we wanted to grow kinda slowly so we could manage it effectively. Our strategy then was to reach out to editors or writers of smaller sites tha…

Wow, great! Thanks for all of the details. Really helps to put things into perspective. Sounds like you're doing all the right things and hustling away. The reason I'm curious is because I "launched" my first web app a few months ago. In actuality it was just a feeler to see how the product faired in the wild - core functionality was there, but greatly lacking features. The only place I shared was HN and it was recei…

yeah!

I updated my profile.

It's banehn and I'm on gmail.

Re: Building a Web Application that makes $500 a Month – Part I

#119
post #76

Earlier quoted context omitted.

They referenced Section II.4.B, namely since native Twitter apps don't "organically display" unfollows, you should not as well. > Respect the features and functionality embedded with or included in Twitter Content or the Twitter API. Do not attempt to interfere with, intercept, disrupt, filter, or disable any features of the Twitter API or Twitter service, and you should only surface actions that are organically disp…

Ah, that does seem to follow from the quoted section. Thanks for referencing it, I appreciate it. It's a big bummer as a potential Twitter-hacker, too. I can see why they wouldn't want clients & add-ons to surface unfollows, but it blankets quite a bit of functionality, and then it comes down to an issue of selective enforcement. Sigh.

You're welcome.

The way I read it is "don't do things we don't already do" which is a really bad constraint, effectively forbidding any kind of innovation. I can understand the spirit of their selective desire to address this specific violation, but I'm not convinced it's as much of a problem as they're making it to be.

Oh well.

Post reply on HN