Posts Tagged ‘software’

Is there room for Nuxeo in the mature and crowded ECM market?

March 15th, 2010

While exchanging with a well-recognized and successful industry expert about our differentiators and the market we are in. Since they popup frequently, I thought it might be interesting to publish the answer.


Bazaar-istanbul

ECM is a mature and crowded market. Is there really room for anything more than a niche player at this late stage in the game?

Hegemonic vendors

At a macro-level, the enterprise content market is composed by 5 hegemonic vendors (OpenText, EMC, IBM, Oracle, Microsoft) and a set of minor ones (~15 notable), after a strong and fast consolidation of this market. Gartner says: 3 top vendors have 52% of the ECM market. The Triad of ECM? ;-)

As many vendors have skipped investment in technology aggregating software from their acquisitions (with the notable exception of Microsoft) much of the current batch of software has been designed 15 years ago and hasn’t evolved much. They have forgotten they are in engineering, not retail. In this world of lean, on-demand, instant-on, the major ECM payers still talk literally in days or weeks to install their software. It’s faster to setup a whole virtual datacenter processing and storing terabytes of data on the Amazon Cloud than setting up a vanilla ECM system!

On top of this technology breakdown, many of these acquisitions have been poorly integrated, to say the least (with a special mention to OpenText on this side). And the pace of the recent consolidation has created a disturbance in the market.

Those two combined dynamics enable new vendors with good technology and the right go-to-market approach to enter the ECM arena, tickle the incumbents and rise, and bring some fresh air and fun to this market.

Perspective shift from customers

We see important shifts in how customers evaluate and choose ECM platforms:

  • More and more Architects are actively involved in the choice of next-generation ECM platforms (not only business users / archive managers) and are putting it at the core of their information system. This sets high expectations in terms of software architecture, integration capabilities or flexibility and technology stack.

  • They need to update systems deployed in the ’00s because incumbent vendors are not supporting those versions anymore => the cost of upgrading is high and they are looking for alternatives. Often we can offer efficient and better replacement for those systems for a fraction of the price of the ongoing maintenance. Let alone the license fees…

  • Given the lack of technical investment and the legacy of major ECM platforms, implementation is complex and expensive => we can do better with today’s technology. Monolithic is no where near the state-of-the-art of software-and Architects care because it directly impacts their ability to make these ECM platforms meet the new business challenges.

Move fast, commoditize legacy, create value with the rest

I really believe that the market maturity combined with the legacy technologies of monolithic players is a key advantage for us: we are disrupting the market by commoditizing the technology (platform) and deriving value from this commoditization.

We target what hurts: the fat and comfortable maintenance stream. We target it with more flexible, up-to-date technology and a company organized to provide superior service for support & maintenance as our customers actually deploy and use our products. That’ll tickle! ;-)

So yes, I’m firmly convinced that there is a room for new players, like us. And timing seems just right for a big one. The market needs to evolve and renew, in the best interest of customers. And they well deserve it, given the challenges of the knowledge era that just starts…

That’s going to be a tough ride. But… feels fun too!

Cheers,

EB.

Commercial Open Source — Or Just a Free Demo?

August 12th, 2009

I’m reading a lot recently about “Commercial Open Source” being the next great thing in the software industry. I’ve just read the presentation “Talk Slides: The Commercial Open Source Business Model” by SAP Labs's Dirk Riehle. It’s a great presentation that really captures the vision and strategy of some high-profile companies in the so-called “Commercial Open Source” arena.

In summary, the “commercial open source” business model is based on the 3 pillars:

  1. a GPL (or GPL-like) software tagged “community”
  2. a proprietary version of the GPL software with some “proprietary extensions” sold using a traditional license
  3. a serious dose of communication efforts to explain how open source magically creates cheap great software for everyone (and that in fact you’re not really selling it) and generates a ton of leads allowing you to get to market faster and cheaper

Core myths of the “Commercial Open Source”

Here is how I analyse the core speech of the current "Commercial Open Source" model. I would be happy to hear about your opinion.

“Community Editions” you mean… “Free Demo”?

I don’t get the fundamental difference between offering a “low-end” open source version of your software and offering a free but proprietary one. Especially when I read that the “Community version” is for “developers, hobbyists and small deployments ‘cause it’s cool and fun tech” while the “Enterprise version” is for “enterprise deployment ‘cause it’s full of tests and stable code.”

Hmmm… how do you turn an untested, unstable software into an enterprise-grade, rock-solid software with “some extension”? Well, you don’t. :-) Either your software is well-tested and rock-solid, or it’s not.

If you just want to create a product line with different features depending on varying customer size, that’s fine but let’s call it this way.

Open source software generates leads, right?

Wrong. Freely downloadable apps generate leads. Free trials generate leads. Smart marketing efforts generate leads. Having access to source code does not generate leads, at least not when you are offering applications (it might be different for middleware or dev tools).

Want to generate leads? Create great software and offer free trial and downloadable software.

“It’s not proprietary software, it’s giving reason to buy when people use the software”

I love this one! Seriously. Of course customers need a reason to buy. That’s why they buy. :-)

The reason to buy is called “license fee for usage right”. It’s been around for 20 years and if you want to give people a “reason to buy” your software, just use a “license fee” for usage and maintenance. That is what it's designed for — it will save you a bunch of marketing dollars.

Open Source is good for Communities

It helps but it’s not enough. And it’s not limited to Open Source.

Openness, honesty, good software and good marketing create community. Ask Atlassian, Google, Twitter, Salesforce or even Microsoft. Not open source, but great communities and vibrant ecosystems.

“Commercial Open Source” or “Ashamed proprietary software”?

There is nothing wrong with selling “usage right to use binary software” (or more often called “license fees”…), which is what all “Commercial Open Source” vendors are doing. It doesn’t prevent you from creating great software, building a community and be nice. It just requires a bit more effort.

It's time to go public and add some clarity to all this. There is nothing wrong selling proprietary software, especially when you're contributing a lot of open source code (I’m a great fan of Atlassian and Day, in this respect). It is nothing to be ashamed of. Just be clear and focus on your software's competitive advantage rather than its open source "nature."

“Commercial Open Source” is not the business model of open source

There is no such thing as a business model of open source, by the way. There are many reason companies are producing open source software (from Microsoft to Google, from Oracle to RedHat). The only common fact: it’s a tsunami in the industry. Everybody’s using it, software vendors being the firsts. And many are producing some.

There are a lot of reasons to produce open source and a lot of ways to make money leveraging it, as some brilliant analysts and bloggers already said (two notable reading: “On open source business strategies (again)” by 451 Group’s Matthew Aslett or “Making Billions with Open Source, Revisited” by Redmonk’s Coté).

Here is how I would summarize it:

  1. Proprietary software (!): Build and distribute proprietary software leveraging open source ones (be it complete apps or just extensions). Take Day Software, quietly producing tons of good open source infrastructure components, they sell a great proprietary app. Or IBM with Geronimo / Websphere. Or Oracle. SpringSource and most “Commercial Open Source” companies fall into this category too. I think it’s the easiest way to make money out of open source.
  2. Support & Packaged Services: Sell support as subscription and high-value packaged services (monitoring, inventory, etc.) for open source software you’re producing. JBoss was the flagship in this business with quite a success making money with it. This is Nuxeo’s business too.
  3. Proprietary distribution: assemble open source software into a proprietary stack. It’s all open source software, but the recipe to assemble the different components together and deliver a coherent and supported stack is kept secret. This can also include some “proprietary services” such as automated updates or monitoring. This is RedHat’s business. Sun seems to look toward this way too (see Solaris and the recent WebStack).
  4. Proprietary tooling: sell proprietary tools that help running / operating / managing open source products. These tools are usually development tools, administration tools or deployment tools.
  5. SaaS: package open source software to deliver apps as a service. This is the business of managed apps hosting (to make apps run) and packaged services (to deliver great customer support and business domain knowledge). This is also Nuxeo’s business.

So in the end, what’s the key point? Is it doing open source no matter what for the sake of hype or is it solving problems by delivering great software and/or services to customers?

I wish people of the Commercial Open Source arena would focus more on the later…; cause it does not diminish their contribution to open source overall nor does it diminish their company’s greatness and value. For the best of the open source industry. These times are about transparency and openness after all…

What do you think? I have spent 10 years in the open source software industry, building a company, living through short-term hypes and various business models. And I'm still learning. :-) Would be really happy to discuss more about all this.

Cheers,

EB.

“Scrum and XP from the Trenches” by Henrik Kniberg

October 9th, 2008

Trying to help our teams (4 of them, each having its own Scrum Master and Product Owner) properly start to implement Scrum, I was looking for more than theory to get them started, to prevent them from common traps and pitfalls. I was getting often the same questions and mistakes in setting up the process. I had to find something to avoid writing my own guide to Scrum… ;-)
And… I've found (actually I remembered a mail, a friend sent me a while back) the gem: "Scrum and XP from the Trenches" by Henrik Kniberg. This is an actual guide for implementing Scrum in your team, although the author says the reverse. It is answering a lot of practical questions and daily issues, staying away from dogmatism and often suggesting several solutions to needs (like: in what to should we keep the backlog? how could it be integrated with our issue tracker? etc.).

And it's free for online reading, so: try the book from InfoQ and buy it it you like it [Amazon, Lulu].

Happy reading!

EB.

PS: plus, it gave me the first opportunity to actually use my new toy, an ebook reader, the Sony PRS-505. And I'm positively impressed by the level of reading comfort.