Tag: SaaS

Pros and Cons of the Freemium Software Business Model

One of the hottest trends in the software business over last several years has been the rise of the “Freemium” business model. For those unfamiliar with the term, a Freemium model is characterized by an entry level version of your software which is totally free to users–forever.

This business model has actually been around in the software industry since the 80’s and was originally referred to as “crippleware” or “lite” entry level versions of software. The term “Freemium” apparently entered the software industry lexicon when used by Jarid Lukin of Alacra in 2006. But enough history. Regardless what you call it, the model on the surface is well suited to the software business due to no (or very low) cost of goods sold.

Whatever term you use, the model is predicated on creating a large “free” user base quickly, usually by using viral marketing methods such as referrals and word of mouth along with other very low cost methods such as SEO. The large free base is then “monetized” by selling advertising to their eyeballs and/or upselling them on premium software features or services. The Freemium model today is widely used in the software biz across a number of form factors including Open Source, SaaS and traditionally licensed software.

What’s most interesting to me about the model is the trendiness of it the last few years since the term Freemium came into use. I see many companies that appear to be adopting it because they feel like so many others are using it — that it must be the right thing to do. But is it the right thing to do in all cases? In my opinion–it is not. Let’s take a closer look.

Freemium Model PROS

Fundamentally viral: he more users you get–the more users you get. Free users will refer other users who could turn out to be paying users.
Allows you to upsell your own (free)customers–upselling a customer that’s already incorporated your tool into his workflow is generally easier than selling a new customer from “scratch”.
Keeps prospects in your target market away from being locked in by the competition.
The barriers to entry to your product line are at the minimum possible (even less friction than free trials and money back guarantees)
Great for startups to say be able to say ”we have XXXXX gazillion users”.
Enables Free Beta testing of new products with a large number of users.
“Free” traffic and user bases can sometimes be converted to advertising revenue.

Freemium Model CONS

Usually has low conversions rates to paid version, average is about 1%–although this obviously varies widely.
If you do offer customer/technical support to free users, it’s potentially a large expense unsupported by little if any revenue.
If you don’t offer support or only offer poor/reduced support to free users (such as forum-only support), what does that do to your conversion rates to paid users–as well as your overall reputation?
If you do offer reduced or no support to free users, lots of time can be wasted trying to figure out who “qualifies” for what level of support .
99% will never pay you a dime–are they REALLY customers?
In addition to customer technical support costs, if you’re SaaS-based the cost of data/bandwidth/hosting for free users can be significant.
Requires EXTREME application ease-of-use to work well.
There is some evidence that having a free version reduces your conversion rates on free trials of your paid product.

The main reasons I don’t like Freemium models, except when circumstances clearly call for it:

Having a free version conditions the market that “free” is the appropriate price.
A free version can reduce the overall value perception of your product
It’s critical to the success of a Freemium model and difficult to get the free/paid feature set split “just right”. If you don’t get this split just right, you either won’t be able to attract enough free users (too little value in Freemium product) or you won’t be able to convert you Freemium users to paid versions (too much value in the Freemium product).
“Free” is a mentality that’s hard to overcome in a user; it’s much harder from convert a free user to a paid user than it is from an entry level (cheap) paid user to a premium paid user. An example of this is the difficulty of online newspapers in converting readers to paid models after years of “training” them that their content should be “free”.
I’d prefer to use available profits on professional marketing programs rather than starving the marketing budget due to excessive support/hosting costs.

Even taking my biases above into consideration, there is definitely a place for a Freemium business model in some situations:

The Best Circumstances to use a Freemium Model

Although the Freemium model has worked in B2B markets, in general I believe it’s better suited to consumer mass markets where viral is possible, price points are already low and free user bases and traffic can be high–making it possible to monetize the traffic via advertising
Entering a market with a very strong, embedded competitor.
When attacking a market with very limited resources or lacking in marketing skills.
With a product has a great “social pull” which lends itself well to viral marketing.
Freemium has already become the standard in your market segment, so you’re almost forced to follow suit.
As an act of desperation when nothing else has worked.

I’m sure there are others circumstances where a Freemium model makes sense–the list above is what comes to mind quickly.

So that’s what I think about Freemium–many will not agree. What’s been your experience with it? Leave a comment below with your own thoughts, lessons or best practices.

Follow Phil Morettini and Morettini on Management via Twitter, Facebook, LinkedIn, RSS, or the PJM Consulting Quarterly Newsletter. Contact Phil directly at info@pjmconsult.com

1 Comment by admin on May 11, 2013

filed in B2C, Business Models, Corporate Strategy, Online Marketing, Product Marketing/Management, Promotion

What Does It Takes to Build a Great Software Company?

Software-based businesses come in many different sizes and shapes: SaaS or cloud-based, mobile, open-sourced, consumer, SMB and Enterprise, etc, etc. Even many successful “hardware” companies could really be viewed as software companies, as they are in fact driven primarily on novel software or firmware under the hood. With the diversity of form factors, it’s very hard to generalize what makes a great software company.

But I believe that there are some common factors among the great ones. It’s much easier of course, to take a look at successful companies and work backwards in a postmortem fashion. The problem with this approach is that you tend to see a lot of “revisionist history” utilized when folks tell the story of what made a company successful.

Institutional technology investors have there own pretty well documented list; in general it goes something like this:

Strong Management Team with relevant experience in the space
Distinct competitive advantage, usually via breakthrough, defensible technology
Product/Service that addresses a serious pain point felt by the target customer
Large market opportunity

You’ll see various flavors of the above list and ordered in a variety of ways, but I think this is a pretty good representation of what VCs and other investors say they look for before they’ll write a big check. When discussing what makes great companies, there’s no doubt in my mind that the list above is valid and important. But I think it’s also incomplete. Here’s a few criteria of my own that I would add:

Management team chemistry

I’ve seen a whole bunch of management teams that looked like a great group on paper from a skills/experience viewpoint. But in practice they couldn’t work together for a variety of reasons: excessive competitiveness, selfishness, incompatible personalities and different communication styles are a few common reasons. As an example, I often see hard-driving CEOs with Type-A personalities who hire exclusively in his/her own image. The resulting management team often resembles a pack of hungry dogs fighting over a single piece of meat, with everyone fighting to be in the lead. Putting together a management team with good chemistry and mutual respect is more art than science and requires a leader with refined sensibilities in the “softer” aspects of management practice.

Lack of management arrogance and openness to learning

Management arrogance big problem that you find in people that perceive themselves as very successful. Sometimes they start to believe their own headlines and think they have all the answers. The problem is that when leading a software company the certain answers of yesterday can be the disastrous strategies of tomorrow, as software markets change so rapidly. I find that most leaders who are able to take their companies to greatness are not so full of themselves that they won’t listen to other internal and external voices. This is an attribute that enables management to navigate the treacherous road up the software industry food chain and raises the odds of taking a software business all the way to the top. Of course there are some famous leaders of large software companies that don’t fit this description–but I believe they are exceptions to the rule.

Realistic self-evaluation at every stage of development

To maximize the potential of a company to reach greatness, it’s important that once you’ve had some success you don’t get become over-enamored with it or underestimate what more is possible. At every stage of a company’s development the financial resources, personnel resources and realities of your market dictate what’s “possible” going forward. It’s sometime very hard to self evaluate where you’re really at as a company; some people are natural optimists and others pessimists. I’ve always felt that a little bit of marketplace paranoia is healthy in a management team. But the closer you can get to “reality” in your evaluation of what’s really possible, the more likely you will be to optimize that next step and keep moving forward on that long path to greatness.

Positive overall company culture

I believe that this may be the most important factor of all when it comes to a path to true greatness. There’s an old sports saying that “it’s not about the X’s and O’s, it’s about the Jimmy’s and Joes”. For those of you who aren’t sports fans, it’s just a funny way of saying that coaching (management) can only do so much; it’s the players (company staff) you recruit that really make it happen. In my opinion, this is very, very true and means that getting the best people possible really makes the difference in how successful a company will ultimately be. What is the biggest factor that allows you to recruit great people? In the long run, it’s a positive company culture that the current employees really feel good about which allows you to recruit great new people.

Those are my thoughts on what it takes to have a GREAT–not just good–software company. What would you remove or add to the list? Leave a comment below with your own criteria for software industry greatness.

Follow Phil Morettini and Morettini on Management via Twitter, Facebook, LinkedIn, RSS, or the PJM Consulting Quarterly Newsletter. Contact Phil directly at info@pjmconsult.com

1 Comment by admin on April 27, 2013

filed in Business Models, Corporate Strategy, General Management, SaaS, Startup/Early Stage

tagged business model, cloud, company culture, consultant, consulting, Corporate Culture, culture, early stage, management, Management arrogance, Phil Morettini, PJM Consulting, SaaS, software, tech, technology, VC, Venture Capital

Software Product Marketing: Horizontal vs. Vertical

An important discussion for most software companies–both in the product planning stage and in the downstream active marketing phase–is the manner in which it will be marketed. The decisions to be made in each phase are separate but closely related. This set of discussions need to happen regardless of whether you are marketing a traditionally licensed application, an open source application or a SaaS application.

One of the more important aspects to this is whether the product will be aimed tightly at one or several vertical segments, or marketed more broadly to the widest possible audience. This is the crux of the vertical vs. horizontal decision. Let’s examine a few topics which can be useful in framing this discussion.

How specific is the “language” of your application to a vertical audience?

This is very important because in some product categories the unique business processes of a vertical can be very important, while in other categories there is great commonality in process and language across industries. If you’ve written your application specifically to solve one market segment’s unique problem, it’s probably VERY specific. When this is the case it’s pretty obvious that you’ll start (and possibly end) with a highly vertical marketing effort. Sometimes as thing go along you may find that you’ve solved a problem for market A, but it’s also useful in market segment B and C–although there often needs to be at least some modification. If you’ve solved a more generic problem that applies to many markets, the decision to market the solution horizontally or vertically can be much less clear.

How big is your overall market?

A key consideration when you’re entering a new market with a new product. The larger the market the more likely it is you will need to take a vertical approach get initial traction. In many cases this means verticalizing the product in the product development phase. But even if there isn’t a strong set of vertical needs with respect to product features and “language”, in large markets a vertical promotional approach may be required to build market traction. It is often far easier to build a brand name and market traction in a tight vertical before you move on to the next segment, than by taking a more scatter-shot approach with no vertical focus.

What is the level of competition in the overall market?

This question is related to first question above as strong competition often goes hand in hand with large markets. They are separate issues, however, and should be evaluated individually. If the level of competition is high, regardless of market size, a new entrant is likely to have a better chance of success with a more vertical approach. It there isn’t significant competition in the segment, you may be able to have success with a horizontal approach, which can be a more efficient way to use both product development resources and marketing dollars.

Market maturity: has the overall market verticalized already?

Regardless of the level of competition and the market size if the larger market has already evolved into a number of vertical sub-markets, it may be too late to take a horizontal approach. It is usually very difficult to defeat entrenched verticalized competitors when entering a market with a horizontal application. The exception to this would be a new competitor with a product that provides a quantum leap forward in functionality (usually as a result of a technological paradigm shift).

What level of marketing resources are available to you?

The level of marketing dollars available to you are quite important in formulating your approach to the vertical vs. horizontal question. As one example, let’s say you are entering a market that is large, quite competitive and you won’t have a lot of marketing budget available. In this case, it would be very important to develop the product upfront with the strongest vertical focus possible and market it accordingly. On the other extreme, you might be entering a market of modest overall size that hasn’t verticalized to a great degree to date and you are well funded, enabling a substantial marketing budget relative to the competition. It this case it might be an easy decision to take the ROI-efficient horizontal approach both from a product development and promotional perspective. There are many potential scenarios between these two extremes which unfortunately will lead to less obvious decision-making.

Is your software a “point” or “platform” application?

Most software applications are “point applications”, meaning they have little or no integration with the rest of the software infrastructure. In addition, any possible customization is generally intended to be done by the application vendor themselves or maybe their channel partners.

I define a software application as a “platform” when it utilizes an open API which enables BOTH channel partners and third party software vendors to write add-on applications which extends the platform software’s functionality in two key area:

1) by adding “vertical” functionality not present in the platform software thereby enabling a complete solution for a specific vertical market.

2) using the API to integrate the application with other parts of the software infrastructure

In this way a platform software application allows a software vendor to “have it’s cake and eat it too” with respect to the Horizontal vs. Vertical discussion. The platform software itself provides basic functionality which can be sold broadly across many markets, while the open APIs enable the product to be tightly customized for specific verticals as required, by both your channel partners and independent ISVs. The platform application can be a product manager’s dream and is the Holy Grail of software when it comes to efficiently serving as many market segments as possible by leveraging partner investments. But it’s not something that can be forced; there needs to be a natural reason for the platform to exist, or there will be no third parties willing to write the add-on applications so critical to the platform’s success. Without these add-on application a platform will more often than not die a quiet death in the marketplace.

In some cases, such as when you write an application which aimed at a problem specific to a single vertical market, the answer to this “vertical vs. horizontal” question is easy. In many other cases you’ve created a product which is useful across several market segments–but do you have the resources to attack multiple market segments simultaneously? How do you approach this common problem? Leave a comment below with your take or shoot us an email with your questions.

Follow Phil Morettini and Morettini on Management via Twitter, Facebook, LinkedIn, RSS, or the PJM Consulting Quarterly Newsletter. Contact Phil directly at info@pjmconsult.com

3 Comments by admin on February 16, 2013

filed in Business Models, Corporate Strategy, Distribution Channels, Product Marketing/Management, Promotion, SaaS, Software/Product Development, Startup/Early Stage, VARs, enterprise software

tagged business model, channel sales, consultant, consulting, early stage, marketing, open source, Phil Morettini, PJM Consulting, Product Development, product management, product planning, Promotion, SaaS, Software as a Service, strategy, traditionally licensed, VAR, vertical market

Selling and Marketing Software Through the VAR Channel: Morettini on Management Video Series

Follow Phil Morettini and Morettini on Management via Twitter, Facebook, LinkedIn, RSS, or the PJM Consulting Quarterly Newsletter. Contact Phil directly at info@pjmconsult.com

No Comments by admin on November 4, 2012

filed in Business Models, Corporate Strategy, Distribution Channels, Promotion, SaaS, Startup/Early Stage, VARs, Videos, enterprise software, sales

tagged B2B, business model, channel, channel sales, consultant, distributor, marketing, Phil Morettini, PJM Consulting, SaaS, sales, software, VAR

Are There Any Software Segments The Cloud Won’t Swallow?

It’s become pretty clear in the last couple of years that we are heading irrevocably toward a cloud-dominated future in the software business. The evidence is irrefutable. To attempt to get a traditionally licensed PC or enterprise software business funded by an institutional investor would be a suicide mission these days.

Whether it’s SaaS, PaaS, IaaS, Cloud-based, web-based, Internet-based—WHATEVER, it’s all still basically the same thing. Some folks get very snippy about all the different definitions, but they are all just different segments or interpretations of the same model: Software hosted outside of the customer’s premises and available via an Internet browser. Although the technology has improved dramatically over time, it’s really the same basic idea as ASP (application service provider) model from back before the Internet stock bubble burst.

In many cases this trend is happening for good reasons, with the primary one being the simplicity the model offers end-users. But like anything, it’s not the perfect fit in all instances. For example, I’m still not convinced this model will ever be definitely cheaper than solutions that rely more on local computing power. For that to happen, I think we’re going to need to go back to the era of much cheaper dumb terminals to replace our powerful PCs. Having all that desktop power and storage (and the associated costs) sitting on your desks unused is pretty inefficient.

In addition, I also don’t believe SaaS and other cloud-based variants are necessarily the most profitable business models for every software vendor, even though institutional investors love it. I recently had a conversation with a venture capitalist and I asked him why the VC community was so in love with software in the cloud, specifically SaaS-based models. After some discussion about the various elements of SaaS and customer premise-based software models, it really came down to something simple: traditionally licensed software companies are valued at 1-3X revenue and SaaS-based companies are valued at 5-6X revenues. Of course, it’s all about the money and this makes perfect sense. But will this valuation gap be sustainable, or is it a market inefficiency that will go away over time? But I digress, that’s a topic for a different debate….

There are some very good (and maybe not so good) reasons that certain segments won’t come completely under the spell of cloud-based computing. Let’s take a look at a few areas where I forecast the cloud won’t become dominant:

Banking

This is one of the toughest software market segments there is. Banks are notoriously difficult to penetrate, and security is paramount. I believe this will be one of the toughest segments for cloud-based solutions to penetrate, and will be even harder to dominate. Certainly they’ll be a lot of cloud-based applications in non-critical functions. But anything that gets at the core banking functions, including customer data or money will be kept private. That might be a traditional on-premises solutions or private cloud-based apps, but anything sensitive from a security viewpoint will be held tight.

Government

I believe this will be a similar situation here to the Banking market. Certainly the Cloud has already penetrated many areas of the government, and will continue to do so. But there are larges segments of government services where the data is just too sensitive. We’ve seen a lot of embarrassing breaches lately with respect to intelligence data that absolutely needs to remain secret. I think we’ll see a pullback from this data being available via the Internet, rather than moving deeper in that direction.

Open Source and Mobile

Outside of the cloud, these are the two software segments that institutional investors will still put money into. It’s true that many mobile applications have a cloud-based back-end, and a lot of Open Source platforms are used to generate cloud-based apps. But both of these areas represent code that will sit on customer-controlled assets and will slow the adoption of a centralized model where all computing is done in the publicly-accessible cloud.

Buyers vs. Renters

Some folks just like to own stuff. While the rental model works for many due to the reduction in software and hardware investment, which saves capital for other purposes, others feel that renting is wasteful. Indeed, SaaS and other lease/rental-oriented models aren’t necessarily the cheapest in the long run. This is really a psychographic attribute that isn’t likely to change among those so-inclined.

100% Service Levels required

The Internet is a long way from the old AT&T Ma Bell monopoly when it comes to service levels. Have you ever had the power go out at a company you work at? In this day and age, when that happens, everything immediately stops. With the every-increasing reliance on Internet-based technologies (and being accelerated by cloud-based apps), the Internet connection going down can have roughly the same effect. The Amazon EC2 Cloud Services outage in April 2011 gives a sneak preview of what can happen to productivity levels if service levels are compromised on a wide scale or for a long period of time.

Security Conscious (and the Paranoid)

There are many out there among us that have their own safes rather than using a Bank’s safe-deposit box, or are building safes rooms or bomb shelters to protect against perceived threats they view as inevitable. Many others are simply very cautious and prudent, and that means holding things close to the vest and not embracing the newest technologies until they are viewed as bulletproof. The profiles vary from the prudent to the paranoid, but the common thread will be slow or no adoption of technologies that are viewed as giving up control of something important.

As we embrace cloud-based applications at an extremely fast rate, my own feeling is that we are headed toward a major, high-profile event that will slow adoption considerably. I’m not sure what form that will take, but it could easily be a major data security breach that causes real damage to a lot of people, or an Internet-based outage that brings a bunch of businesses to their knees. There are many examples already which support that these types of events are quite possible. Several times a year now I get a notice that my private data has been compromised by one vendor or another. The Amazon EC2 outage discussed above already gave a number of people pause about being held captive by this model.

So that’s my take on some areas we’ll see little (or at least slow) adoption of public cloud-based software models. Do you see other areas I left out? I’m sure this will be a bit controversial as well—some out there disagree and believe the Cloud will take over the world. I’d like to hear from all of you, regardless of your view. Post a comment to add to the debate.

Follow Phil Morettini and Morettini on Management via Twitter, Facebook, LinkedIn, RSS, or the PJM Consulting Quarterly Newsletter. Contact Phil directly at info@pjmconsult.com

5 Comments by admin on May 29, 2012

filed in B2C, Business Models, Corporate Strategy, General Management, Operations, SaaS, Software/Product Development, enterprise software

Starting and Growing a Software Company in a Difficult Fundraising Environment

Some would say that it’s ALWAYS a difficult time to raise funds for a startup company. In general, I’d agree. With the exception of a few brief moments, such as pre-Internet Bubble in the late 90’s where money was being thrown around like air, fundraising is hard. There are a few lucky folks that don’t sweat this startup task, like repeat entrepreneurs who hit it big the first time, or those with truly obvious ground-breaking IP. But for most it’s a grueling and soul-sucking necessity.

Today fundraising for a startup company is tougher than every. The Venture Capital (VC) business is in disarray, with the number of active firms in the process of shrinking. The financial crisis and general economic malaise has made finding capital from nearly every source more difficult, from traditional banks to angel investors. So if you’re planning on starting a company today, it might be time to get creative.

Most of the ideas presented here are applicable to any type of company. But for those smart about it, a software-based business is one that can be started and grown with minimal, or zero, outside capital. This has always been true in the software business, but a number of developments have made bootstrapping even a more realistic possibility today. You will need to accept upfront that it can be done, and structure everything you do with minimal financial resources in mind.

Successfully bootstrapping is tough if you’re a first time entrepreneur, especially for those that have been working in large companies, with all the trapping that come with that. But embracing the proper attitude early on is essential if you’re going to have to bootstrap your company, at least in the beginning. Let’s examine some tactics that can increase the odds of startup success:

Understand early-on the level of capital you’ll have available

This is crucial. Most get going on their business, moving ahead and worrying about funding once they have a business plan, prototype/beta, etc. Only then do they put together an investor pitch and think about how much money to raise. But it can be really helpful to have a realistic view as early as possible how much money will be available to you in the early days. No question this is hard to do and by definition the result will be inaccurate. In reality, a number of things will dictate how much money you’ll have available: Management team reputation and track record, investment contacts, dilution philosophy, local investment resources, business model, IP, etc. The key point here is to do your best to understand how much money you’ll realistically have available at startup and early on….

Structure your business accordingly

….then design your business model to fit your prospective available funding. In reality, this rarely happens. Most design their business, and then try to raise money to fund it. As a result, for example, I see people start enterprise software companies, with complex products at high price points that demand a team of outside sales reps and field engineers with $150-250K comp plans. Most startups won’t be able to attract the funding to support this sales model. Or adopting a Software-as-a-Service (SaaS) approach, without planning for the added operational expenses required with a SaaS model, essentially taking on the role your clients IT department. If you can match your business model to your expected capital resources from the beginning, your chances of success go way up.

Start while you’re still working

One of the best things a startup entrepreneur can do is to start working on your business while you still have a job. This is especially true of the technically-skilled software company founder. Many software companies have been started by a sole programmer, writing the initial product on his or her laptop while sitting at home in the kitchen. It’s one of the beauties of the software business; you can create a product with very little capital investment. Of course, care needs to be taken that you don’t use any of your employer’s resources or do anything on company time. Make sure that you aren’t violating any of agreements signed with your employer. But once you stop working to start up a new venture there’s no telling when your personal income will start flowing again. So do as much as you can, before cutting the cord with your steady income.

Do it yourself and don’t be wasteful

Entrepreneurs often find that they can actually do things they never dreamed they could. When dealing with scarce capital, it’s critical to make sure that you actually NEED to pay someone else to accomplish a particular task before parting with your cash. This will lead to personally doing a lot of mundane activities that you don’t really want to do. But it’s important to take those duties on early on to conserve cash. Also try not to waste money on ANYTHING, not just labor. Count those paperclips! The corollary to this is when you really do need outside help, DON’T SKIMP and just do an unacceptable job internally. Bad marketing is an example of this for the technically-oriented founder. This can be truly penny wise and pound foolish, and can cost you much more money in the long run than you save in the short term. Recognize what skills you just don’t have that are absolutely critical to the business, and save money elsewhere so you can afford outside assistance in those crucial areas.

Don’t reinvent the wheel

I referred earlier to it being easier than ever to build a software company with minimal capital. Development tools have matured to make development quicker than ever. Many target platforms have much less memory constraints, reducing the time needed to produce code that is extremely memory-efficient. There are many pre-built modules for standard functions available for a modest cost. Ten years ago it might have taken a half million dollars to build a quality website that you now can replicate for a few thousand dollars. As a software startup, make sure that you scour all pre-existing resources for things that you can use, before you build them yourself.

Outsource and off-shore, if appropriate

Another area responsible for much lower costs in starting a software business is the potential for outsourcing/offshoring. This isn’t for every company or every situation, but where it makes sense, it can both reduce your costs significantly and expand the availability of critical development resources. While everyone would prefer the developers under their own roof, in many cases there just isn’t the right talent where the company is located–or the budget to fully staff with full-time, onsite employees.

Don’t ignore international markets

A big area which most software companies ignore initially for their products is international sales. It’s natural to want to focus on your domestic market first. But doing this exclusively can cost you some excellent growth opportunities, even from the very beginning. This is particularly true for US-based companies. The US is the toughest market in the world. It’s the biggest, and the bulk of the software industry is located there (all looking at the US market first….). As a result, the competition is almost always less in non-US markets. So there is low hanging fruit to be had, plus you can partner in many markets with distribution partners whom have existing market presence, and can take on much of the marketing investment required to gain traction. All of this can mean an excellent return on a modest investment. Once you’ve invested so much to create valuable product IP (which is very “perishable”, by the way), don’t limit your return on that investment by focusing on a narrow geography, if at all possible.

Don’t give up and enjoy the journey

Don’t ever give up prematurely. The most important thing is to keep grinding until you start to gain traction. Starting up and growing a software company is an exciting–and difficult–endeavor. Above all, I believe you need to be able to enjoy the journey, in addition to having your eye on the end prize–success. There will be difficult times where you need the willpower and stubbornness to push through. Often startup success is found by staying alive long enough for good fortune to find you.

That’s my advice on starting up a software company and growing it in relatively tough times. Post a comment if you have your own experiences to add.

Follow Phil Morettini and Morettini on Management via Twitter, Facebook, LinkedIn, RSS, or the PJM Consulting Quarterly Newsletter. Contact Phil directly at info@pjmconsult.com

3 Comments by admin on August 8, 2010

filed in Business Models, Corporate Strategy, General Management, Startup/Early Stage, enterprise software

tagged business model, early stage, growth, management, Product Development, SaaS, software, startup, strategy, VC

Selling SaaS through the VAR Channel

The move toward Software-as-a-Service (SaaS) is the strongest trend in the software business in recent memory. It changes the software business model in a number of fundamental ways. For the purposes of this article, I’m assuming the reader has a basic understanding of the SaaS business model. I’m also going to assume a basic understand of what a Value Added Reseller (VAR) is and does. I’ll focus on the fit between SaaS and the VAR distribution channel.

The VAR channel has been a major factor in the B2B software business for a long time. There are tens of thousands of VARs, most of them now focused on specific vertical markets. While it is still possible to find a horizontal VAR, in a market of any size you’ll likely find a nice number of VARs specializing on that segment of customers. As a result, anyone who is selling software (whether via traditional licensing or SaaS) would love to have this stable of key market influencers representing their product. Let’s take a look at the situation:

Major SaaS strengths

Simplicity of startup for the customer – For many SaaS apps, getting started is as simple as signing up, obtaining a user name and password. Contrast this with the lengthy, complex and sometimes extensive setup and configuration period for some B2B apps. (This strength is a potential problem for VARs).
Available from any web browser - This is one of the great capabilities driving the SaaS revolution. Of course, traditional apps can have a web-based interface as well, but SaaS apps by definition are web-centric. Browser-based apps can limit functionality in some cases, but is becoming less of an issue all the time.
Simplicity of maintenance for the vendor - This is a big one. With traditional on-premises apps, the vendor has to deal with “pushing” updates to the client, often into wildly varying hardware and software environments. With SaaS, the vendor presses a button and the new version is universally available to everyone. This is a huge advantage leading to reduced rollout costs for the vendor, and less pain for the client. (Also a potential problem for VARs)
Less IT infrastructure required by clients - Theoretically a company could nearly eliminate their IT department by adopting all SaaS apps. As a practical matter, this isn’t happening in companies of any size, and likely won’t. But any reduction in reliance on perennially overworked IT departments is usually seen as a good thing. (Potential problem for VARs, but also an opportunity)

Major VAR motivations

Sell Services (not products) – Contrary to the expectations of channel neophytes, VARs are generally seriously interested in products to the extent that they have the ability to generate service revenue for the VAR. (Early SaaS models eliminate many traditional service revenue streams)

Secure ongoing revenue – VARs don’t own intellectual property(products) to stabilize long-term revenues as a rule, so they’re always interested in ways of “smoothing out” their business with predictable, ongoing revenue streams. (SaaS eliminates much traditional service revenue, but subscriptions open up new possibilities)

Maintain client control – VARs are very sensitive about retaining control of the relationship with their clients. They view these relationships as hard-won, and without owning the intellectual property, they are probably the most strategic aspect of their business. (VARs shy away from vendors who try to wrest account control from them, and many new SaaS vendors have this “direct-first” mentality).

The Gap

The problem as discussed in the above paragraphs is that the ways VARs traditionally make money (installation, training, integration, customization, support, client control) have been eliminated or severely reduced as opportunities by first generation SaaS vendors. Frankly, it’s never been easy for any software vendor to recruit VARs who are “active” with their products. The current situation sets up the typical first generation SaaS vendor as an arch- enemy to VARs. The SaaS vendors aren’t attractive partners due to the lack of potential service revenue (and often aren’t looking to partner), but are targeting the VAR’s customer base. To some, it looks like the end of the VAR channel for anyone running a SaaS-based company. Sound like a caution sign to SaaS vendors, one which makes the vendor focus strictly on direct selling? Maybe–but let’s explore a few ideas for changing the equation.

Ideas on how to bridge the gap and attract VARs to your SaaS offering

There are some forward-thinking SaaS who have been able to leverage the VAR channel for their companies. But at this point, they are few and far between. For many of the reasons stated in the above paragraphs, there is no established, tried and true model for attracting VARs to a SaaS offering today.

The biggest thing I’d like you to consider with respect to the sentence underlined above, is that when things are least established, there is the MOST opportunity for newcomers. Since there is no established perfect SaaS/VAR cooperative business model yet, no SaaS player is dominating in this still very influential channel. For a newcomer, this creates great opportunity and potential payback for creative approaches. Let’s take a look at a few such ideas to attract VARs:

Design your SaaS offering from the ground up for easy customization and integration

Unfortunately I don’t see many SaaS vendors considering channel strategy when designing their first product. In the early days of SaaS, enabling customization and integration with other products was tough to do. Now the tools are there to make it very possible, but it’s a lot harder if you try to do it “after the fact”, once your architecture has been set and the first commercial release is done. This one step can be a huge asset when you are later trying to design programs attractive to VARs, and it can of course be a huge advantage with certain end users as well.

Offer solid upfront margins, but focus on downstream revenue streams for your VARs

I recommend offering competitive upfront-sale margins, but going overboard here can be a waste of resources. Remember that VARs don’t build their business on upfront product sales revenue. Focus on finding ways VARs can make money dealing with you after the initial sale is complete. As an example, how about sharing downstream subscription revenue–but only if the VAR creates X amount of new sales revenue for the year? This is an example of a win/win which could lead to great loyalty to your offerings, tying the VAR’s interest to your business in the long run.

Instead of building a large in-house consulting team, use VARs to help fill IT gaps for your customers

VARs have a lot of capability to offer services that your end users might require and demand. Rather than competing with VARs (and using scarce capital that could be deployed elsewhere), take a look at creating programs to utilize the best of your channel partners as your outsourced consulting team.

Create a program to enable the outsourcing of upfront product training to your VARs

Initial product training is a great example of a “consulting service” to outsource to your channel. Most product groups see training as a necessary evil and an afterthought, often giving it away for free–while providing it with insufficient attention from the end user’s perspective. With the right tools, a VAR could turn this into a profit center for their business, reducing your utilization of key resources on a non-core activity, while tying the VAR tightly to your products.

Be careful to allow your VARs to continue to lead in account management activities

In everything you do, keep in mind that the VAR is paranoid about account control (with good reason, unfortunately). Remember, you are in a business partnership with the VAR, and you need to trust them to do the right things for your joint business interests in the account. If you don’t feel like you can trust a particular VAR in this regard, don’t change your program to wrest account control from your channel. Stop doing business with that VAR.

I’m optimistic that adopting a few of these ideas can give you a leg up over the competition in building a productive channel business. I hope that you’ll find this article provocative, if not accurate in your view! This is an emerging, rapidly changing environment. Please post a comment with your own thoughts to expand the discussion.

Follow Phil Morettini and Morettini on Management via Twitter, Facebook, LinkedIn, RSS, or the PJM Consulting Quarterly Newsletter. Contact Phil directly at info@pjmconsult.com

2 Comments by admin on July 18, 2010

filed in Business Models, Corporate Strategy, Distribution Channels, Product Marketing/Management, SaaS, VARs, enterprise software

tagged business model, channel marketing, channel sales, conflict, direct sales, distribution, enterprise software, marketing, online, product marketing, SaaS, software, Software as a Service, software developer, traditional software license, VAR

Will SaaS Lead to the Death of Software Product Management?

There is a lot of talk in the software business these days about changing business models, particularly the trend toward SaaS (Software as a Service).

Will SaaS business models dominate the software business?

Many consultants, pundits and other industry figures are proclaiming that SaaS will very soon take over the world; saying if you’re not on the bus soon, you’re going to be out of business. I believe this is a bit overstated, but the strong trend toward the SaaS business model can’t be denied.

My opinion on SaaS adoption: When bandwidth is unlimited and close to free, all IT systems are totally secure, the Internet is as reliable as old AT&T; and every customer in the world decides they want to rent everything and own nothing–then I’ll agree that SaaS is heading toward 100% market share. As I said above there’s a strong trend in this direction, but we’re a long way from there.

Is software product management dead?

I’ve written about SaaS a number of times before, and since it has become very important in the software business I’ll continue to do so frequently. What I want to address today is another opinion some “experts” are also espousing: that the trend toward SaaS means the end of the Product Management function in the software business.

I find this statement to be downright silly.

When following this debate, it’s important to take notice that many of the folks proselytizing these opinions have businesses whose success is based upon these predictions actually coming true. It’s always important to consider conflicts of interest among the debaters.

In one recent webinar they trotted out a SaaS software company that was growing briskly every year with no product managers in the company. What wasn’t said is that it was always possible to find software companies (of the traditional sort) who didn’t have a product management function. Software companies are often founded by programmers, and they haven’t always seen the need for Product Management. There are very successful companies where the developers talk directly to the customers, with no product managers at all. However, the facts are that a very small percentage of companies that do business this way are successful, and its usually based upon special circumstances: the rare developer who understands markets and customers as well as he does coding, markets where the developers themselves are perfect customer proxies, etc.

So while software companies without Product Managers have always been out there, it just hasn’t been a broad formula for success. Trotting out one SaaS company successfully doing business this way (incidentally, I saw some big holes in their model long-term) doesn’t impress me much.

I’m not defending the status quo–I’ll say it once again, there is a huge move to SaaS in the software biz. Many (and maybe most) will be doing business this way in the near future. However, like most over-hyped trends, this are some pretty big overstatements being thrown around.

SKILLED product management will always be important

The argument being made is that many of the functions Product Managers currently perform are obsolete under the SaaS model. With continuous development more practical using SaaS, there may be fewer (or no) new version introductions. So the old waterfall chart with MRDs being created for the new version may go away along with new product introductions. I’m sure you get the picture. SaaS is a pretty fundamental change to the software business model, so you wouldn’t expect a product manager’s job to be stagnant under such change.

But those predicting the death of product management are focusing on the more mundane aspects of Product Management. The essence of this critical function is the ability to understand markets and match widespread, aggregate customer needs to the technical skills and IP of your company–creating a PRODUCT which can be sold to these many people. It doesn’t matter whether you deliver this PRODUCT over the Internet in a hosted manner using monthly subscriptions, or in the more traditional on-customer premises, licensed model. Product Management is about creating a profitable PRODUCT well-matched for a market segment. It matters not whether you are engaged in customer facing marketing/promotional activities, or upfront product planning–the product manager’s understanding of market needs and how your company can fulfill those needs is crucial in a product business. Otherwise, you’re just selling custom software–one-off’s for every customer. That’s a different business–not a bad one–and one you which doesn’t require product managers.

Can Social Media replace Product Management?

Another thing being bandied about by my favorite pundits is the impact of communities and other social media for its potential impact on product development. The thinking goes that there will be much more direct interaction with the end customer, leading to tremendous amounts of data available to ISVs. While SaaS is very well suited to communities (although not exclusive–they can be well utilized by traditional licensed software vendors), the ability to more easily obtain direct customer comments, and maybe take votes on potential new features doesn’t eliminate the need for product management. To the contrary. While communities and other forms of social media are very powerful tools, don’t mistake more data and customer access with actionable market intelligence. Data needs to be interpreted, and skilled marketers are best positioned to discern who’s telling you what and why–the underlying motivations behind any customer feedback. So all of this added customer access and resulting data will only put a premium on good product management, to use these powerful new tools and data for quicker action and to allow better product planning decisions. Remember, SaaS competitor down the road will have access to the same tools and data that you do.

It is rare to find a developer who has truly exceptional product management skills. That’s not a knock on developers; as a whole they are an extremely sharp bunch. But specialization in life happens for a reason–very seldom is someone the best at everything. Developers are trained to write code and build applications, not understand markets or extract the “truth” from customers. Different types of people’s brain’s work differently, and a good developer and good product manager are an example of this.

I find that it’s when a talented, open-minded development manager teams with a market-savvy product manager, that most great software applications are made. So no, I don’t believe that the Product Management function is going away anytime soon in the software business. There are many important changes going on in the business, the SaaS business model not the least of these. With any change in business model, functional roles will evolve and change. But I believe strongly that Product Management is a fundamental, important role that will remain critical in software businesses far into the future.

That’s what I think about SaaS and product management–what do you think? Post a comment to start the discussion! Follow Phil Morettini and Morettini on Management via Twitter, Facebook, RSS, or the PJM Consulting Quarterly Newsletter.

3 Comments by admin on October 12, 2009

filed in Corporate Strategy, Product Marketing/Management, SaaS, Social media, Software/Product Development

tagged community, consumer software, IP, ISV, market intelligence, marketing, MRD, Product Development, product management, product manager, SaaS, Social media, software, Software as a Service, Web 2.0

Cloud Computing, SaaS and Such–Have We Read This Story Before?

I have this incredible feeling of déjà vu.

Cloud computing and Software as a Service is all the rage. In my practice at PJM Consulting, I am very involved in software startup activity. Nearly every new software company that I see today is being built on the Software as a Service business model. It’s all the rage–so much so that it appears that any self-respecting software entrepreneur would be embarrassed to start a company using the traditional software licensing model. Even if an entrepreneur was so inclined, good luck finding a VC who would even consider funding such a company. No one wants to look like a dinosaur.

It’s all well and good–there is definitely a real trend toward SaaS and Cloud Computing, with many good reasons for it. But most high technology trends are initially a bit over-hyped, and tend to get ahead of themselves. In addition, this particular story seems ever so familiar to a tech veteran that’s been around for a few of these cycles.

The first bit of history this reminds me of is the old terminal/mainframe model from the early years of computing. There were some real advantages to this model, but also some big disadvantages as well–which opened the door for the golden age of PCs and networking.

The second era that the current SaaS wave reminds me of is “Web 1.0″, when Web-based hosted software (then called ASP rather than the modern SaaS terminology), was first going to take over the world. The current trend seems so very similar because it was around the Web 1.0 years of the late 90s/early 2000 when the traditional software license business model was first proclaimed dead. At that time nearly every new business plan was based upon an ASP model.

So some of this fast-moving Cloud Computing or SaaS trend is new–but much of it could be viewed as recycled from past trends. Let’s look at the Pros and Cons of this computing model:

ADVANTAGES

* Enables “Utility-Style” computing – variable expense instead of. capital investment
* Allows an end run around overwhelmed IT departments (like PC networking did)
* Supposedly “On-demand”–use only what you need, when you need it
* More efficient use of compute resources by time-slicing large farms of cost-efficient computing resources
* Web-based allows anywhere, anytime availability
* Off-site storage of data assists disaster recovery preparedness

DISADVANTAGES

* Immature and inherently more difficult Security
* More difficult integration with other applications
* Internet latency
* Internet reliability
* Data resides outside the company firewall
* Costs over time aren’t necessarily lower for customers
* Lower margins for software vendors–aren’t always accounted for in current pricing

SUMMARY

I believe that the trend toward computing in the cloud will continue, but there will be some stumbles and pullbacks along the way. Cloud Computing and SaaS has some inherent strengths–but also some under-publicized weaknesses. Many software vendors are overlooking the weaknesses at this time, as is typical of any new and hyped technology. Traditional licensed software hosted by the user still has its strengths and a definite place in the market. Like many mature technologies and business models, the death of traditional software licensing has been greatly exaggerated. Once the early hype passes, decisions on whether to computer within the firewall or in the cloud will once again be made on the individual merits, costs and user needs for a particular application within a particular company. That’s how I see it–post a comment with your opinion so we can look at all viewpoints.

Phil Morettini
PJM Consulting
http://www.pjmconsult.com/

9 Comments by admin on May 4, 2009

filed in Corporate Strategy, General Management, Operations, SaaS, Software/Product Development, enterprise software

tagged ASP, Cloud Computing, firewall, internet, IT, Licensing, mainframe, SaaS, software, terminal, traditional software license, Utility Computing, Web 1.0

Inside TeleSales versus Outside Sales in Software and High Tech Companies

There are many ways to deliver your software and technology products to the market. For example, one and two step distribution through third party channels, direct marketing/sales over the Internet, OEM relationships and many variations of these, as well as many other methods.

One classic method of delivering products to the marketplace is by using a direct sales force. Within the direct sales methodology, two of the most popular variations are an outside sales force and an inside telesales group.

Inside sales forces utilizing telesales are cheaper per rep, so your cost of sales is reduced, and you can potentially afford more reps. Outside sales forces can provide additional credibility and stronger relationship with the account. How do you choose between the two methods? Does it sometimes make sense to use both? Let’s take a look at some of the key aspects to consider when making this decision:

PRODUCT COMPLEXITY AND LENGTH OF SALES CYCLE
Probably the most important consideration in this discussion is the complexity of your product offerings, and the corresponding typical length of your sales cycle. Simple products –particularly traditionally licensed software or SaaS– with shorter sales cycles obviously lend themselves to the less expensive telesales approach. If you have a complex product that requires more in the way of hands-on demos, application engineering and other high-touch sales support, an outside sales force may be warranted.

BRAND STRENGTH AND STAGE OF COMPANY LIFECYCLE
Another important factor is the position of your company in the marketplace. Take an example of two companies selling the same product to the same market. The newer company with less market presence and a weaker brand may require an outside sales force to maximize its market penetration. The more established brand and company might be able to get by with a lower cost inside telesales approach in similar circumstances.

PRODUCT PRICING
Product price is another important element in this discussion. All things being equal, higher priced products are more likely to require outside sales, while more modestly priced ones may be able to be sold effectively with only an inside sales force. The higher the price the more “high touch” your sales approach will most likely need to be, especially after you get past departmentally approvable price points and into enterprise-level committee selling. Low price products, unless sold in high volumes, may just not profitably support the use of an outside sales organization.

TARGET CUSTOMER PROFILE
Is the target company large or small, is the prospect themselves young or old, progressive or traditional? It’s important to understand your customer profile and buying style in deciding how best it will be to sell to them. This course is often decided on a case-by-case basis for individual customers. But in making this decision on how to structure your direct sales force, it’s important to characterize your target market in aggregate. For example, if the bulk of your target market is older, traditional companies and you are trying to sell to their IT departments, you’d shouldstrongly consider building an outside sales force. Many of these customers come from the old “Glass House” era that was dominated by IBM, and are used to having sales people physically call on them. On the other hand, your prime prospects may be in a newer, SMB market segment that has prospects who are more comfortable with remote communications methods. These folks also have less staff and less corresponding time to meet with outside reps. These targets may be well-served by a competent inside sales force.

HYBRID SALES STRUCTURE
In some cases a mix of inside telesales and outside reps works best. Here is an example of when this might be optimal:

A product with a low sales price that lends itself to an inside sales force, but the product is something that major accounts can use in great quantities, justifying an outside sales force to call specifically on these accounts.

COMPANY CAPITALIZATION
How much money does the company have? Sometimes, there just isn’t enough capital to initially invest in an outside sales force, even if the situation ideally calls for it. In these cases, it makes sense to start with an inside sales force, and do the best you can–supporting with as much outbound marketing as you can muster. There are many ways to compensate in this situation, even if it’s not ideal. We’ll cover the details of this scenario in another article. Suffice it to say that it’s preferable to get by with a sales structure that may not be optimal, rather than bankrupt the company with an outside sales force that it can’t yet afford. I’ve seen this occur more than once in my consulting practice at PJM Consulting.

SUMMARY
Like any other key structural decision that senior management faces in developing a software or hardware company, it’s important to carefully consider the details of your particular circumstances. Many times managers will quickly settle on replicating what they know and are comfortable with from their past experience, or simply attempt to copy what the market leader does. Both of these approaches leave you vulnerable to a potential critical strategic mistake. Be thoughtful upfront in your approach to how to structure your direct sales force, and you are likely to be rewarded with optimal push in your chosen market segment.

Follow Phil Morettini and Morettini on Management via Twitter, Facebook, LinkedIn, RSS, or the PJM Consulting Quarterly Newsletter. Contact Phil directly at info@pjmconsult.com

No Comments by admin on February 5, 2009

filed in Business Models, Corporate Strategy, Startup/Early Stage, sales

Morettini on Management

General Management and Marketing Advice for Software and Tech Companies

Pros and Cons of the Freemium Software Business Model

Software Product Marketing: Horizontal vs. Vertical

Selling and Marketing Software Through the VAR Channel: Morettini on Management Video Series

Starting and Growing a Software Company in a Difficult Fundraising Environment

Selling SaaS through the VAR Channel

Inside TeleSales versus Outside Sales in Software and High Tech Companies

Links

Search Blog Articles

Topic Categories

Recent Article Comments

Article Archives