Integrating Sales and Marketing at Software and Technology Companies

In some, but not all tech companies, the Sales and Marketing functions are managed separately. They are separate, but closely related functions that some people (especially technical folks) have a tendency to confuse. Normally, there is a VP or Director heading up the Marketing department, and another VP or Director leading the Sales staff. But it is also not unusual to see a VP or Director of Sales & Marketing who leads both functions at once.

This all seems benign enough, so what's the issue? The issue comes when actual revenue fails to meet the forecast--that's when the finger-pointing usually begins. Unfortunately, not meeting forecasts is a common event in technology businesses, where forecasting of new software and tech products can be particularly challenging. When that finger-pointing starts, it often breaks out first between the Marketing and Sales departments--here's how the ensuing "discussion" might go:

SALES: "You haven't planned products that our customers want to by. You've priced them too high. And those leads that you've spent SO MUCH money on that you are giving us aren't qualified, and are essentially worthless to us."

MARKETING: "You're not selling the right products as we directed, or presenting the positioning of our product line properly. All you do is try to sell on price, constantly discounting and hurting our margins. If you'd follow up on all the leads we gave you, get off of the golf course and work more than 4 hours a day, you'd be well over quota and the company would be doing fine."

Sales folks and Marketers are different types of people, and tend to view the world differently and from their own selfish perspectives. This often nasty "discussion" as simulated above is far from uncommon, and can get pretty ugly--which can really hurt a company in trying to reach its goals. So what's the right way to get the Sales and Marketing departments to work together as a team, avoiding all of this counter-productive ugliness?

SOLUTIONS TO REDUCE POTENTIAL CONFLICT


The VP of Sales & Marketing
One way to greatly reduce this conflict is to have a common leadership for the Sales and Marketing functions. This usually means having a VP-Sales & Marketing in your organization. If you can find the right person to fill this role, this can actually be a very good solution. Having a single leader can go a long way toward eliminating or at least greatly reducing this conflict, assuming he has a balanced background and perspective, and is fair, not favoring one department over the other. Good people to fill this role are out there--but are very rare, in my opinion. There are far more managers who have been put in the position of VP-Sales & Marketing than there are those who were suited for the role. Most of the time you end up with a manager that understands one function well, and gives short shrift to or completely screws up the other function. . You will often find this combined VP position in companies that are not "marketing-intensive", where the sales function is the dominant aspect of the job. If the Marketing function is truly less important, a company can get by with this structure, although it usually isn't ideal. You can read more about the issues with a VP-Sales & Marketing role in a previous article that I've written entitled "Big S, little m".

CEO Demands Communication and Cooperation
If care isn't taken, the very different personality types in sales and marketing can lead to some pretty intense conflicts. I've been a soldier, captain and general in this war--and let me tell you, it isn't pretty. I've also (effectively) filled the role of VP-Sales & Marketing, which is a story for another day. Much like the battles between Marketing and Engineering that I've previously written about, I have seen this battle play out regularly in the companies that I have worked for as an employee, as well as at many of my clients in eight years as a consultant at PJM Consulting. Things can get out of hand very quickly, and paralyze a company. In many cases, the key is how the CEO handles the situation. He must go well out of his way to be a fair arbitrator in these discussions. Even the most benign comment can appear to show favor to one side, in the eyes of the other. Don't ignore or deny the problem, or assume it will be handled at the VP level. It is the CEO's responsibility to prevent, recognize and fix this problem. Be careful that you don't inadvertently make decisions or set up policies that reward or tolerate company politics.

Departmental Social Integration
I recommend planning activities which allow sales and marketing counterparts to get to know each other as "people" outside of their project activities. In many ways a successful outcome is all about relationships, so closely monitor the personal relationship between VP-Marketing and VP-Sales. Also, make sure that the VPs are monitoring the relationships below them. Ensure both VPs are open and honest with about the relationship between departments. Also watch for arrogance (especially from "experienced veterans") when screening potential new hires for either department that will interface with the other --arrogance often usually the trigger which starts the battle rolling

Integration of Departmental Functions
Encourage the sales department to get marketers in front of their customers. Hire marketing people that have had some sales or business development experience, who understand dealing directly with customers--and know what's it like when your living depends upon making your quota. Insist that the marketing department include the sales folks in determining what a "qualified lead" looks like. If you can get agreement on this up front on this important issue, much of the finger pointing goes away when things don't go as planned.

Joint Goals and Compensation Structure
It currently isn't common to design department or individual goals which cross marketing and sales functions, but if you can find a way to do this, you are structurally setting up the desire and need for close cooperation. Design goals and MBOs to reward the two departments for working together. Also, don't ever allow one department to "get ahead" by blaming the other--tie them together as much as possible in your goal setting.


SUMMARY

To limit issues between sales and marketing functions and ensure that they "sing from the same sheet', make sure to pay close attention to the individual departmental activities, which can nevertheless greatly effect the perceived performance of the other department. Optimizing the cooperation between sales and marketing demands an up front look at things such as the corporate structure at the highest levels, the social fabric of the company, compensation structure and use of MBOs, and formal cross-departmental reviews so each department can influence the other department's approaches. All too often in my practice at PJM Consulting, these things aren't taken into consideration until after the fact--when things have already blown up and there is a mess to clean up.

That's my view on this all too common conflict. What has been your experience in this area? Post a comment and begin a discussion.

Phil Morettini
PJM Consulting
www.pjmconsult.com

Integrating the Marketing and Engineering Functions at Technology Companies

In most tech companies, Product Marketing and Product Development/Engineering are managed separately. There is usually a VP over the Product Development function and another over the overall marketing function, which usually includes future product marketing/planning.

While this is certainly an appropriate way to organize a tech company, there is a great danger in one are when it comes to these separate operating "silos": the planning of new products.

I have a particularly strong opinion on this topic, with an extensive product marketing background and also having worked as a product developer earlier in my career (albeit in a non-tech business).

With respect to current products, the silo approach isn't much of an issue. The day-to-day activities of the marketing and engineering departments are very different, and can be managed separately quite successfully.

It's in the future product area that things can get messy. Product Marketing and Product Development both have a key role to play here, if the company is to optimize the process of planning, developing and introducing the best new product possible. The problems is that at every level, from the VP-level down to the engineering project managers and marketing product managers, the product marketing and engineering functions are often staffed by individuals with very different world outlooks when compared to their direct counterparts in the other department.

Inevitably, if care isn't taken, these very different personality types can lead to some pretty intense conflicts. I've been a soldier, captain and general in this war--and let me tell you, it isn't pretty. The battlefield often is a company's strategic plan, which ends up in a trampled mess. I have seen this battle play out regularly in the companies that I have worked for as an employee, as well as at many of my clients in eight years as a consultant at PJM Consulting. It sometimes gets so ugly it paralyzes a company, putting it at a severe disadvantage vs. competitors who have less of a conflict.

THE "WRONG" WAYS TO HANDLE THIS POTENTIAL PROBLEM

Unfortunately, most CEOs that I meet are not all that in tune to how damaging these conflicts can become.

Often they will ignore or deny the problem, thinking it is a responsibility to be handled at the VP level.

Another strategy that I have seen companies put in place is to extract the product planning function from the marketing department, and put it under engineering. This will often greatly reduce or eliminate the conflict, but it akin to throwing the baby out with the bathwater. As I said earlier, both marketing and engineering have a key role to play in product planning. This strategy effectively removes the voice of the customer, which is a key role that the marketing department should be playing in any successful software or tech company. As much as product developers think it looks easy, they almost never have the mentality or experience to accurately read markets or customers. Almost no one is great at everything; monitoring and reading markets, and technical product development, are two very different skill sets. Having both mentalities involved in a positive way leads to far better products in the end.

Finally, if they happen to have come from one side of the battle or the other, CEOs sometimes "take sides" in the battle--predetermining the winner. The problem is there is never any real winner in this battle--and the only certain loser is the company and its shareholders.

A CEO can choose to let Marketing have the upper hand--and this may work out adequately in commodity products where there is very little engineering differentiation. In any other circumstance, results will likely be sub-optimal.

Or he can let Engineering win and dominate the planning process--which is a very common occurrence in early stage, technically-driven software and tech companies. But this generally only works well for products made by engineers, built for engineers (the early days of Hewlett Packard are an example of this strategy working successfully). For every company that has used this approach successfully, there are probably hundreds or even thousands that failed in large part because of it.

Ultimately, to make sure that this conflict and its dire consequences are to be avoided, there is one key thing that needs to happen:

IT IS THE CEO'S RESPONSIBILITY TO PREVENT, RECOGNIZE AND FIX THIS PROBLEM.

So what steps can a software or tech CEO take to be on the lookout for this problem--and more importantly, what can they do to prevent it from developing?

*It's all about relationships: closely monitor the personal relationship between VP-Marketing and VP-Engineering
*Make sure that the VPs are monitoring the relationships below them
*Make sure they are both VPs are open and honest with you about the relationship between departments
*Plan activities which allow engineering and marketing counterparts to get to know each other as "people" outside of their project activities
*Be careful that you don't inadvertently make decisions or set up policies that reward or tolerate politics
*Design goals and MBOs to reward the two departments for working together
*Don't ever allow one department to "get ahead" by blaming the other--tie them together as much as possible
*Hire marketing personnel that can talk the language of engineers
*Screen product development hires who will interact with Marketing for the not uncommon attitude that engineers are "superior" human beings
*Encourage the marketing department to get product developers in front of customers
*Watch out for arrogance when screening potential new hires for either department that will interface with the other --arrogance is usually the trigger which starts the battle rolling

SUMMARY

Marketing/Engineering conflict over the product planning process is a common problem that is often overlooked by tech company CEOs. A certain amount of creative tension can exist between the two departments, and be totally healthy. All too often, though, this tension turns into a bloody fight which is destructive to the company's prospects. It is not "fait accompli", however. It can be minimized and even prevented by a watchful and proactive CEO.

That's my take on a common issue which is rarely discussed out loud. Have you had your own issues in this area? Post a comment to add to our discussion.


Phil Morettini
PJM Consulting
www.pjmconsult.com

Channel Pricing Strategy for Software and Hardware Products

Pricing software products is always a difficult exercise. With high product development costs, but near zero costs of goods sold, there are many different strategies that people have followed successfully (and not so successfully!) over time. Pricing hardware products is a bit simpler because there is generally a significant cost of goods sold that acts as a governor on pricing behavior. But even with hardware, technology markets are dynamic and fast moving. And it's a complex enough topic when all sales are going direct--once you bring channels into the picture, it only gets worse.

CHANNEL CONFLICT
The biggest concern most companies have when pricing for multiple channels is channel conflict. I have seen many companies who actually AVOID selling through channels for fear of the pricing implications it brings. They are afraid of a channel undercutting their direct sales force in price, and channel conflict in general, which arises as a result of different prices being presented to customers from representatives of different channels. But this doesn’t have to be so; with a savvy understanding of the implications of pricing actions. This comes from both experience, and "paying attention to what actually HAPPENS in the marketplace. If you price properly and run your channel programs well, you can sell successfully via multiple channels--with these channels living in relative harmony.

VALUE-BASE CHANNEL PRICING
I've written about value-based pricing before, in the context of the perceived value of a product, as seen by the end-user, being the guidepost for pricing actions. A similar concept exists for channel discounts. Rather than taking a simplistic approach and give the greatest discount to the channel players that move the most product ( a destructive strategy--more on that later), it's important to measure how much "value" a particular channel provides both you and your end-user customers. Look at things like 24/7 support, inventory & product availability, technical expertise, credit services, and the like. In this case, it is helpful to let the cost of delivery of each of these attributes be your guide to the value they provide.

VALUE-BASED CHANNEL DISCOUNT STRUCTURE
For example, you may figure that the cost of a VAR providing 24/7 support to end users (meaning YOUR company doesn't have to) is equal to 5% of the list price of the product. And the inventory held by a retailer (again, meaning YOUR company doesn't have to hold it, at a cost) is equal to 2% of the list price. And so on and so forth. Using this value-based method, you can calculate the actual costs borne by your partners in delivering marketplace value, and use this as a guidepost in building your channel discount schedules for various types of channel partners. This value-based channel pricing approach is not well-known, and seldom considered; most people seem to figure the only value worth extra discount is sales volume. If you use a value pricing approach, you actually have a chance to build a multi-channel strategy that "clicks on all cylinders" by providing discount structures that are equitable based upon cost and value associated with each channel.



LIMIT VOLUME DISCOUNTS
If you choose the "more volume=greater discount approach, your multi-channel strategy is a house of cards which will soon collapse around you. One channel will quickly grow to dominate, and the other channel types will soon quit selling on your behalf, and wither away.


THE GOAL IS TO MAXIMIZE SALES THROUGH ALL CHANNELS
Again, the key is to not let one channel dominate. Ideally, you would like all channels to be presenting prices to the end customer that are equal. In reality, that pretty much can't happen without price fixing (which some folks may be able to get away with, but that's another story….). But you should strive as much as possible to have end user pricing equity for all channels. But this is where the counter-intuitive part of this discussion comes in to play. Most people pricing high tech products have a tendency to price based upon the volume of product a particular channel player can move. It seems logical--why wouldn't you want to incent and reward a partner with better margins if they are selling more products?

While this appears logical, it is actually penny-wise and pound-foolish. In fact, it is usually catastrophic to your plans to maximize sales through multiple channels. Let's look at a simple case of how this often "breaks" a multi-channel strategy for a common case: a vendor selling through both retailers and VARs.

A SIMPLE EXAMPLE
Retailers provide a vendor with a point of purchase holding inventory, where their customers can go to immediately purchase a product. VARs often don't hold inventory, but provide other services important to the vendor and some customers, such as tech support, training and integration with other software and hardware products. Each may have an important role to play in the overall strategy to maximize vendor sales.

But the retailer will usually be a high volume partner, with the VAR less likely to be a volume outlet (although the VAR CHANNEL, in total, may hold great promise to move volume). If you structure your pricing by volume, the retailer will get better discounts. Because individual VARs generally have higher costs spread over lower product volumes, they actually need HIGHER discounts to stay even in pricing potential to the Retailer. This situation is exacerbated by the fact that retailers tend to be volume-oriented, usually accepting a relatively small, fixed margin on everything they sell. If you provide discounts based upon the volume that a partner moves, what will happen is inevitable: The retailer will take over your channel business, because the VARs will be "squeezed out" by the relatively low prices charged by the retailer. They won't be able to make a profit on your products, so they will ignore the business, and you will lose the opportunity to realize significant sales through the large (in aggregate) VAR channel, especially those customers that desire the service and support they supply. I am oversimplifying this situation, of course, because VARs are more interested in the service revenue that a product can pull, than they are in product margins. But I have seen this scenario play out many times and kill product sales through VARs channel that might otherwise generate health sales through that channel. This can be a heavy penalty for naïve technology product managers who are charged with pricing their products and moving them through multiple channels, but who don't fully realize the consequences of their actions.

SUMMARY
Pricing seems pretty simple on the surface--when channels are involved, it's anything but. It's important to fully think through the downstream effects of your pricing policies when multiple distribution channel are involved. Let me know if you have questions, or you own channel pricing stories that you'd like to share.

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