Category Archives: enterprise software

Thoughts on the Jive Registration Statement (S-1) and Initial Public Offering (IPO)

I finally found  some time to read over the approximately 175-page registration statement (S-1) that enterprise social networking software provider Jive Software filed on August 24, 2011 in support of a upcoming initial public offering (IPO) of its stock.

In this post, and subject to my usual disclaimers, I’ll share some of my thoughts on reading the document.

Before jumping into financials, let’s look at their marketing / positioning.

  • Jive positions as a “social business software” company.   Nice and clear.
  • Since everyone now needs a Google-esque (“organize the world’s information”) mission statement, Jive has one:  “to change the way work gets done.”  Good, but is change inherently a benefit?  Not in my book.
  • Jive’s tagline is “The New Way To Business.”  Vapid.
  • Since everyone seems to inexplicably love the the tiny-slice-of-huge-market argument in an IPO, Jive offers up $10.3B as the size of the collaborative applications market in 2013.  That this implies about 2% market share in 2013 at steady growth doesn’t seem to bother anyone.  Whither focus and market dominance?

Now, let’s move to financials.  Here’s an excerpt with the consolidated income statement:

The astute reader will notice a significant change in 2010 when Jive Founder Dave Hersh stepped down as CEO and was replaced with ex-Mercury CEO Tony Zingale.  Let’s make it easier to see what’s going by adding some ratios:

Translating some of the highlighted cells to English:

  • Jive does not make money on professional services:  they had a -17% gross margin 2010 and -13% gross margin in 1H11.
  • In 2009,  a very difficult year, Jive grew total revenue 77% and did so with a -15% return on sales.
  • In 2010, Jive grew revenue 54% with a -60% return on sales, while in 1H11, Jive grew revenue 76% with a -64% return on sales.
  • In 2010, Jive increased R&D, S&M, and G&A expense by 127%, 103%, and 132% respectively.
  • In 2010, Jive had a $27.6M operating loss, followed by a $30.6M operating loss 1H11

To say that Jive is not yet profitable is like saying the Tea Party is not yet pro-taxation.  For every $1.00 in revenue Jive earned in 1H11, they lost $0.90. People quipped that the Web 1.0 business model was “sell dollars for ninety cents.”  Jive seems to be selling them for about fifty-three.

But that analysis is unduly harsh if you buy into the bigger picture that:

  • This is the dawn of a large opportunity; a land-grab where someone is going to take the market.
  • You assume that once sold, there are reasonably high switching costs to prevent a customer from defecting to a competitive service.
  • These are subscription revenues.  Buying $1.00 of revenue for $1.90 is foolish on a one-shot deal, but in this case they’re buying a $1.00 annuity per year.  In fact, if you read about renewal rates later on in the prospectus, they’re actually paying $1.90 for a $1.00 annuity that grows at 25% per year.

I’d say this is a clear example of a go-big-or-go-home strategy.  You can see the strategic tack occurring in 2010, concurrent with the management change.  And, judging by the fact that they’re filing an S-1, it appears to be working.

Before moving on, let’s look at some ratios I calculated off the income statement:

You can see the strategy change in the highlighted cells.

  • Before the change, Jive spent $1.16 to get a dollar of revenue.  After, they spent $1.90.
  • Before, they got $2.91 of incremental revenue per incremental operating expense.  After, they got $0.90.  (It looks similar on a billings basis.)
  • Before, they got $6.76 of incremental product revenue per incremental S&M dollar.  After, they got $1.73.

Clearly, the change was not about efficiency.  You could argue that it was either about growth-at-all-costs or, more strategically, about growth as a landgrab.

But we’re only on page 6 of the prospectus, so we’re going to need to speed up.

Speaking of billings and revenues, let’s hear what Jive has to say:

We consider billings a significant leading indicator of future recognized revenue and cash inflows based on our business model of billing for subscription licenses annually and recognizing revenue ratably over the subscription term. The billings we record in any particular period reflect sales to new customers plus subscription renewals and upsell to existing customers, and represent amounts invoiced for product subscription license fees and professional services. We typically invoice the customer for subscription license fees in annual increments upon initiation of the initial contract or subsequent renewal. In addition, historically we have had some arrangements with customers to purchase subscription licenses for a term greater than 12 months, most typically 36 months, in which case the full amount of the agreement will be recognized as billings if the customer is invoiced for the entire term, rather than for an annual period.

The following table sets forth our reconciliation of total revenues to billings for the periods shown:

This says that billings is equal to revenue plus the change in deferred revenue.  Billings is a popular metric in SaaS companies, though often imputed by financial analysts, because revenue is both damped and seen as a dependent variable.  Billings is seen as the purer (and more volatile) metric and thus seen by many as a superior way to gauge the health of the business.

For Jive, from a growth perspective, this doesn’t strike me as particularly good news since billings, which were growing 99% in 2010, are growing at 59% in 1H11, compared to revenue which is growing at 76%.

Now we’re on page 8.  Happily the next 20 pages present a series of valid yet unsurprisingly risk factors that I won’t review here, though here are a few interesting extracted tidbits:

  • The company had 358 employees as of 6/30/11.
  • They plan to move from third-party hosted data centers to their own data centers.
  • Subscription agreements typically range from 12 to 36 months.
  • They do about 20% of sales internationally.
  • They recently completed three acquisitions (FiltrboxProximal,  OffiSync).
  • There is a 180 day lockup period following the offering.

Skipping out of page-by-page mode, let me pull some other highlights from the tome.

  • There were 44M shares outstanding on 6/30/11, excluding 15M options, 0.8M in the options pool, 0.9M shares subject to repurchase.  That, by my math, means ~59M fully-diluted shares outstanding after the offering.
  • Despite having $44.6M in cash on 6/30/11, they had a working capital deficit of $15.9M.
  • The Jive Engage Platform was launched in February 2007.  In August 2007, the company raised its first external capital.
  • The Jive Engage Platform had 590 customers as of 12/31/10, up from 468 at 12/31/09.  There were 635 as of 6/30/11.
  • The dollar-based renewal rate, excluding upsell, for 1H11 for transactions > $50K was over 90%.  Including upsell, the renewal rate was 125%.
  • Public cloud deployments represented 59% of product revenues in 1H11.
  • The way they recognize revenue probably hurts the professional services performance because they must ratably take the PSO revenue while taking the cost up-front.

One thing soon-to-be-public companies need to do is gradually align the common stock valuation with the expected IPO price to avoid a huge run-up in the weeks preceding the IPO.  Gone are the days where you can join a startup, get a rock-bottom strike price on your options, and then IPO at ten times that a few weeks later.  Companies now periodically do section 409a valuations in order to establish a third-party value for the common stock.  Here’s a chart of those valuations for Jive, smoothed to a line, over the 18 months prior to the filing.

This little nugget was interesting on two levels, bolded:

The core application of the Jive Engage Platform is written in Java and is optimized for usability, performance and overall user experience. It is designed to be deployed in the production environments of our customers, runs on top of the Linux operating system and supports multiple databases, including Microsoft SQL Server, MySQL, Oracle and PostgreSQL. The core application is augmented by externally hosted web-based services such as a recommendation service and an analytics service. We have made investments in consolidating these services on a Hadoop-based platform.

First, it seems to suggest that it’s not written for the cloud / multi-tenancy (which, if true, would be surprising) and second, it suggests that they are investigating Hadoop which is cool (and not surprising).

More tidbits:

  • 105 people in sales as of 6/30/11
  • 122 people in R&D as of 6/30/11
  • Executives Tony Zingale (CEO), Bryan LeBlanc (CFO), John McCracken (Sales), and Robert Brown (Client Services) all worked at Mercury Interactive.  The latter three were brought in after Zingale was made a director (10/07) but well before he was appointed CEO (2/10).
  • Zingale beneficially owns 7.5% of the company pre-offering.  This is high by Silicon Valley standards, but he’s a big-fish CEO in a small-pond company.
  • Sequoia Capital beneficially owns 36% of the company.  Kleiner Perkins owns 14%.
  • I think Sequoia contributed $37M of the $57M total VC raised (though I can only easily see $22M in the S-1).
  • If that’s right, and if Sequoia eventually exits Jive at a $1B market cap, that means they will, on average across funds, get a ~10x return on their investment.  $2B would give them 20x.

What’s left of my brain has officially melted at page F-11.  If I dig back in and find anything interesting, I’ll update the post.  Meantime, if you have questions or comments, please let me know.

As a final strategic comment, I’d say that investors should consider the possibility of an increased level of competition from Salesforce.com, given their massive push around “the social enterprise” at Dreamforce 11.

Highlights from 2Q09 Software Equity Group Report

I’m not sure which better explains my recent decrease in blog post frequency: bit.ly or being out of the office. Either way, I wasn’t kidding a few weeks ago when I said I’m changing my sharing pattern. Much as popular business authors take one good idea and inflate it into a book, I now realize (thanks to bit.ly) that I have been taking what could have been one good tweet and inflating it into a blog post. While I’ve not drawn any definitive conclusions, thus far I’d say I’m sharing many more articles with significantly less effort than before.

Going forward, my guess is that steady state will be ~2 posts/week (instead of ~5), but those posts will supplemented by 5-10 tweets/day (RSS feed here). Because of this, I’ve added the Tweet Blender widget to my home page, made it quite large, and have set it up to include not only my direct tweets (@ramblingman) but all tweets that include the word ramblingman to catch re-tweets and such. This will probably result in the inclusion of odd items from time to time — apologies if anything offensive comes up — and if this becomes a problem I’ll change the setup.

I’ve re-enabled Zemanta after turning it off for several quarters because I found it too slow to justify its value. They’ve put out a new release, and since I’m interested in all things vaguely semantic web, I figured I’d give it another try. Finally, I’m still considering renaming the blog to either Kellblog or Kellogic, but doing so is a daunting project (think of all the links that break) which I’m not yet ready to tackle at present. So, watch this space.

The purpose of this post, however is to present highlights from the Software Equity Group’s 2Q09 Software Industry Equity Report. Here they are:

  • Consensus IT spending forecasts for 2009 predict 8% decrease in overall spending
  • Top five CTO spending priorities from the Goldman Sachs 3/09 survey: cost reduction, diaster recovery, server virtualization, server consolidation, data center consolidation
  • The SEG software index had a 23.7% positive return, bouncing back from a decline in 1Q09
  • Median enterprise value (EV) / sales = 1.4x, up from 1.2x the prior quarter
  • Median EV/EBITDA = 9.4x, up from 7.7x the prior quarter
  • Median EBITDA margin = 14.9%
  • Median net income margin = 3.9%
  • Median TTM revenue growth = 5.2%
  • Baidu and SolarWinds topped the EV/sales charts with values of 16.2x and 10.0x revenues, respectively
  • The great software arbitrage continues with companies >$1B in revenues having a median EV/sales of 2.2x while those <$100M have a mean of 0.7x. This theoretically means that the median big company can buy a median small one and triple its value overnight.
  • Database companies median EV/sales was 1.8x
  • Document/content management companies median EV/sales was 2.4x
  • Median SaaS vendor EV/sales was 2.6x, suggesting that $1 of SaaS revenue is worth $1.70 of perpetual revneue. (Though I worry the overall average includes SaaS so this could be understating it.)
  • Four software companies went public in 2Q09 raising, on median, $182M with an EV of $814M, an EV/revenue of 3.6x, and a first-day return of 17.3%
  • Five companies remain in the IPO pipeline with median revenues of $58.7M, net income of -$2.2M, and growth of 46.4%
  • 285 software M&A deals were done on the quarter with $3.1B in total value. This was down from 296 deals in the prior quarter worth $7.3B. (The lowest total value in the past 13 quarters.)
Related articles by Zemanta

Goldman Sachs Smacks Software Stocks

See this story on SeekingAlpha (which might consider renaming itself SeekingShelter), entitled Goldman Slaps Most Software Stocks.

Excerpt on aggregate spending:

The worst of the IT-spending slowdown likely remains in front of us, as we start the clock on slashed 2009 budgets. We forecast 0 percent revenue growth for our group, below consensus at 5 percent, and 1 percent earnings growth, below Street at 2 percent.

The most interesting point addressed is whether the downturn will drive consumers to open source (i.e., nominally “free”) software:

There has been much discussion in the blogosphere about open source software and how it will see a surge of adoption do to its lower cost. Goldman quite rightly says this will not be the case. I have written that CIOs will hunker down and stick with the tried and true (which is not open source in most large-sized enterprises) and Goldman is in agreement, seeing a consolidation of functionality with big, established vendors and a moving away from the concept of seeking best-of-breed point solutions regardless of vendor.

On sectors:

So in terms of non-defense technology companies we are batting two for two: Neither hardware not software will be spared over the next several quarters as the outlook remains dim for both.

Happily for Mark Logic we have a large defense / intelligence business, which I believe will offer shelter from the storm. And, as I’ve argued before, for non-advertising-driven media companies, I believe that GDP growth (or lack thereof) is a second-order effect relative to seismic changes driven by the Internet and Google to which MarkLogic helps them respond.

Fun Google Parody Video: Complexity is Good

I stumbled into this video while reading Stephen Arnold’s recent post, Google Search Appliance: Showing Some Fangs. In the post, Stephen offers a pretty comprehensive look at the Google search appliance (GSA) prompted, I believe, by a new release that includes features such as personalized search results, alerts, and broader language support.

If you’re interested in the new features, see this video here.

If you want to have some fun, check out this video which portrays Google’s view of a typical enterprise search software sale, complete with the cheesy salesperson.

As I’ve repeatedly maintained (e.g., 1, 2, 3, and 4), I think the GSA is going to consume the “crawl and index the intranet” segment of the search market, pushing classical enterprise search vendors up-market, and eventually into an un-winnable conflict with DBMS vendors.

Thoughts on Category Creation and Information Access Platforms [Revised]

[Revised 8/2/08; still working on cleaning up this consciousness stream.]

Back in the old days, it seemed easy to create a category in software. Look at the database market, for example:

  • IBM invents the relational DBMS (RDBMS) category
  • Oracle, Ingres, and Informix enter in a largely undifferentiated way, though Informix eventually drifts towards the low-end/cheap segment
  • Sybase creates the derivative category of high-performance OLTP RDBMS.
  • Arbor re-christens the failed multi-dimensional DBMS as the OLAP Server
  • Tandem creates the non-stop RDBMS with its superb fault tolerance
  • Illustra launches the universal DBMS and is quickly acquired by Informix
  • Sybase launches the bitmap-indexed DBMS with SybaseIQ
  • Teradata launches the data-warehouse DBMS category

And you can find just as many examples outside database-land.

  • ASK defines the manufacturing resource planning (MRP) category
  • SAP hijacks MRP, redefines it as ERP, and goes on to become the world’s largest applications software company
  • PeopleSoft invents the HRMS category
  • Gartner Group’s Howard Dresner invents the business intelligence (BI) category, re-christening and re-framing what was formally known as DSS or EIS.
  • Siebel pioneers the sales force automation (SFA) category
  • Scopus pioneers call center automation (CCA)
  • Companies like Rubric pioneer enterprise marketing automation (EMA)
  • Siebel, through acquisition, coalesces SFA, CCA, and EMA into a single category called customer relationship management (CRM)
  • Oracle and SAP work to coalesce CRM back into ERP. Such is the ebb and flow of categories.

(And I could go on and on — BPM, KM, CMS, WCM, ECM, LMS, DRM, SCM, PLM, ETL, DI, EII — but I think I’ll stop here with the initials list.)

People are still creating categories today, and sometimes it looks easy. Uber-categories have been quite popular in the past decade as people have focused on different ways of developing and delivering software:

  • SaaS as an uber-category has worked well, with a variety offerings in various SaaS sub-categories (e.g., Salesforce, NetSuite)
  • Appliances have done pretty much the same thing — i.e., offering an appliance alternative for a wide variety of existing categories (e.g., a data warehouse appliance a la Netezza)
  • Open source has also done the same thing — again serving as a different flavor/dimension for a wide variety of largely existing software categories.

Only a few genuinely new categories have emerged, virtualization being the most obvious example. (Though you could argue that virtualization is itself an uber-category covering storage virtualization, server virtualization, et cetera.)

Companies are still working to carve new categories, particularly in the database market:

Sometimes vendors and/or the analysts who cover them try to impose either a straight name change (e.g., from MD-DBMS to OLAP) or a strategic shift (e.g., from BI to analytic applications) in category. Sometimes they’re just bored. Sometimes a vendor’s trying to redefine the market in line with its strengths. Sometimes an analyst is trying to make his/her mark on the industry and earn the coveted “father/mother of [category name],” much as Howard Dresner successfully did with BI.

BI got bored with its name several times during my tenure at Business Objects. At one point both the analysts and Informatica were trying to re-dub the category “analytic applications” in an attempt to get a fresh name and raise the abstraction level from tools to applications. Informatica nearly died on that hill.

Later, analysts tried to redefine the category, dubbing it corporate performance management (CPM), and arguing that business intelligence needed to link with financial planning systems. While knowing actuals is good, knowing actuals compared to the plan is better, and using actuals to drive the future plan better still. Cognos nearly tripped over itself repositioning around the CPM, ultimately acquiring Adaytum, which in turn lead to SRC’s eventual acquisition by Business Objects.

In an art-imitates-life sort of way, one wonders if the analysts predicted a move in the market or provoked it? My chips are on the latter.

This stream-of-consciousness is a long way of winding up to a single question: are enterprise search vendors successfully repositioning themselves as “information access platforms” or not?

Background: the enterprise-search-related vendors (e.g., Fast/Microsoft, Endeca) and search/content analysts who cover them are in the midst of an attempted category repositioning:

  • The word “enterprise search” is now seemingly dead, having been contaminated by the Google Appliance. When a shark gets in the water, all the fish jump out.
  • The word “information” is increasingly being used as a unifying term to describe both data and content (aka, unstructured data)
  • Enterprise search vendors are increasingly calling themselves “information access platforms” (though not generally abbreviated as IAP, I will do so here for brevity).

For example, consider Endeca’s corporate boilerplate:

Endeca’s innovative information access software that helps people explore, analyze, and understand complex information, guiding them to unexpected insights and better dec
isions. The Endeca Information Access Platform, built around a new class of access-optimized database, powers applications that combine the ease of searching and browsing with the analytical power of business intelligence.

I have a number of concerns on and related to this attempted shift:

  • The important thing about categories is that they exist in the mind of the customer. Analysts and vendors can try to put them there — but they have to stick. In my mind, IAP is not sticking. I have never heard a customer say: “I need to go out and get an IAP.”
  • I do, however, believe that “information” might well stick as an overall term, meaning both data and content (aka, structured and unstructured data).
  • It is not clear to me why someone who desires a unified platform for “information” would turn to a search vendor. Search engines were designed as read-only indexes to help people find documents containing tokens; hardly ideal as an application development platform.
  • In my estimation, someone managing “special” data should turn to a database vendor. While databases have classically not handled “special” data well, databases were designed as application platforms, and there is a whole new class of specialized databases emerging for handling various “special” types of data.
  • While I think a unified platform is a dandy vision, I think no one is close to delivering a unified platform that handles all types of data equally well. Bolting Lucene and MySQL together isn’t a platform. Relational databases still do a poor job with both content and many types of data (e.g., sparse, hierarchical, or semi-structured). XML servers (like MarkLogic) handle XML brilliantly, but need work before they can match RDBMSs at classical relational data.
  • I believe that someone who needs a crawl-and-index the intranet value proposition should use the Google Appliance; so I think the search vendors are correct in their desire to flee, I don’t think that “information access platform” is a good refuge.

Overall, my chips remain on the don’t come line for the attempted category repositioning from “enterprise search” to “information access platform.” You can find my stack on the come line for the emerging “special-purpose database” category and “XML servers” as an instance of them.