Commentary

Serdar Yegulalp
 

An Open Source Vendor's Biggest Competitor: Its Customers?

When my colleague Charles Babcock spoke to Red Hat CEO Jim Whitehurst, one sentence that fairly leapt out at me was "[Red Hat's] biggest competitor is simply people who stop buying subscriptions." So where do they go from there?

When my colleague Charles Babcock spoke to Red Hat CEO Jim Whitehurst, one sentence that fairly leapt out at me was "[Red Hat's] biggest competitor is simply people who stop buying subscriptions." So where do they go from there?


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

First, some context. The above statement appeared in a paragraph about the value of software subscriptions as Red Hat's major revenue stream. Obviously there are any number of reasons why people would stop buying Red Hat subscriptions, with them finding another product line being one of the biggest  Another would be that they've reached a comfortable plateau of functionality for the time being and don't see a pressing need to throw more money at stuff that simply goes unused.

Digression: There's also a third possibility. What about the folks who get their sea legs with an open source product (Red Hat or otherwise), and then realize they'd rather rely on the people they have in-house to continue the job? There is more than a little irony at work here. One of the reflexive assumptions about open source is that when you put it to work for you, it's empowering -- you can take steps with open source software that weren't possible at all (or only after great difficulty) with proprietary stuff.

But does that mean the average open source vendor's doomed to run into this wall, where they end up with their customers causing their own version of empty-nest syndrome? Probably not. I don't see this scenario being more than a very small percentage of how subscription-supported open source ends up -- and even if it does, I'd gamble that the people who soldier on by themselves may well contribute any work they accomplish back to the community.

Digression over. My main thought here is what kinds of work an open source vendor with a subscription-based model has to pull off to keep both new and existing subscriptions coming in and not going out, and figure out how to make subscriptions genuinely useful to customers who could go any number of other ways -- roll their own solutions, go proprietary, or ally themselves with yet another open source vendor.

The best way to do that is to be proactive -- to go after the people you already have and ask them: "What else are you trying to do?" (Not, "What do you need from us?") As colleague Mike Fratto put it in a message aimed at vendors in a slightly different industry: don't pretend that just because no one asks for something it's not something they want. Sometimes the greatest and most pressing needs go unarticulated precisely because they're so huge.


Follow me on Twitter: http://twitter.com/syegulalp


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links