The deal will come as a relief to Kazeon’s long-suffering shareholders. The company was founded in 2003 and, over the past 6 years, it raised over $60 million in equity financing, double the amount it usually takes successful software companies to reach profitability. But despite all that investment, revenue has been hard to come by. According to former Kazeon employees, the company’s revenue totaled only $7 million over the past 12 months. Perhaps as a result, there’s been a lot of management turnover, and last year the board retained a recruiter to find a new CEO. In light of all that, selling the company for $75 million, or 10 times trailing revenue, is a great outcome for Kazeon’s shareholders. It also provides some level of job security for Kazeon’s employees, many of whom have been offered retention bonuses to stick around.

On the other side of the coin, the deal also makes sense for EMC, which needed to flesh out SourceOne, its recent re-branding of the Email Extender archive. In launching SourceOne in April 2009, EMC described it as an integrated portfolio of products: SourceOne Email Management for email archiving; Discovery Manager for legal holds of email; Celerra and Centera for storage; and Discovery Collector for identifying and collecting data from desktops and file shares. EMC owned all of those products except one: Discovery Collector, which instead was to come from EMC Select Partner, StoredIQ. It is widely known that EMC tried repeatedly to acquire StoredIQ but was rebuffed. So instead, it purchased Kazeon (i.e., the Kazeon Information Server) so that it now owns all aspects of SourceOne and does not have to rely on partners.

Will this eDiscovery deal be successful? We will have to wait and see, but Seagate’s experience is not encouraging. A year after it acquired Metalincs, Seagate laid off most of the staff and hired UBS to help it sell what was left of the electronic discovery company. There have not been any takers.

There has been progress towards answering this question, thanks mainly to the analyst community. George Socha and Tom Gelbmann’s EDRM framework has been immensely helpful in breaking down electronic discovery into its component steps. Other analysts, like Debra Logan at Gartner, were quick to embrace the framework, prompting every software provider to follow suit. As a result, there is today a common language that everyone uses to describe the e-discovery process.

The Electronic Discovery Reference Model (EDRM) breaks down the e-discovery process into a series of steps. Companies looking to buy e-discovery software to lower costs typically map different software products to each of these steps, to make sure that they cover the entire process.

But having a universally-agreed framework is only half the answer. To eliminate customer confusion, there also needs to be agreement on how different software products fit into the framework. This is especially important since there is no single, end-to-end solution for e-discovery which covers all aspects of EDRM. So customers are forced to think about how different software solutions fit together. And that is where things begin to fall apart.

Many software vendors feel it is advantageous to claim that they do everything, even though they do not. Customers are rightly suspicious of those claims, and so press vendors to provide more detailed information – hence the question, “when you say you do e-discovery, what exactly does that mean?”

In light of that, how can litigation support teams, corporate counsel, or legal IT people figure out which e-discovery solution best meets their needs? From observing this decision-making process hundreds of times, I have found 3 simple steps are incredibly helpful.

Step 1: Read the analyst reports

Two reports in particular make for required reading. One is Gartner’s MarketScope Report, which is available for free at certain sites; the other is the 451Group’s recent e-discovery report, which is summarized in a publicly available presentation. The helpful thing about the 451 Group’s report is that it tells you which software companies do which parts of the EDRM process. You do have to buy the report to get the full picture (it’s well worth it!), but the publicly available presentation will give you a flavor for their analyis, and I have drawn from that presentation in the figure below:

Analyst firms like the 451 Group map software vendors to the EDRM framework according to what they actually do, which is often different from what software vendors claim they do.

The 451 Group’s analysis highlights several important points. First, it shows that there is no single end-to-end solution. Even the products of giants like EMC (SourceOne), HP (IAP), and IBM (CommonStore) only solve one piece of the puzzle, information management. Second, it shows that customers have choices at each stage of the EDRM process. For example, to solve the problem of identification, collection, and preservation of electronic information, customers can choose from solutions as diverse as Guidance EnCase (forensic collection), Index Engines (back-up tapes) and Mimosa NearPoint (email archive). Third, it provides an independent assessment of what vendors do, as opposed to what they may claim. For example, Kazeon claims analysis and review capabilities, whereas the report shows its product does identification, collection, and preservation; Recommind claims its Axcelerate eDiscovery and MindServer products do processing, whereas the report finds that they do not.

Step 2: Evaluate the products prior to purchase

Just as anyone would test-drive a car prior to purchase, it’s critical to test-drive e-discovery software. Any vendor should be willing to provide their software free of charge for an evaluation on-premise. The most effective evaluations are when the customer uses the product themselves, either on a live case or test data. This is far preferable to just sending the data to the vendor who then loads it into their system, as in that scenario there are too many opportunities for the vendor to hide their product’s shortcomings.

Step 3: Check references carefully

The trick with references is to insist on relevant references. It’s not good enough for the vendor to dredge up some random person who says nice things; or even a credible knowledgeable person who is using the product in a completely different way. For example, if a company is happy with Autonomy’s IDOL for enterprise search, that does not tell you much about what Autonomy might be like for e-discovery. What really counts are references from other customers who are using the product for the same application that you are.

All this can sound like a lot of work, but I have seen people go through the process in as little as a month, and be much happier for it. A little work up front can save a lot of time (and heart-ache!) later on.