Interwoven sold order to a web that kept breaking

At Match.com, the trouble was not finding somebody to love. It was letting everybody update the website. Marketing wanted changes. Designers wanted changes. Sales wanted changes. In a 2006 interview, Peng Tsin Ong remembered the result: “they were breaking things left and right.” A website had become a shared workplace without an adequate system for sharing the work.

That observation helps explain Interwoven better than the phrase “enterprise content management.” The company sold a way to coordinate people whose contributions had to appear together, correctly, on a screen. Its name has largely receded. Its central problem has had no such good manners.

A website needs a production line

Ong’s comparison was wonderfully unromantic. Factories had production lines. Legal work had document management. Websites, initially small enough for a few people to improvise, were becoming something else. He recalled seeing Cisco’s enormous website operation and recognizing the coordination problem ahead. The opportunity was in the growing number of hands touching the same deliverable.

Interwoven began in 1995 and shipped its first product in May 1997. It went public in October 1999. Those dates place it in an awkward but fertile interval: the web was becoming a business necessity while the routines for running it were still being invented. A company could put up a site much faster than it could agree who was allowed to change it.

Think of a bank preparing a new product page. A writer changes the offer. A designer replaces the image. Someone must check the wording. Someone else must decide when the approved version goes live. This is an illustrative workflow, but it captures the appeal of TeamSite: giving separate participants a controlled path toward one published result.

The expensive part was permission

TeamSite handled authoring, site layout, workflow, approval, archiving and tagging. OpenDeploy addressed deployment; LiveSite addressed delivery. MediaBin organized approved marketing assets. The useful distinction is between making content, deciding that it is ready, and moving it into public view. A finished paragraph is only one component of a finished publishing operation.

In a 2004 review of TeamSite 6.1, eWeek reported a departmental starting price of $49,000 and an enterprise starting price of $159,000. These are historical software prices, not present-day offers or complete implementation budgets. Still, they make the intended buyer unmistakable. This was a purchase for an organization with enough publishing complexity to make control valuable.

The business combined licenses with support and services; later offerings also brought hosted services into the portfolio. Customers bought software, but they also needed deployment expertise. Interwoven’s partner network included systems integrators and digital agencies. For a buyer, that ecosystem mattered: the software had to work with an existing organization, not merely arrive in a box.

First, the customers closed their wallets

The early financial story contains a sharp turn. Revenue rose from $16.8 million in 1999 to $202.7 million in 2001, then fell to $126.8 million in 2002 and $111.5 million in 2003. A website might remain essential while the budget for improving its management disappeared. The need and the purchase were two different things.

Interwoven’s 2002 report described reduced IT and web spending, delayed decisions and dependence on large transactions. It reported a $148.6 million net loss that year. The first break in the growth story was demand and spending, rather than evidence that companies had stopped needing content management. A long enterprise sales process becomes especially uncomfortable when buyers postpone the end of it.

Competition also pressed in. Documentum, FileNet, Vignette and other vendors pursued overlapping needs. In-house development remained an alternative. The comparison was consequently broader than whose editing screen looked nicest: it involved integration, distribution, project costs and how much of the content lifecycle one supplier could cover.

The documents changed the conversation

In 2003, Interwoven and iManage announced a stock-and-cash merger valued at $171 million. They had already formed a partnership and reseller agreement that February. The stated reason was specific: customers wanted collaboration and management of documents and corporate knowledge alongside the web content capabilities they already used.

“Customers across the board are demanding more comprehensive, end-to-end solutions delivered by a single vendor.”Martin Brauns, Interwoven chairman and CEO, 2003

That is the clearest public answer to what changed the company’s direction. The visible website was only part of the information estate. The merger brought document management and collaboration into the business, including the product family associated with WorkSite. Legal firms became an important part of the picture. Their valuable content was often a working document or an email, rather than a public page.

The company extended the other end of the process too. Acquiring Optimost in 2007 brought website optimization into the portfolio. Publishing could be followed by testing different versions. The proposition grew from getting the approved material online to learning which material performed better. Yet the common thread remained the same: turn loosely coordinated information work into a managed operation.

A profitable business changes hands

By the end of 2008, Interwoven reported more than 4,700 customers worldwide and over 400 additions during the year. Reported orders included adidas, Aetna, Bank of America, DLA Piper and Hilton. Its DevNet developer community had passed 25,000 members. These were the signs of a working enterprise ecosystem, with customers, specialists and reusable components around the software.

Annual revenue reached $260.3 million, up 15%, with reported net income of $32.0 million. In January 2009, Autonomy announced its approximately $775 million acquisition. The deal therefore deserves more precision than a story of a broken company being rescued. Interwoven had faced serious trouble earlier; its final full independent year was profitable.

Autonomy’s interest included legal information management and eDiscovery. An IDC analysis also described a decade-long commercial relationship involving KeyView technology. The acquisition joined businesses that already knew something about each other. Later, HP’s 2011 purchase of Autonomy brought the Interwoven products under another owner.

The company disappeared; the work travelled

The software families eventually separated. iManage leadership purchased its product suite from HP in 2015. In 2016, OpenText agreed to acquire a group of HP customer experience assets, including TeamSite, MediaBin and Optimost, for approximately $170 million. That figure covered a package of products; it is not a resale price for Interwoven alone.

OpenText subsequently introduced Web CMS as TeamSite’s expanded successor. Its 2026 product updates still address large-scale content operations, governance and publishing. Buyers investigating that lineage today should examine OpenText Web CMS; buyers following the document management lineage should examine iManage. The historical name points toward two different present-day destinations.

For anyone building a company, the transferable lesson is quite practical. Watch the handoffs around a task. Who can change the work? Who checks it? Who decides which version counts? Who gets blamed when it reaches the customer incorrectly? Ong found a software opportunity where several professions collided over one website.

That approach pays only when the coordination burden is real. A small site with one editor may gain little from elaborate approval machinery. A larger organization with overlapping teams, repeated assets and costly mistakes has a different calculation. Before buying a platform, map the work. The map may reveal a business opportunity. It may also reveal that two clear rules would do.