Open Source Strategies, Inc.

My friend Phil Simon is writing an interesting book called “The New Small” about how today small businesses are taking advantage of emerging technologies. We started talking about how open source software is affecting small businesses.  I realized that open source has made a fundamental shift in the relationship between technology and small businesses.  Instead of being a tool of large enterprises, technology is helping today’s small businesses leapfrog passed their larger competitors, thanks to open source software.

[Read more →]

Filed under: About open source, About Open Source Strategies by Si Chen - 1 Comment →

We’ve just launched our first e-commerce site with Magento, and it’s the new opentaps online video store.

On this site we will be offering downloadable training materials for opentaps Open Source ERP + CRM. Some of these, like the training video for setting up products in the OFBiz catalog manager, would also apply to OFBiz as well.

We envision this site eventually to be a place where all the opentaps service providers and developers could sell their  training materials such as videos or e-books about opentaps or their add-on modules.

Some Thoughts about Magento

Here’s what I learned from this experience with magento:

1. Compared to other open source shopping carts or e-commerce systems, Magento is much more polished and out of the box ready to use.   We made very small changes to the out-of-the-box CSS styles, but the catalog display pages and most importantly the customer checkout sequence worked for us without any made modifications.
2. The way that Magento handles downloadable products like online videos is also well thought out. It allows you to have a sample download, so your customer can preview before buying.   You can set the number of times a customer can view the download. Last of all, it scrambles the download URL link for you, so somebody can’t just e-mail a download link to their friends  and have them get it for free.
3. The configuration was fairly consistent. Most of the setup could be done in the administrative user interface, though a couple things like call out messages were hard coded and required modifying files.
4. The administrative user interface is very professionally done and consistent.
5. Nevertheless, setting up an online store is still work.   There were quite a few screens you had to go around to set up your store, categories, products with prices, links, etc.  It almost makes me wonder “aren’t there other online video stores out there?” Shouldn’t there be a standard template already?

Filed under: About open source, About opentaps by Si Chen - 3 Comments →

When I first found out about open source software, I felt the sky was the limit — with the source code, I could do anything now! But after working on open source ERP for the last seven years, I’ve come to realize that customizing software, even open source software, should not be taken lightly. I recently spoke with Phil Simon, long-time enterprise software veteran and author of The Next Wave of Technologies and Why New Systems Fail, and asked him for his thoughts on when you should customize open source software such as ERP and CRM. Here’s what he had to say:

Customizations and Open Source Applications

One of the issues that I have routinely seen over my years as a software consultant concerns customizations. On many a project, the functionality of a COTS application did not meet one of my clients current business practices. Invariably, this would beg the question, “Should we customize the system?” In this post, I’ll look at this from the angle of open source applications.

Reasons for Customizations

I could reinvent the wheel here, but there’s no point. The best post that I have seen on this comes from my friend, John Henley of Decision Analytics. Henley details some advantages to customizing an application. They include:

• Core competencies
• Your other front/back-office systems require it
• You want additional fields and/or different field sizes
• Regulatory requirements

Henley notes an interesting paradox of customizations. Specifically one trap that almost every organization falls into is that of customizing under the false pretense of core competency when in fact what they are doing is customizing to make their ERP to look and work just like the system it is replacing. The second edition of my first book, Why New Systems Fail, takes a deeper look at open source applications, as they continue to make inroads against traditional on-premise applications from the SAPs and Oracles of the world.

In the book, I write:

Organizations considering customizations should look carefully at their available options, ideally with the help of experienced business and technical consultants. It is imperative that they carefully consider the short- and long-term implications of these customizations, lest they be stuck with an unsustainable status quo and paint themselves into a corner.

Against this backdrop, I can’t help but wonder: Are customization decisions fundamentally different for clients with COTS apps versus those with OS ones?

Five Considerations

It’s an interesting question. To answer it, consider the factors:

Who Will Support Your Customizations?

Let’s be honest here. The vast majority of “standard” support agreements between clients and on-premise software vendors do not cover customizations. For example, if you want to change the way that the program calculates employee taxes or runs a P&L, you can certainly do so. However, if you read the fine print of your support agreement, you would have violated its terms. You can call support for help, but expect to be billed for assistance.

One of the main advantages of open source is that it allows you to customize the software more easily. That’s a major value proposition of OS: they understand that businesses have different needs and don’t have such rigid rules about customizations. Don’st expect unlimited bites at the apple, however. Open does not mean free; if you need support for your customizations, read the support agreements carefully to determine what will and will not be covered. OS projects could be supported by the original developer, like OpenTaps or SugarCRM, which is equivalent to a vendor. Will your vendor support your customizations without incorporating it back into their core product? Not always. Alternatively, they could be supported as part of the open source project by the community, but in that case, your customizations would have to be open sourced as well. Finally, since the source code is openly available, a third party could potentially support your customizations, but the process of getting another group to work with your source code might not be so easy.

Too many customizations is ill-advised in either environment

One of my favorite IT books of the last year is Roger Sessions’ Simple Architectures for Complex Enterprises. Sessions writes about Kevin Drinkwater, CIO at Mainfreight. Drinkwater is “widely recognized for his innovative approach to IT and for the cost effectiveness and agility of his solutions.” In a nutshell, Kevin understands the need for simplicity and, to this end, has a long history of minimizing or removing complexity from many environments. While aiming for simplicity doesn’t guarantee “success”, it sure decreases the chances of failure. In other words, regardless of whether your organization goes with COTS or OS, aim for simplicity. It’s just simpler for everyone involved.

Upgrades and ticking clocks

Here’s a—and perhaps the—major advantage of OS apps. You control the application. You are not beholden to a vendor’s forced upgrades. Many first-time clients of major vendors foolishly expect that the customizations will work after an application patch or upgrade of versions. Don’t. Again, you are not compelled to upgrade with open source.

Ease of customizations

There are too many different types of customizations, COTS apps, OS alternatives, and programming languages for me to make some type of sweeping generalization here. Just make sure that you do your homework. Don’t assume that an OS customization is easier because it’s OS. Spend some time to understand how easily your application can be customized, and how maintainable those customizations are over time. Note the two are not necessarily the same thing–some applications make customizations easy to make but very hard to maintain.

Not all customizations are created equal

We’ve all been here. Some VP or Director is accustomed to seeing a report in a certain way and, like a bulldog, won’t let go until s/he wins. Changing the sorting on a report or the name of “front end” field is fundamentally different than changing batch programs behind the scenes that affect thousands of transactions each cycle.

Conclusion

There’s no one right answer about whether an organization should customize its app (OS or not). Just think about the factors discussed in this article before going down this road. Make sure that your organization budgets the time and financial and human resources to effectively handle the customization. Finally, test whatever changes you have made before going into production. Most OS projects are modular in nature: it’s required for the parallel development style of an OS project. In that sense, technically the average OS project should support add-on modules and customizations more easily than proprietary apps. Of course, each project’s technical structure is different. First check everything carefully.

Filed under: About open source, About opentaps by Si Chen - 5 Comments →

I “met” Phil Simon earlier in the month and have been following his blog, twitter posts, and  cartoons ever since.  Phil’s been in enterprise software a lot longer than I have, and now he’s writing about a variety of interesting topics about technology.  We started talking about cloud computing and open source — and I just had to put in my two cents.  So I did my first guest blog post about cloud computing and open source on Phil’s blog.  I hope you’ll take a moment to read it and browse the rest of Phil’s site.

Filed under: About open source by Si Chen - Comments Off

In this part of our series on An Open Source Business, let’s take a look at our friends in the online music space and see what we can learn from them.

The Deal recently had an article about online music startups which should strike a chord with anybody who’s thinking about or trying to make a business out of open source.  Look at what they had to say:

“huge numbers, lots of hype, a surfeit of hope and a major chance of failure… some of the business models are inherently economically unfeasible… It’s completely unsettled and more and more fragmented…The rules of the industry and the economics of the industry have completely changed…Technological advances offer more and more delivery mechanisms, user options and wizardly new features…However, just who can make money off all this is almost as uncertain now as it was five years back…Everyone is gambling there will be a way to monetize distribution of recorded music, But no one has come up with the solution…Last year’s great hopes are this year’s busts.”

Sound familiar?  It should.  In a nutshell, open source business models share the same strategic problem that these online music startups have: how do you make any money when most of what you provide is available for free? Let’s look at the ways:

Free the Software, Sell the Services

Just about every commercialized open source project follows this business model.  The software is free, but the developers charge for services such as support, training, customization, and software development.  Sometimes the services are “productized” into manuals, seminars, installation CD’s, and packaged support, but the idea is the same.

This model works well…to an extent.  For example, we’re the main developers of opentaps Open Source ERP + CRM, and we’ve found that users are indeed willing to engage us for opentaps-related services because of our experience and knowledge with the system.  However, we’ve also found that users are willing to hire us mostly for customizations which are unique to their needs.  We’re still responsible for the architecture and user interface of opentaps ourselves, and that’s why since the release of opentaps 1.0 we’ve invested in everything from integrating Spring, Hibernate, and the Google Web Toolkit to building a Domain Driven Architecture.

Like the Free Version?  Please Pay Us for Even More!

Many open source software developers, and virtually all open source software companies funded by venture capitalists, engage in the “commercial/open source” model.  An open source edition is available free of charge to attract potential users, and a fancier commercial version is available for pay.

This is not an easy business model.  Let’s go back to music as an example.  I like Pink Floyd, but if you gave me The Dark Side of the Moon for free, would I pay you for Ummagumma, The Final Cut, and every other song by Pink Floyd?  No, I wouldn’t.  (Another example is travel: how many people actually pay for First Class?)

But perhaps the best evidence that this is a difficult business model comes from the commercial open source companies themselves.  Compared to a few years ago, their websites are de-emphasizing the open source version (sometimes you really have to look even to find the download page), and their “community edition” licenses are increasingly restrictive.

Nevertheless, I think this is a model which could be very successful if two conditions are met:

1. You must have a very large open source user base.  Think MySQL.
2. You must segment that user base carefully and identify the unique needs for your “enterprise edition” product.  The need must be fundamental — a little bit of eye candy and a few cool features alone won’t be enough.

Be careful, though: if you execute this model incorrectly, you could easily lose the goodwill of your open source users and unwittingly give away a viable commercial product for free.

The Alchemy of Open Source

There is a famous story of the Stone Soup, where many free ingredients came together to make an amazing finished product.  Lest you think it’s just a fable, Red Hat and Ubuntu do exactly that–they’ve combined major open source projects such as Linux, Gnome, Apache, Firefox, Thunderbird, OpenOffice, and MySQL and built major businesses from them.

This is the business model we’ve chosen for opentaps so far.  We’ve built opentaps from major open source projects such as Apache, Funambol, Google Web Toolkit, Jasper Reports, Pentaho, MySQL, PostgreSQL, and too many others to name here.  We’ve had to be patient at times, but over the years, we’ve grown as all those other projects have matured.  Amazingly enough, these open source projects have put us years ahead of many commercial ERP systems technically and enabled us to build opentaps sustainably, so that we now have a fully integrated ERP and CRM system with business intelligence, ecommerce, and mobility integration without any VC funding.

But this is not an easy business model to execute.  You must be willing to understand other open source projects and have the technical ability to work with them.  Most importantly, you need patience.  With this business model, you are growing with the community of open source projects.

In the End . . .  Just Make it Better

No matter what business model you choose, ultimately you’ll succeed if you make technology easier and better for your users. In the online music world, there actually has been a great success story — iTunes.  They’ve done it by making downloading music easy and fun.  So learn from them.  If you can make software easy and fun, you will be successful.  Next to a great product, the business model is just a footnote.

In the next part of An Open Source Business, we’ll take a look at marketing strategies for open source software.

Filed under: About open source, About opentaps, An Open Source Business by Si Chen - 13 Comments →

A group of graduate students from the Lancaster University in Lancaster, UK contacted me last year regarding a research project they were doing. They wanted to compare open source and commercial ERP systems for the retail industry and evaluated opentaps Open Source ERP + CRM, openbravo, and Microsoft Dynamics NAV (Navision).

They were kind enough to share their results with us, and you can read it at Opentaps In Retail. I hope you would find it interesting.

Filed under: About open source, About opentaps by Si Chen - Comments Off

We’ve been working on an integration of the Magento e-commerce platform for opentaps Open Source ERP + CRM, and some of our long-time users have also talked about integrating opentaps with Spree. I took a quick look at both and make some notes about them. Since we’re not developers of or service providers for either one,  and we plan to support integration with both in opentaps, I hope you’ll consider this an unbiased if somewhat “bird’s eye” comparison of Spree vs. Magento.

Spree

Spree is lightweight and easy to use, and the user interface for both the online store and the backend administrative module were quite intuitive. There is a good amount of documentation on the Spree website, and the authors of Spree seem really interested in helping you understand their system and work with it.  Their BSD license is one of the least restrictive open source licenses.   There is an active community around Spree, as evidenced by the Spree extensions available.  Finally, Spree is written in Ruby on Rails, which is a very well-thought out web development frameworks.

Magento

Magento is a much bigger application than Spree.   Its  online store is also very intuitive and easy to use, but it’s altogether more polished and commercial-looking than Spree. The backend administrative applications are bit more complex, though. The free documentation available seems to be just  the Magento wiki, which has a lot of content available but is not as consistent. There are also several books on Magento, ranging from to Magento: Beginner’s Guide to The Definitive Guide to Magento and php/Architect’s Guide to E-Commerce Programming with Magento. (Note: I haven’t read these books yet and can’t give them any recommendations.) Finally, Magento is written in PHP and the code seemed well-organized on first inspection, which means that a good developer should not take too long to get familiar with it.

Magento has a  commercial/open-source licensing model, and the free version is licensed under the OSL 3.0 license. The OSL 3.0 is also a true open source license approved by the Open Source Initiative,  but it is more restrictive than the BSD and the GPL license. (See the GNU Project’s comments about the OSL, for example.)  Still, do not view this as purely negative. If the commercial/open source licensing model can support full-time professional developers to work on Magento’s open source version, then ultimately it would benefit most real end users of the open source Magento  e-commerce platform.

The biggest advantage for Magento, though, seems to be its large number of third party modules available. There are over 1300 add-on modules available for Magento.  (And the opentaps-Magento integration will soon be one of them!)  Although most of these are commercial (as in “for pay”), and many of the free ones are in “beta” status, there still seems to be a lot of stable, free modules available.

How to Choose?

My personal opinion is that this comes down to a decision between Ruby on Rails and PHP. You should ask yourself which one you would prefer to work with and feel more comfortable with. However, keep in mind that while Ruby on Rails has been a very successful web development framework, PHP is simply the most dominant one today.  (See for example O’Reilly’s State of the Computer Book Market and the TIOBE Software Index.)  Therefore, there are many more developers, service providers, and add-on modules for PHP than Ruby. For example, Facebook’s developer API is mainly for PHP.  Until Ruby on Rails comes up with a “killer app” that does something which PHP fundamentally is not well-suited for, I would not expect this to change.

Filed under: About open source by Si Chen - 14 Comments →

I listened to a very good talk last weekend by Eric Qualman, author of Socialnomics, about social media and social networks. Eric had a lot of  good examples about how companies such as JetBlue, McDonald’s, and Burger King are taking advantage of social media to promote their brands and their products.

But what about small businesses? What if you are a startup or a neighborhood business, and you don’t have the millions of potential fans that a JetBlue or McDonald’s would have — not yet anyway?

This is actually a situation we’ve faced ourselves, starting opentaps Open Source ERP + CRM on a shoestring. And looking back, we’ve only been able to do it because we were able to tap into an online social network called “open source,” which is an online collaborative community of software developers that predates Twitter, Facebook, Google — even the Internet itself.

What we’ve learned don’t contradict what Eric and other people have said about social marketing, but there are a few twists I would like to point out:

Join a Bigger Network

When you are small, your network is also small, so you try becoming a prominent part of a larger network, instead of just promoting in your own network. For us, this meant making ourselves known in the larger open source community of software developers and users looking for open source software by releasing our software and our ideas to them.  Fortunately, people liked them.

Network (verb) through the Networks (noun)

Use social networks as an opportunity to network with other people in compatible fields.  For example, we’ve benefitted from associating with other open source software projects, such as Apache, MySQL, PostgreSQL, Funambol, Pentaho, JasperReports, etc.

Be Memorable

Most importantly, be memorable. Be different. Believe it or not, the small business has the advantage here. People are always looking for interesting new things to talk about.  If you are a small business with a memorable product or service, the word will spread a lot faster now than ever before.

Filed under: About open source, About opentaps, About Social Media by Si Chen - Comments Off

At the beginning of every road, the possibilities always stretch infinitely to the horizon. So it always seems when one is starting a business as well. But could your open-source project actually support a business as well?

The answer is not always “yes.”

On the surface, even the concept of an “open source software business” seems to be an oxymoron. “Open source” means software that is freely available for users to download, use, and distribute. A “software business” means charging for that software, be it from licensing, support, or documentation. So how could an open source project be used to build a software business?

To answer this question, we need first to understand why both commercial and open source software models work in the first place.  Commercial software offers features. In return for my money, this shiny package will (hopefully) offer me out-of-the-box features that meet my needs. Open source software, on the other hand, offers code. I can go somewhere, get the source code for free, then customize and extend it as I need. The software freedom that Stallman originally talked about is really a freedom through code: I am “free” with open source software not because I got the software free of charge, but because I have its source code, so I can change it to suit my needs. Therefore, commercial software will appeal to people who are looking for stable, easy to use, and supported features, whereas open source software will appeal to people who are looking for well written source code to modify or customize.

Not all software have both groups of people. For example, there are certain types of software which practically nobody wants or needs to modify or extend, so open source has a limited value proposition (other than being free of charge.) In this case, you might be better off releasing your software as shareware: give it away for free, but keep the source code, and then ask people to pay for an enhanced version.  (A modern alternative to this model would be to offer it free online and sell ads.) Conversely, there are some types of software, especially in the open source world, which are really not intended to be used out of the box and therefore are only valuable to programmers willing to work with the code. These might work adequately as open source projects, but you will probably have a very difficult time making a business out of them.

Therefore, to have an open source software business, you need to find a type of software where there are people who need the source code and where there are people who would pay for out of the box features, stability, ease of use, and support. We think we’ve found it with business applications software, such as ERP and CRM software. Virtually all ERP software, even multi-million dollar commercial packages, must be customized, so our users will appreciate having access to the code. Ease of use, stability, out-of-the-box features, and support are things that business users are used to paying for as well. It was this thinking which led us to create the opentaps Open Source ERP + CRM business applicaitons suite.

If you think you have found such an open source project, I will write more about how to build software for both open source and commercial users in the next installment of our series on “An Open Source Business.”

Filed under: About open source, An Open Source Business by Si Chen - 8 Comments →

Many entrepreneurs view venture capitalists with a reverence reserved for royalty, so it be surprising to hear that it’s been rough for the royals too. A recent article in The Deal entitled “Honey, I Shrunk the VCs” tells us just that. Return on venture capital funds have fall into single digits, and out of several thousand funds out there, only a few hundred are making active investments. The rest can be expected to disappear as their portfolio companies “unwind.”

The culprits?

I believe open source has contributed to #3 from this list. Whereas ten years ago, startups bought Sun servers and ran (and paid for) Solaris and Oracle, not to mention commercial software development tools, today’s startups can get up and running with Linux, MySQL, PHP, Java, and Eclipse. Even Solaris is open source and free now. Thanks to open source, it’s easier to start an online business than ever before, so there’s less need to get “funded.”

But open source is still moving forward. Consider opentaps Open Source ERP + CRM. This is an open source suite of business applications, including CRM, accounting, inventory, warehouse and supply chain management, which is freely available. Could these free applications lower the cost of startups in biotechnologies, clean energy, or resource management? I hope so.

More importantly, though, because opentaps is open source, you can study it and modify its source code to suit your needs. This means that it’s not just a set of free applications, but also a toolkit or framework. Could that help create new and innovative applications that we haven’t even dreamt of yet? I hope so.

Now, I don’t think venture capitalists are irrelevant. As long as starting something is hard (and it will probably always be), we’ll need smart people who could help us sift through our ideas and push us forward. But I do hope with open source, making great ideas come true gets a little easier.

Filed under: About open source, Uncategorized by Si Chen - Comments Off