Archive for the ‘Open Source’ Category

Freemium and OpenSource Funnels

Thursday, July 22nd, 2010

In my last blogpost titled “Why Free? Why Now?” I provided some background on the impetus and the reasoning behind LoopFuse’s move to provide a free marketing automation offering. It has been only three weeks since our launch of FreeView, but the response has already been overwhelming. One of the most interesting changes that comes with a move into a freemium model is the shape of the funnel. Over the past several years I’ve studied the funnels of dozens of companies and I’ve noticed that those companies based on freemium models (including opensource) show some very distinctive and interesting patterns.

The Mouth of the Funnel

The first distinctive feature of a freemium-based funnel is obviously that the funnel’s mouth becomes extremely large. Providing anything of significant value for free will attract a large number of people. The number of people attracted is directly related to the amount of value provided for free and inversely related to the “friction” in obtaining that value. For example, when Ben and Jerry’s offers a free ice-cream cone a line will form. But as the line grows the “friction” to obtain the free ice-cream becomes a disincentive for people who realize that waiting an hour in line for a $3 cone may not be worth the effort. However, if the free item were an iPhone instead of an ice-cream cone then the length of the line would naturally extend much farther as people weighed the value of their time against the inconvenience.


Freemium companies must not only ensure that their free offering provides significant value, but also that the “friction” required to obtain that value is minimized. For example what information must the prospect divulge about him/herself and/or his/her organization to access the free offering? What setup and configuration tasks must be completed? How aggressive is the push to migrate from the free offering to the paid upgrade? The value of the free offering minus the total friction required to obtain that value will directly drive the relative size of the earliest stages of the funnel.   Of course, in order for people to consider a free offering they must be aware of it. While word-of-mouth is a key component of the freemium marketing strategy, there is still a very important role for traditional marketing to drive awareness.

Behavior-Driven Funnel Definition

The second distinctive feature of a freemium-based funnel is the segmentation of the funnel based on behavior. Traditionally the progression of a lead through the segments of the funnel has been based on external indicators such as registration, download of collateral, participation in webinars, product trial download, contacting sales for assistance, etc.  However, due to the volume of leads being managed inside the funnel, a freemium model must provide a hyper-efficient means of measuring the progression of a lead towards purchase and must maintain a level of accuracy in that measurement to ensure that we are not overwhelming the sales team with unqualified leads. Therefore, the segments of the funnel may need to become more specialized based on data being collected directly from the usage statistics of the free offering. For example, in our own funnel, LoopFuse knows exactly how many users, leads, forms, lists, nurturing programs, reports, and campaigns are in use by every single FreeView user. These statistics are key criteria for the promotion of a lead inside of our own funnel segments. This type of integration is usually much easier with SaaS freemium models than with pure opensource models because the usage statistics are more readily available.

The Patient Sales Model

The third distinctive feature of a freemium-based funnel is the lack of momentum in the early stages of the funnel. In a former life I worked at an opensource company and we used to discuss the concept of the “patient sales model”. The concept was based on our observations that it often took YEARS before a free user was ready to purchase a premium upgrade. A user would download the software, become familiar with it’s capabilities and limitations, and it would become part of his/her default toolkit. At some point in the future he/she would pull out that software and would run into a limitation that could only be overcome by upgrading into a premium version. At this point the value proposition is clear to the purchaser, the friction of adoption is zero, and the prospect is usually ready to pay for the value they are receiving. However, there is no magic formula that will predict when this circumstance will present itself. Freemium models front-load the funnel with lots of users on the basis that eventually they will run into this situation.  Also, traditional metrics such as days-to-close can become misleading in freemium models unless you start the clock at the point of opportunity creation rather than lead creation.

While the LoopFuse freemium offering (FreeView) is only a few weeks old, we can already see the momentum impact at the front of the funnel. We have already revised our internal funnel segmentation to better utilize the FreeView behavioral data to more accurately identify those prospects who are gaining the most value and are therefore more likely to pay. I am fascinated by the funnels of freemium and opensource companies and look forward to watching the evolution of our own funnel and the subtle patterns and idiosynchrasies we identify along the way. For a great in depth article on the “Fundamentals of a Volume Market Engine” I highly recommend reading Fred Holahan’s article on OpenSource Business Resource.

Tech talk – Cloud, Multitenant, J2EE, Open Source and other techie buzz words

Friday, March 26th, 2010

I’ve been asked a lot lately to talk about our solution platform and technology used here at LoopFuse, so figured it would be worth a blog… To start, LoopFuse OneView is an on-demand marketing automation software solution. In a nutshell, this means it is software hosted by a vendor on the internet that can be run using a web browser without having to install any software, so is ready for use immediately. This is also called SaaS (software as a service), which is a term originally made popular by vendors such as SalesForce.com. Lately the term “Cloud” has replaced SaaS as the new buzz word.

Cloud computing as a concept and even as a practice has been around for a long time. Although “the cloud” is often seen as a synonym for SaaS, it actually is a broader term in that it refers to hosting all types of internet based services such as remote file storage and not just packaged software solutions. Many “cloud” hosting vendors exist, but the most well known one is Amazon with their AWS (Amazon web services) which includes offerings ranging from data storage to payment services to distributed database hosting.

Although there are many upsides for on-demand software vendors to deploy in the cloud, there still exist a few downsides as well; the main one being loss of complete control of the NOC (network operations center) they run their software service from. For many on-demand applications that are not mission critical, such as photo sharing sites, the tradeoff between losing control of network operations and the cost savings of outsourcing their IT is very acceptable. However, for mission critical applications such as marketing automation where businesses rely on leads being captured to drive revenue, the tradeoff can be less compelling.

At LoopFuse, we made the decision to host all our core services ourselves within our own NOC instead of hosting with a cloud hosting provider such Amazon. Collectively, we’ve had a lot of experience building out network infrastructures and felt this would be the best way for us to ensure the reliability, security, and scale which our customers would depend on. To date, this decision has proven to be a good one. For example, under the Amazon EC2 Service Level Agreement the target uptime is at least 99.95%. While this is very good, it could potentially translate into almost 55 minutes of downtime since the beginning of this year (54.72 to be exact). The actual uptime for the LoopFuse lead capture service since the beginning of this year has been 100% (i.e. no downtime). Even though just under an hour of downtime over a three month period may not seem like much, not being able to capture leads after launching a major customer acquisition campaign would be a major problem for most businesses. Another area where having complete control of the NOC is beneficial is being able to implement specific security controls. An example we encountered of this at LoopFuse was a customer who worked with government agencies that had the specific requirement of degaussing hard drives containing their data after being decommissioned. Because we have direct physical access to all our hardware running within our NOC, we were able to meet this requirement.

Another somewhat unique decision we made related to being an on-demand software provider is how we implemented our multi-tenant architecture. Most SaaS vendors use a multi-tenant architecture where all their customers share all the same hardware, application instance and the same database instance. Although LoopFuse OneView is a multi-tenant application with shared resources, all customer accounts are stored in separate database instances. Because every customer has their own database instance, there is no commingling of customer data (i.e. customer A’s leads to not sit next to customer B’s leads within a database table). Besides being inherently more secure, customers having separate database instances also helps will scalability since can allocate hardware based on size and usage of individual accounts. For example, many smaller customers can be put on a database server where share hardware resources such as CPU and memory and a large enterprise customer can be put on a similar database server by themselves. This prevents the smaller customers from being impacted by the larger customer consuming all the hardware resources and vice versa. Also, scaling up as more customer accounts are added is not limited by what a single server can handle across all customer accounts which would require expensive hardware upgrades, but instead can simply add more reasonably priced servers to the server farm.

Finally there is the actual technology we used to build LoopFuse Oneview, which is primarily J2EE (Java Platform, Enterprise Edition). This was an easy decision for us since Roy Russo, the other founder, and myself both came from JBoss, an Open Source J2EE vendor, we were already very familiar with J2EE.  As you might guess, we also deploy on JBoss as well.  Using J2EE, along with JBoss, provides many inherently “enterprise” features such as clustering, failover, load balancing, caching, and distributed processing along with enterprise grade security via JAAS.

We also use a number of other Open Source products such as Red Hat linux and MySQL.The use of Open Source technologies and products was a no-brainer as well since we were already well aware of all the benefits.  The first and most obvious benefit is cost.  The next biggest benefit of Open Source is access; not only to the code but to information.  Because of free and open access within the Open Source world, it is much easier to find information about issues and work-arounds, how to implement specialized requirements, and best practices in general.  This is a very powerful benefit and one of the main reasons access to our customer support portal is free and open to all.

Empowering Sales with Business Directory Integration

Wednesday, September 23rd, 2009

Empowering Sales with up-to-date contact information on contacts and interested prospects is essential in this day and age of high-volume, low-touch sales processes. LoopFuse OneView offers Sales organizations deep integration with a great number of common 3rd-party business directory and news sites, easily accessible from any visiting Company’s analytics page.

The current integrated 3rd party directories and news sites are pictured below, and include direct-linking to information providers such as Hoover’s Business Directory, Jigsaw, Google News, and ZoomInfo.

Hoover's Business Directory

Jigsaw

What, no Google news for Eloqua? ;-)

Because the level of integration is “native” and presented as a hot-link, LoopFuse is able to provide the added value and information to sales organizations at no cost to us and therefore no additional cost to LoopFuse customers… and sales people are much happier for it all. ;-)

Drupal / LoopFuse Integration Module Released

Tuesday, July 22nd, 2008

Today, our friends at Drupal announced the release of the LoopFuse OneView integration module for Drupal. The module, now available from the Drupal website, allows for pluggable integration between the Drupal CMS and the LoopFuse OneView Marketing and Sales Automation platforms. This is a natural pairing for two technologies that are widely used throughout the internet – Our products have a considerable overlap in who they appeal to… Marketing and Sales executives.

The original impetus for this module, was started by Chuck D’Antonio under the Acquia umbrella. Much of it came about as Acquia became a LoopFuse customer and felt a tighter integration that would benefit the community would be fruitful. This is OSS, as it was meant to be. I couldn’t agree more. ;-)

Taking the press release at face-value would be a mistake, as there is an important message here, regarding the future direction of both companies. I believe it is evident that Drupal has continuously set itself apart from other Web CMS  by appealing to a more sophisticated crowd. The same is true for LoopFuse. At the same time, however, I would state that both companies have a fair understanding of what it means to have mass appeal… allowing a simple user to get up-and-running in minutes, yet enabling high-end users with unlimited flexbility and scalability. This is a delicate balancing-act for any company, but one that I believe our friends at Drupal/Acquia know very well how to master.

IBM, Sun, and "The Community"

Thursday, May 15th, 2008

Being a former member of the JBoss ranks, I can’t help but laugh when I read folks from Sun and IBM endlessly pontificating in the blogosphere about OSS business models and “The Community”’s role. This focus on OSS and “Community” seems to be a new M.O. for both of them, after years of being proprietary vendors, and outright Anti-OpenSource.

So What exactly makes this so funny, and why the about-face?

Sun: You’re great at building hardware – Fantastic and trend-setting hardware that blows away just about everything on the market. Your software has generally sucked. We can’t even measure the amount of suck, its so large. At some point you decided that JBoss was hammering away at your software and figured it would be in your best interest to fight fire-with-fire. ie. throw the software over the wall in to OSS-land and hope for the best. (I won’t even comment on how the (JCP) Java Community Process, is akin to the World Bank, with vendors talking behind closed doors, NDA’s, and little active input from the Java community.)

IBM: You’re a consulting company… err…. “Global Services” Company. Just because you bought that mess Geronimo and throw some developers in the Apache ranks, doesn’t make you a carrier of the OSS torch, but keep blogging and we’ll keep laughing at you.

So how did we all end up in bizarro-world… where Sun and IBM are now the mouth of OSS?

The JBoss impact

JBoss took a big bite out of the industry. BEA (as much as they won’t admit it) crumbled largely because they could not compete with JBoss’ innovation, price, and adoption rate. IBM had their hand forced in to buying Geronimo – a fight fire-with-fire approach. Sun’s organization has always lacked and simply couldn’t compete with JBoss at all, and so it was slowly dying.

… and now the deck is shuffled. Red Hat buys JBoss and proceeds to let the fruit rot on the vine, thereby creating a vaccuum for these two to dive in. Of course, they’re diving in without any clue on how to run an OSS business. Remember, these are the same guys that were on the losing end of the OSS fight for years, and have zero talent in their executive ranks on how to run an OSS business.

There is a vaccum in Java OSS, as Red Hat leadership has been largely impotent – not knowing what to do with JBoss. The JBoss “mouth” in the community is gone and so is their drive. I have hopes that the new leadership inside of Red Hat can clean house – Leave JBoss alone, give it more money, energize the ranks, and PLEASE clean up the mess within Red Hat mangement. There is no reason why Red Hat could not be bigger than Sun and maybe IBM one day, given the proper vision and execution. Red Hat has a large bulls-eye painted on its back, because of its own doing and now has IBM, Sun, Oracle, Canonical, and others aiming at it.

I don’t have a dog in this fight, but I do get annoyed listening to blow-hards talk about “The Community” and how to run an OSS Business, when just a year ago they were both large megacorps intent on fighting OSS (and getting their butts handed to them). I tend to ignore the public discussions they fuel, as they’re largely wrongheaded, and their opinion on OSS business models is backed by zero experience and education. My only advice to the “New Leaders of OSS”, is to perhaps hire some proven OSS talent. Sun did well buying MySQL – perhaps MySQL’s vision can infect Sun. IBM is just utterly clueless as usual, and trying to find a way to push more bus-loads of $400/hr consultants – things never change at Big Blue.

So who should you listen to on OSS Business Models and Community issues these days? The companies that aren’t sucking up all the air in the room, but are quietly making it happen: SugarCRM, SpringSource, Hyperic, Zenoss, Alfresco, Zimbra, MySQL, and Zend. These guys have it right. They’ve been at it for years and have learned how to grow a community and execute on the OSS Business Model (which isn’t a one-shoe-fits-all).

Thats my $0.02. Now grab some popcorn, sit back, and keep reading the Sun/IBM dynamic-duo expouse their pearls of wisdom…

UPDATE: The looniness gets loonier with the IBM guy now advising Sun on how to pull together “like” products in to a “family”. He’s citing WebSphere CE as a success story. Maybe the guy from Sun will respond on the success of JavaDB and we’ll truly have an idiot convention on our hands.

SpringSource makes a big move

Tuesday, January 29th, 2008

It was announced today that SpringSource is acquiring Covalent. For those who are not interested in the happenings in the technology space, no reason to read further. For those that are, this is BIG news.

For those not familiar with Covalent, they are the commercial entity behind several Apache projects, Apache Web Server being the most notable. Although not as flamboyant as other open source business, they are THE guys you would want to go to for Apache Web Server support. Heck, they are the guys that JBoss partnered with so can include Apache Web Server support alongside Tomcat and JBoss support.

To me, this acquisition signals intent to broaden the reach of SpringSource towards being the source for a larger stack. So compared to the much talked about LAMP stack (i.e. Linux, Apache, MySQL, Php/Perl), another popular stack is LAMJ (i.e. Linux, Apache, MySQL, Java). Spring is already well positioned to be a top provider of the “J” in the stack and now the “A” as well.