Defining An Open Source Marketing Strategy

1 week ago, we had a meeting of the executive management team of Mindquarry where I presented the envisaged Mindquarry marketing strategy for 2007. Let me share some of the basics with you which you should not miss in your marketing strategy presentation.

Focus Your Activities

The most important aspect is of course to focus our marketing activities. It’s very critical especially for startups to do this right. For example, Mindquarry had a German Web site until recently, in parallel to the English version. We dropped it, because we will focus on the international market in 2007 and the visionaries as well as early adopters. These groups usually understand English very well. Getting rid of translations in this early phase of our business will allow us to concentrate on basic marketing activities.

Define Your Niche

It was also important to define the niche of Mindquarry well. We decided to go for “Mindquarry, the Open Source Collaborative Software”. As you can see at our Web site which got relaunched today, we added this to the logo in the header. Wikipedia and a good friend of mine helped me to sort out the niche.

The niche implies that Mindquarry is a new product in a new market, as the term Collaborative Software is not yet as widely known as for example Enterprise Content Management or even Operating System. It is of course a challenge to position our product well, especially because it addresses a rather new market in the Web 2.0 space. Open Source can certainly help us to achieve a high visibility.

Organisational Success Factors

I identified two critical organisational success factors for our marketing:

  • Coordinate well between sales, marketing and development from the early days. Otherwise, business and product development will lack behind.
  • Coordinate marketing campaigns between teams with the goal to push a message out to the market at once.

Remember that you will also have to address your community, which will include developers of other companies as well as their marketing and sales personnel. Hence, take care of internal and external coordination.

Marketing Style

Mindquarry is a Web 2.0 company, hence we will also do a lot of social marketing. This means, we will heavily make use of communication tools such as blogs, podcasts, Wiki, etc. This includes that I will happily share with you what’s going on within marketing at Mindquarry (as I do here). My vision is to make Mindquarry’s marketing a public project to some extent, where Mindquarry asks for feedback before or after we implement something. For example, you might have guessed that our CEO does not quite like the green download button 🙂

Marketing Execution and Deliverables

Don’t forget to think about what you are actually going to do when you define a marketing strategy, for example:

  • your team resources and how you would like to grow the team
  • events you plan to attend (trade fairs, conferences, etc.)
  • collaterals (brochures, business cards, etc.)
  • the infrastructure you need to manage marketing (task manager, file sharing, etc.)

Coaching

Especially in an Open Source company, marketing is a lot about coaching your colleagues in doing marketing themselves. This includes how to do good customer or conference presentations, how to write a nice blog entry, etc. In the end, if you give to your colleagues, you will get back from them – and this is what will keep the wheel turning and ensure a good coordination between marketing and other teams.

Of course, marketing coaching also includes your Open Source community. There will be externals who will approach you because they plan to write an article about your product. Help them and offer to review their text!

Check out Ian’s excellent entry A Marketing Model for Open Source for more on Open Source marketing strategies.

Self-made LAN in My New House

Roughly one week ago, me and my wife moved to our newly built house. I made sure that almost all rooms have two ethernet plugs. Actually, I set up the whole LAN infrastructure myself – which I am really proud of.

There are duplex Cat7 cables from almost every room going down to the basement where I reserved a little room (about 2.5 square meeters) for the servers rack (Triton). We have an external Wireless Access Point (Linksys) which I will turn on once the weather is good enough to sit on the terrace.

Here’s a picture of me connecting the cables with the patch panel (Telegärtner, some of the best ones on the market), using an LSA plus tool:

Connecting cables with patch panel using LSA tool

This picture shows the bottom of the server rack, where I mounted the patch panels and the Linksys switch:

Patch panels and switch

Here’s the whole baby, including one Linux file server, one server with Windows for communication and media (phone, fax, least cost router, UPnP), plus one NAS as backup storage device and a 4-port KVM switch (Trendnet TK-400K, works well for a good price) to rule them all via one monitor, keyboard and mouse:

Server rack

You bet that the server room got finished first 🙂

Defining Commodity Features of Open Source Software

Open Source software is often being referred to as commodity products. This is particularly true for OSS databases like MySQL or PostgreSQL. Developers of such systems can heavily make use of defined standards. In this case, it’s the various SQL standards. These standards define the general functionality set your product should have. They help you define the commodity features of your software.

The question is: where do you get your software requirements from if the OSS product you are developing cannot rely on any or only a few standards?

Let’s take a look at two other types of OSS products: Enterprise Content Management (ECM) and collaborative software. I used to work for an Open Source ECM vendor until recently and just started to work for a company offering Open Source collaborative software. Hence, I might be able to provide some useful information.

For ECM vendors, there exist a few standards in different areas of ECM. This is because ECM comprises a very broad set of functionality, e.g. content editing, workflow management, document management, accessibility, etc. Yet, these standards cover only a small fraction of what makes up a full-fledged ECM system. In fact, ECM is very much about customer-specific implementations and integration of legacy systems. It is a lot about experience, best practices.

Hence, a successful Open Source ECM project can define the set of commodity features by listening to its:

  • customers
  • partner companies
  • developers and users community

These groups have different impact in different OSS ECM projects.

For example, eZ Publish is equally influenced by all three of them. At Alfresco, there is massive know-how of customer needs, simply because they have John Newton on board, co-founder of the very successful proprietary Documentum ECM. It will be interesting to see how eZ Publish and Alfresco will compete in the future. This will largely depend on how well the eZ Publish developers react upon market needs and on how fast Alfresco can grow its Open Source community. It’s actually not black and white, because customers can be a part of your developers community.

Before I talk about the interesting aspects of commodity features in collaborative software, one more note about highly standardized products: Of course, the MySQL developers need to also think of market needs. They first implemented the very basic features which made their RDBMS useful for simple, yet common scenarios in Web development. Standards do not free you from deciding which ones to implement first, but they help you to save time collecting all the potential features.

Now about collaborative software: Most development here is based on best practices. The interesting point is: these best practices are mostly already available in the Web. To be more precise: in the Web 2.0. At Mindquarry, we implement collaborative software which includes a Wiki, task and document manager (conversation tools for email and instant messaging coming soon).

Where do we get our basic ideas from? Well, from Wikipedia, Jabber, Bugzilla, etc. Mindquarry’s commodity features are out there in the Web and have been tested by a lot of users for several years. With Mindquarry, the trick is not about simply imitating an already existing and proven software infrastructure. It is about connecting the various bits and pieces of social software into one coherent infrastructure which you can use e.g. in your Intranet.

The point is: You can see the difference between the Web 1.0 and the Web 2.0 also in how OSS vendors define the commodity features of their products. An RDBMS is largely a Web 1.0 tool. It has at least one foot in the old days, when companies fought about software standards. Social or collaborative software is Web 2.0, you can find and influence its standards in the Web by providing efficient and rich user experience.

Of course, Web 2.0 standards rely on Web 1.0 standards, but the Web 2.0 is more about best practices and de facto standards on the user level compared to logical definitions of standards on the developers level. Again, the reality is not black and white. Take a look at MySQL’s and PostgreSQL’s ANSI92 SQL-defying LIMIT clause. It’s a best practice approach and shows that OSS developers always listened to their developers community just like Web 2.0 developers today listen to their users.

From 17 000 to 500 000 Google Results for "Mindquarry"

On Friday last week, Germany’s biggest IT news site Heise News wrote about the first public release of the Mindquarry Open Source teamwork software. Another big German IT site, Golem, also wrote about it.

This brought the Mindquarry Web servers almost down to their knees due to traffic caused by downloads of the Mindquarry software. At Friday, we had around 100 gigabyte changing owners caused by 2500 downloads, 7000 unique visits and 30 000 hits.

1/3 of the traffic has been caused by the two German sites, with 25% of visitors coming from Heise, 9% from Golem. The biggest share, about 28%, actually came from StumbleUpon, 5% via del.icio.us, 33% from various other sites.

The aftermath of the release PR can best be seen in the Google results when searching for “Mindquarry”: Before Friday, it was 17 000, right now they are at 500 000.

Update: Forgot to mention that Lars also blogged about the release PR aftermath.

del.icio.us Browser for Web Applications

While at Badajoz, my tOSSad colleague Al Harris pointed me to a fantastic del.icio.us browser they developed at KnowNet.

You can try out the del.icio.us browser online. It’s fantastic! The top window allows you to browse for bundles and tags. It provides a slide to minimize or maximize the number of displayed tags:

KnowNet del.icio.us tags browser

Beneath the tag browser, the list of items and related tags is being displayed:

KnowNet del.icio.us items browser

The browser is JSON-powered. Feel free to contact Mike Malloch of KnowNet if you’d like to see the code. Al did not know the license, he basically told me that they are happy to share and don’t really care about licensing – sounds like true Open Source 🙂

New Job at Mindquarry

March 1st, I will start my new job at Mindquarry as VP Marketing.

Mindquarry’s Open Source product is enterprise social software, simply called “Mindquarry”. It supports spontaneous collaboration by including a Wiki, task tracker, file management, etc. The software is MPL licensed, version 1.0 will soon be available to the public. There’s an early access program available upon request.
The company was founded in 2006, it is located in Potsdam, Germany close to Berlin. The main investor is HP Ventures of SAP co-founder Hasso Plattner.

I’ll be in charge of strategic and operational marketing and community relations.

What I like most about this new job is:

  • I move from an Enterprise 1.0 Open Source company (eZ Systems and its eZ Publish ECM) to an Enterprise 2.0 Open Source company (Mindquarry).
  • Having 5 years of PHP programming experience, I am now looking forward towards working for a Java company. Although programming is not part of my job, I am very interested in digging deep into the code to really understand the application’s inner workings.

I actually have known one of Mindquarry’s co-founders for a few years via internet: Lars Trieloff. We only recently met in person. His expertise always impressed me.

I created a dedicated Mindquarry RSS feed for my future postings about Mindquarry, also served by the newly created Planet Mindquarry.

At this cross road of my professional life, I would like to especially thank the following persons who always supported me:

  • Zak Greant
  • Georg Richter
  • Aleksander Farstad

Thanks guys! And of course, thanks to my wife, my biggest supporter 🙂