Tag Archives: Pipeline

The Top 7 Marketing Metrics for a QBR or Board Meeting

The other day an old friend, a highly accomplished marketing executive, asked me a simple question: if you only had five metrics to summarize marketing performance for a quarterly business review (QBR) or board meeting, what would you pick?

In this post, I’ll share my answer to that question. (Hint: I cheated and used seven.) 

I made my list from scratch. In order to avoid any anchor bias, I refused to even look at the draft list she sent me before coming up with my answer. 

I kinda cheated a second time because I grouped each metric under a heading. I like to remind people of marketing’s priorities, hopefully demonstrating alignment in the process. And, if marketing is not aligned, taking a grouped approach provides a clear opportunity for someone to speak up. Note that unlike some Kellblog posts, I won’t talk much here about formatting the metrics [1]. Instead, I’m going to focus on the metrics themselves. What should we measure?

If I were to present these, I’d preface this by saying, “Good morning, great to see everyone, and as a reminder, here’s what we do here in marketing. In priority order, we …”

We Make Pipeline That Closes

1. Marketing-sourced pipeline generation. I prefer measuring pipeline generation using opportunity count, not dollars, both because it’s more visceral and, particularly when there is a broad range of opportunity values [2], it can be impossible to know the value of an opportunity without getting fairly far into the sales cycle [3]. (And don’t worry, we’ll cover dollars below in metric three where it matters even more.) This metric is about count. Think: we agreed that marketing needed to generate 110 stage-two opportunities [4] during the quarter and we generated 120.

2. Marketing-sourced pipeline conversion. Because we understand that the point is not just to generate pipeline (which is really only a leading indicator), but to generate sales, we measure the conversion rate of marketing-generated pipeline. The trick is that this is an inherently lagged measure and the longer your sales cycle, the longer your lag. To make this concrete, the table below demonstrates an idea I call time-based close rates. If you generate 120 opportunities this quarter, while 23% of them may close in the fullness of time, 2% close this quarter, 4% next quarter, 10% the quarter after that, and so on.

Because sales lives quarter-to-quarter [5] and will die waiting for the fullness of time, we must factor this progression into our planning. We must also account for it in our metrics and the only good solution I know is to use trailing twelve month (TTM) conversion rates [6] [7]. Note that the CMO is stuck on the horns of a dilemma: either face criticism for using a lagging but highly sales-aligned indicator or face criticism for using a leading indicator that might not result in sales [8]. I’ll take the former in this case, particularly because so many other marketing KPIs are only leading indicators of sales. 

We care about pipeline that closes, not just pipeline that gets created or advances to demo stage, but pipeline that closes. I show that caring with this metric.

We Tee Up Sales for Success Each Quarter

3. Day-one pipeline coverage. This ties to my idea that the CMO should be the quarterback of the pipeline. Not just the marketing-sourced pipeline, but the whole pipeline. Most companies have four sources of pipeline with specific targets for each. For example, 60% from marketing, 20% from partners, 10% from outbound SDRs, and 10% from sales. The way most organizations are structured, the only person who owns all four sources is the CEO. Thus, insanely, in most organizations there is no natural owner for the overall pipeline other than the CEO. Because the CMO should always have the CRO’s back, because the CEO should delegate this important responsibility even if there is no natural owner, and because marketing is usually the majority pipeline contributor, I believe that the CMO should be the official owner of the overall pipeline. 

This means it’s the CMO’s job to ensure that sales starts every quarter with aggregate 3.0x pipeline coverage and, as a key part of that, to forecast next-quarter starting pipeline. That forecasting process should start early enough that you can still do something about forecasted problems, e.g., no later than one full quarter in advance. ”Doing something” might mean asking for more demandgen dollars or asking one of the other pipeline source owners (e.g., partners) to step up to higher targets. Worst case, it means escalating the forecasted and as-yet unresolved problem to the CEO.

The metric here is simple. The philosophy behind it is not [9].

We Generate Pipeline Efficiently

4. Demandgen cost per opportunity. Because we understand that SaaS companies effectively buy customers and that most SaaS companies require more than one year to recoup their investment in customer acquisition, we continually seek to reduce our demandgen cost per opportunity [10]. I pick demandgen cost per opportunity rather than overall marketing cost per opportunity because I want to put emphasis on the incremental (aka variable) cost of generating opportunities. If I want to measure overall marketing efficiency, I can use the marketing contribution to the CAC ratio. Here I want to focus on demandgen cost because it excludes fixed marketing costs that aren’t linked to generating opportunities (e.g., CMO salary, PR firm retainer) and because the primary business question I want to answer is: how much will it cost to generate 50 more of them? To do that, I don’t need to hire a second CMO or increase the PR retainer. 

If you take this approach, someone will eventually criticize you saying, “you’re deliberately understating the total cost of marketing-generated opportunities by including only demandgen costs,” to which you will reply: ”No, I am correctly stating the demandgen cost of opportunities because that’s the business question I’m trying to answer, and if you want to talk about overall marketing efficiency we can look at the CAC ratio and marketing’s contribution to it, including the sales/marketing expensive ratio.” [11]

We Get the Word Out

5. Awareness. Important as it is, demand generation is not the only thing we do here in marketing. We’re also responsible for getting the word out, making sure potential customers have heard of the company, have a positive opinion of us, and would consider us if and when they go shopping for a solution [12]. Towards that end, we run a number of programs to drive awareness/opinion/consideration in the market including public relations, brand advertising, and content marketing. Demandgen itself generates awareness as a by-product. 

To get an aggregate measure of these activities, we run a quarterly survey of buyers that measures:

  • Unaided awareness. Name vendors that come to mind in the XYZ space.
  • Aided awareness. Have you ever heard of vendor? [13]
  • Positive opinion. Do you have a positive opinion of vendor?
  • Consideration. Would you consider purchasing vendor?

While we’re happy to share the full report with anyone interested, in the QBR meeting we present aided awareness for ourselves and our top competitors.

6. Organic web traffic. The other way we measure general awareness is through organic web traffic, specifically how many unpaid visitors we get per month on the website. Are people finding us on the Internet and visiting our site? This is a coarse measure, but it allows us to keep an eye on how we are doing over time and relative to our competition [14]. 

We Care What Sales Thinks

7. Internal marketing CSAT. We view sales as our internal customer and our overall mission as to make sales easier. Towards that end, we run an internal customer satisfaction (CSAT) survey of sales each quarter and report back sales’ overall CSAT rating with marketing at the QBR. In order to inform our OKRs, we ask about many things (e.g., priorities, challenges) in this survey and the full report is available for anyone who attends the QBR.

I’ll conclude with a slide that summarizes this post.

# # #

Notes

[1] There has been some great content produced about this and in great detail of late — e.g., the Iconiq Go-To-Market Reporting Guide. While I’ve not yet reviewed it with a fine-tooth comb (because it’s both long and brand new), it looks quite good on my initial skim.

[2] Thus you end up using a placeholder value for new oppties which is effectively a proxy for counting them. If you create new oppties at zero value in such situations, I don’t pollute the pipeline with lots of proxy-valued oppties and, if I want to, I can always create “implied pipeline” by substituting 0 with the overall ASP or segment ASP. It’s impossible to do the reverse, because if your proxy value is $50K, you won’t know if a $50K oppty is a real value or a proxy value. 

[3] The other problem is that opportunity value is not single-valued but changes over time. So if you want to do pipeline metrics on value then you immediately beg the question: when? When the oppty was created? When it was 90 days old? When it hit stage 3? The world is much simpler if you just deal with counts for pipeline generation targets.

[4] Aka, sales-accepted opportunities. Generally in the sense that two keys have turned: an SDR thought it was an opportunity and passed it to sales, and a quota-carrying seller concurred.

[5] A favorite quote: ”I want salespeople who live in 90-day increments.”

[6] The simpler approach is to look at the TTM close rate of the year-ago cohort of new opportunities. The more complex approach is to look at the TTM close rate of all oppties generating in the past year, effectively stacking and sliding the progression (close rate vector) above. 

[7] At the 1Q24 QBR in January, I would say we generated 120 oppties in 1Q23 and 24 of them closed during 2023, for a 20% TTM close rate. (Unbeknownst to me at the time, 3 more will eventually close per the last column but that hasn’t happened yet. I could mention as an aside that 3 more are in the forecast for this quarter if I wanted to, assuming that none have close dates beyond that.)

[8] Such as stage 4 oppties or, while I don’t like demo as sales stage, oppties that reached demo. These are further down the pipeline than stage 2 oppties, but they are nevertheless still leading indicators and not sales. Because getting to these intermediate stages happens faster, the conversion rates are less lagged, but they are alas still leading indicators. I’ve talked to many CEOs who hooked everything to demo as a key stage, only to find that they were doing lots of demos, but not making many sales.

[9] People indoctrinated with a silo mentality may find it illogical or impossible to be accountable for something they don’t fully control. Think: how can I own the overall pipeline when I’m only responsible for generating 60% of it? I challenge such people to change their thinking to: I have two jobs. One is to generate 60% of the pipeline. The other is to make sure sales is teed up for success every quarter. I do that by forecasting starting pipeline coverage, leading a small team of leaders to decide what to do when we’re forecasting below target, and when needed escalate the problem early to the CEO.

[10] And the other way we try to reduce customer acquisition cost per dollar of ARR is to provide programs, tools, and training that increases the s2-to-close rate. We need to think of this as reducing demandgen cost per opportunity while holding quality constant (or improving it) where quality is measured by the s2-to-close rate.

[11] For die-hards, I’m often guilty of conflating incremental (i.e., marginal cost) with fixed vs. variable cost. The CMOs salary is a fixed cost. Demandgen is a variable cost in that it varies with volume. Total demandgen spend / total oppties generated = average cost per opportunity which is the actual calculation I’m encouraging. A true marginal cost would be the incremental cost of generating 1 more oppty, e.g., the cost of getting enough clicks to generate enough leads to generate a single opportunity. Here I think the average cost works fine and the real improvement is excluding the fixed costs that blur up the incremental cost of getting 10 or 50 more. But I’m sloppy in my language sometimes.

[12] And trying to accelerate that shopping trip is another thing we do in marketing, but the specific focus here.

[13] For most early- and growth-stage startups, <vendor> and <product> are synonymous. For bigger companies, you need to separate them. It’s not: have you heard of Salesforce? It’s: in the CX space, have you heard of Salesforce Experience Cloud?

[14] There is a nuance here but I do think companies should track this for both themselves and their competitors. The nuance is that for your own site, you can “know” how much traffic you get, but for the competition you can only “guess,” using tools like Ahrefs or SimilarWeb. The trick is when their guess for you is off, there can be a tendency to dismiss the competitor data as well. That’s a mistake. Present your own data for you over time (that you “know”) and then, when doing competitive analysis, compare the “guesses” using only the guess data, basically hoping for compensating and consistent errors in the process.

What Do “Pipeline Coverage” and “Forecast” Mean When Your Sales Cycle is 30 Days?

I grew up in enterprise.  I have already written a post on the tricky problem of mapping one’s mindset from enterprise to velocity SaaS, meaning smaller deals, shorter contract durations (e.g., month-to-month), and/or monthly-varying pricing [1].  That post was focused on what, if anything, “annual recurring revenue” (ARR) means such an environment, and how that impacts metrics that rely on ARR as part of their definition (e.g., CAC ratio).

In this post, I’ll continue in the velocity SaaS direction by exploring short average sales cycles (ASC), as opposed to short contracts.  Specifically, what does it mean in short ASC companies when you discuss common concepts like pipeline coverage and the sales forecast?

Let’s demonstrate the problem.

In enterprise, quarterly pipeline (defined as the sum of the values of opportunities with a close date in the quarter) is somewhat intertwined the notion of long sales cycles.  Meaning that in a company with 9–12-month sales cycles, virtually every deal that has a chance of closing within the quarter is already in the pipeline at the start of the quarter.  Thus, you can meaningfully calculate “coverage” for the quarter by dividing the quarterly starting pipeline by the quarterly sales target.  Most sales VPs like a 3x ratio [2].

Thus, the concept of pipeline coverage implicitly assumes a sales cycle (significantly) longer than the coverage period.  That’s why most companies don’t look at out-quarter pipeline coverage much (though they should) and if they do, they expect a much lower coverage ratio.

Now, let’s imagine an average sales cycle of 30 days and — rather than futzing with cohorts, statistics, and distributions [3] — let’s assume that all oppties are won or lost in exactly 30 days [4].

In this scenario, at the start of the quarter, what is the pipeline coverage ratio? It’s 1.0x.  Why?  We have zero pipeline for months 2 and 3 of the quarter.  If we assume that we have 3.0x coverage for month one and that the quarterly goal is evenly distributed across months, then we’d have 3.0x, 0.0x, and 0.0x for the three months of the quarter, or 1.0x overall [5].

In this example, quarterly pipeline coverage is basically meaningless because two-thirds of the pipeline you need to close during the quarter hasn’t been created yet.  Assuming a 30-day MQL-to-opportunity lag, one-third is working its way through the high funnel and the other third is still a wink in marketing’s eye.

If quarterly pipeline coverage is basically meaningless in short ASC companies, then what is meaningful?

  • Examining monthly pipeline coverage. Instead of week-3 quarterly pipeline coverage [6], we should look at day-3 monthly pipeline coverage — dividing the starting monthly pipeline by the monthly sales target. (After that, you can use to-go pipeline coverage to get continuous insight.)
  • Treating months 2 and 3 the way you’d treat next-quarter and the quarter thereafter in enterprise. Using a pipeline progression chart to see how the out-month pipeline is shaping up.
  • Getting marketing to forecast starting pipeline for month 2 and month 3, based on what they have already generated in the high funnel and their current pipeline generation plans for month 2.

Inherent in my point of view is that the definition of “coverage” is based on opportunities that already exist in the pipeline. Call me untrusting, but somehow I can’t feel covered by something that hasn’t been created yet.  Some might define quarterly coverage in this environment using month 1 pipeline plus month 2 pipeline forecast and month 3 pipeline plan.  But to me, that’s not coverage.  And it’s objectively not the same thing as pipeline coverage when we use the term in enterprise.

Now, let’s zip back to reality for a minute.  In the velocity companies that I work with, ASC is closer to 60 days and with a pretty broad distribution where maybe 90% of the deals close within 30 and 120 days.  Happily, this means you will have month 2 and month 3 opportunities in the starting quarter pipeline, but it nevertheless also means you will be increasingly reliant on to-be-generated opportunities across the months of the quarter.

In this case, I would make a three-layer forecast:

  • Sales (from existing opportunities). Forecast month 1, 2, and 3 sales using the normal sales forecasting process.
  • Marketing, from the high funnel. Use existing MQLs and your standard conversion rates, ideally time-based time-based (not just the total rate, but the rate split by time period)
  • Marketing, from planned demandgen. Forecast responses, then use standard conversion rates and ideally time-based. (Ideally you can start with your inverted funnel model.)

This approach is preferable to looking only at pipeline generation (pipegen) because a pipegen approach:

  • Tends to ignore the oppties that are already there
  • Almost always ignores that time-based nature of close rates
  • Uses an average sales price (ASP) as the proxy value for an opportunity [7].

In the example above you can clearly see how much of the forecast comes from existing opportunities (51%), how much from the existing high funnel (36%), and how much from planned demandgen activities (13%).

Finally, I have the same problem with the word “forecast” as I do with “coverage” in the short ASC world. They’re not quite the same thing as they are in enteprise. First, let me define “forecast,” along with its cousins, “plan” and “model.”

  • The plan is about accountability. It’s what we signed up for and accountable to. Budget is a synonym [8].
  • The model is a driver-based model of the business. It’s a calculated output (e.g., opportunities generated) given assumptions for a number of inputs and the way they interact (e.g., demandgen spend, MQLs generated, conversion rates).
  • The forecast is about prediction. It’s someone’s latest prediction for an output (e.g., bookings) given all available information at the time it’s made.

The plan is what we were willing to sign up for last December (when we received board approval). The forecast is what we think is going to happen now.  We used models to help build the original plan and we can certainly re-run those models today using actuals as inputs to see what they produce.

In enterprise, the sales forecast is all about the deals in play.  What if Mike closes deals A, B, and either C or D.  The buyer at deal E promised me they’d give us the order.  Given everything we know about Sally’s deal F, what value do we think it will close at?  Sales VPs spend hours in Excel (or a modern forecasting tool like Clari) running scenarios to arrive a number.  It’s usually more about different combinations of deals than it is about probabilities and expected values.

In the velocity world, as discussed above, the forecast cannot be only about existing deals. If you want to forecast a quarter, you’ll need to include results from the high-funnel and planned demangen. I’d still call it a forecast, but I’d know that it’s not quite the same thing as a forecast in enterprise. And by presenting in the three layers above, you can remind everyone of that.

# # #

Notes

[1] Monthly-varying SaaS is a different concept, which I used in that post, featuring short contracts (e.g., month-to-month) where the spend can vary every month, usually as the result of a flexible user-based pricing model, a consumption-based pricing model, or a hybrid pricing model (e.g., base + overage).  In such environments, simple SaaS concepts like ARR can quickly lose meaning, as do the metrics that rely on them (e.g., CAC ratio).

[2] Which I think had its ancient origins in the idea that you win 33%, lose 33%, and 33% slip. (Thus assuming a 50% competitive win rate.) Regardless of its roots, 3x (starting) coverage is a widely accepted norm, so much so that I fear it’s often a self-fufilling prophecy.

[3] We’re ignoring the distribution of average sales cycle length for closed/won deals, its standard deviation, and the fact the three different outcomes (i.e., win, loss, slip) will likely have three different average opportunity cycle lengths (e.g., you usually lose faster than you win), each with its own distribution.

[4] And, most unrealistically, that deals never slip to a subsequent period. We’re also assuming that all opportunities are generated on the first day of month, an exactly 30-day lag from MQL to opportunity, and that all MQLs are generated on the first day of month, and convert in exactly 30 days. (And, for the detail-oriented, that every month is 30 days.) Overall, with these simplifying assumptions, you start every month with only the opportunities generated from MQLs generated the prior month and only those opportunities. There is no leftover pipeline sloshing around to confuse things.

[5] The reality is likely somewhat less than 1.0x because we’d normally expected to some backloading (“linearity”) of the quarterly target across the months of the quarter.  In enterprise, that backloading is severe (e.g., most enterprise cash models assume a 10/20/70 distribution). In velocity SaaS, I’ve seen from 30/30/40 (i.e., pretty flat) to 10/20/70 (i.e., as backloaded as enterprise), typically reflecting a quarterly (as opposed to a monthly) sales cadence which is usually a mistake in a velocity model.

[6] To intelligently compare pipeline across quarters we need to fix a point in time to snapshot it. In enterprise, I prefer day one of week three because it’s early enough to take actions (e.g., reducing expenses), but late enough so sales can no longer credibly claim they need more time for pipeline cleanup (aka, scrubbing).

[7] In enterprise, this is a major sin because deal sizes vary significantly and values should be inserted only after discovery and price-point socialization (e.g., “you do know that this costs $150K?”)  In velocity, it’s a lesser sin because the deal sizes tend to be more similar.  Either way, if all we’re doing is counting opportunities and multiplying by a constant, then why not just admit it and count opportunities directly? The more sophisticated the proxy, the more I like it (e.g., using $10K for SMB, $25K for MM, and $75K for ENT).

[8] Technically, I’d say budget is a synonym for the financial part of the plan. That is, a budget is only one part of a plan. A plan would also include strategic goals, objectives for attaining them, and organization structure.