Morettini on Management

General Management and Marketing Advice for Software and Tech Companies

Tag: traditionally licensed

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

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