Category Archives: Pipeline

The Ten Most Read Kellblog Posts in 2024

It’s always fun to go back and look at my stats, and my best-of page (which amazingly came in at #11) is getting sufficiently long that I need to find additional summarization mechanisms.

So this year, I thought I’d share the top-ten Kellblog posts of 2024 (year to date) regardless of the year in which they were written.

  1. Kellblog predictions for 2024. My tenth annual predictions post topped the list. I’m already working on my 2025 predictions which I hope to publish before the end of December.
  2. What it really means to be a manager, director, or VP. Written in 2015, this continues to be a top post every year and, as a result, is the all-time #1 Kellblog post.
  3. The top 7 marketing metrics for a QBR or board meeting. A 2023 post I wrote after a friend asked: “blank slate, what 5 metrics would you present to the board?” I cheated and did 7.
  4. The key to dealing with senior executives: answer the question. Another perennial favorite, this 2012 post is the one people mention to me the most. Think: “I forwarded that to my team!”
  5. The one question to ask before blowing up your customer success team. The first 2024 post on the list, I wrote this to encourage people to take a minute before Slootmanizing their CS department.
  6. Demystifying the growth-adjusted enterprise value to revenue multiple. This 2024 post explains the metric and, in a quest for syllabic parsimony, suggests naming it the ERG ratio, after the PEG ratio.
  7. Go-to-market troubleshooting, let’s take it from the top. If you’re chronically missing new bookings plan, then read this 2024 post and listen to the SaaS Talk episode that covers it.
  8. Target pipeline coverage is not the inverse of win rate. I saw one too many people invert their win rate to set pipeline coverage targets and wrote this 2024 post to show them the error of their ways.
  9. Simplifiers go far, complexifiers get stuck. This classic from 2015 starts with a poignant joke. Question: What does a complexifier call a simplifier? Answer: Boss. Learn why by reading it.
  10. Playing to win vs. playing to make plan: the two very different worlds of Silicon Valley. This 2024 post explores how the valley has fractured into somewhat distinct VC- and PE-backed worlds.

Keep an eye out for my 2025 predictions later this month. And thanks for reading.

Board-Level Questions On The Marketing Budget

Since many of you are in the midst of presenting your annual marketing budgets to your CEO, CFO, and board, I thought I’d write a quick post to remind people what board members actually care about when it comes to the marketing budget.

I understand that, in the throes of budgeting, CMOs can get dragged down into a lot of detail. Diving to a deep level of detail is important, because that’s usually the difference between a real plan and a basic budget.

But, remember people: when we’re talking to the board, we need to be board level. Otherwise, they’re going to mistake you for the VP of marketing operations. (Was the CMO out sick today?)

The board doesn’t want:

  • Vapid marketing cheerleading, particularly if the company is missing plan
  • Overwhelming volume (e.g., 28 slides with a 15-slide appendix)
  • “Banker slides” that overload them with numbers
  • Recycled QBR slides, built for a different audience and purpose

While I’m all in favor of a few introductory slides that present current-year marketing performance, they should be sober and matter of fact. Too often, when CMOs try to present such slides, they end up sounding like this:


So what does the board want?

  • A short deck, maybe 5-8 slides (with a slide on 2024 performance, a list of key objectives, an organization chart, and an overall budget)
  • Some slicing-and-dicing of the demandgen budget that discusses both coverage and efficiency
  • Slides that are custom built for the board audience

And what are the questions that are actually on their mind?

  • What are marketing’s key objectives for the year? Do they align to corporate strategy? Do they align to sales? Are they the right objectives?
  • Where did the budget come from?  Was it trended off last year or built from a bottom-up model?
  • If it was trended, is the total spend growing slower than revenue? Could it be growing slower still? Should it be growing faster?
  • If it was built off a model, who built the model? Are they any good? Is there a single model for sales, marketing, and finance, or is there a cage fight behind the scenes? Can we hit plan if we rely on this model?
  • What does marketing spend look like as a percent of revenue? As a percent of new ARR bookings? Are those percents going down over time? How do they compare to benchmarks?
  • What is our CAC ratio and CAC payback period? How much is marketing contributing to each? Is marketing’s relative contribution going down or up?
  • And if they’re good, what is the sales/marketing expense ratio and how has that trended over time? How does it compare to industry benchmarks? On whose back are we placing the GTM efficiency monkey, and what risks does that entail?
  • Where does the CMO want to spend the marketing money?  How much is going to people vs. programs vs. infrastructure? How has that mix changed over time?
  • Is there any marketing money outside marketing? Does the CEO carry a pet-projects budget for billboards? Do we run a massive user conference? If that money’s not in the budget I’m looking at, then where is it?
  • Do the CRO and CMO seem aligned on the marketing budget and priorities? If not, where do they differ? Does the CMO seem caught in the middle between CEO and CRO priorities?
  • Does the company have an overall model for who generates how much pipeline? That is, pipeline generation targets by pipeline source (aka, “horseman”) by quarter?
  • Has each pipeline owner accepted clear responsibility for their portion of the pipeline and a have a clear plan to deliver it?
  • Does marketing have a plan for how they are going to spend the proposed demandgen dollars? Can I compare that plan to our historical performance to see if it’s realistic?
  • Is marketing focused solely on pipeline generation or do they also worry about pipeline coverage?
  • Does the marketing plan show pipe/spend and cost/oppty ratios? How does the plan compare to our historical performance? Are we increasing efficiency? Is that spreadsheet magic or are there actual reasons why those ratios should increase?
  • Where are we looking at using AI to improve marketing efficiency? What are we experimenting with? How big an improvement can we expect? Have we looked at AI SDRs?
  • How much money is going into squishy things like branding? Can the CMO defend that proposed expense? Do the CEO and CRO agree that this squishy spend is a priority?
  • Can I trust the CMO to execute this plan? If we give them what they ask, will they deliver on the pipeline generation goals and key objectives?

I’m not suggesting that you proactively answer each of these questions in your eight slides. But these are the questions you should be ready for. In terms of how I’d map these to slides:

  1. Current-year marketing performance. Metrics on the left, OKRs on the right.
  2. Next-year proposed OKRs.
  3. Next-year proposed organization chart.
  4. Top-down S&M analysis, e.g., CAC, CPP, sales/marketing expense ratio, history, benchmarks.
  5. Top-down marketing budget analysis, e.g., spend by people/programs/infra, headcount, total cost/oppty.
  6. Overall pipegen and coverage model, e.g., targets by horseman, how pipegen ensures coverage
  7. Demandgen budget analysis, e.g., spend by channel, pipe/spend, DG cost/oppty, coverage.
  8. Menu of 3-5 optional programs with benefits and costs — i.e., try to sell the top ideas you couldn’t fit into the baseline plan in a quest for incremental money.

(Edited 12/2/24 at 9:04am to include last section on slide mapping.)

Why Great Marketers Look at Pipeline Coverage, Not Just Pipeline Generation

“How’s it going at StartCo?” I asked.

“Great,” the CMO replied. “We hit 105% of our pipeline generation (pipegen) goals last quarter, and with a healthy pipe/spend ratio of above 10.”

“Nice,” I said. “How is sales doing?”

“Oh, that’s another matter,” the CMO said. “They landed at 82% of new logo ARR plan.”

Quick: what’s wrong with this conversation?

Answer: if the purpose of marketing is to make sales easier, marketing cannot be “doing great” when sales is 82% of plan. Period. Always.

What’s driving this problem? Part of it is me-, me-, me-oriented metrics like pipegen. Or more specifically, pipegen from marketing, which is about how marketing did relative to its pipeline generation goals. But let’s remember the point of pipeline is to ensure sales has a shot at success every quarter. And that marketing is not the only pipegen game in town. And that different pipegen sources have different conversion rates (or, as I like to say, nutrient density). Oh, and even if the entire pipegen machine is firing on six cylinders, that we can still end up with pipeline shortages.

What’s the underlying problem? Call it myopia, parochialism, or stovepiping. Or (as my English friends might say) that marketing is simply missing the bloody point.

Let’s use a table to make things more concrete.

The first block shows that the company, with one small exception, is generally delivering on its pipegen targets and that they hit 105% of plan last quarter.

The second block shows that our friends in sales are struggling. Sales performance has consistently decreased for the past six quarters, from beating plan with 109% to coming up well short at 82%.

The third block shows that while pipeline conversion has been pretty stable at around 34%, starting pipeline coverage has been steadily deteriorating from 3.1x to 2.4x. Most companies can’t make plan when starting with 2.4x coverage. It’s clear that we have a starting pipeline problem.

But the fourth block shows that while the performance across pipeline sources is somewhat varied, that we don’t have an overall pipegen problem. While SDRs and sales are struggling, their contributions are a small part of the mix (10% each) and the gap is more than offset by above-target contributions from marketing and alliances. Moreover, because alliances pipeline usually converts at a higher rate than SDR- or sales-generated pipeline, the mix change should impact yield favorably.

So, what the heck is happening? How are we consistently beating our pipegen targets, but consistently behind on starting pipeline? Three thoughts come to mind:

  • Our model is wrong. We built a model for pipeline generation targets that relied on assumptions about win, loss, and slip rates as well as pipepline expansion and shrinkage. Somewhere that model is deviating enough from reality that we are hitting pipegen goals but missing starting pipeline coverage goals. Maybe we made mistakes in the first place or maybe reality has drifted away from that model. But let’s remember that God didn’t send us the model on stone worksheets and that hitting model-driven targets is not the point. Generating sufficient pipeline coverage is.
  • The most common reasons for model drift are decreased win rates, increased average sales cycles, and decreased average deal sizes. But here we’re seeing healthy and consistent week 3 pipeline conversion which makes me want to look elsewhere for an explanation.
  • This is actually a tricky situation to diagnose. We’re hitting increased pipegen targets, but starting pipeline is flat. The normal diagnosis would be increased loss and/or slip rates, but starting pipeline conversion is both healthy and consistent. Hum. This leads me to think that timing is off — while we’re generating the right amount of pipeline, not enough of it is landing in next quarter, suggesting that buying timeframes may have lengthened. This is one reason why I care so much about pipeline segmented by timeframe and not just rolling four quarters or all-quarters (aka tantalizing) pipeline.

Back to our main argument: the point of the entire pipegen machine is not to beat model-driven pipegen targets. It’s to give a sales a chance to make the number each quarter. And that is far better measured by starting pipeline coverage than by pipeline generation. And that’s why great marketers look starting pipeline coverage first and then pipeline generation after that.

Good marketers say, “I hit my marketing pipegen goals. Go me!” Great marketers say, “We helped tee-up sales for success this quarter. Go us!”

And the best marketers don’t think their work is done at stage 2 — they know there’s plenty marketing can do both to increase close rates down the funnel and expansion in the bow tie thereafter.

But that’s the subject of another post.

Go-To-Market Troubleshooting:  Let’s Take It From The Top

So, you’re missing plan and revenue growth is down.  Well, welcome to the club.  You’re certainly not alone in these times. 

In this post, I’ll discuss what you can do about it – specifically, how you can apply some of the ideas I’ve discussed in Kellblog to troubleshoot go-to-market (GTM) performance.  I’ll focus on troubleshooting new business (“newbiz”) ARR plan attainment, the area where most companies seem to be having the most trouble [1].

Don’t Knee-Jerk Blame the Plan

The immediate temptation when missing plan is to blame the plan.  “It’s not realistic.”  “It was driven by the fundraise, not the bottom-up.”  But blaming plan is a poor place to start for two reasons.                        

First, you signed up for the plan when you submitted it to the board for approval.  Next time, if you don’t believe in a proposed plan, don’t be so quick to fold in the face of internal pressure.  Remember the old Fram oil filter commercial and think, “you can fire me now or fire me later” so if you’re asking me to sign up for a plan that I don’t think I can achieve, you might as well fire me now [2].  The need to make such difficult judgments is the price of admission to the sales leadership role.  Cop out at your own peril, because they will indeed fire you later.

Second, when you follow the approach in this post, if the plan is unachievable it will emerge from the data.  So, bite your tongue, avoid any initial temptation to blame plan, and instead go look at the funnel.

The Two Questions and Two Metrics

Recall in this post, I argued that you should ask two questions when you’re missing plan.   Every quarter: 

  1. Are we giving sales the chance to hit the number?
  2. Is sales converting enough of the pipeline to hit the number?

That’s it.  Everything comes down to these two questions.  No matter the root problem, it will be revealed in answering them.  Remember, the way to make plan for twelve consecutive quarters is one at a time.  So why not focus on next quarter?  And if you’re chronically missing plan, why not make a steady-state assumption to simplify things further? [3]

Starting with the above two questions makes things simple by breaking the entire funnel in two.  Simplifying the problem is important because you can quickly and irrecoverably descend into analytical quicksand.  When I first meet them, many companies are neck-deep in such quicksand, comparing dashboard clips, reports, and spreadsheets derived from different systems, lost in an endless sea of non-footing detail, having completely lost the business forest for the salesops trees.

Note that neither of the two above questions assigns blame.  As a consultant, I have the distinct advantage of not caring where the trouble is, making me a disinterested party, de facto impartial.  I encourage CXOs to adopt a similar approach, simply stating facts, avoiding blame (e.g., inferred causes), and acting as dispassionate analysts when analyzing GTM problems.  While you will eventually need to ask why you have certain problems, it’s always best to start with simple statements of fact, get agreement on them, and build from there.  For example:

  • “We consistently start quarters with insufficient pipeline coverage” is a blameless statement of fact.  It does not say whose job it is to generate pipeline (if that’s even been detailed out across sources) or why they are failing to do so.
  •  “We are converting a below-normal percentage of our week 3 pipeline,” less obviously, is also a blameless statement of fact.  While it’s clearly the job of sales to convert pipeline, the statement makes no assertion as to why we are seeing abnormally low conversion rates (e.g., pipeline quality, change in competitive market, sales execution).

When it comes to metrics, the first of the above questions is measured by pipeline coverage, more precisely week-3 pipeline coverage [4] [5]. The second is measured by a conversion rate, specifically week-3 pipeline conversion rate.  Notably, this is not a win rate, and please read this post to ensure that you understand why.

Are We Giving Sales a Chance to Hit the Number?

Make a chart like this one to answer this question.

Here you see, for newbiz ARR for the trailing nine quarters, week 3 pipeline dollars, week 3 pipeline coverage (pipeline/plan), ARR booked, week-3 pipeline conversion, and the pipeline coverage target implied by the week-3 conversion rate (i.e., its inverse).  Pipeline conversion rates are more interesting when viewed in conjunction with plan attainment, so I’ve added ARR plan and plan attainment as well. 

Analyzing this chart, we can see a few things:

  • From 1Q22 through 1Q23 we converted about 33% of the pipeline
  • We were also consistently hitting plan in that timeframe
  • Starting 2Q23 we started with only 2.3x coverage, converted a healthy 40% of it, but still came up short, at 91% of plan. 
  • That rough pattern continued in 3Q23 and 4Q23
  • 1Q24 started with the weakest coverage in the past nine quarters (1.9x)
  • While sales is forecasting record conversion of that pipeline (45%), we are nevertheless forecasting to land at only 86% of plan
  • I’m not sure I believe the forecast because 45% conversion is borderline unrealistic and could simply be the CRO trying their best to hold the line

I conclude that this company is starting with insufficient pipeline.  That is, they’re not giving sales a chance to hit the number.  How do I conclude that?

  • By comparison to pipeline coverage benchmarks.  3.0x is the typical pipeline coverage goal and you’ll note that in the good times (1Q22 through 1Q23) we consistently started with 3.0x+ and we consistently made plan. 
  • By comparison to pipeline conversion benchmarks.  33% is a standard conversion rate.  Here we are running at 40%+, which is best-in-class conversion.  Pipeline conversion is not the problem.
  • More importantly, by comparison to ourselves.  In our recent history, we consistently made plan when we started with 3.0x+ coverage and missed it when we started with 2.3 to 2.4x.  This quarter (1Q23) we’re starting with 1.9x, forecasting record conversion, and still only 86% of plan.

The solution to the insufficient pipeline problem is, unsurprisingly, to make a plan to generate more pipeline.

Here are some of the high-level steps in making that plan:

  • Define pipeline generation targets across the four major pipeline sources.  It’s surprising how many companies don’t start with this basic step.  For bonus points, over-allocate the goals to target 110% of what you need. [6]
  • I prefer to set these targets by opportunity count, not pipeline dollars, because I think it’s more visceral and less easily gamed [7].
  • Do a cost/oppty analysis across your pipeline sources to get an idea of how much money any given pipeline source (e.g., alliances, demandgen) would need to create, for example, 20 more oppties next quarter.  Remember to focus on variable, not average, cost [8].
  • Be sure to check with the leader of each pipeline source on their ability to absorb extra money to generate more pipeline.  If you have 12 SDRs reporting to one manager, they may need to bring in another manager before hiring 3 more SDRs.  Alternatively, sellers may have extra time on their hands and the ability to put more time into outbound.  Alliances may have a hot candidate they want to hire, but no open headcount, and could execute quickly if one were opened.  It’s not just about money; it’s about the ability to productively spend it.
  • Accept that you may be overallocated to sales versus pipeline generation.  In this case, the best solution might well be to terminate the bottom N sellers and convert the newly liberated budget to pipeline generation — so that everyone else has a chance at success.  This is painful, but sometimes necessary, and after you’ve had to do it once, you’ll be more careful to plan holistically in the future.

This all goes without saying that no pipeline analytics will work if you lack basic pipeline discipline – i.e., if you don’t have clear definitions for stages, close dates, oppty values, and forecast categories, and if you don’t regularly enforce them via periodic pipeline scrubs.

The Floating Bar Problem

Before diving into pipeline conversion, let’s address a special case of insufficient pipeline:  one where the pipeline initially looks sufficient but burns off at an above-average rate across the quarter.  You can see this by looking weekly at to-go pipeline coverage.

What’s usually happening in these cases is that some material percentage of your week-3 pipeline is effectively fake.  This happens because, when pipeline is scarce and if sellers are under pressure to each carry 3x coverage [9], they will take lower-quality opportunities into their pipeline.  For example, long-shot oppties that appear rigged for the competition, immature oppties where sellers hope to create a buying timeline, or self-nurture leads that may only become real oppies in the future.

I call the tendency to work on lower quality oppties in tough times, the “floating bar problem” because sales silently lowers (or in good times, raises) the bar for admission into the pipeline.  This is insidious because the result is fake pipeline that creates an illusion of coverage which disappears as the quarter progresses.

The solution to his problem is simple in theory, but hard in practice.

  • Sales management needs to hold the line on what gets into the pipeline, applying the same standards in tough times as good ones.
  • If sales management wants to allow sellers to work on low probability “oppties,” that’s fine but, well, get them out of the opportunity management system.  Use tasks to track work.  But only promote a lead to an oppty when it meets the standard for being an oppty.

If, for example, SDRs are passing low quality stage-1 oppties to sales that should not show up in the numbers as a reduced pipeline conversion rate.  Instead, it should show up in a higher stage-2 rejection rate.  This point is completely lost on most sales managers so please make sure you understand it.  If you maintain pipeline discipline, lower quality oppties should show up not as a reduced stage-2 to close rate, but as an increased stage-2 rejection rate.  And pipeline discipline starts at stage 2 – where sales decides to accept or reject oppties.  It’s wrong to accept sub-standard oppties, pollute the oppty management system with fake pipeline, convert little of it, miss plan, and wreck the company’s pipeline analytics in the process.

I’m not trying to prevent sales from working on whatever sales management wants them to work on.  But I am saying one thing:  whatever they are, don’t call them oppties in “my” oppty management system if they don’t meet the defined standards for oppties [10].

Is Sales Converting Enough of the Pipeline?

While it’s the job of sales to convert pipeline into ARR, that doesn’t mean sales execution is the only factor that drives conversion rates.

Here you see conversion rates plummeting, dropping by 11 percentage points between 1Q23 and 2Q23 and then by another 5 percentage points by 4Q23.  By the 1Q24 forecast, the pipeline conversion rate has been effectively cut in half from ~32% to ~16%.  Note that during the recent dark times (from 2Q23 to 1Q24) we have been starting with ~3.0x pipeline coverage, but converting so little that we’re landing in the dismal range of 47% to 65% of plan.

Let’s assume we have the operational basics covered, so this is real pipeline, validated and scrubbed by sales management, and held to consistent standards over time.  But we’re converting a lot less of it than we used to.  Thus, I conclude that the company’s problem is pipeline conversion, not pipeline coverage.

What possible factors could be driving reduce pipeline conversion rates?  Well, there are a lot of them, so we’ll talk about each.

  • Changes in averages (i.e., ceteris non paribus).  Most productivity models assume a constant average sales price (ASP) and average sales cycle length (ASC).  If ASPs go down, you will hit your count-based targets, but miss your dollar-based ones.  If ASCs increase you may preserve your eventual close rates, but stretch them out over time, reducing quarterly conversion rates and plan attainment. 
  • ASP decreases.  Typically, due to budgetary pressure and increased price competition, but also can be due to an overreliance on discounting.  Some of this is inevitable in a downturn.  You can mitigate it through pricing and packaging changes (e.g., new add-ons to preserve price and/or offset churn at renewal).
  • Slip rate increases.  When ASCs lengthen, more deals slip to the following quarter(s).  Pipeline scrubs can provide early detection and deals reviews can offer re-acceleration strategies.  The biggest risk is that these deals never close at all and simply hit no-decision or derail.
  • Win rate decreasesWin rates usually decrease when a new competitor enters the market or when an existing competitor leapfrogs your product or your market position (e.g., passes you in market share).  Competitive research, sales training, and selling the roadmap are the usual responses.  
  • An absence of big deals.  Some CROs run their business as a mix of baseline deals to hit say 60-80% of plan, topped up by big deals that provide the rest.  During a downturn those big deals may evaporate leaving only the run-rate business.  The usual response is a strategic accounts program to focus on generating big deals and a focus on pipeline generation in the run-rate business to cover the gap.
  • Pipeline substitution.  This is a subtle problem due to a change in pipeline mix, with low-converting pipeline substituting for high-converting pipeline.  This is dangerous because you “look covered” at the start of the quarter but end up below plan at the end.  Let’s drill in a bit here.

Pipeline Substitution

Not all pipeline is created equal.  Pipeline for certain products often converts at a higher rate than others.  Pipeline conversion rates typically vary by source, e.g., with outbound SDRs typically converting at a low rate and alliances converting at a high rate.  Pipeline conversion might also vary by geography, with established geographies delivering high conversion rates than emerging ones. 

See this chart for an example:

In this example, we start every quarter with $10M in pipeline.  In 1Q23 through 3Q23 we convert 25% of it, but in 4Q23 we convert only 20%.  What happened?  The pipeline mix changed.  Starting in 4Q23, we substituted $2M in high-converting pipeline (from sales/outbound and alliances) with $2M in low-converting pipeline (from SDR/outbound).  Blended pipeline conversion thus dropped from 25% to 20% as a result of this change, effectively substituting nutrient-rich pipeline for nutrient-poor pipeline while keeping the overall amount the same. 

Identifying these problems is a lot of work because you’ll need to segment pipeline by multiple variables — such as pipeline source, product, geography, business segment (e.g., enterprise vs. corporate accounts) – to get historical average conversion rates and percent mix, and then see if changes in pipeline composition are driving reductions in conversion rates.  If so, the usual solution is to re-aim your pipeline generation back to the high-converting segments.

In this post, we have shown how you can troubleshoot go-to-market problems by splitting the funnel in two and focusing on two questions:

  • Are we giving sales the change to hit the number each quarter, as measured by pipeline coverage.
  • Is sales converting enough of the pipeline to hit the number, as measured by pipeline conversion.

I’ve also provided numerous notes and links that you can use to deepen your knowledge of how to solve these problems.

# # #

Notes

[1] The same analysis approach can easily apply to expansion ARR, which should be analyzed independently via its own funnel because it typically has different conversion rates and shorter sales cycles. 

[2] Deadheads will understand that I had to resist writing, “nothing else shaking, so you might just as well.”

[3] Think:  given that we’re off rails, forget the plan for a minute and let’s analyze what do we need to do to add $4M in newbiz ARR every quarter?  This liberates you from needless, complexifying math that makes it harder to see the answer and is a great way to start in the crawl-walk-run exercise of getting back on track.

[4] More precisely, day-1, week-3, current-quarter pipeline coverage.  Snapshotting Sunday night before the start of week 3 gives you a consistent point to compare across quarters.  Waiting until the start of week 3 gives sales (more than) enough time to clean up the pipeline after the end of the prior quarter but is still early enough to be considered “starting pipeline.”  Note that you may need to apply corrections for any deals that close in the first two weeks of the quarter.  A high-class problem, at least.

[5] Or, in a monthly cadence, day-3 pipeline coverage.  See my post on the mental mapping from quarterly to monthly cadence for more on this concept.

[6] There is a cost to this type of insurance; it’s not great for your CAC ratio if you don’t end up over-performing plan (which ceteris paribus, starting with 110% of your pipeline target, you should).  But it does reduce the risk of missing plan.  To me, the correct sequence is to focus on making plan first, before focusing on efficiency — but you need to have the cash to underwrite that philosophy.

[7] For example, one big deal that masks what’s otherwise a pipeline starvation situation.  If you’re going to set targets on dollars (which typically involves using some placeholder value) then you should create the oppties with a close date far in the future (e.g., one year) that sales can pull forward once they further qualify the account.  The alternative is usually generating lots of fake pipeline that is auto-dumped into next quarter that gets pushed out in the first weeks of the quarter.  Also, see this for more on ensuring pipeline coverage by seller, and not just in aggregate.

[8] You’re not going to hire an extra CMO, an extra PR agency, and an extra product marketer to generate 20 more oppties.  Those costs are effectively fixed.

[9] And putting them under such pressure can run in diametric opposition to pipeline discipline and enforcing pipeline standards by encouraging reps to enter dubious deals as pipeline to get their manager off their backs.

[10] I say “my” oppty management system to remind people that carrying sub-standard oppties has impacts well beyond themselves and that oppty management system is the company’s property, not theirs.  For old movie fans, when speaking of the oppties in “my” oppty management system, I’m always reminded of Cool Hand Luke: “what’s your dirt doing in Boss Keen’s ditch?

Target Pipeline Coverage is Not the Inverse of Win Rate

I was reading a SaaS benchmark report the other day and encountered this line:

“Win rates declining [over the two-year period] from 23% to 19% might not seem all that significant. But in terms of required pipeline, it represents a dramatic shift from 4.3x to 5.3x coverage.”

It’s the kind of sentence that you might read, nod your head in hasty agreement, and then keep going. But you’d be wrong to do that. Quite wrong. And a lot of people make this mistake.

Thus, in this post, I’ll explain why it’s wrong to invert win rate to calculate target pipeline coverage, demonstrate that with a spreadsheet, and then give you a better way to determine target pipeline coverage.

Before diving into the math, let’s take a second to sanity check the conclusion reached above: you’re going to need 5.3x pipeline coverage [1]. Given that the rule of thumb for pipeline coverage is 3.0x, how do we feel about requiring 5.3x? My thoughts [2]:

  • I wonder who’s going to generate that? In many companies, it’s primarily marketing. So this potentially passing the buck: “hey marketing, we’re not closing as much as we used to, so we need more coverage.” It’s your problem, now.
  • At what cost? Let’s say that it costs $4K to generate a sales-accepted (aka, stage 2) opportunity [3]. If we needed 3x coverage before — e.g., 30 opportunities (“oppties”) to generate 10 deals — now we are going to need 53. That’s 23 more oppties at an incremental cost of $92K. Who’s going to pay for that? What’s that going to do to our CAC ratio and CPP?
  • Why do we lose so much? Sales is telling us that they can win only 19% of the oppties that they accept as valid sales oppties? That strikes me as low. If a tougher macro environment means lower quality stage 1 oppties, then why is sales accepting them? Lower quality stage 1 opportunities should show up in a higher stage 2 rejection rate, not a lower win rate [4].

So, if the answer is that we need 5.3x pipeline coverage to make plan, I’m going to have a lot of questions without doing any math at all. But now, let’s cut to the math.

What is Win Rate?

Most people define win rate as follows:

For all oppties that reached a terminal state during the quarter, win rate = wins / (wins + losses). I call this narrow win rate because it excludes no-decisions (also known as derails) where an oppty hits a terminal state without anyone winning it — for example, where the customer decided to stick with the status quo or the whole evaluation gets derailed by a surprise merger [5]. Because derails can happen a lot [6], I define an additional metric, broad win rate = wins / (wins + losses + derails).

Note that both of these win rates exclude slips, when the close date for an opportunity is moved out of the current quarter into a future one. Slips happen a lot. In fact, my basic rule of thumb is you win a third, you lose a third, and you slip a third [7]. Also note that I’m doing this on a count basis, not a dollar basis, which is my default preference [8].

You should already see why inverting win rate is not a great way to determine pipeline coverage requirements:

  • It’s ambiguous. Which win rate, narrow or broad?
  • Slips are common, but excluded from win rates. (Definitionally, because slipped oppties do not hit a terminal state in the quarter.)
  • The timing is wrong. We use pipeline coverage at the start of the quarter to see if we have a chance at hitting the number. But win rates are based on when oppties die, not their start-of-quarter status.

What is Close Rate?

I define close rate as a cohort-based metric that answers the question: given a set of oppties, what percent of them do we close/win [9] in some time period. For example, the six-quarter close rate for the cohort of stage-2 oppties created in 1Q22 = oppties in the cohort closed in the period [1Q22 to 3Q23] / oppties created in 1Q22. Let’s show it with an example:

The first block shows oppty count, the second shows percent. Here, we see a 27% six-quarter close rate. You can also run a cumulative rate along the bottom of the table that would show, for example, that the four-quarter close rate is 23%.

Win rates are period metrics that tell you what happened to the oppties that a hit a terminal state in a given period. Close rates are cohort metrics that tell you, in the fullness of time, the percent of a set of oppties that we win.

  • They are different.
  • They are both valuable.
  • Win rates are great for tracking progress against the enemy.
  • Close rates are great for knowing how much value we expect to extract, and when, from a set of oppties.
  • Neither is good if you want to invert something to find required pipeline coverage.

Week 3 Pipeline Conversion Rate

Let’s look at a different metric. Instead of starting with the fate of oppties in the pipeline, let’s start with an early-quarter snapshot of the current-quarter pipeline and then compare it to how much we close. Ideally, we’d take the snapshot on day one of the quarter, but that’s not realistic because sales invariably needs some clean-up time after the end of a quarter. Ergo, I typically use week-3 starting pipeline. If you have a monthly cadence, I’d suggest doing this same analysis on a monthly basis and using day-3 starting pipeline [10]. You can then calculate week-3 pipeline conversion rate = new ARR closed / week-3 starting pipeline. See [11] for some notes on this metric.

Because the conversion rates often differ significantly between new and expansion business, most people segment week-3 pipeline conversion rate by new business (newbiz) vs. expansion. In my endless desire to keep things simple, I always start with the total, unsegmented pipeline and break it out later if I need to. The reality is that while the conversion rates are different, if the mix remains roughly constant, it all comes out in the wash.

Here’s a table to show this concept at work:

To get implied target pipeline coverage, I take a trailing nine-quarter average of the week-3 pipeline conversion rate (34%) and then invert it to get 2.86. You could also have fun with the percent-of-plan row, asking questions like: what pipeline coverage do we need to hit plan 90% of the time?

In this post, I’ve hopefully blown a hole in the conventional wisdom that you can invert win rate to get target pipeline coverage. And I’ve provided a far better metric for accomplishing that task: week-3 pipeline conversion rate.

My metrics brother Ray Rike and I recently released an episode of our podcast, SaaS Talk with the Metrics Brothers, on this very topic. The spreadsheet for this post is here.

# # #

Notes

[1] When I used to help my kids with math homework, I’d always include a sanity check review of the answer. If you’re calculating the mean summer temperature in Alaska and the answer is 451 degrees, then go back and check your work.

[2] And I find that rule of thumb high in many situations. At the last company I ran, we could consistently hit plan with 2.5x coverage.

[3] In practice, the average cost of a stage 2 oppty varies considerably. I think a range of $2K to $10K probably covers 90% of cases, with a mean around $4-5K. These are mid-market and enterprise figures. SMB is presumably cheaper. These are sales-accepted so the cost is equivalent to your stage 1 oppty cost dividied by your stage 2 acceptance rate (typically 60-80%).

[4] Yes, I’m aware of the “desperation effect” whereby sellers with weak pipeline accept lower-quality opportunities, but sales management must fight to hold some objective quality bar to preserve pipeline discipline, to ensure resources are only put against quality oppties, and to ensure the validity of pipeline analysis. So yes, the effect is real, but it’s sales management’s job to limit it. (See the “floating bar” problem discussed here.)

[5] Many people code no-decisions as losses and then have a reason code for no-decision. I think this potentially blurs up win/loss analysis because losing to a competitor is different from a no-decision. (Plus, it usually precludes putting no-decision codes on no-decisions which I also want.) The fact is they are two different cases: losing to a competitor vs. an evaluation process ending without selecting a winner.

[6] Particularly in new markets where people are primarily exploring whether they want to buy one at all. In more developed markets — where the customer is more likely thinking, “I’m going to buy one, the question is which” — you should see lower derail rates. And those derails should be more surprise-driven — e.g., we got acquired, the CFO quit, we missed a quarter, we failed an audit, we’re being sued, etc.

[7] Which implies in a 50% narrow win rate, a 33% broad win rate, a 33% slip rate. This is realistic if you are one of two competitors going head-to-head in a market segment. If it’s more of a horse race, I’d expect to see a lower rate. Also, the “a third, a third, a third” rule excludes derails which you can skim off the top. For example, if 20% derail and the balance split by thirds, then you win 27%, lose 27%, and slip 27% of your deals.

[8] I prefer counts to dollars because they’re more visceral and less messed up by big deals. If you are running two sales motions (e.g., corporate and enterprise), I’d first try to stay count-based, but segment the analysis before going to a dollar basis. But there’s a time and a place for both.

[9] Which some might prefer to think of as a “closed/won rate,” but that’s too many syllables for me.

[10] Both generously allows about 10% plus or minus of the period to elapse before snapshotting: 3 days out of 30 (10%) and, depending on how you calculate weeks and what day the quarter starts on, up to 14 days out of 91 (15%).

[11] This assumes (a) sales cycles much longer than the period (e.g., 6-12 months) and (b) no sales are made prior to the snapshot. It ignores (a) deal expansion or shrinkage after week 3, and (b) where closed/won deals came from (e.g., they may be in the week-3 snapshot, created after it, or pulled-forward from a future quarter). This asymmetry bothers some people but it’s really supposed to be a macro measure. The real risk you face using it is when ceteris aren’t paribus.