Tag Archives: Alliances

Mark Tice Returns:  It’s Time For SaaS Companies To Do A Channel Check.

About three years ago, I had a conversation with an old friend that led to a post, Ten Pearls of Enterprise Software Startup Wisdom from My Friend Mark Tice.  In that (quite popular) post, I shared Mark’s top ten list of mistakes that enterprise software startups make in sales and go-to-market.  If you’ve not read it, take a look — particularly (in today’s environment) with an eye toward mistakes five through ten.

I enjoy talking with Mark because our skills and experience are complementary.  My core is marketing.  Mark’s is partners.   While we’ve both done bigger things from those foundations (e.g., Mark was a CEO and an operating partner at a PE firm), I believe you’re never quite as comfortable and fluent as you are in the area where you grew up. 

Moreover, since partners is generally considered even more of a dark art than marketing, it’s great to have a friend in the business.  When it comes to partners, the Twitter cliché few understand this is actually a reality.

Before diving into Mark’s guest post, below, I want to try and drain the swamp by defining some basics:

  • Partners should be used as the catch-all term to describe companies with whom you have one or more relationships that are presumably friendly and mutually beneficial.
  • Alliances are a type of partner relationship.  Alliances partners collaborate with you to help sell your software, but — and this is key — they do not sell your software.
  • Channels are another type of partner relationship.  Channel partners sell your software (i.e., “they take the paper”) and they may do so either working in collaboration with you (e.g., a local system integrator who does implementations and takes paper) or on their own (e.g., a software vendor who embeds your product in theirs and sells the composite).

The thing that took me years to learn is that we should classify relationships, not companies.  For example, Deloitte is one of several global systems integrators (GSIs).  GSI is a type of company; it describes their business.  It is not a relationship type.  In fact, a software vendor may have several different partner relationships with a GSI.  For example,

  • A North American co-sell relationship (alliance) whereby the GSI agrees to place the vendor on their recommended solutions list, work with them to sell and implement customers, and perhaps do some joint marketing programs.
  • They may have a global embedded resale relationship (channel) with the GSI’s Financial Services practice where the software vendor’s product is sold as part of a bigger vertical solution, with no involvement from the vendor.
  • There may be a services relationship (channel) where the GSI agrees to use the vendor’s strategic consultants, acquired at a wholesale price, blended into the team responsible for a project (and in order to ensure there is specific product expertise on the team).
  • There could be a value-added resale relationship (channel) in certain regions (where the vendor does not yet have a presence) where the GSI sells the software and associated services, acting as a geographic distributor in those regions.

Thus saying, “we have a GSI relationship with Deloitte,” as you can hopefully see, doesn’t make a lot of sense. GSI is a type of company. We can and often do have several different relationships with a single GSI.

To summarize, at a high level there are two types of partner relationships: channels and alliances. Channels sell software, alliances don’t.

Note that most people are not this rigorous in their thinking and tend to use partner, channel, and alliance as synonyms and refer to companies using relationship types — and confusion can sometimes result.

With those basics in place, let’s move on to Mark’s top five recommendations for how SaaS companies can do a “channel check” — well, I suppose he means partner check, but channel check does have that alliterative ring to it.

Over to Mark 🡪

The other day Dave and I were discussing how companies are adapting to the many changes in today’s landscape and I honed in on one of my favorite topics, partnerships. 

For healthy SaaS companies, 25 to 50% of ARR is positively influenced in some way by partners.  Some resell.  Some recommend.  Some create a vacuum in the market that can be exploited (e.g., technology alliance partners). And yet, in most SaaS companies, the person looking after partners has an office that’s the equivalent of Harry Potter’s bedroom underneath the stairs and their phone only rings when the company needs a quote for a press release or sponsors for the user conference.  Compound this general lack of attention with reductions in headcount and tough economic times, and partners can devolve from an afterthought to a never-thought. 

As a former channel sales manager, strategic partners executive, CEO, and operating partner at a private equity (PE) firm, I talk with a lot of companies (and investors) about how to leverage partners to grow SaaS businesses.  Here’s my list of top five partner-related issues that you can use to do a “channel check” on your SaaS company. 

Just for fun, we’ll do it in countdown format.

5.  Enablement.  More often than you might expect, partners depend not on your partner program, but on relationships with individual sales reps or marketers to get the latest news, slide decks, competitive information, and collateral. The simple fix is to spin up a portal that gives partners self-service access to basic sales tools and training.  Yes, you should be careful to keep confidential information confidential — and that might require a few edits here and there — but providing easy access to the latest and greatest information will really improve the health and abilities of your partners.

4. International.  We could dedicate the entire blog post to going international, but we’ll keep this brief by focusing on an example I recently found working with a $50M SaaS company.  They were the leader in the US market but in fourth place internationally, so I asked why they weren’t paying more attention to the international opportunity.  They answered that they needed to focus on getting another few points of market share in the US and that they viewed international as “tactical revenue.”  Now I’m not sure what they meant by tactical revenue [1], but my take is any revenue that we can get — without introducing new core product requirements [2] — is good revenue and if we can’t get it ourselves, then why not use partners to get it?  Moreover, geographic distribution is one of the cleanest forms of partnership because you can set up distributors to entirely avoid dreaded channel conflicts [3].

But in this company, the person running partners was an entry-level marketer who lacked both the experience and the influence to drive the business. They’d signed partnerships with geographic exclusivity, partners were pricing far below market, and (despite the low prices) their win rates were far below those of the direct sales force.  The worst example was when a partner who had long-term exclusivity in a major country called to inform the company that they were handing off their business to their son because he was too old to keep working in construction and who had zero software experience.  (Guess we won’t be selling anything in that geography for a while.)

Don’t do this.  Instead,

  • Leverage geographic distributors to sell your software in low-hanging-fruit countries [4].
  • Sign de facto preferred, but not exclusive distribution relationships.
  • Pick the de facto preferred partner based on who presents the best market development plan for the geography.
  • Hire a professional partners or channels manager to oversee the distributor relationships.

3. Pricing.  There are 3 keys to channel partner pricing. First, make sure the price list is appropriate for the intended market. This is most obvious in the international example above, but it also applies domestically — e.g., if partners are representing your company in the mid-market, be sure your pricing is appropriate for the value you deliver and your position in that space.  Second, be sure your pricing includes all of the elements required for success (e.g., starter kits).  Don’t give partners a partial price list that leaves customers hanging in deployment or solution development.  Third, always tie a channel partner’s discount to your price list and not net revenue.  (Or, if you have to use net revenue, then make sure there’s a sufficiently high floor price in the contract [5].)  Royalties based on net revenue almost always encourage partners to discount your product disproportionately and shift the revenue to the higher-margin portions of their solutions. 

2. Sales alignment and compensation.  Getting the right alignment and compensation structure requires a Goldilocks solution.  Paying a kicker to reps when partners resell may cost you additional commissions and lost ARR if there was an opportunity to take the deal direct.  But refusing to pay a finder’s fee when a partner brings you a big deal may cost you not only that big deal but also drive the partner (and all their other deals) to a competitor. Getting clear on how you want the sales team to interact with partners and tuning sales compensation to match is key.  It’s hard work.  There is no one right answer.  And there will always be conflicts — the goal isn’t to eliminate them, but to manage them.

By the way, if you haven’t adjusted your sales and partner compensation models for a few years, then they’re unlikely to be “just right” today.  Run a review. 

1. Partner strategy.  Most SaaS companies treat partners as tactical extensions to their business – necessary evils on bad days and nice-to-haves on good ones. The key is to get clarity on what you want from partners, identify and recruit the right partners on the right business terms, put together the right enablement program, and then execute like crazy.

The strategy and elements underneath it should be revisited once a year as your business evolves. You change over time and so do your partners.  You need to revisit strategy and relationships accordingly.

What should you do to make sure you’re maximizing your partner ecosystem?  Remember these three principles:

  • Channels are about optimizing market reach versus margin. 
  • Partnerships shouldn’t be an afterthought. Tending to the basics of partnerships should be part of business as usual.
  • You get the channels/partnerships you deserve.

There’s a simple test to see if your partner strategy and program are sound. Hop on a Zoom (or get in a conference room) with your CEO, VP Sales, VP Marketing, and head of partnerships.  Ask everyone to take five minutes to write down a short description of your partner strategy and list your top 3 partners. Then spend 30 to 60 minutes talking about your answers, how well they align, where they don’t align (you might be surprised here), and what you want to do to get on the same page.  Agree on a new set of goals and then set OKRs accordingly.

Once you get more deliberate about partners, there are three things to keep in mind:

  • The 80/20 rule definitely applies to partners. You don’t have to do anything extraordinary to make the business thrive. Do the basics and do them well and that will almost always lead to success.
  • If your company is challenged to sell direct, fix that first. Don’t fall into the trap of thinking, “we can’t sell our products, so we’ll get partners to do it for us.”  It never ends well [6].
  • Most SaaS companies will exit to larger software companies and the best exits often start with partnerships. It’s never too early to partner with big players and form executive-level relationships so when the acquiring General Manager hopefully signs up to pay above-market price for your company, they’ll do so with the full confidence that you can deliver.

# # #

Notes (by Dave)

[1] They probably meant non-strategic or opportunistic revenue which is a reasonable concept when considering target markets.  That is, if you have a strategic focus on financial services, that revenue is strategic in the sense that you are actively looking for more of it and thus eager to hear about product requirements that will enhance the product for other financial services customers.  But, at the same time, if a pharma company wants to buy the product “as is,” then you should be happy to sell it to them.  With strategic revenue, you can entertain new product requirements discussions.  With opportunistic revenue, sales need to sell what’s on the truck.

[2] And if the product is properly built, localization isn’t really a core product requirement.  Moreover, localization isn’t even always required.

[3] By using either contractually exclusive (undesirable) or de facto preferred partners in any given geography.  

[4] That is, where it’s easy, where localization requirements are limited, and you don’t need to build language skills within your company to work with local staff.

[5] They can always call to request a special discount below the floor.  In practice, this usually acts as a highly desirable big deal detector.

[6] Amen to that.

Mark is currently working as an advisor.  If you want to reach him, shoot him a LinkedIn message or Inmail. If you have questions or comments, you can also post them as blog comments here and I’ll make sure Mark sees them.

The Four Sources of Pipeline and The Balance Across Them

I’ve mentioned this idea a few times of late (e.g., my previous post, my SaaStock EMEA presentation) [1] and I’ve had some follow-up questions from readers, so I thought I’d do a quick post on the subject.

Back in the day at Salesforce, we called pipeline sources “horsemen,” a flawed term both for its embedded gender pronoun and its apocalyptic connotation.  Nevertheless, for me it did serve one purpose — I always remembered there were four of them.

Today, I call them “pipeline sources” but I’ve also heard them referred to as “pipegen sources” (as in pipeline generation) and even “revenue engines” which I think is an over-reach, if not a well intentioned one [2].

While you can define them in different ways, I think a pretty standard way of defining the pipeline sources is as follows:

  • Marketing, also known as “marketing/inbound.”  Opportunities generated as a result of people responding to marketing campaigns [3].
  • SDRs, also known as “SDR/outbound,” to differentiate these truly SDR-generated oppties from marketing/inbound oppties that are also processed by SDRs, but not generated by them [4].
  • Alliances [5].  Opportunities referred to the company by partners, for example, when a regional system integrator brings the company into a deal as a solution for one of its customers.
  • Sales, also known as “sales/outbound,” when a quota-carrying salesrep does their own prospecting, typically found in named-account territory models, and develops an opportunity themselves.

Product-led growth (PLG) companies should probably have a fifth source, product, but I won’t drill into PLG in this post [5A].

Attribution issues (i.e., who gets credit when an opportunity is developed through multiple touches with multiple contacts over multiple quarters [6] [7]) are undoubtedly complex.  See note [8] not for the answer to the attribution riddle, but for my advice on best dealing with the fact that it’s unanswerable.

Now, for the money question:  what’s the right allocation across sources?  I think the following are reasonable targets for a circa $50M enterprise SaaS company for mix of oppties generated by each source (all targets are plus-or-minus 10%):

  • Marketing:  60%
  • SDR/outbound:  10%
  • Alliances:  20%
  • Sales/outbound:  10%

Now, let’s be clear.  This can vary widely.  I’ve seen companies where marketing generates 95% of the pipeline and those where it generates almost none.  SDR/outbound makes the most sense in a named-account sales model, so I personally wouldn’t recommend doing outbound for outbound’s sake [9] [10].  Alliances is often under 20%, because the CEO doesn’t give them a concrete oppty-generation goal (or because they’re focused more on managing technology alliances).  Sales/outbound only makes sense for sellers with named-account territories, despite old-school sales managers’ tendency to want everyone prospecting as a character-building exercise.

And let’s not get so focused on the mix that we forget about the point:  cost-effective opportunity generation (ultimately revealed in the CAC ratio) with broad reach into the target market.

Now, for a few pro tips:

  • Assign the goal as a number of oppties, not a percentage.  For example, if you want 60% from marketing and have an overall goal of 100 oppties, do not set marketing’s goal at 60%, tell them you want 60 oppties.  Why?  Because if the company only generates 50 oppties during the quarter and marketing generates 35 of those, then marketing is popping champagne for generating 70% of the oppties (beating the 60% goal), while they are 15 oppties short of what the company actually needed.
  • Use overallocation when spinning up new pipeline sources.  Say you’ve just created an RSI alliances team and want them generating 10% of oppties.  By default, you’ll drop marketing’s target from 70% to 60% and marketing will build a budget to generate 60% (of say 100) oppties, so 60 oppties.  If they need $3K worth of marketing to generate an oppty, then they’ll ask for $180K of demandgen budget.  But what if alliances flames out?  Far better to tell marketing to generate 70 oppties, give them $210K in budget to do so and effectively over-assign oppty generation to an overall goal of 110 when you need 100.  This way, you’re covered when the new and presumably unpredictable pipeline generation source is coming online [11].

# # #

Notes

[1] Video forthcoming if I can get access to it.

[2]  The good intentions are to keep everyone focused on revenue.  The over-reach is they’re not really engines, more fuel sources.  I am a big believer in the concept of “revenue engines,” but I use the term to refer to independent business units that have an incremental revenue target and succeed or fail in either an uncoupled or loosely coupled manner.  For example, I’d say that geographic units (e.g., Americas, EMEA), channels (e.g., OEM, VAR, enterprise sales, corporate sales), or even product lines (depending on the org) are revenue engines.  The point of having revenue engines is diversification, as with airplanes, they can sputter (or flame-out) independently.  (As one aviation pioneer was reputed to have said:  “why do I only fly four-engine planes across the Atlantic?  Because they don’t make five-engine planes.”)

[3]  I will resist the temptation to deep dive into the rabbit hole of attribution and say two things:  (a) you likely have an attribution mechanism in place today and (b) that system is invariably imperfect so you should make sure you understand how it works and understand its limitations to avoid making myopic decisions.  For example, if an oppty is created after several people downloaded a white paper, a few attended a webinar, an SDR had been doing outreach in the account, the salesperson met a contact on the train, and a  partner was trying to win business in the account, who gets the credit?  It’s not obvious how to do this correctly and if your system is “one oppty, one source” (as I’d usually recommend over some point allocation system), there will invariably be internal jockeying for the credit.

[4]  SDRs are often split inbound vs. outbound not only to ease the tracking but because the nature of the work is fundamentally different.  Hybrid SDR roles are difficult for this reason, particularly in inbound-heavy environments where there is always more inbound work to do.

[5]  My taxonomy is that there are two types of “partners” — “channels” who sell our software and “alliances” who do not.  In this case (where we’re talking about pipeline generation for our direct salesforce), I am speaking of alliance partners, who typically work in a co-sell relationship and bring the company into oppties as a result.  In the case of channels, the question is one of visibility:  are the channels giving us visibility into their oppties (e.g., in our CRM) as you might find with RSIs or are they simply forecasting a number and mailing us a royalty check as you might find with OEMs.

[5A]  Product meaning trials (or downloads in open source land), which effectively become the majority top-of-funnel lead source for PLG companies.  This begs the question:  who drives people to do those trials (typically marketing and/or word of mouth)

[6]  One simple, common example:  a person downloads a white paper they found via through a search advertisement five quarters ago, ends up in our database, receives our periodic newsletter, and then is developed by an SDR through an outreach sequence.  Who gets the credit for the opportunity?  Marketing (for finding them in the first place and providing a baseline nurture program via the newsletter) or SDR/outbound (for developing them into an oppty)?   Most folks would say SDR in this case, but if your company practices “management by reductio ad absurdum” then someone might want to shut down search advertising because it’s “not producing” whereas the SDRs are.  Add some corporate politics where perhaps sales is trying to win points for showing how great they are at managing SDRs after having taken them from marketing and things can get … pretty icky.

[7] Another favorite example:  marketing sponsors a booth at the Snowflake user conference and we find a lead that develops into an opportunity.  Does marketing get the credit (because it’s a marketing program) or alliances (because Snowflake’s a partner).  Add some politics where the alliances team has been seen as underperforming and really needs the credit, and things can get again yucky and confusing, leading you away from the semi-obvious right answer:  marketing, because they ran a tradeshow booth and got a lead.  If you don’t credit marketing here, you are disincenting them from spending money at partner conferences (all I, no RO.)  The full answer here is, IMHO, to credit marketing with being the source of oppty, to track influence ARR by partner so we know how much of our business happens with which partners, and to not incent the technology alliances group with opportunity creation targets.  (Oppty creation, however, should be an important goal for the regional and/or global system integrator alliances teams.)

[8]  My recommended solution here is two-fold:  (a) use whatever attribution mechanism you want, ensuring you understand its limitations, and (b) perform a win-touch analysis at every QBR where a reasonably neutral party like salesops presents the full touch history for a set of representative deals (and/or large) deals won in the prior quarter.  This pulls everyone’s heads of our their spreadsheets and back into reality — and should ease political tensions as well.

[9]  Having an SDR convince someone to take a meeting usually results in a higher no-show rate and a lower overall conversion rate than setting up meetings with people who have engaged with our marketing or our partners already.

[10]  Put differently, you should stalk customers only when you’re quite sure they should buy from you, but they haven’t figured that out yet.

[11] And yes there’s no free lunch here.  Your CAC will increase because you’re paying to generate 110 oppties when you only need 100.  But far better to have the CAC kick up a bit when you’re starting a new program than to miss the number because the pipeline was insufficient.