The second thing that any technology startup must do is to take the market. - Ben Horowitz

In good organizations, people can focus on their work and have confidence that if they get their work done, good things will happen for both the company and them personally. It is a true pleasure to work in an organization such as this. Every person can wake up knowing that the work they do will be efficient, effective, and make a difference for the organization and themselves. These things make their jobs both motivating and fulfilling. “In a poor organization, on the other hand, people spend much of their time fighting organizational boundaries, infighting, and broken processes. They are not even clear on what their jobs are, so there is no way to know if they are getting the job done or not. In the miracle case that they work ridiculous hours and get the job done, they have no idea what it means for the company or their careers. To make it all much worse and rub salt in the wound, when they finally work up the courage to tell management how fucked-up their situation is, management denies there is a problem, then defends the status quo, then ignores the problem.

Let’s look at the case of Opsware. Why did I sell Opsware? Another good question is why didn’t I sell Opsware until I did? At Opsware, we started in the server automation market. When we received our first inquiries and offers for the server automation company, we had fewer than fifty customers. I believed that there were at least ten thousand target customers and that we had a decent shot at being number one. In addition, although I knew the market would be redefined, I thought that we could expand to networks and storage (data center automation) faster than the competition and win that market as well. Therefore, assuming 30 percent market share, somebody would have had to pay sixty times what we were worth in forward credit to buy out our potential. You won’t be surprised to find that nobody was willing to pay that. Once we grew to several hundred customers and expanded into data center automation, we were still number one and were more valuable stand-alone than any of the prior acquisition offers. At that point both Opsware and our main competitor, BladeLogic, had developed into full-fledged companies (worldwide sales forces, built-out professional services, etc.). This was significant, because it meant that a large company could buy one of us and potentially execute successfully (big enterprise companies can’t generally succeed with small acquisitions, because too much of the important intellectual property is the sales methodology, and big companies can’t build that).

I often see teams that maniacally focus on their metrics around customer acquisition and retention. This usually works well for customer acquisition, but not so well for retention. Why? For many products, metrics often describe the customer acquisition goal in enough detail to provide sufficient management guidance. In contrast, the metrics for customer retention do not provide enough color to be a complete management tool. As a result, many young companies overemphasize retention metrics and do not spend enough time going deep enough on the actual user experience. This generally results in a frantic numbers chase that does not end in a great product.