The Arsdigita story
Saturday, January 2nd, 2010I am surprised that I’ve never before linked to all of this stuff. This story has shaped my thinking on a lt of things. First of all, I learned SQL by reading Phillip Greenspun, back in 1999. And the way Arsdigita fell apart (and Greenspun’s and Michael Yoon’s and Eve Anderson’s various accounts, have played a huge role in how I think about a large range of issues, from funding, to startups, to ethics, to how different people try to manage the truth.
Michael Yoon’s account has always struck me as possibly being the closest to the truth, partly because he is the most self-critical.
So now I present an alternative perspective, the lessons that I learned from ArsDigita, both good and bad. This is not an apologia for the VCs who funded ArsDigita or for the post-VC management of ArsDigita, of which, for a time, I was a member. I recognize that the VCs and the management team (again, I include myself) made many mistakes and, at times, committed outright wrongdoing. My hope is to show you that there is much more to the story than what Eve wrote in her diary and that my truth is not as black and white as hers.
…Eve’s article reminded me, ironically, of the story of Adam and Eve. According to her, pre-VC ArsDigita was truly Edenic:
A company that was profitable from Day 1. A company that built products that were useful to many other companies. A company that had ethics, that treated the breadwinners (programmers) with respect, a company that could afford to help people and give away software and training, while still having enough left over to grow and save a few $million in the bank.
Then came the Fall:
… until the venture capitalists arrived on the scene. Lying to customers and employees became commonplace. Greed replaced philanthropy as each of the company’s unique programs was dropped. … The technical and managerial incompetence of the VCs and those they hired drove the company into the ground.
I read Milton in high school, so Eve’s thesis is clear enough to me: Venture capitalists = Satan.
But what exactly happened when the VCs “arrived on the scene”? Did they arrive in a Publishers Clearing House Sweepstakes van, ring the doorbell, hand us one of those enormous checks, and then trick us into signing it before we could read the fine print? Or did they break down the door, walk us down to the ATM at gunpoint, and demand that we deposit their $38,000,000? Facetiousness aside, my point is that the management of pre-VC ArsDigita (including Philip) signed the VCs’ term sheet of its own free will. (In the spirit of full disclosure, I should mention that I thought that taking the money was a good idea, mainly because I thought we were going to go public and get rich; had it been up to me, I probably would have made the same decision.)
Eve’s description of the transaction itself is impersonal: “In late March 2000, ArsDigita received $38 million in financing, primarily from General Atlantic Partners and Greylock, with a bit thrown in by Bain and Trident Capital as well.” ArsDigita is presented as a passive entity, not doing anything, just receiving, but that is misleading. We were not merely receiving; we were taking.
So why did we take? What was the Forbidden Fruit that tempted us to risk Eden? Here is Eve’s explanation of why we took the VC money: “A small group of developers earning lots of money, making clients happy, and developing and releasing a useful software product is wonderful, but … to make a substantial impact on the world, you gotta grow.” On the desire to make a substantial impact, I agree with Eve. I came to ArsDigita with a deep cynicism about the IT industry, and saw ArsDigita as an opportunity to show the world a better way. (When it appeared that we might make a lot of money in the process, that only made me happier.)
Of course, “making a substantial impact” is a rather vague goal, so I’m not even sure if my definition of “a substantial impact” coincides with Eve’s. My main objection, however, is to the implication that a blend of altruism (”making a substantial impact”) and manifest destiny (”you gotta grow”) was the reason that we took the VC money. In the open source world, there are many examples of software (notably, Linux and Apache) making a substantial impact on the world without the benefit of a large infusion of VC cash.
Philip’s explanation of why we took the money is more substantial than Eve’s. The first reason he presents is: “Companies don’t like to rely on enterprise software from small companies. There is too much risk that the vendor will go bankrupt. Open source ameliorates this risk to some extent but the tendency to stick to IBM, Microsoft, and Oracle is strong. We tried to present a face of financial invincibility to the world.” In other words, companies would refuse to buy from us unless we could appear to be “financially invincible,” an appearance that, presumably, we’d project by sitting atop a mountain of VC cash. Certainly, a 38 million dollar vote of confidence from top-tier VC funds is a boon when trying to persuade prospective customers of your staying power, but, just a few paragraphs earlier, Philip relates how “customers were knocking like crazy,” name-dropping Siemens as “a good example” of our clientele, brought to our door by the Boston Consulting Group. With one of the world’s largest corporations on our client list and one of the world’s most prestigious management consultancies as our partner, weren’t we already defying the conventional wisdom that said we had to have VC backing in order to land big customers?
Philip provides three more reasons for taking the capital:
We figured that we could use the extra money to place some bets on product development and marketing. Under the product development rubric we thought we’d not make the client teams carry the full weight of ACS development on their shoulders. If they found a client whose needs were similar to what we wanted in the product, we’d do the job for a low-ish price to get experience with that problem … and develop reusable code to enhance ACS. Under the marketing rubric we’d expand our “education marketing” program. Finally, we wanted working capital. A company with $20 million in revenue really needs to have about $10 million in the bank in case a customer doesn’t pay, the economy turns soft, an important project is late, etc. Because we’d been growing 1000 percent per year we never had more than a couple of million dollars in the bank.
These all seem reasonable enough, but were they, in addition to the Face of Financial Invincibility, really compelling enough — independent of any other consideration — to convince Philip, the majority owner and CEO, to sign that term sheet, to give up his complete control of the company? I don’t think so. I think Philip wants to have it both ways, maintaining that ArsDigita was so innovative and visionary that giants like Siemens came to us, while, at the same time, claiming that we needed VC dollars and the VC stamp of approval in order to survive in the market.
So what else was motivating Philip? My theory is impatience, a perfectly understandable emotion in those Gold Rush times. I felt it too. When I first joined ArsDigita, Philip used to ask me about Sapient, because he was interested in the fact that they had never taken outside investment and yet managed to make it big. The nutshell version of Sapient’s story is that they started as two guys in 1991 and slogged it out for years, growing organically, until they went public in 1996. In 1999, the notion of waiting five whole years to cash out was absurd. Philip stopped asking me about Sapient, presumably after he’d made up his mind to pursue the VC crapshoot.
Writing now with the benefit of hindsight, my point is not to say “I told you so” (because I didn’t). Rather, my point is that we pre-VC ArsDigitans, must also bear responsibility for what happened to the company.
Writing now with the benefit of hindsight, my point is not to say “I told you so” (because I didn’t). Rather, my point is that we pre-VC ArsDigitans, must also bear responsibility for what happened to the company.
Philip disagrees:
How could these three guys [Peter Bloom (General Atlantic), Chip Hazard (Greylock), and Allen Shaheen (CEO)] have achieved such dreadful results? For that it is worth looking at what kind of leadership is required for a software products company. First, you probably want someone who has previously founded and run a company or been CEO at a company founded by others (i.e., not someone who has been an employee his or her whole life). Second, you probably want someone who has previous experience as an executive in the software products business. Third, you probably want someone with domain knowledge. Fourth, you probably want someone with technical knowledge.
Whatever strengths Peter, Chip, and Allen may have, all three were 0 for 4 on the qualifications listed above.
So what does this say about Philip, that he so poorly qualified his own investors? It’s not as if Philip met Peter and Chip for the first time on the day after we got the money. Philip’s four qualifications are not subjective. From the sound of it, Philip should have been able to ask Peter and Chip four yes-or-no questions each and then rule them out on the spot. If nothing else, Philip is at least guilty of inadequate due diligence.
As for Eve, she concurs with Philip, saying: “Greylock and General Atlantic Partners have mis-managed ArsDigita into the ground.” She does not acknowledge that the pre-VC management made a single mistake, justifying even the decision to accept the VC money with the facile rationalization that “you gotta grow.” She appears to believe that it is 100% someone else’s fault that ArsDigita failed.
To me, this is a gross oversimplification, a symptom of deeply entrenched denial. ArsDigita was a good company, especially in the beginning, and I miss it, the way that it was back then, but I think it’s false to claim that ArsDigita was perfectly noble in its aspirations to grow, an innocent victim of the VCs’ ruthless predations. I also think it’s disingenuous to gloss over the fact that, at the end of the day (to borrow one of our second CEO’s favorite phrases), we took 38 million dollars of someone else’s money.
The truth I see is more complicated. How could it not be? After all, we were, and are, human beings, blessed and cursed with the full array of human traits: idealism, optimism, ambition, arrogance, naivete, jealousy, and, last but certainly not least, greed.
..There is at least one more lesson to be learned, from Eve herself, who writes:
Richard Buck was very impressed with my work and told multiple people that I could do as much work in one day as most people do in two weeks. Given what I’ve written about Richard Buck so far, one might be disinclined to lend much credence to his opinion of my work. But my performance reviews have concurred: dedicated, brilliant, super-efficient, “capable of doing anything she sets her mind to,” extremely high standards, a “tough but fair” manager. So I was certainly no slacker by anyone’s standards.
Eve appears to believe that Richard Buck is dishonest about everything except his high opinion of her. Similarly, she presents snippets from performance reviews as evidence of her own excellence. This excerpt illustrates what I call Oblivious Sacred Cow Syndrome. Whether you like it or not, whether it’s fair or not, if you are a co-founder/team leader/VP/girlfriend of the chairman/etc., you are a Sacred Cow, and people will blow smoke up your ass. I know this from firsthand experience, because I too was a team leader, and I saw people hesitate to be honest with me, for fear of causing offense.
My fellow team leader DVR felt no such compunction when he wrote, in a peer performance review, that I was too concerned about making people happy and that, while he had never seen me offend anyone, he had never seen me inspire anyone either. (He also complained that I didn’t work enough hours, but that’s another topic altogether.) While this criticism stings, as do the criticisms of ACS 4 that I discussed above, I value the fact that they aren’t blunted by Sacred Cow deference, that they are honest, and I have tried to learn from them.
In many ways, the worst thing about being an Oblivious Sacred Cow is that you miss the opportunity to learn from your own mistakes, since no one is willing to tell you when you make one. Of course, if you actually believe your own hype (or appear to), that only alienates you further. I saw this happen to Eve at ArsDigita: While members of Eve’s team frequently complained about her lack of management skills, few, if any, felt comfortable addressing their issues with her directly; instead, many of them simply requested a transfer to a different team. Similarly, while everyone granted that Eve was prolific, people who had to use and/or maintain her code (for example, her ACS 3.x Ecommerce module) often derided it as ugly, full of kluges, etc. Of course, it’s not nice that all of these criticisms were made behind Eve’s back, and the excerpt above makes it clear that Eve is blissfully unaware of these alternate perspectives on her performance and abilities. She would, I expect, say that they are flatly untrue. However, whether or not these criticisms of Eve were completely fair or accurate, the real question is: Wouldn’t Eve herself have been better off if people had felt that they could approach her with their criticisms? At least then, she would have had the opportunity to refute some of the criticisms and learn from the rest.
In many ways, the worst thing about being an Oblivious Sacred Cow is that you miss the opportunity to learn from your own mistakes, since no one is willing to tell you when you make one. Of course, if you actually believe your own hype (or appear to), that only alienates you further. I saw this happen to Eve at ArsDigita: While members of Eve’s team frequently complained about her lack of management skills, few, if any, felt comfortable addressing their issues with her directly; instead, many of them simply requested a transfer to a different team. Similarly, while everyone granted that Eve was prolific, people who had to use and/or maintain her code (for example, her ACS 3.x Ecommerce module) often derided it as ugly, full of kluges, etc. Of course, it’s not nice that all of these criticisms were made behind Eve’s back, and the excerpt above makes it clear that Eve is blissfully unaware of these alternate perspectives on her performance and abilities. She would, I expect, say that they are flatly untrue. However, whether or not these criticisms of Eve were completely fair or accurate, the real question is: Wouldn’t Eve herself have been better off if people had felt that they could approach her with their criticisms? At least then, she would have had the opportunity to refute some of the criticisms and learn from the rest.
Eve Anderson’s account is probably an important contribution to the overall record. All the same, I have trouble giving it the same credit as Michael Yoon’s. First of all, there is no trace of self-criticism, no self-reflection about the obvious mistakes Phillip Grenspun and others did to damage the company (including the initial decision to take venture capital money in the first place). Also, she has apparently removed her essay from her website (the old link simply redirects to the front of her site). The fact that she felt the need to take it down suggests that she was embarrassed to have others reading it, which suggests that she is not comfortable with everything that she said in it. (She currently works at Google, she remains active in the tech community, possibly she felt her essay was overly accusatory, in a manner that those who work with her must surely fear – after all, if they ever fire her, will she write that way about them?). Since she removed her post from her site, I had to track it down using the Internet Way Back Machine. As I am afraid this will disappear entirely at some point, I quote it at length (the following copy is from February 12th, 2002):
This is a story about a company. A company that was profitable from Day 1. A company that built products that were useful to many other companies. A company that had ethics, that treated the breadwinners (programmers) with respect, a company that could afford to help people and give away software and training, while still having enough left over to grow and save a few $million in the bank.
That is, until the venture capitalists arrived on the scene. Lying to customers and employees became commonplace. Greed replaced philanthropy as each of the company’s unique programs was dropped. But, this is a company, and the goal is to make money — any positive impact on the world is secondary, right? The real question is: how much money did they make?
The technical and managerial incompetence of the VCs and those they hired drove the company into the ground. All but 10 of the 240 employees were fired, laid off, or quit. All of the $40+ million in venture capital was squandered. The monthly operating profit turned to loss as more talentless executives were hired who threw out the company’s old, useful products and put their blind faith in engineers who spent millions building complicated software that solved no business problems.
This is a story that will teach you something about building a software product, about profitably running a company, and about what can happen if unqualified organizations obtain control.
The Birth of ArsDigita
Since the early days of the Web, I had been building web sites for big-name clients in California with my friend Aurelius Prochazka. Meanwhile, Philip Greenspun and two of his friends, Jin Choi and Tracy Adams, were doing similar work out in Massachusetts. When I moved to Massachusetts in 1998, we joined forces and were quickly able to quickly attract high profile clients, such as Levi Strauss, Environmental Defense, and MIT Press.Our band of programmers, called ArsDigita (”Digital Arts”), was profitable from the beginning. We had no office, no marketing staff, no letterhead. But we did have a few thousand dollars’ worth of computer equipment and our five motivated selves.
The Birth of the ACS
It didn’t take long for us to realize that we were solving some of the same problems over and over again for each of our sites. It doesn’t matter if a site sells custom-made slacks, lets people share their photography knowledge with other enthusiasts, helps people fight environmental battles against companies polluting their groundwater, facilitates the trading of financial instruments, or helps people find the best combination of red, white, and sparkling wines for their next soirée.Every site we built needed:
1. to talk to a relational database management system (RDBMS) to facilitate the collection of content from its users
2. a means for registering users and recognizing them upon their return to the site
3. a permission system to enable administration of the entire site, a section of the site, or an individual content item
4. a mechanism for grouping users so that they can be served content or given permissions appropriatelyInstead of reproducing this for each client, we wrote a general data model, a few web pages, and some shared procedures, and called this collection of code the ArsDigita Community System (ACS).
We distributed the ACS free and open-source, not merely to be altruistic, but because it made sound business sense. If you are doing professional services, the best way to get your name out, have more clients find you (yes, free marketing), and improve the code base is to share it with the open-source world.
The ACS began as a small core of functionality, but more opportunities for code reuse quickly arose. Many of our clients wanted discussion forums. Quite a few needed ecommerce. Polls and portals and intranets and calendars and address books were repeatedly requested. It would have been foolish to build this functionality one-off for each client. It would have been a wasted opportunity to build this only for ourselves and not let our work reap the benefits of an open-source release. Hence we began the release of ACS modules that could run on top of the core. Dozens of useful modules were created, and that is what led to the adoption of the ACS by programmers and companies world-wide.
Growth
A small group of developers earning lots of money, making clients happy, and developing and releasing a useful software product is wonderful, but … to make a substantial impact on the world, you gotta grow.And grow we did. At first it was difficult to hire people because developers don’t feel safe working for a company with no office or regularly-scheduled payroll. So, in the fall of 1998, we moved into an office. It didn’t cost us much to rent a lovely old house in Harvard Square (complete with showers and kitchen, both which were well-appreciated after nights of obsessive coding). In January, we began a payroll system so that people’s paychecks would no longer be tied to when our clients paid the invoices. Even if people were earning a bit less than before the structure was imposed, they were happy with the change. We were still earning a large profit each month. And now it was easy to hire people.
On January 1, 1999, ArsDigita had 5 employees. By January 1, 2000, we were up to 57, almost all of whom were developers. We had very little overhead and profits were rising. Around this time, we started looking in earnest for venture capital in order to accelerate growth and to allow ourselves the luxury of taking developers off of paying client projects so they could work full-time on our core product, the ArsDigita Community System (ACS).
By the end of March 2000, we had 110 employees (almost double what we had 3 months previously), 7 offices, healthy profits, plenty of cash in the bank, and $20 million in annual revenue, with the revenue figures still on an upward trend.
…Life post-capital
Revenue continued to rise to about $25 million in 2000. Is this due to the VCs’ genius and vision, or merely a result of the momentum built up before their arrival? Was the subsequent downfall, starting in mid-2000, due solely to the effects of the weaker economy in the United States?It became increasingly clear to the employees, the customers, and the outside developer community that the VCs and those they had put into management had no idea what they were doing. They discarded the practices that had made ArsDigita a profitable company, destroyed the company culture, and showed their complete technical incompetence by throwing out the ACS, which had been repeately used to solve real business problems, and replacing it with new, partially closed-source software package that was hard to use, had serious performance problems, and met only a small fraction of the business needs that the ACS did.
By the middle of 2000, it was clear that the new management did not understand the mission in front of them. New engineers at our company were routinely complaining about the level of competence and experience we were provided by aD. Communications with the new CEO were unreasonable and frustrating. Contacts at aD went from programmers to project managers to sales VPs. All these people were trying hard, and in some cases doing pretty well – but aD had lost the things that made it unique and successful.
– Josh Stella, former ArsDigita client, April 26, 2001One of the reasons I joined ArsDigita is its inspiring mission statement, which states that we do not ever lie to customers. The mission statement goes on to say that companies who lie to their customers need to spend time training their employees in the official lies before they can talk to customers, thereby making lying unprofitable…. This week, we were not honest with our customers about the severity of the security holes we discovered in the ACS. We employees even had to sit through a training session so that we would know how to discuss the security holes with our clients. This is a serious contradiction of our mission statement.
– Walt Mankowski, former ArsDigita employee, July 14, 2000It was sad to see the company slowly being destroyed. It was as if all the life was being sucked out of the company and we had no idea why. Everything that made ArsDigita what it was slowly disappeared until all that was left was just another buzzword-spewing faceless corporation. ACS users moved on, joining in support for projects like OpenACS that still had the spirit of the former ArsDigita… Meanwhile, aD corporate slowly began to shut down programs, including the one that got me to be an ACS user in the first place: ArsDigita Prize. One day a small message appeared that said simply “The prize has been cancelled for 2001.”
– Aaron Swartz, past ArsDigita Prize winner, April 24, 2001It is easy to locate marketing copy on ArsDigita.com. However, it is difficult to get to the information that is actually interesting to anyone building or running an online community, or deciding whether to hire ArsDigita’s services.
– anonymous user of arsdigita.com, September 4, 2000ArsDigita was the company I dreamed of working for when I graduated… In 2000 everything began shifting. ACS 4 seemed an excellent thing, and everybody was excited, but it was never finished and then everything just turned to Java. Nothing against Java, but even I know that you can’t sell a product that’s not here yet. What happenned to the culture? None of the names and faces we knew posted to the bboards anymore. A few aD faces posted regularly, but mostly we saw a bunch of people only posting questions about the products they should be familiar with, and sporadically. Allan Shaheen only addressed developers twice, in what seemed to be posts typed by his secretary. ArsDigita’s website turned to being a brochure more than anything else, which is not bad if you don’t forget other things.
– Roberto Mello, computer science student, April 24, 2001For months now, I’ve been trying to figure out how aD’s management can just ignore the ACS community (and the ACSish market) they way they have. Barely speaking to us; releasing incomplete, unscalable, untested software to us; and finally just abandoning the whole thing midstream. And the only thing I can think of is that they are trying to clear out the community, get rid of the community memory, for when they rollout their closed source, java solution.
– Jerry Asher, developer, April 25, 2001I heartily agree with you about the unfinished condition of ACS 4.x. We (furfly) have lost at least one prospective client because of it, perhaps more, and the project we’re working on now is waaaay behind schedule, much of which is due to our stumbling over ACS 4.x issues. This is not to say that it is unusable, or unfixable, but only that it is unfinished – I don’t want to disrespect the hard work that went into it, only the decision to release it before it was ready.
– Janine Sisk, Furfly co-founder, April 25, 2001ArsDigita, an e-commerce company in the midst of layoffs and a major product overhaul, is bucking the trend of comrades selling open-source software… The change will allow the company to reach profitability by the first quarter of 2002… The company laid off 29 employees in the last week.
– CNET, April 5, 2001.The founders fight back
Philip Greenspun has never been one to hide his opinions. If he thinks that an idea is stupid, he will bluntly say so. Therefore, Philip had many things to say after April 2000.Philip’s harsh words displeased the other board members (Allen, Chip Hazard from Greylock, Peter Bloom from General Atlantic, and ArsDigita’s COO, Ern Blackwelder) so much that they stopped having board meetings after December 2000. Instead, they had “investor meetings” where all the board members except Philip (the chairman) were invited. In March 2001, Peter Bloom sent Philip an email, threatening public humiliation if Philip didn’t resign from the board. Philip went to visit his lawyer who reminded him of his rights as majority shareholder.
It was time to regain control of our mis-managed company before it became nothing but a shell. On April 5, Philip Greenspun and Jin Choi, together holding a substantial majority of ArsDigita’s shares, had a shareholder vote that gave the founders majority control of the board. They demoted Allen from President and CEO to only President, elected Philip CEO (one spot on the board is reserved for the CEO), promoted Tracy Adams and me (both already Vice Presidents) to Executive Vice President and placed us on the board as well, removing both Allen Shaheen and Ern Blackwelder. The two venture capitalists retained their seats on the board. But we had control.
Yes, it had required drastic measures to ensure that our ideas would be heard, but we were willing to now work hand-in-hand with Allen and the VCs to return ArsDigita to a state of health. But we didn’t get the chance. Six days later, on April 11, 2001 Allen Shaheen, Ern Blackwelder, General Atlantic, and Greylock filed a lawsuit against Philip, Tracy, and me:
ALLEN SHAHEEN, ERNEST )
BLACKWELDER, GENERAL ATLANTIC )
PARTNERS 64, L.P., a Delaware )
limited partnership, GREYLOCK )
X LIMITED PARTNERSHIP, a )
Delaware limited partnership )
and ARSDIGITA CORPORATION, )
a Delaware corporation, )
)
Plaintiffs, )
)
v. ) Civil Action No. 18821
)
PHILIP GREENSPUN, EVE A. )
ANDERSSON and TRACY E. ADAMS )
)
Defendants. )Now, I’m not a lawyer, but I never understood how it could possibly be legal for ArsDigita Corporation to be listed as a plaintiff, since that would have (obviously) been against the wishes of ArsDigita’s majority shareholders. And how could it be legal for General Atlantic Partners, Greylock, Allen Shaheen, and Ern Blackwelder take hundreds of thousands of dollars out of ArsDigita’s bank account and use it to pay their lawyers to sue ArsDigita’s majority shareholders?
The case came very close to going to court but, at the last possible moment, the plaintiffs came to a settlement agreement with Philip. Perhaps the plaintiffs were afraid they would lose the case because the judge had looked at their “evidence” and said that he was uninterested in approximately 90% of it. The plaintiffs’ lawyers had wasted their time and, more importantly, ArsDigita’s money, preparing a case about Philip Greenspun’s personality instead of thinking about whether someone’s personality gives one a right to try to illegally seize control of a company.
In the settlement, Philip received $7.6 million. In return, he gave up more than half of his stock, resigned from the board, promised not to attempt to execute any control over the company, and signed a non-disclosure agreement. Before the settlement, Philip owned more than half of ArsDigita’s stock. Now that the VCs owned more than half the stock, they had no need to settle with any of the other defendants.
The VCs poured a few more $million into ArsDigita so that it could take a few more gasps of air before collapsing.
…Now, What?
What has ArsDigita been doing over the past year?Lying to the employees and to the press:
Tech startups aren’t exactly on the front burner nowadays in the market for initial public offerings, but ArsDigita is steaming ahead anyway with plans to go public next year… The four-year-old Cambridge, Mass. Web software company is hoping to kick off its initial public offering some time in 2002… If it keeps growing and building its customer base, and the IPO market continues its gradual comeback, ArsDigita will be able to take itself public, Shaheen figures.
– Steve Gelsi, CBS.MarketWatch.com, May 24, 2001, a few weeks before Allen Shaheen admitted during his deposition that he didn’t think ArsDigita would ever be able to go publicFiring people, spending money:
Beginning Thursday, ArsDigita Corporation has cut a confirmed 24 (from 165) employees and announced plans to close the Berkeley, CA, office. Rumor from several connected inside sources has the final tally climbing to 67 (or higher) over the next few weeks. Late last week the CEO was demoted by the VCs and replaced with Dan Keshian (http://www.greylock.com/team/DanKeshian.asp), one of Greylock’s partners, while they wasted another $10 million (reportedly) on the company, presumably to help it stumble along to a fire sale. Those not yet gone are those in engineering, upper management, or are working on billable projects. Those on billable projects will be terminated upon project completion. Standard severance is reportedly 1 month salary plus unused vacation.
– FuckedCompany, October 11, 2001Building products that nobody wants to use:
When the VCs and Allen Shaheen seized control in April 2000 the company had revenue, profits, a customer list of AOL, HP, MIT, Oracle, Siemens, etc., a $160+ million valuation, $41 million in cash. In about 1.5 years the same company had a product that nobody wanted to use (though it was based on more fashionable tools), no profits, no cash, and few customers. Despite the infusion of more cash and a new CEO, a Greylock partner, in the fall of 2001, the company continued to spiral downward. Now they are dead and RedHat is buying some bones.
– FuckedCompany, February 7, 2002And trying to make some money for themselves out of the scraps:
ArsDigita, a privately held software company in Cambridge, was shut down on Tuesday. At least some of the company’s assets, primarily from its professional services division, will be sold to Red Hat Inc., an open-source Linux software company in Durham, NC, according to sources close to the company… Dan Keshian, a venture partner at Greylock, became ArsDigita’s CEO in the second half of last year to lead the company to profitability. Keshian was not present when the shutdown and sale were announced to employees.
– Jeff Miller, Mass High Tech, February 7, 2002Lessons learned
Over the past 1.5 years, the VCs and their management team have taken a profitable, healthy, interesting company and:* spent the profits that ArsDigita had saved
* spent all the capital raised
* destroyed an excellent software product
* released a horrible product a year behind schedule
* hired a slew of incompetent managers
* fired the people who made ArsDigita profitable
* repeatedly lied to customers
* repeatedly lied to employees
* repeatedly lied to the press
* repeatedly lied to the outside developer community
* and given themselves big bonuses as a rewardGreylock and General Atlantic Partners have mis-managed ArsDigita into the ground.
What can we learn from this? Be clear about control. Don’t assume that people with MBAs know a thing about business, let alone technology. Don’t throw out your prime source of revenue before another one is in place. Fashionable programming languages don’t equal useful software. Don’t lie. And steer clear of General Atlantic Partners and Greylock.