If you see any errors or omissions, leave a comment and I’ll fix it.

I’ve started more than six microISVs over the last decade and, not counting the open source projects, none of them made it to market. Why? Let me tell you…

The internet is littered with the tumbleweeds and debris of startups that failed to launch. The evidence of them is right there in the blogosphere if you know what you’re looking for. It usually goes something like this.

Post #1 – Day 0: Welcome to microInitech! We’re going to change the world.
Post #2 – Day 1: Well, I’ve got everything in place to start coding…
Post #3 – Day 7: Got most of the framework built.
Post #4 – Day 20: Sorry I haven’t blogged much, I’ve been so busy!
Post #5 – Day 40: Here’s a link to a cool random web page I found.
Post #6 – (3 years later): My pet died today. I’m sad…

Now, don’t get me wrong. These are smart people with lots of talent and motivation. They didn’t fail because they were incapable. They didn’t fail because they were unable to produce a good — or perhaps excellent — quality product that would truly make someone’s life easier. They failed for one of the following three reasons.

My life goals were not compatible with the business’ needs. This is the primary reason I’ve never successfully launched a microISV. Running a business was never compatible with my goals for my life.

It’s taken me more than forty years, but I’ve finally learned to see myself from the outside. Today, I intellectually understand more about what motivates me and my actions than I ever did “growing up.” Looking back on the last decade, I clearly see that my priorities have been: me, my family, my friends, and my faith. I also see how I love helping people and I’m motivated by that “ah, ha!” moment people get when I teach them something. Lastly, I know that I love writing code, seeing it run without crashing, watching something spring forth from nothing.

I didn’t see anything in there about wanting to run a business. Did you?

Operating a microISV involves wearing a lot of hats. Just ask Bob Walsh. He’s built an entire business model around your to do list.

When I started each of my microISV projects (I really shouldn’t call them microISVs, since they were never more than an exercise in writing code), I was motivated by one of two things. I either had a really cool idea, or I wanted to make some side money and I figured it would be easy. These were the wrong reasons and that’s why I always failed to launch.

So, what are the right reasons for launching a microISV? Well, that depends on you. First, you need to figure out what your personal goals are and decide if they are compatible with the work that goes into starting a microISV. For example, you may want complete control over your work environment, from hours of operation, to location, to the dress code. This is control you’ll never possess working for someone else.

Once you know what your personal goals and motivations are, look carefully at what is involved in running a business. I mean really think about what you’re getting into. I didn’t, which is brings us to the second reason I never launched a successful microISV…

I didn’t truly understand what goes into running a business. My father-in-law owned and operated a small print shop for over thirty years. He learned that running a print shop involved more than putting ink to paper. There were taxes, accounting, suppliers, delivery, advertising, and customers. Boy, were there customers! Ones that didn’t pay. Ones that were never satisfied. Ones that needed it now! Ones that needed it better than perfect.

My father-in-law doesn’t know a compiler from an icon. But, it’s blindingly obvious to him that you’ll be doing more than pushing bits when you start your microISV. Let me list some of the issues you’ll have to deal with as your microISV goes live: piracy, data security, licensing, SEO, marketing/advertising (yes, their different), graphic design, copyright, risk management, accounting, taxes, sales, legal, hosting, web site administration, and customer support. Boy, will there be customer support!

Many of you are thinking you’re perfectly comfortable learning and doing those things, right? And, that’s the great thing about us. We’re really good at adopting new skills. Here’s the rub. You’ll be doing these things more than you’ll be coding. Let me say that again, with more emphasis…

You’ll spend more time on business operations than on creating and enhancing your product.

Let that sink in. Think about it for more than a moment. Doing paperwork for your accountant and the tax collector. Constructing marketing materials with just the right fonts and whitespace. Checking with a lawyer on the solidity of your license agreements. Listing and prioritizing risks and mitigation strategies. Sending DCMA takedown notices to copyright violators and software pirates. Answering the same customer support questions over and over and over again.

For me, I never really considered these aspects. Oh, I intellectually knew what I was doing, but I never really thought about doing them. Day after day. Which leads me to my last point.

I didn’t really want success. I just wanted to create something. I love writing software and occasionally I get an “itch” to write something. It runs on a cycle of every two years or so. I see a gap in the market for something I now I can create, so I create it. When I’m working on it, it consumes me. I think about it all the time. I talk about it with my wife. I show it friends and colleagues. I draw up business plans. I design marketing websites. I start writing blog entries.

Then, a funny thing happens. I get close to finishing and the fire dims. The need to create is satisfied. I lose focus and interest. I can only assume this is how artists feel when they sculpt and paint.

My microISV never launches. I add to the litter. Another tumbleweed on the internet.

Well, that was depressing!

My purpose in writing this is not to discourage you. I want to open you eyes. One day, you may find yourself wondering why you can’t seem to get your microISV launched. One day, you may wonder why it’s launched but no ones buying. Or, you may be there already.

If you are, you need to ask yourself. Am I doing this for the right reasons? Are my personal goals in line with the business? Do I really want to succeed? Am I spending my time on the right things. (Hint: if you’ve already launched, its probably not time to focus on coding).

Once you know you’re launching a microISV for the right reasons, you can focus on doing the right things. There are countless resources available to get you to the chasm and across it. Find those resources. Stretch your limits. Build new skills. Succeed.

Your microISV doesn’t have to be another tumbleweed.

For information about research into microISV operations, visit the microISV Research Alliance website, where you will find links to popular microISV resources.