Running a Software Business on 5 Hours A Week
kalzumeus.com
kalzumeus.com
Patrick is trying to derive generic advice by formalizing his personal experiences. While it is useful to know what worked in his case, it is still just one project, an isolated experience.
I've been in a similar situation myself. I have sold a startup that settled me and my family for life, and things unfolded pretty much as I expected them to from the start to the acquisition. But the more I think about the whole experience now the more I am becoming convinced that there was a great deal of chance involved. And over the years I started describing my startup less in terms of how things should be done and more how they worked for me.
In other words, once you are lucky, twice - you are good. Once you are "twice", then it will be Insightful. Until then it's just Interesting. Feel free to disagree ;)
o Code is 10% of the business
o Wall Clock Time vs. Calendar Time
o Avoid Events, Plan for Processes
all seem broadly applicable and non-obviousIs pretty obvious to anybody that's ever had or worked in a business.
The other two are common sense. But that doesn't mean that it isn't good to re-iterate these things every now and then, but if you fell off your chair because of any of those three sentences then you do not have much - or even any - business experience, and likely are not quite ready to make the jump.
There are some much deeper insights in that piece than those:
- I started this business to make an extra $200 so I could spend it on video games without feeling guilty
That's a really good one, it shows you that no matter what goal you have when you start out your business you are not going to be even near it (in a positive or a negative sense) when you're a couple of years down the line. After all, why didn't he stop when he made his goal? Why all the extra work? Clearly we set our goals, then the goal becomes the new 'base', and we set another goal. If I can make $200, how about $400...
Another gem:
- The 'time as debt' view. That's a very interesting way of looking at time, and I think that if it is an original then that alone is a huge contribution to running a small business. It also says in no uncertain terms that if you want to run a small business, any small business, you should learn how to do some minimal automation.
There is lots of other good stuff in there, but those two stand out for me.
One really good thing too, is that in spite of doing this for years, Patrick never quit his job or skimped on it. He waited until the right moment, probably constrained by the $-in-the-bank as well as the amount of money made on a daily basis by the job vs the project.
Of course, one data point like this is useful if we look at all the other stories we get here on a daily basis.
It is worth more these days, but that is because people searching for [bingo card creator] are probably looking for Bingo Card Creator (for example, with five seconds of checking into my stats, I can guarantee at least 30% of folks searching for it last week and clicking on my site already have an account with me).
(Have I mentioned that "Google owns navigation on the Internet"?)
On a related note, I'd be very happy to pay you for an SEO consultation.
"Organic searches with the word 'bingo card' makes up ___ percent of my sales."
As you say, tho-- might be hard to parse out brand searches. But every single one of your holiday-specific landing pages benefits from "bingo card" being in your URL. Isn't long tail SEO a big part of your acquisition?
OPs time as an asset/debt idea is right up with what I believe, since people seem to believe their time is free...I believe it's better off outsourced so I can spend the one resource I'll never get back. Good article.
:)
I generally buckle down for a few weeks of hard coding (meaning 4 hours a day for 3 or 4 days a week), once or twice a year, and the rest of the year I'm just doing customer service, system administration stuff, and limited marketing. Just maintaining the architecture for the sites is the biggest time sink -- one of the webapps has two different kinds of database servers (MongoDB in the front, MySQL in the back), web servers, worker servers doing incremental processing/rollups... and I keep things PCIDSS compliant which means self-audits, lots of security patching, etc.
Running affiliate programs for my products and encouraging customers to use them to refer others has been extremely important. Affiliates do all the PPC marketing, article marketing, social bookmarking FOR me, with their affiliate links.
Just goes to show there are a hundred ways to run a successful business. The venture backed 60-hour-week startup isn't the only option.
I realize that HN doesn't encourage heavy self-promotion, but what is this business? Where is its website? Your story sounds wildly implausible, though it obviously isn't impossible.
Still, it reminds me of the comments I got on my post about "You’re Not Going to be a Professional Blogger, Regardless of What the Wall Street Journal Tells You:" http://blog.seliger.com/2009/06/17/youre-not-going-to-be-a-p... . People would say things like, "I run a group of online entrepreneurs, and am a member of another, and between the two groups there are well over 200 people, a majority of whom are pulling down 6 to 7 figure incomes based primarily on the advertising on their blogs, not by “selling ancillary services.”" But they wouldn't link to the sites in question! To me, such claims smell bad.
I'm extremely open about my business. I've thought about writing this type of article to share on HN before, but it always comes across as bragging instead of sharing so I can the idea soon after starting.
This is not an overnight success story. I earned my first paycheck on the internet when I was 15 or so, 10 years ago. I've had a long time to build my skill at development and marketing, try ideas, and build up my user base across the websites.
Some of the sites took a year or two to break even on up front costs and hardware. But since I build services that require almost no ongoing development or support beyond basic "how do I sign up, where do I find feature X" questions, each customer added in the following years is almost pure profit.
Very incremental, steady growth, and sometimes a leveling off. A bigger business wouldn't want a site to level off at a couple thousand a month in revenue, but if it's only supporting and supported by one person, a couple of those and yes, you hit 6 figure annual profit.
I also sell websites from time to time, if they level off and it seems like it'll require more work than I'm willing to put in to reverse that trend. Here's a site I sold on Flippa for $90,000 earlier this month. It generated over $200,000 in sales in the 18 months leading up:
http://flippa.com/auctions/84185/11000month-Revenue-No--1-In...
I'm trying to do something similar with http://visualwebsiteoptimizer.com/ - hopefully I will also be able to join the "5-hour workweek" club.
Thanks for replying. Yup, I am committed to the product and thankfully it has been positioned as one of the easiest website optimization products available. What I meant by the comment was that I was quite impressed by W3ROI as a product and thought it was a consistent effort. But when I realized it is a "5 hour" effort, I was really surprised.
Rest assured the product isn't going anywhere. I have built a team (not a single man effort anymore) and is a serious startup now. What I said was a bit like hyperbole, sorry if it came across as I am abandoning the product :)
Personally, I'm always interested in such stories about running businesses on the side or full time. Businesses, mind you, not startups aiming to sell in a year. Those are very different in terms of decisions taken and work style and such.
Plus, if you've got it, flaunt it.
And this is not "work four hours per week to gain huge success in life". Like everything else he writes, this is backed by expedience, external constraints, and data-backed experience.
Patrick's business is what I call the Chicago School of Startups. (I might have just made that up.) (And at the risk of tweaking Joel, as Fog Creek Software seems to be following the Chicago model.) This is, like 37Signals, a self-funded operation, and eventually self-sustaining. The SV School, or more precisely, the YC school, emphasizes the path of seeking venture capital, and has the side benefit of a seriously enviable network of other founders and former founders.
What has been most interesting is the data-driven nature of his decisions. Many longwinded discussions on HN have focused on the importance of design,. Patrick, among others, points to A/B tests (not to mention highly successful sites like Craig's List) indicating that such design obsession might be misplaced. Minor heresy: while Mac developers are very graphically intensive people who will buy software just to lick it if the UI is good enough, many Mac users are just regular people. My Mac version has a conversion rate fully twice that of the Window version, and it is not noticeably pretty.
Perhaps there is a little leeway to tease Patrick--it does not seem that this five hours per week is sustainable. It is successful enough that he is quitting his day job, and I bet he now can't help but spend more than five hours per week on it. Congratulations.
It is a very open question how much I'm going to be working after I go "full time", but I've rarely seen myself do great things after ~20 and that would leave me with plenty of time to catch up on living, so I think I might try that on for size. But hey, if I decide to do more or less in any given week, there won't be anybody to tell me not to.
If you can do this one on average at 5 hours per week, theoretically after the initial burst you could sustain 8 such jobs in parallel.
This is one of the more important bits of advice I've seen Patrick give, and I think it applies to those of us full-timing with our companies even more. Your lawyers are going to tell you that contracts matter a whole lot, too. And just like Patrick with the company in Nagoya, your ability to prevail in a dispute, contract or not, is usually going to be nil.
This is something I think a lot of us learn the first time they get into a dispute (for instance, when we are first aggrieved by a giant business partner who breaches our carefully-considered contracts.)
The reason contracts don't protect businesses is that they cost too much to enforce. When you're not in the same league as your adversary, they will simply outlast you. The same dynamics do not apply to an attempt by Consolidated Gypsum to make themselves whole on a debt by trying to take your house.
Incorporate early. There's no good reason not to.
"Are you considering starting up a business because you wish to work on wonderfully interesting technical problems all of the time? Stop now — Google is hiring, go get a job with them. 90% of the results of your business, and somewhere around 90% of the effort, are caused by non-coding activities"
But... then who is eligible to build a complex product? Like writing a database from scratch, or some other complex piece of work. I think a startup should also be able to do it somehow.
In Patrick's case, doing it this way got him from full-time job to full-time startup entrepreneur without taking a dime of money from anybody but his customers. We'll see what he comes up with after a few years of doing it full time.
Finally, writing a database from scratch? Crappy business to get in to even if you're full time!
As for who is eligible to build a complex product? Nobody. If you set out to build a complex system from the start, it invariably won't work at the end. Remember Gall's Law:
http://en.wikipedia.org/wiki/Galls_law
Before you cite counterexamples like Linux or Google, it's worth considering what they looked like when they started. Linux started as a terminal emulator that would spit back "ababa" when you turned on the computer. Google's early webserver was a dozen or so source files that looked vaguely like Tornado, except that instead of having all those webframeworkey goodness like regexp-based dispatch rules and templates, it would just issue "prints" on the file descriptor for the user's connection.
If you want to write a database from scratch, you should start with some sort of basic persistent key/value store. Then give your values a column-like substructure. Then figure out how to index it. Then figure out how to index it based on multiple columns. Then figure out how to handle joins and sorts. Then slap an SQL parser on top of it, and you'll have something similar to MySQL c. late 1990s. Then endure all the laughs as people say you're not a "real" database, and put in 10 years of incremental improvements while you add transactions, and better SQL compliance, and query optimizers, and wire protocols, and replication, and clustering, and all that stuff.
At the beginning of last year I made a similar move from being a Japanese salaryman to my own business. I was writing code in a notebook on my 1.5 hour train commute and on my lunch break and then typing it up on weekends. After I went full-time on my own business I found that the scope of what I wanted to do expanded and my productivity dropped. Also, the time-management skills that worked well on a part-time basis didn't work as well when I went full-time. I also found that it was easy to get sidetracked by side-projects and that personal life (time with friends, holidays) became a larger part of my life. I also found that a lot of things that I wasn't so great at (web design, graphics) etc. took up a large amount of my time.
So I would be interested to hear your thoughts on time-management, prioritization and working from home once you go full-time if you decide to do this as a series.
Oh man. Maybe it's just me being an ignorant American, but doing that for anything but a company you founded is just crazy. I can't believe that's the norm in Japan.
This hits close to home as I am gradually learning that I provide far more value to the world by using my knowledge to have others do technical implementation than if I were doing it myself. For someone who loves code, it's a painful transition. But I think you can learn to love business just as you learned to love code.
So yeah, you get more leverage by using your knowledge to mentor others to do the development for you. But you could end up getting stuck as CEO of a startup that's in a backwater corner of the industry, rather than as a developer in a company that's doing interesting world-changing stuff that you can then leverage when you start your company later.
Regarding 'backwater corners' - isn't this article about how to provide value in the backwater corners of the software industry? Printing and generating bingo cards is about as backwater as you can get, but I see nothing wrong with that. I'm also in the food industry and I understand that you don't grow up to be McDonald's (a restaurant which has - from my perspective - provided incredible value all over the world) overnight. Ray Kroc grew McDonald's by serving what was then an expensive burger to a niche clientele. Then he expanded from there. I don't see why a similar strategy isn't sane in the software industry.
The point is not "I'm not capable of coding this, I must hire someone smarter", it's "I'll manage someone to do the coding I don't have time for, and they can observe my attempts to run the rest of the business (or whatever)."
That's the number one reason why some clients of mine comeback to me saying their last developer didn't quite accomplish what they wanted. And the reason why sometimes I have to struggle to fix bugs and identification (yes, many low-cost devs don't have a tab key) on other peoples code.
You normally get what you paid for, but I hope it worked nice for you.
Hell, most IDEs would indent your code correctly for you, I'd have to actually work to override eclipse's auto-indentation!
Seems like once you've finished working 10 hours every day for your lifetime employer, there's not much to do than the obligatory heavy drinking!
The upside to it is miniscule: I know I can sell thousands of copies of software for $30, because I've done it, and am reasonably certain that I could sell accounts at a new SAAS for $100 / month, given time to work on it. I am not sanguine about my ability to sell thousands of copies of a book/ebook -- my most loyal blog readers number in the hundreds, if that. I'd also expect massive pushback on the prices that I think make sense -- for examples, take a look at every launch of a non-software info product on HN. (I think I'd be particularly at risk for that because a non-trivial portion of my audience likes the fact that I started a business for $60 -- and when you have $60 in your budget, $X00 on a book is right out.)
There are also psychic costs to me. I kind of value my participation at HN and the Business of Software, for example. It is my sanity-preserving lifeline. I'd really hate to have every post carry the implicit disclaimer "Warning! He is trying to sell you something."
As far as I can tell, writing a dead tree is /easier/ than writing a ebook, and distribution is easier, etc... you keep less of the money, but more of the credibility.
If you have competition like in 99% of the niches...you'll be working a lot more than that
His points are especially relevant to people working with lots of competition.
In a broader sense of the word "competition", my program is a proper subset of Microsoft Excel, I compete with the world's savviest Internet publishers (like Demand Media) for large portions of the queries of interest to me, and a portion of my queries are dual-use for a multi-billion a year industry. (Teachers are not the only folks interested in the top ten for [bingo cards].)
I mean, its not like I went and made a URL shortener or zip file extractor, but I also didn't go make something so staggeringly unique the world had not heard of it before or since.
(I have always paid by task, not by hour -- as you might have noticed I tend to center on small, well-defined projects with easily verified deliverables. I cultivate trust with my freelancers such that they know I'm not going to screw them on a neverending scope-creep deathmarch for the $400 project. Thus, I've really got no clue whether they're taking their sweet time doing projects or figuring out ludicrously efficient ways to do them and earning more per hour than I do -- and if they have done that, bully for them.)
Peace.
http://www.kalzumeus.com/2009/12/18/bingo-card-creator-year-...
All the power to him however.