Site icon Kellblog

What a Pipeline Coverage Target of >3x Says To Me

I’m working with a lot of different companies these days and one of the perennial topics is pipeline.

One pattern I’m seeing is CROs increasingly saying that they need more than the proverbial 3x pipeline coverage ratio to hit their numbers [2] [3].  I’m hearing 3.5x, 4x, or even 5x.  Heck — and I’m not exaggerating here — I even met one company that said they needed 100x.  Proof that once you start down the >3x slippery slope that you can slide all the way into patent absurdity.

Here’s what I think when a company tells me they need >3x pipeline coverage [4]:

# # #

Notes

[1] e.g., from marketing, sales, SDRs, alliances.  I haven’t yet blogged on this, and I really need to.  It’s on the list!

[2] Pipeline coverage is ARR pipeline divided by the new ARR target.  For example, if your new ARR target for a given quarter is $3,000K and you have $9,000K in that-quarter pipeline covering it, then you have a 3x pipeline coverage ratio.  My primary coverage metric is snapshotted in week 3, so week 3 pipeline coverage of 3x implies a 33% week three pipeline conversion rate.

[3] Note that it’s often useful to segment pipeline coverage.  For example, new logo pipeline tends to convert at a lower rate (and require higher coverage) than expansion pipeline which often converts at a rate near or even over 100% (as the reps sometimes don’t enter the oppties until the close date — an atrocious habit!)  So when you’re looking at aggregate pipeline coverage, as I often do, you must remember that it works best when the mix of pipeline by segment and the conversion rate of each segment is relatively stable.  The more that’s not true, the more you must do segmented pipeline analysis.

[4] See note 2.  Note also the ambiguity in simply saying “pipeline coverage” as I’m not sure when you snapshotted it (it’s constantly changing) or what time period it’s covering.  Hence, my tendency is to say “week 3 current-quarter pipeline coverage” in order to be precise.  In this case, I’m being a little vague on purpose because that’s how most folks express it to me.

[5] In my parlance, slip means the close date changes and derail means the project was cancelled (or delayed outside your valid opportunity timeframe).  In a win, we win; in a loss, someone else wins; in a derail, no one wins.  Note that — pet peeve alert — not making the short list is not a derail, but a loss to as-yet-known (so don’t require losses to fill in a single competitor and ensure missed-short-list is a possible lost-to selection).

[6] Where sales management should be scrubbing the close date as well as other fields like stage, forecast category, and value.

[7] To paraphrase James Mason in The Verdict, salesreps “aren’t paid to do their best, they’re paid to win.”  Not just to have a 33% odds of winning a deal with a three-vendor short list.  If we’re really good we’re winning half or more of those.

[8] The nuance here is that sales did accept the pipeline so it’s presumably objectively always above some quality standard.  The reality is that pipeline acceptance bar is not fixed but floating and the more / better quality oppties a rep has the higher the acceptance bar.  And conversely:  even junk oppties look great to a starving rep who’s being flogged by their manager to increase their pipeline.  This is one reason why clear written definitions are so important:  the bar will always float around somewhat, but you can get some control with clear definitions.

[9] In such cases, companies will often “grandfather” the oppty into the rep’s new territory even if it ordinarily would not have been included.

[10] Which it all too often doesn’t.

Exit mobile version