Home » Sales

Category Archives: Sales

(Shared) Sales Force Not Selling (all of) Your Products? Three Common Levers to Create Sales Focus (Part 3 of Series)

In the first post of this series, I discussed the widespread assumption in the Tech industry that shared sales forces help encourage “Survival of the Fittest” products. In the second part of the series, I discussed a checklist you can use to determine if your products can be sold via a shared sales force.

In today’s post, I will be talking about the Pros, Cons and Reality of the “Three Common Levers to Create Sales Team Focus”

Does “Survival of the Fittest” work for a shared sales force? Sometimes, but from what I’ve seen, more often there are major distortions to the “fittest” based on other factors that drive attractiveness to sales. In my experience the products that get sold by a shared sales force are not necessarily “the fittest”, but instead, the products that meet more “human” needs – like reps looking to meet their quota, hit their “accelerators”, or even just to keep their jobs for next quarter – and are often dictated by the comp plan. The way they vote with their time may or may not coincide with what the executives feel are the longer term interests of the company. Of course, a company falters if they miss short term performance needs, but I would argue that just as many tech companies falter when they sell the “products they know, or can sell fastest, until the differentiation for those products withers and they and the company are left in a weak strategic position…

In my experience, there are 3 main tools that most tech organizations use to gain sales rep focus.

3 Tools to Manage “Product Sales” in a Shared Sales Force

  • Tool #1: Provide Transactional Incentives for Product Sales
  • Tool #2: Provide Sales Overlays to Create Additional Sales Focus and Expertise
  • Tool #3: Adjust the Compensation Plan to Provide Incentive to Sell Products

Tool #1: Provide Transactional Incentives for Product Sales

Creating Focus

Transactional incentives are the most common approach to influence sales rep behavior and focus. We’ve all seen this approach till we are numb and a bit confused by the overlapping incentives that are running from different groups each quarter.

Pros

  • $s influence a coin-operated sales team
  • Can be effective for transactional sales

Cons

Is “lack of an incentive” really the reason you don’t have focus on all your products?

Tool #2: Provide Sales Overlays to Create Additional Sales Focus and Expertise

Creating Focus

Since Overlays only sell particular products, they can’t get distracted by easier sales, and they wake up every morning trying to sell your product. Often these overlays are SEs, so they can provide both technical expertise and some sales coaching specific to the product.

Pros

  • Have a team focused on successful selling of a product
  • Provide a feedback loop for product marketing or business units seeking customer feedback on their market

Cons

  1. Typically provide double compensation for the same sale, to encourage collaboration
    • And as any sales executive knows, you don’t want to pay 120% of sales payout for 80% achievement…
  2. Sales overlays have different goals and it is common for organizations to have INTERNAL sales engagement across products. As companies get larger (think HP, Cisco, even mid-sized companies like VMware) different Reps have different agendas at the same customer
    • The Account Reps/Teams who own the overall account and get credit for all sales into the account
    • A great vendor sales rep is often quite “controlling” of the decision makers and timing for discussions within their accounts, and this instinct tends to undermine efforts by those who have different roles, including:
      • Your Sales Overlay Teams that must sell their product
      • Your Strategic Alliances that are trying to sell joint solutions into the same account
      • Your Channel partners who might be selling your product as part of a larger solution that won’t close till next quarter

Tool #3: Adjust the Compensation Plan to Provide Incentive to Sell Products

The most common approach to setting a compensation plan is “a dollar is a dollar”, where the comp plan does not differentiate whether the sale is for Product A, Product B, Training or Professional Services ($ all goes to the same place anyway, right…???)

Creating Focus

  • Quota for individual product groups. For example, a Reps $500K quarterly target might include a minimum $100K from a particular “Strategic” product group
  • Accelerators for certain “emerging/strategic” products (e.g. earn 150% quota credit for selling emerging Product X)
  • Carve-outs – making some easier, “low-hanging fruit products” or categories of sales not part of the compensation plan. For example, many/most technology vendors do not pay their field account reps for Renewals, because that might unnaturally incent Reps to “farm” the renewals business, rather than “hunt” for new business

Pros

  • $s influence a coin-operated sales team
  • Impact to compensation can be significant enough to influence behavior (more than incentives)

Cons

  • Must be utilized sparingly, or comp plan is too complex and Reps get mixed signals on organization priorities
  • Complex comp plan with accelerated payout can result in sales reps making their number, but the organization missing bookings, revenue and profit forecasts.

But here is the dirty little secret of shared sales forces…

Even if you can assign a Product-Specific quota and have an Overlay Sales Force it is quite possible that your organization will lose sales focus (and revenue) on some products

What can organizations do to have a cost effective sales force and sell all their products? In next weeks post I will talk about some “Out of the Box” approaches organizations can use to gain the cost advantages of Shared Sales Forces AND Sell a wide range of products.

I welcome any comments below — And make sure you “Follow” our blog (look for the “Follow” link on the left sidebar) and have your say. I’m also available as a public speaker, to support local and global events in Silicon Valley, or the rest of the flattening world…

For more details, and to stay in touch with this community, contact me or Subscribe to our “Climbing Out of the Box” Newsletter via the form below.

(Shared) Sales Force Not Selling (all of) Your Products? Use the “Shared Salesforce Checklist” to Uncover the Issue (Part 2 of Series)

Last week I talked about challenges tech organizations encounter when they use a shared sales force to sell multiple product groups. The organization may indeed recognize increased sales efficiency, but also may see a drop in sales and profits derived from some products. Which of these effects is larger depends on your business – but beware of adopting a shared sales force, without taking a hard look at the potential negative impacts on some parts of your business.

(Shared) Sales Force Not Selling (all of) Your Products?

In Part 2 of the series, we will talk about the variables that make a shared sales force across products a success, and when the benefits are an illusion.

When does using a shared sales force work well?

At a high level, it can work well when the products or the business model for the products being sold fit together in some way. In this weeks’ post I will explore this fit in more detail and talk about a tool that I have developed and have used over the years to help companies think through when a shared sales force approach makes sense for an organization. I call this tool, “The Shared Sales Force Checklist”, and the checklist is shown in Figure 1 below.

A good way to get started is to complete the checklist yourself, and then get additional perspectives from customers, and folks within your sales, marketing and product organizations. You will notice that while the questions are Yes/No, you need to think about the underlying question before you decide if the answer is the same for both products. For example, to answer, “Sold to Same Customer”, you need to define target customer for each product. You can use the “Description” column on the right to fill in these details. By comparing the answers from customers and your internal staff, you can make a lot of progress determining how well your products fit together for a shared sales force. 

Figure 1: The “Shared Sales Force Checklist”

Shared Sales Force Checklist

 

 Let’s take a look at the questions in the Checklist in more detail. A single shared sales force selling multiple product groups can work well when:

  • They are Targeted to the Same Organization
    • If you are selling to different types of organizations, you may not be able to get sufficient customer intimacy to sell both product groups For example, problems can arise if one product is sold mainly to Healthcare and another is sold as a horizontal sale across industries.
  • They are Sold to the Same Buying Group and Decision-Makers
    • If you must sell to very different buying groups within an organization – like Line of Business for one product and IT Operations team for another, you may find that it requires a completely separate set of sales calls and account relationships.
  • They Solve Related Problems and are Part of Complementary Solutions
    • If two products are part of the same solution, like two components of the corporate network, you may find that both projects are part of some of the same projects – and therefore get solution synergy.
  • There is “Shared Learning” Across Products
    • If two product groups have a different set of baseline technology and industry learning needed to sell them effectively, training can be difficult and the sales team may resist requirements for hours of enablement training.
    • For example, it may be difficult to sell one product that fits into the network and another product that optimizes storage with one sales force. Your sales team would need to be educated on technology, industry trends, problems and competitors for two separate ecosystems of vendors – a lot to ask for a group of employees who are supposed to be spending their time with customers…

There are also some other significant elements of the GTM for Products that can accelerate or sabotage efforts to share a sales force, and in my experience, organizations tend to overlook or discount their importance.  A single shared sales force selling multiple product groups can work well when:

  • They Have a Similar Sales Process
    • For example, if one product is sold transactionally based on price, and another is a consultative ROI-based sale, they will be very hard to sell with one sales force.
    • I saw this in one client where they had two similar products, but one was sold directly to developer teams and the other was an Enterprise sale. The Product Marketing folks that sold to developers kept expecting the sales team to carve out part of their time to sell their product, but were consistently disappointed…
  • They Have a Similar Route-to-Market
    • For example, if one product is sold by a group of Enterprise Sales Reps on Global Accounts and another is sold by System Integrators who build the product into their solutions, they will be hard to sell with one sales force

In next week’s post, I will talk about the 3 main tools that Technology vendors use to prevent issues with using a shared using force, when these tools are effective (and when they don’t have the intended consequences…)

I welcome any comments below — And make sure you “Follow” our blog (look for the “Follow” link on the upper left) and have your say. I’m also available as a public speaker, to support local and global events in Silicon Valley, or the rest of the flattening world…

(Shared) Sales Force Not Selling (all of) Your Products? (Part 1 of a Series)

For many technology vendors, a Shared Sales Force across multiple product groups is reality of how they go to market and sell their products. Sometimes this approach brings the hoped-for coverage synergy and robust bookings, But as we have all seen in our careers, sometimes “things don’t work out so well…” If you’ve had the role of VP/GM or Product Marketing for a product business unit, you know that

“SHARED SALES FORCE” OFTEN EQUALS BUSINESS UNIT FRUSTRATION AND LOW SALES $

A friend of mine used to be the VP and GM of a Product Business Unit with a tech vendor with many product groups and about $700M in revenue. His organization used a shared sales force across many business units, and his business was allocated a share of the cost of several other sales organizations within the company (that could conceivably sell his products). The problem was that despite all of these “allocated” sales resources, none of the sales teams to spent time selling his product (which did not help his BU performance…). After a year or so, he concluded that he could not control his own destiny, and he chose to move on to greener pastures.

salesperson-choice

The challenge is that when organizations use a shared sales force across multiple product groups, the sales team is asked to vote with their time, by focusing on selling some products and not others. The Tech industry generally sees this decision as an application of Darwin’s “Survival of the Fittest” theories on evolution, to “Survival of the Fittest” tech products.

Shared Sales Forces are usually seen as a way to gain sales efficiency. While it always makes sense to look for ways to reduce the cost of sales…

My experience is that tech vendors often make the decision to use a “Shared Sales Force” without fully accounting for how the approach will also reduce revenue (and profit) for some products…

Some lost revenue is inevitable and planned for, but what if some of the product groups lose a significant amount of their sales, or even just do not grow as expected. Would the decision to use a shared sales force still make sense? Of course the answer is “it depends”, but I think it is fairly common practice is to make the change to a shared sales force based on “financial necessity”, and assume that the BUs and the Sales Team will “figure out a way to make it work”.

The issue is that what often what happens is an accompanying reduction in sales and profit from some products – which can make a decision made for a “financial necessity” into a “financial disaster”…

Let’s take a look at a sample scenario below.

  • In Table 1 we have the baseline situation with 5 products being sold, each with different revenue and gross margin %.
  • In Table 2, we see a potential scenario of how that revenue could change with a shared sales force. The new approach works very well for Product A and Product B, which see 18% and 20% revenue growth respectively. The problem comes with Products, C, D and E (which have smaller revenue, but a higher GM% (perhaps due to lower competition, or a developing market). These products see significant revenue decreases and lost margin $.

Shared Sales Force Impact 1

Shared Sales Force Impact 2

Table 3 below shows that in this example, the Total Revenue $ Decreases by $4 Million (=96-100) and Gross Profit Decreases by $4.65M ($55.30-$59.95) – not exactly the outcome that the company wanted…

Shared Sales Force Impact 3

I am not saying that this always happens when companies go to a shared sales force

What I am saying is that companies need to be honest with themselves, recognize that this scenario can happen, and factor this into the decision on how to structure their sales organization

Technology Companies tend to assume that that sales and the product teams will “figure out” a way to minimize this issue, but depending on your situation, the revenue you lose may be gone forever… So how do you know when you are pursuing better sales effectiveness and when you are pursuing an “illusion”?

In next week’s post I will talk about “The Shared Sales Force Checklist”, a tool that I’ve developed to identify when different product groups can be sold together successfully – and when the hoped-for synergy is an illusion…

I welcome any comments below — And make sure you “Follow” our blog (look for the “Follow” link on the upper left) and have your say. I’m also available as a public speaker, to support local and global events in Silicon Valley, or the rest of the flattening world…

For more details, and to stay in touch with this community, contact me or Subscribe to our “Climbing Out of the Box” Newsletter via the form below.

Channel Not Ready to Sell: Do You Make “Enablement” Real with “On-the Job” Training? (Part 5 of the Series)

A number of my recent posts have focused on challenges and best practices to “enable” your channel and drive revenue. Below is the list of the posts so far:

Channel Not Ready to Sell?

 

In the final post of the series, we will be talking about Natural Law #5

  • Sales Engagement: How Channel Enablement Becomes Revenue $

 onthejobtraining image

 

Let’s start with a baseline question – How much training does it take for someone to be able to do something effectively? That seems like a reasonable question, but it actually misses a critical point of enablement.

  • In order to be “enabled” to do something, people need to learn how to do it, and then they need to practice the skills they’ve learned

But think about the “enablement” programs that you’ve seen in your career. How many of them provided opportunities to practice what was learned? I’ve seen it happen it happen occasionally, but not often. Sometimes the vendor coordinates “Role Plays” in a workshop setting, and I’ve done whiteboard training where the participants broke into small groups and practiced whiteboarding to each other. But for many vendors Training = Enablement, because creating “practice” can be complex, hard to measure, expensive and difficult to scale.

That statement defines the dilemma that tech vendors face:

  • Partners need practice to be effective selling
  • But providing a programmatic way to get practice can be complex and difficult to scale

What can vendors do the provide opportunities to practice and get partners “enabled to sell”. The answer is something that the sales reps do every day – talk to customers (and to do it with partners, as the final step in “enablement”). What I am suggesting is connecting your “Enablement” plan to your Sales Engagement approach.

Those of you working in large vendors may be reading that suggestion with skepticism – how can a field Rep at a complex vendor and a lot of partners (like Cisco or HP) participate in “channel enablement”. After all, that is the Enablement Team’s job and is done by “corporate” folks, leaving the field to do their job, to engage with customers….I see your point, but hold that thought for a second.

 

When have you seen “enablement” work well, so that the teams in the field are confident that they can rely on the local channel partners to initiate and close sales opportunities?

 

In my experience, “enablement” works when there is a strong connection between the local sales team and the partners. That connection often occurs in smaller companies where the local sales team has responsibility to recruit and enable partners in their region, to help them in selling deals in their territory (but no so often in larger companies with fragmented responsibilities). Part of the value in this model is that the local sales team feels that they are accountable for helping to “enable” the partners in their region, to help them in selling. But a large part of the value is the local sales team, not only trains the partners, they go with them on sales calls and provide feedback on their progress. In other words, “THEY PROVIDE ON THE JOB TRAINING”.

That sounds wonderful, but it does not scale well to a larger company. You can’t expect the local sales team to own recruitment, on-boarding and the enablement process for all their partners. But the local sales team could be accountable for the “last mile” of enablement, which helping partners practice what they have learned by going after real sales opportunities together.

How would this work? The critical element is creating a channel program requirement that the “last mile” of enablement occur in the field with the local team. In this model, it would be part of their role to work with the partner to jointly engage with customers (and get on-the-job-trainijng). In effect, the process would work the same way it works for the channel-savvy and channel-friendly reps that you already have:

  • New partner or newly certified partner calls the local team looking to work together on some opportunities
  • Often the onus is on the partner to provide the first couple of contacts for targeting – after all, they have many local customers, just not with the vendor’s product (and what vendor does not want that???)
  • As the vendor sales team and partner get used to working together and have some success, the vendor reps bring the partner into opportunities
  • As the relationship matures, the vendor sales rep and the partner start to do joint account targeting and selling, with defined roles like “Partner SE runs the POC” follow up from the intial meeting…”

That process is really just basic sales engagement. But for many vendors, this process only occurs where you have sales reps that understand how to work with partners and drive revenue. With channel program design, there are always important details to define and operationalize, but this approach is a winning solution for vendors and for partners.

The opportunity is to build this approach into your channel enablement plan and “Package” the Enablement (see my recent post on this) this into your channel program to scale. This approach has the following benefits:

  1. Create a set of “enabled” partners who have both the training and experience necessary to help vendors drive revenue
  2. Help the vendor field standardize on a best-practices sales engagement approach that creates new sales opportunities and a community of enabled partners in their territory

I welcome any comments below — And make sure you “Follow” our blog (look for the “Follow” link on the upper left) and have your say. I’m also available as a public speaker, to support local and global events in Silicon Valley, or the rest of the flattening world…

For more details, and to stay in touch with this community, contact me or Subscribe to our “Climbing Out of the Box” Newsletter via the form below.

Channel Not Ready to Sell? Perhaps You are Not “Packaging” Your Enablement Within Your Channel Program (Part 4 of a Series)

In the last couple of months, I’ve done a series of posts about challenges technology vendors face in “enabling” their partners to sell their products.  Below are the posts so far.

Channel Not Ready to Sell?

This week we will focus on Natural Law #4

  • Enablement must be “Packaged” within a Channel Program, To Drive Adoption and Channel revenue…

The first question you may be asking yourself regarding this Law is, “What on earth is “Packaging” (and why is it a Law?)

Package and Question Mark

That is exactly the question one veteran Sales Training/Sales Readiness executive that I worked with asked when he added Channel Enablement to his group’s charter. The first meeting he attended included someone from partner programs, the channel sales executive for the region and a person whose team managed the marketing relationships with key partners.

The new Channel Enablement leader launched into an outline of his vision for a training curriculum – and the rest of the team sat silently. Finally one of the attendees spoke up – “Why would the partners want to take this training and how does it help them get started selling today?”  The new channel enablement guy answered with some platitudes on how it would help the partners sell “better”, but it was clear that he did not really get the #1 different between enablement for channels and the sales training program vendors provide for their Reps:

 

  • Vendor Reps MUST sell your products (or they are not around very long) and your sales executives can tell them they MUST do certain things (like take a particular training) 
  • Channel Partners have other options – and are governed by “Why should I care” If a channel partner, and in particular an individual Rep, SE or Consultant does not see value to them TODAY for your training, you can be assured that they will spend their time somewhere else…

This principle was discussed in detail in my post, “Channel Not Selling Your Products? 3 Questions You Can Ask to Diagnose the Problem.

  • Question #1 is “What is the Value Proposition for Partners to Sell your Product?
    • And how can they get started making money today…

They key is to get partners to participate in enablement is to think of the situation from their perspective, and use the 2 motivational tools that we humans respond to, “the Carrot and the Stick”. In the language of technology vendor channel programs, the Carrot and Stick translate to

  • “What are the Benefits associated with participating in the channel enablement activity/taking provided by the vendor that incent partners to the training?”
  • What are the Requirements from the vendor that provide a compelling “stick” to participate in partner enablement?

Let’s illustrate “Packaging” with a specific example

In the period 2008-2012 NetApp created the FlexPod architecture to sell their products with Cisco and VMware – but channel enablement was difficult. The challenge was that the products cut across compute, storage, network and virtualization and was therefore difficult for partners to market, sell and deliver. One partner I talked to during that period said that selling FlexPod was a “6-legged sales call”, because the partner’s staff were siloed with different individuals focused on VMware, Cisco and NetApp technologies, and only a few Reps, SEs and Consultants with sufficient skills to sell and deliver, cross-silo.

Clearly the partners would need to be “enabled”, But creating great training would not be enough – How could Cisco, NetApp and VMware “Package” the enablement, so that partners would participate, and eventually sell more of their solution/products?

Building Block graphic

A good way to get started on “Packaging” your enablement is to conduct an exercise where your team brainstorms potential “Packaging” options. I’ve found that this exercise gets the item on the agenda and sometimes creates some surprising and successful “Packaging”

  • Have a baseline discussion on the partner business model (multiple products, relatively low product margins, need to control costs and maximize selling time)
  • Brainstorm potential “Carrots” and the “Sticks” that could have be used to drive participation in enablement (and more sales of your product…)

Then you and your team are in a good position to evaluate the feasibility of these options, and to create the appropriate “Packaging” for channel enablement.

  • The Carrot – Potential Incremental Benefits could include things like:
    • Exclusivity / Fewer Authorized partners – could limit sale of a product to only the partners that have met enablement requirement.
      • Vendors are often hesitant to take this step, but it is a powerful incentive to partners to participate in a program (and often has limited downside because untrained partners will often sell very little of complex solutions anyway and may cause customer sat issues, when they do…
    • An incremental margin to partners that complete enablement requirements
      • Provide additional discount at Distribution on every sale for partners who meet the requirement
      • Provide rebates on qualifying sales, for partners who meet the requirement
    • Access to vendor staff that can help the partner sell, such as SEs, Specialists and other staff, for on-site training and sales engagement
      • Access to staff can often be the most valuable benefit of all, particularly when it leads to account planning and joint customer engagement.
      • However, this benefit can be hard to quantify because vendors often provide vague benefits like named account manager – and partners later find that they are one of 30 partners on their contacts partner list…
    • Other benefits – get creative!
      • By looking at what it takes to sell your product, you can often find hidden gems that are very important to partners and are relatively easy and beneficial to you as well – but you have to look
  • The Stick – Potential Requirements to Drive Participation in the Enablement could include things like:
    • Require partners to complete the enablement to get access to product/solution-specific benefits.
      • In the FlexPod example that could mean some number of trained or accredited staff Reps, SEs and Consultants) – to be eligible for the incremental benefits above (discount, access to sell product, etc…)
    • Require partners to complete enablement to gain additional program benefits from earning a higher tier in the partner program
      • Many vendors have a tiered program, where partners earn “Gold” status based on meeting requirements – and one of the most common requirements is to have a certain number of technical certifications or sales accredited staff
    • Require partners to complete enablement to gain the benefits of a specialization or badge in the partner program
    • Other Requirements – what do partners really need to do to be successful?
      • I often find tech vendors end up listing a series of generic benefits and requirements that are not enforceable, and would have little impact if they were met.
      • Ask your team, “what is really needed to be successful” and build this into the Requirements. Maybe it’s a demo center, customer references, certifications in related technologies or even marketing skills – but make the requirements meaningful!

I’m amazed by how often I see major product launches and detailed enablement plans created by vendors – without really grappling with these questions (and the WIFM for partners). Not surprisingly, vendors don’t get the participation or the revenue impact they expected (and they leave partners muttering to themselves once again that “vendors just don’t understand my business…”)

I welcome any comments below — And make sure you “Follow” our blog (look for the “Follow” link on the upper left) and have your say. I’m also available as a public speaker, to support local and global events in Silicon Valley, or the rest of the flattening world…

For more details, and to stay in touch with this community, contact me or Subscribe to our “Climbing Out of the Box” Newsletter via the form below.

Want to Sell Solutions, But at the Velocity of Transactions? Connect Your Sales Plays to Provide a “Path” to a “Destination” (Part 4 of a Series)

A common concern among sales executives is the “velocity” of their sales approach. As we’ve been talking about in this series, concern about “velocity” often keeps tech vendors from trying to sell “solutions”.   In this series, I’ve been talking about the 4 Steps to “Sell Solutions at the Velocity of Transactions.”

Now that we’ve established a “Destination” and a “Path” for your customers, what should technology vendors do to get customers to adopt their Solutions and Products? If you looked at 10 sets of marketing materials and sales tools from across the industry for storage, networking, management, converged infrastructure, virtualization and cloud solutions, you would assume that the answer is – “build tools to sell your product/service”?

But as one of my professors in college used to say, “If you put that answer on your paper come Q day, you’ll get a BIG RED X, (Heh, Heh, Heh).” (more…)

Channel Not Ready to Sell? 2 Simple Steps to Enable Channel Revenue (Part 2 of Series)

In last weeks’ post I talked about the “5 Natural Laws of Channel Enablement”, and how following these approaches can help technology vendors “Climb out of the Box™” and drive more revenue through their channels. We also talked in detail about Natural Law #1 – the importance of enabling your partners to do something specific – not just know more about your product.

The 5 Natural Laws of Channel Enablement

  1. Enable Your Channel to Do something (not Know something)
  2. Enablement ≠ Training – Training and Tools must go “hand-in-hand”
  3. Channel Sales Training ≠ Vendor Rep Sales Training – Enable Channel partners based on how they sell
  4. Enablement must be “Packaged” within a Channel Program, to drive adoption and channel revenue
  5. Sales Engagement: How channel enablement becomes revenue $

This week I will talk about talk about Natural Law #2 and difference between enabling your channel and training your channel…

(more…)

Channel Not Ready to Sell? Perhaps You are Violating One of the “5 Natural Laws of Channel Enablement”? (Part 1 of a Series)

Channel Not Ready to Sell?  First of a 5-Part Series

One of the critical success factors in GTM Program is how well a technology vendor engages with the channel to jointly sell.  The channel enablement team must face a broad set of challenges, ranging from how to onboard new partners, assure that partner sales teams, their SEs, and often their consultants have the information they need to be successful.  And these tasks need to be supported in introductory and advanced versions, for multiple products and solutions.  As if this wide-ranging charter is not enough of a challenge, “enablement” teams must deal with the inevitable tension between Sales Organizations and Field Readiness teams that train sales reps and SEs and feel that Channel is never “enabled enough” and don’t factor in that partners are not required to take vendor training (or to sell their products…).

In my experience, many of the common approaches to channel “enablement” are ineffective, and part of the many outdated, “Boxed” set of practices in the tech industry that have evolved over the years,  based on the old world of hardware-centric selling. These practices limit vendor success and revenue.  Providing proven alternatives to these types of practices is a big part of the Andrews Consulting Group focus, to help technology vendors “Climb Out of the Box”, and accelerate revenue for their products and partnerships.  Check out my post, “Are You Executing Outside of the Box? – The Checklist”,  to see see how your organization compares to these practices.

So how can technology vendors address these challenges, and drive more revenue through their channel? 

A good way to think of best practices for channel enablement is in terms of the 5 Natural Laws of Channel Enablement below. In today’s post I will talk about overall needs for channel enablement, and Natural Law #1 in more detail. (more…)

Want to Sell Solutions, But at the Velocity of Transactions: Are You Using a “Hook” to Create “Pull”? (Part 1 of a Series)

“Sales Process “is a dirty word to many technology vendors, because they interpret it to mean a slow sales approach that delays the sale of your product, and causes Reps and Sales leaders to miss their number…

As I discussed in my post, “What 3 Questions Indicate Whether You Need to Sell Solutions”, and “Are you Jumping to the Product Sale too Early (and missing revenue…), product selling works best in a few situations early in the sales cycle, and is required late in the sales cycle in nearly all tech business– but in most situations, tech vendors market and sell based on product too early in the sales cycle – causing vendors to miss revenue opportunities.

So what are proven approaches to market and sell in situations where Solutions Selling is required? That is the topic of my post today. (more…)

Marketing and Sales Messages Not Aligned? Tie Your “Message Map” to a “Solution Blueprint” (Part 5 of a Series)

Over the past year, I’ve done a continuing series on what it means to market and sell “Solutions”  Today’s post is Part 5 of the Series

I’ve talked a lot about the advantages of using “Solution” (rather than “Product” messaging to connect to customers, and drive more revenue for your products, but the question I often get sounds something like this:

“OK, I see the advantages of using Solution Messaging – What do I do now?” 

That question is the focus of my post today.

The key to messaging Solutions is a tool that I call “The Solution Blueprint”, a visual tool that helps technology vendors communicate the value of their offerings in terms of “Solutions” to customer problems – and accelerate revenue. I talked about this tool in more detail in my Solution Blueprint post. In Figure 1 below, you can see an diagram that describes the key elements of the Solution Blueprint. (more…)