Morettini on Management

General Management and Marketing Advice for Software and Tech Companies

Tag: traditional software license

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

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/