James Dixon’s Blog

James Dixon’s thoughts on commercial open source and open source business intelligence

Open Core Business Model Revisited

with 5 comments

After the Open Source Business Conference last week a few analysts have been chiming in on the ‘open core’ business model for commercial open source companies:

Matt Aslett : http://blogs.the451group.com/opensource/2010/03/25/winning-and-losing-with-open-core/

Brian Prentice : http://blogs.gartner.com/brian_prentice/2010/03/23/open-sources-reality-distortion-field/

Matt’s first point is that:

The proprietary vendors are now using open source collaborative development and code to lower the costs and improve the quality of their own product development, and are better quipped to compete with open core vendors thanks to their installed base, larger resources, and product maturity.

What I don’t think Matt appreciates is that than open source business model is not just a different development strategy. Executing well using this model affects every department within a company – particularly sales and marketing. You use mass-marketing techniques instead of enterprise-sales techniques. I don’t see the large proprietary vendors changing that much. Also you have to factor in ratios of open source code to proprietary code: from 100% open in a pure-play, 80-99% in an open-core play, and 0-2% for the big proprietary vendors. If a large vendor manages to reduce their development costs by 10%, you are not going to see them drop their license fee by 80%, particularly because the license fees cover the sales and marketing costs.

Another mistake is to view the ‘product maturity’ of the incumbent proprietary vendors as an advantage for them. Some of these product are bloated, and very hard to install and configure. This is not an advantage against open source software which needs to be easily to consume – otherwise the model does not work. In many cases the large vendors want to limit (or carefully manage) access to the software before customers purchase it, because they know the experience of using it is not great.

Matt’s second point is:

The shift towards software services (SaaS, managed hosting, cloud-based delivery), where the value being delivered is via services, rather than products.

Matt’s point here is that an open-core approach is irrelevant in this environment. That’s true, but you can say the same of pure-play open source and proprietary software. Since this applies to all software development strategies I don’t see the relevance of it.

Brian’s first point is about the VC-centric nature of open source start-up in the USA:

There’s a yawning gap between the value open source provides a venture capitalist (VC) and what it provides an end user.

I think this is the wrong comparison. Brian seems to think that VC-based companies and self-funded companies have different attitudes towards making money. Having done two self-funded start-ups, and now a VC-backed one (Pentaho), I can say that we would still be using an open-core model if we were using our own money.

His second point:

Open-core is a largely a re-tread of tired, old SMB packaging strategies which have almost universally failed in the market.

This is ridiculous. An open source distribution model, and the adoption of the software by an active community, is nothing like the SMB packaging strategies of the proprietary vendors. The community and enterprise editions are marketed consistently to all companies of every size – there is no different positioning or pricing for the SMB space. Making software available for $0 and converting a small (<1%) set of the community into customers, is very different from taking a huge expensive piece of enterprise software and trying to sell a cut-down version of it for less down-market.

Second point:

I’m not sure most open-core business models have been successful in building large external code contributions

Brian is fixating on code contributions – a common failure. Ignoring the other (in my opinion) 95-99% of all contributions. Take Apache Tomcat – the majority of the code has been written by a small group of people (lets assume 100), but the user base is in the millions. Certainly the software would not exist without those 100 developers, but without the large community of millions, Tomcat would be a hobby for 100 developers, nothing more.

His third point is about the companies that acquire these start-ups:

Who are those likely buyers? Increasingly it appears to be the very same established vendor community that are saying “ya, I do open source too!” So much for a compelling new business model!

When it comes to the M&A decisions and processes of large proprietary software vendors (and I’ve been through a few of these), I doubt whether the issue of ‘open-core’ or ‘pure-open’ would ever come up. It will come down to sales, brand, traction, and community. If ‘pure-play’ open source companies are as successful (or more successful), than the open-core companies, they are just as likely (or more likely) to be acquired by proprietary vendors as open-core ones. I don’t see the relevance of this point.

Written by James

March 26, 2010 at 1:55 pm

5 Responses

Subscribe to comments with RSS.

  1. Hi James,

    As you know I’ve been arguing for many years that business models around open source are about more than just development and licensing. I focused on the collaborative development benefits that proprietary vendors are getting from open source because these are the main benefits that open core vendors are passing up by controlling the development of the core – although as you note they do enjoy other benefits.

    My point about SaaS and cloud is that they focus attention on value delivered through service, rather than product. I would argue that pure-play open source vendors already have that focus and are therefore less likely to be impacted by the transition to the cloud than open core and proprietary product vendors.

    Matt

    Matt

    March 26, 2010 at 6:23 pm

    • Good points, but I wonder about how this would actually work.

      Look at Spago BI or another services-based open source company and ask ‘what services do they provide?’. In the case of Spago BI they provide install, configuration, and on-premise implementation assistance to create a custom BI application. How do they make this SaaS or cloud based? Every customer’s application is different. There is no economy of scale. A SaaS application needs to be metadata driven so that the binary image is the same for all customers, only their data is different. To move to SaaS or cloud Spago will be in the business of providing on-site image building assistance (which they will have to charge for) and then charge again for the SaaS offering. This doesn’t align well with any of the successful SaaS company models.

      My point is that while Spago provides services, the services they provide are incompatible with a SaaS or cloud service.

      I think the danger is in the word ‘service’. The ‘service’ that a SaaS provides is utility/pay-per-use consumption of a product, not of professional services – its a different way of providing and pricing a product. The ‘service’ that a pure play open source company provides is professional services, which cannot be easily hosted, scaled, or priced.

      James

      March 26, 2010 at 7:15 pm

  2. […] the very definition of “community” is being adapted to suit the open core narrative. What has largely interested the corporate IT world is the concept of a community as a collection […]

  3. […] Marten Mickos says open source doesn’t have to be fully open Open Core is Not Open Source Open Core Business Model Revisited Gartner Smackdown on Open […]

  4. […] Marten Mickos says open source doesn’t have to be fully open Open Core is Not Open Source Open Core Business Model Revisited Gartner Smackdown on Open Core « LinuxCon Brazil 2010 pymegacli […]


Leave a comment