Morettini on Management

General Management and Marketing Advice for Software and Tech Companies

Category: VARs

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

A Software Startup Video Case Study

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

Starting Software Product Businesses Within Service Companies

The focus of my consulting practice is on commercial software product businesses, whether traditionally licensed, mobile, open source, SaaS–or some combination of all. While many software product businesses are originally organized with that purpose in mind, a remarkably large number of others started in another business. Let’s take a look at a few service-oriented scenarios which tend to grow into or spin off software product businesses:

Software (consulting) services

It’s very common for a product to be developed out of a software services company, which can mean a range of services such as consulting or outsourcing. These companies are being asked to design/create full applications, either for internal use by end user customers or as actual commercial software products. As a result, these service companies are in good position to recognize software product opportunities; sometimes these products are created by a funded service contract (if the service company is savvy enough to retain code rights!).

Government contracting

This is a very similar situation to the Software Services example above, with a couple of important differences. Government contractors are often not pure software development organizations; they may create hardware or provide other services as their government customers dictate. So they may not have a culture which emphasizes software development. Even more importantly, it can be tricky to retain rights to code developed with government funding–contracting expertise and an upfront emphasis on rights retention are critical in these circumstances.

Hardware/Systems

Another common scenario is software developed within a hardware or systems-oriented company. While not strictly fitting into the service category, I’ve included this example because it’s another common way software product companies are started that doesn’t fit the traditional methodology. The fact is that even in hardware companies these days, most of the innovation and IP is software-based. So it’s not at all unusual to see software developed as part of a systems approach that is later seen as having a market as a standalone application, apart from the hardware. Many successful software companies have started as spin-offs from hardware or systems-oriented companies.

VARs

Here’s another slightly different flavor of the Software Consulting Services example we began with. VARs are solutions providers for end user customers and are frequently asked to extend existing applications which are lacking in some way, integrate these solutions with other applications, or even write a standalone custom application. They are therefore well-positioned to get an early view of (and sometimes a customer-funded head-start developing) products needed to satisfy unfilled end users needs.

End user

End users often have in-house development capabilities and develop their own applications. In this case, the “service” organization is the internal IT department. These applications are often developed because of a “hole” in the existing commercial product offerings available in the marketplace. Forward thinking organizations may further develop and then spin-off these internal applications into commercial products.

So that’s a look at how organizations which aren’t-software product-oriented end up with a software product business. It can be a really great way for a software business to start–but there are many things that can prevent the successful transition into a going concern software product business. Here’s a list of a few:

Issues Which Can Prevent Success:

Culture

This is a frequent culprit in the failure of product businesses which are developed in the various service environments as discussed above. Depending upon the parent’s business, a mismatch in culture can come from a lack of understanding of either the software or product aspects of the resulting new business. For example, the management team of and “end-user” company that has developed a product may not be sufficiently software-savvy to make the right decisions to put the new business on a solid footing. A business executive in a software services company may not understand what it takes to develop a product to commercial product standards, or successfully market it. One of the biggest mismatches in culture often occurs within a government contractor. The “common business sense” required to be successful in the contracting business is shockingly different than that of a commercial software product business. The cultures are nearly polar opposites–It’s like English vs. French.

Capitalization

Often the cultural differences listed above or low overall capitalization of the parent company leads to the most common problem of these software product spin-offs: lack of proper initial capitalization. One of the attractive aspects of the software business is that it requires much less investment capital that a manufactured goods business–but it’s still a product business. Product businesses require more capital than service businesses. So even if you’ve created a great mousetrap, if you don’t have the money required to continue to develop it as well as market it–at least until you’re cash-flow positive–failure is quite likely.

Not productized

Maybe the most common problem of all is the lack of “productization” of the software application prior to launch as a commercial product. The level of usability, functionality and reliability required in the commercial product marketplace far exceeds the standards of the custom software application market. When you are supporting a single company directly with a custom app, you can afford a level of support which can overcome minor deficiencies in the areas listed. Once rolled out to a mass market of users in the software product marketplace, these deficiencies can kill a promising new product very quickly.

Me-too Products

One of the areas of expertise lacking in a service-oriented company (almost by definition) is Product Marketing/Management/Planning. The lack of this functional expertise can lead to a number of mistakes. One of the elementary mistakes that I see surprisingly often is not ensuring that you are making a novel “contribution to the market”. A software product startup with the 19th product to enter an existing market, with no discernable competitive advantage, is a great way to lose money.

Lack of software product industry experience

If you add up the potential mistakes listed above, most of them can be mitigated by the addition of software-product company operating experience. Sadly, in many instances the parent service company senior management is too proud or simply ignorant and unable to acknowledge this weakness. This potential weakness can be alleviated by hiring an experienced operating executive, or retaining a software product industry management consultant such as PJM Consulting.

The bottom line to all of this is that there are alternatives to the more conventional approaches of creating a traditional investor-funded or founder-bootstrapped software product company. Whether created intentionally from the beginning or a “happy accident”, companies started this way can provide an advantage of significantly reduced capital-requirement-to-profitability compared to traditional startup methods. But there are potholes and roadblocks that must be avoided to prevent crib death of embryonic software startups born this way.

So that’s some of the lessons I’ve learned with regards to creating product businesses from service companies. Is this something you’ve done or witnessed others attempt?–what were your results? Pitch in with your two cents — post a comment 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

Creating a Distribution Channel Where One Doesn’t Exist

One of the least well understood activities in growing a hardware or software business is the building of distribution channels. This looks very easy to the uninitiated, but in reality it’s extremely difficult. There are many subtleties that are far from obvious, and some aspects that are necessary for success are downright counter-intuitive. Building a distribution channel for your company is difficult in the best of circumstances.

How hard is it when there are no current, obvious existing channel partners already selling your category of products to start with?

It’s very hard. In fact, most people in the know would likely tell you to forget about it, and not even try. That might actually be pretty good advice, because this activity could easily become a real time and money sink if you’re not careful.

But the other side of the coin is that this might be the circumstance where building a channel carries the very highest potential payoff. One of the great truths I’ve discovered in my career is that the most effective marketing and sales strategies are the ones that haven’t yet become mainstream in your marketplace. Once a strategy or tactic becomes very popular, the results become watered down until at some point it’s marginally attractive at best. In terms of strategy, this move fits in the “high risk, high reward” category. But the payback, if successful, is extremely high.

In terms of strategy, creating your own channel definitely fits in the “high risk, high reward” category. Because while it’s very difficult, if successful, you alone among all competitors in your segment will have the leverage and resulting strategic advantage that a well-executed channel strategy can provide.

So the question is how do you go about this? Where do you even start if there are no existing channel partners for your category? Let’s take a look at a few places to mine that I’ve found some success in the past:

Adjancent Markets

This is the most fertile place to begin, imo. The first step is to think strategically about what type of software application or hardware product is complementary to yours. Whose product might it make sense to integrate with your own, for example? These types of potential strategic partners might also have existing channel partners that might be interested in selling your product as a companion product. An example scenario that I recently successfully implemented for a client was an analytics software company that uses a lot of data to help forecast and mitigate decision risk. We were able to attract a number of channel partners in two adjacent categories: Business Intelligence (BI) and Project Management. Both of these categories are large, with good-sized existing channels selling their solutions. BI creates a lot of date which could be used by my client’s software for forward-looking action, and the Project Management category involves a lot of complex decision-making and risk mitigation which was a natural fit for my client’s software.

Private Label/OEM products

Potential OEMs are another great place to look for channel partners. One obvious possibility is hardware OEMs for a software company, where the software might be integrated with the hardware for a full solution. If the hardware OEM has a channel, Voilà! you have a channel. Even if the hardware company isn’t interested in an OEM relationship, you might be able to entice them into a more vanilla reseller relationship with light or no integration. Lastly, you can always approach their channel directly to sell you software as an add-on product to the hardware vendor’s.

Former Employees

The first two categories above are pretty fertile with respect to creating a channel from scratch. After mining those two approaches, we’re getting into the area where you’ll need some really creative thinking. The first idea is former employees; I’ve seen many VARs who have started their systems integration business by specializing in their old employers products after leaving the mother ship. Another similar possibility is a former employee who lives in or moves to another country; they might start an entrepreneurial “exclusive” distributorship in that country.

Former Competitors

Very similar to the “Former Employee” category above is partnering with employees of former competitors whom you may know or come across. They will likely have similar knowledge and skill sets to your former employees, so the same type of potential applies. The only caveat here is you need to be careful of any existing relationships with your competitors or special agendas that could poison a potential relationship.

Product Fans

This category of prospective partner is again very similar to the former employee and competitor categories in terms of potential. A user or former user who loves your product and who you have a good relationship with can be a good candidate for an entrepreneurial VAR/distributor startup, whether domestic or international. The area to be careful of here is they may be very skilled in your product and some internal operating specialty, but may be poorly prepared to market, sell and run an overall business. This of course is a potential risk in the former employee and competitor categories as well.

These are some ways you can take the difficult step of creating your own channel from ground zero. Has anyone else tried this–what were your results? What are your ideas on how best to go about it? Please post a comment 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

The Rise and Fall of Novell

Once again one of the great brand names of High Tech has been prominently in the news, this one  for it’s demise as a standalone company. This time it’s Novell, Inc.  Attachmate announced that it had closed its purchase of Novell, which becomes a brand of Attachmate.  The price was $2.2B–not chicken feed, but much less than the promise held by this company in the distant past.

This company holds a special place in my memory. In the early 90’s the Novell name was synonymous with Networking. The company was a pioneer in Corporate Networking, and played a major role in helping to create this market as we now know it. When I entered this market in 1990, the company’s core product, NetWare, held a commanding 70%+ market share in the networking software space, which was already very large at the time, and growing at a rapid rate. It was in this environment that I began my first general management position, starting up a systems and network management software business. Netware being the dominant NOS at the time, I got a very close look at the company’s activities, and some of the decisions and events that began Novell’s long decline. Novell is still a $1B business, but in terms of power and prominence, they are a shadow of the company I kept a close eye on in the 90s. There’s been speculation that the company would be an acquisition candidate for some time, so the news isn’t a big surprise. But it’s a story which is a cautionary tale, and many lessons for tech company management teams that don’t want to “blow it”.

So what caused the unfortunate change in fortunes for this former industry high-roller?

It’s a familiar story, actually, especially for those of you who are regular readers. The Novell story is particularly interesting, because several factors, each one itself capable of wreaking havoc on a solid company, came together to put this company into a long nosedive.

MICROSOFT-ITIS

The first problem was what I call “Microsoft-itis”. Novell became very successful on the back of its flagship NetWare platform, which drew the attention of Microsoft. Microsoft tends to become unhappy when any other software company grows too big, too fast. The upstart is then viewed as a potential threat in Redmond, as well as the fact that the market this other company has helped grow now becomes large enough to be attractive to MS. So the first problem was getting in the gun sight of Microsoft. Now, it’s hard to blame the company for this, it’s more of a side effect of success. This situation has caused problems for many a company, and is enough unto itself to throw a large majority of companies off their game. To have Microsoft target you is quite disconcerting, and if you don’t make the right decisions, you may be in serious trouble. How a company reacts to this challenge is critical, and in truth, often life or death.

ARROGANCE

Unfortunately, in some cases, being targeted by Microsoft sometimes builds a company up in its own view. It’s almost a baptism into the big-time. Microsoft is worried about us; we’re a peer to them now! We must really be smart! This leads to a false sense of security about the company’s true position in the market, leading to the second factor which can bring a company down—Arrogance.

Novell had plenty of excuses to be arrogant, even without Microsoft’s attention. They were truly dominating the Network Operating System business. The brand was dominant, the product was good, and the worldwide distribution network of VARs and distributors was second to none. Sales people at Novell no longer had to sell—they took orders. That led to a need to keep the big ball fast growth rolling, even as the market matured and became quite large. Wall Street, you know. Novell became known as a company that pushed, rather than created via pull marketing. There were numerous channel-stuffing scandals, so sales people could make their quarterly numbers and max out their bonus. No matter, things were well in hand, Novell was on a roll.

The closest competitor at the time was Banyan, with their VINES operating system. Banyan had a nice niche in the largest, WAN oriented corporations, but was no threat to Novell’s dominance. There was also a fast growing peer-to-peer player, Artisoft, who had a nice niche in the entry level market. Again, Artisoft posed no serious threat. And then there was Microsoft, with its alliance on the LAN Manager NOS with 3Com. At the time, Microsoft’s distribution strategy was still to primarily be an OEM supplier, preferring to let others take the lead in bringing the product to the end user market. They had piggybacked the hardware vendors with DOS and the emerging Windows 3.0, and were attempting to use that strategy in the Networking market with 3Com as their main partner. 3Com at the time was a dominant networking hardware vendor. They also teamed with many suppliers of UNIX software to create private label versions of LAN Manager for each UNIX flavor—HP UX, for instance. There were about 17 other platform partners, as I recall. It looked like a formidable syndicate which could challenge Novell for market leadership.

However, like many early Microsoft entrées into new markets, the offering was a joke. LAN Manager ran on top of OS/2, which should tell you something about its lack of success, right there. Technically inferior, with too many players involved to advance and support it, LAN Manager never gained significant traction vs. Netware, even with huge amounts of money being poured into development and marketing. Major new releases would be announced, each which was supposed be the one to give Novell a run for its money. It became a running joke in the network business. At this point, Novell looked invincible.

LOSING FOCUS

Then the arrogance at Novell rose to new levels. Apparently thinking Microsoft couldn’t beat them at their own game, Ray Noorda and senior management at Novell decided to also take on Microsoft on their own turf. Not only that, but to compete across many, many categories. They decided they wanted to become the new Microsoft, and in doing so opened a multi-front war against a larger competitor, with far more resources (See Hitler opening up the Russian front in the War against the Allies).

Novell bought WordPerfect to compete with MS Word, Quattro Pro to compete with Excel, and announced a dizzying array of additional new initiatives. (See Netscape taking a similar approach in its heyday, as well as Google is now, as we speak—that ought to be interesting). No one, I repeat, NO ONE, has won a multi-front war with Microsoft. The people that have fended them off (which is a small list), when MS has put them in their headlights, have done so by sticking to their knitting, and playing by the rules of their own market segment. Intuit is a notable example, which was able to keep MS in a minor role in the Personal Financial software segment, by advancing and focusing on its own offerings and current market.

WHAT HAPPENED?

Well, many of you who have been in High Tech for a while probably already know the result. Microsoft finally split with 3COM, developed Windows NT, essentially building Networking into the Operating System. This finally began to hurt Netware, and although it wasn’t an immediate rout, over time NT became the clear winner. The terminator of Redmond can be knocked down, but they almost never give up—they just go deeper into their pockets, and keep on coming.

The acquisitions that Novell made were already second or third tier products, and their markets were outside of Novell’s core market and competency. Drained of resources and fighting losing battles on many fronts, Novell was soundly defeated, ultimately selling off many of its acquisitions, retrenching and changing their strategy—quite a few times over the years, I might add. They went into a long, slow decline, and once this begins at a large company, it’s very difficult to truly turn it around.

WHAT IF?

So what would have happened it Novell hadn’t reacted like Netscape later did, choosing to battle it out toe-to-toe with Microsoft, blinded in a fit of rage and bravado? What if they had followed a similar strategy to the one that Intuit took? What if they had marshaled their resources, and kept their focus on maintaining the lead they had in Network Operating Systems and related businesses—which were pretty big markets in their own right? Hindsight is always 20/20, but my guess is that they would have had a much better chance of continued success—and possibly avoided the headlines in the Trade Magazines of the last few weeks.

Have you seen similar missteps in your own companies or markets?—please post a comment below to share the insights.

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

International Expansion: Partner or Invest?

This is an age-old question facing software and hardware companies. In this article we’ll examine the pros and cons, as well as the specific conditions that should drive your decision process.

Two basic options confront a tech company considering a foray outside of their home market:

  1. Set up your own subsidiary hiring your own employees to “put on the ground”
  2. Partner with established traditional distributors or strategic partners in the target foreign market

Let’s look at some of the key factors to consider when designing an international business development strategy:

Available Capital

How much money does your company have available for international expansion? If the answer is “not much”, this alone can be the deciding factor in your decision. If capital is very scarce, you’re almost forced to start out using distribution partners. This isn’t all bad, in my opinion. Using partners initially when you are an international newbie is a much lower risk way to start, and allows you to learn this part of the business without “losing your shirt”. I’ve seen a number of control-oriented management teams invest large amounts of money by putting people on the ground in subsidiaries, only to waste it in spectacular failure. Often this failure is due to inexperience.

Product Price and Complexity

If you have a high priced, technically-complex product with a long sales cycle, you will tend to benefit more than others by having people on the ground in the foreign market. These are the types of products which are most often sold directly, even in home markets. In this scenario, even if capital is tight and you can’t afford to put down a fully-loaded subsidiary with a dedicated direct sales force in every foreign market, it still may make sense to put some folks on the ground. As an example, you might be able to afford a channel sales rep and a couple of field engineers to support a large network of sophisticated local country distributors and VARs, across an entire continent like Europe or Asia.

Management Skills

What is the skill set of your corporate management team? If no one on the team has any experience with indirect distribution, for example, it’s going to be pretty tough to successfully build a working distribution channel in FOREIGN MARKETS which are far from home, in more ways than one. In this case, the most cost effective thing to do is to add someone to the top management team with the requisite skills and experience, or at least retain a long term consultant. Going without this hire often seems the cheaper route initially, but in most cases this end up being “penny-wise but pound-foolish” in hindsight.

Local Market Cost Structure

Each foreign market should be evaluated individually before deciding an approach for that market. For example, in large emerging markets with low costs (such as China, India, Brazil for many verticals) it may make sense to put your own people on the ground, regardless of the distribution strategy. When costs are low and the market is strategically important in the long run, the relative benefits of having your own subsidiary are high. In a high cost market with lower sales potential (Switzerland and Norway may be good examples for some businesses,) relying exclusively on a dedicated local partner may be a better way to go.

Availability of Partners

In some cases what may be the best strategy for your company and market in theory is overridden by facts on the ground. Many vertical software and hardware markets have a well established set of distributors and resellers dedicated to their marketplace. In these cases it’s relatively easy to find an appropriate distribution partner. But what if you’re in a business in which this ISN’T the case, which is not all that unusual? Or maybe there is an established channel, but you’re late to the game and all the obvious “good” partners are tied up with your competitors. Sometimes you may choose to not enter that market immediately. But if the geographic market is considered strategic, then you will need to choose a course that looks sub-optimal in theory. That might mean biting the bullet and outlaying the investment to start your own subsidiary. Or, you might find a local entrepreneur with the skill set to set up a new distributorship. If it’s a geographic market that you just HAVE to participate in, then you will find a way!

There are obviously a wide range of combinations and intermediate options, but “partner or invest” represent the extreme ends of potential strategies. In many cases (particularly large, established markets) the optimal distribution strategy will be a combination of these two main approaches: pairing a wholly-owned subsidiary with local distribution partners. In smaller markets, partnering with an established distributor or strategic partner may be the only viable strategy. In other cases, the optimal strategy may be dependent on the specific factors of a particular marketplace (local costs, available partners, etc).

What’s most important is to closely analyze your specific company’s situation and vertical market, as well as the “facts on the ground” in each individual geographic market. Resist the temptation to simply copy your competitor’s strategy or fall back on approaches that you are comfortable with from other vertical and geographic markets. That is how you make mistakes.

What’s your approach to international expansion? Post a comment and share your own personal experience.

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

How Soon Should Your Software or Hardware Company Go International?

This is a question that frankly doesn’t come up often enough at early stage tech companies. There is usually an assumption that you first conquer your home market, and then sometime way down the road, when you are already flush and successful, it will be time to expand internationally. US-based tech companies are most guilty of this often questionable thinking.

What’s wrong with this approach, especially for US-based companies? After all, the US is the largest market in the world, and it’s far easier to sell to customers close by, then it is halfway around the world. With this the case, why should you use your scarce early-stage capital in a risky international expansion? This is how the thinking goes.

The problem is that you may be leaving significant low-hanging fruit on the table, at the very time that you need those customers the most. Let’s look at 4 important reasons to go international as soon as possible:

Reasons for Early International Business Development

Early adopters needed

As an early stage software or hardware company, you need to find early adopters of your product. These folks fit a certain psychographic profile, and they are rarer than the average customer. You sometimes need to cover the earth to find them. Limiting your geographic net unnecessarily only makes the job harder.

Distribution partnerships can provide tremendous leverage for a young company

This is one of the big reasons to go international that newbies don’t understand. They think that with all the money they are spending to penetrate the home market, selling internationally will be much more expensive yet. Not necessarily. In many markets, you can find distributors who will take on much or most of the marketing and sales load, reducing your investment tremendously and allowing you to leverage their existing relationships–rather than “starting from scratch”.

Many markets are less competitive than your home market, especially if it’s the US

Unless your home market is a tiny one, there are most likely many underserved markets available to you that have a lot of low hanging fruit. Why? Every startup software or tech company thinks the same and focuses initially on their home market. Since the bulk of the tech business is located in the US, it’s by far the most brutally competitive of all.

Beat your competition to the punch

Getting to a market early can often mean the difference between success and failure. If you’re the first one in a country or region, the early adopters and other low-hanging fruit are there for you alone. You will get your pick of the best distribution partners, and your product category will be “fresh” news for the media. Once established, it will be hard for later arriving competitors to push you down the market share ladder, even if they are larger than you overall.

So when should a company go International? The short answer is as soon as you can possibly do it. But what’s most important is to fully evaluate when “as soon as you can” actually is.

What to Evaluate Prior to Deciding to Go International

Your product must be stable

This should go without saying, but the only thing that causes a greater catastrophe than an unstable product is an unstable product distributed worldwide! Don’t do this–make sure things are solid before venturing away from where it’s easiest to “babysit” early problems.

Your product must be “market-tested” in your home market

While I’m a proponent of aggressive international business development at an early stage, there is such a thing as “too early”. Make sure that you know your product has a market before going far away from home. It’s a pointless exercise to be recruiting distributors and customers in foreign markets with a product that doesn’t really hit the mark, and one which doesn’t even had a reference customer list. If you can’t gain 10 or 20 or 30 customers close to home, heading far away likely won’t help.

Inventory or License only

Businesses that involve large amounts of inventory are one of my exceptions to aggressive early international development. That means hardware companies generally need to be more careful that software companies. Companies that distribute through retail channels involve more inventory than those who sell via VARs or direct, so they also need to be more cautious. The issues that come with inventory such as repairs and returns are exacerbated by borders and distance. So if you’re inventory intensive, maybe start with one smaller market rather than a large regional rollout, to test that everything goes smoothly before placing a big bet.

Direct or Channel distribution

If you have to establish your own local foreign operation, hire a bunch of people, rent office space, etc–you generally need to wait. Most startups can’t afford this type of risk and investment. However, although some feel this route is their preference due to control, it’s generally not mine. It’s quite risky and slows your international progress rate down significantly. Most companies can start out by using partners, and usually this is a good long run strategy as well. If you’re wildly successful and really feel the need for total control, you can always buy out distributors later on.

English or Local Language

English is the universal language of technology. In some vertical markets (such as IT software) English language-only products are fine. These are markets where you can make the fastest penetration after proving your product in your home market. If you do need local translations, they really aren’t that expensive in most cases and can be done quickly, and distribution partners can often help. But make sure that you don’t skimp on a good translation; nothing will hurt your local credibility more than language that isn’t proper, or at worst, makes no sense.

Safety, Legal or Electrical Specifications

This is also an area that can slow down the potential for fast international market development. Many countries or regions have safety or electrical standards that will require product modification or testing (and thereby investment). There are also legal aspects that need to be considered (European privacy laws when selling security or marketing software, as an example.) Don’t let these stop you from doing an evaluation of your international prospects, but these factors can change the calculus of your decision making.

SaaS

If you’re a software company using the SaaS model there may be very little downside to early international business development. If latency isn’t an issue for your product, you may need no international investment at all. Or maybe you need your servers hosted in other parts of the world to reduce latency issues, but this shouldn’t be a huge investment. You still need marketing in the local markets, either by your own direct (albeit remote) methods or through partners. But given the potential rewards, these investments should be a small price to pay.

Process or Cultural Differences

When you first go into a foreign market, it’s important to understand that you can’t fully comprehend the local culture, as well as how commerce functions. Listen more than you talk at first. Hire a consultant if you can afford to. Partners can also help greatly here. But if you are a savvy international business person it certainly raises your odds when attacking foreign markets early on.

Existing Demand

Are there customers “chomping at the bit” for the benefits your product offers? Or will there be a bit of an education process and a long sales cycle? Obvious existing demand is a key indicator for aggressive international business development.

The bottom line is that going international quickly can be a big boost to early growth for a tech company. Be careful, but not overly cautious. Evaluate your specific situation, and take the plunge if the odds are with you. What’s your take on the proper pace for international business development? Post a comment or send us your story.

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

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

Promoting Software and Hardware Products through the VAR Channel

With the exception of some software and hardware vendors who sell super-expensive products to the largest enterprises, a large percentage tech companies uses the Value Added Reseller (VAR) channel, to one extent or another. So how do you best go about doing this successfully? Create a great product, throw it to the channel, and sit back and collect the money?

If only it were so. Unfortunately, many tech companies new to the channel find out the hard way that you will fail by taking the word “seller” in the VAR label too seriously. For those of use with experience in the VAR channel, you know that it is still incumbent upon the vendor to create end user demand for their product. Yes, you need to market to VARs as well. And you will take whatever “push” you can get from the channel. But you must have an active promotional program aimed at end users for a realistic chance at channel success.

So what are the best marketing approaches to support channel sales activities? If depends, of course, on the specifics of your product, market, price point, etc. But let’s take a quick look at some popular promotion methods used in conjunction with channel sales. I’ll break it down into three basic categories:

End user demand creation

This is first and foremost the most critical activity. It’s an unfortunate fact that most new players in the channel don’t understand this initially. Many have to learn it through a painful hands-on lesson, which sometimes leads to rejecting use of the channel outright, due to spectacular failure. It may be counter-intuitive, but it doesn’t even matter whether you establish end user demand for your products by selling direct or via the channel. The important thing is that with few exceptions there needs to be serious interest in your products at the end user level if you’re to successfully sell through VARs. In fact, it’s almost always necessary to be successful selling directly to end users, before you can hope to have a successful VAR channel for your products. Almost any end user marketing method that fits with your product type and budget can be used to create this demand, but here are some commonly used promotional types:

• SEO (Search engine optimization)
• PPC (Pay per click) advertising
• Press relations
• White paper marketing
• Targeted online banner advertising
• Direct mail, but traditional and email
• Social media marketing (Blogs, Twitter, Linkedin, Facebook, etc.)
• Trade shows

VAR recruitment

In addition to creating end user demand, you’ll also want to market directly to VARs, to get them interested in actively working with you and your products. An important point to remember is that the VAR channel is very large, and generally segmented into many vertical categories. So however you approach them, don’t waste time (yours or theirs!) by contacting VARs who aren’t doing business in your target end user segments. Here’s some common recruitment approaches:

• Direct email through available VAR lists
• Phone campaign using available lists
• Internet research with direct email or phone approach
• Trade Shows (VARs frequent them, and it’s a great opportunity for personal contact)
• Have a highly successful product with strong end user pull (VARs will find you!)

Cooperative marketing with the channel

Lastly, once you’ve created end user demand and recruited enough VARs to have a “program”, you need to establish standard methods of working with your new partners to create and fulfill demand. VAR programs come in all shapes and sizes depending upon the market, and I’ve seen a wide variety of promotional opportunities included in these programs. One of my personal favorite “getting started” methods is to offer to pay for and execute a direct mail campaign (blind to the vendor, if necessary) introducing you and your product family as a new partner of the VAR. Below are some promotional activities that are very commonly included in VAR programs:

• Co-op advertising/promotion with the vendor provides funding for approved VAR-executed promotional programs up to a set percentage (3-6%) of sales of your products
• Free or discounted demo units
• Special pricing for large opportunities
• Co-selling with your in-house sales force
• Deal registration
• Additional discounts for completing product training, certifications or maintaining premium support levels
• Co-branded product literature and other use of the vendor’s logo
• Website and catalog listings of authorized or “preferred” VARs
• Rebates for volume sales (not recommended; fraught with danger)
• Vendor-funded introductory direct mail campaign

That’s my quick primer on successfully promoting your products for sale through the VAR channel. Many of you have your own experience in this area; post a comment or a question to activate our discussion.

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