I’ve written about this topic a lot over the years, but never before integrated my ideas into a single high-level piece that not only provides a solution to the problem, but also derives it from first principles. That’s what I’ll do today. If you’re new to this topic, I strongly recommend reading the articles I link to throughout the post.
Scene: you’re consistently having trouble hitting plan. Finance is blaming sales. Sales is blaming marketing. Marketing is blaming the macro environment. Everyone is blaming SDRs. Alliances is hiding in a foxhole hoping no one remembers to blame them. E-staff meetings resemble a cage fight from Beyond Thunderdome, but it’s a tag-team match with each C-level tapping in their heads of operations when they need a break. Numbers are flying everywhere. The shit is hitting the proverbial fan.
The question for CEOs: what do I do about this mess? Here’s my answer.
First:
- Avoid the blame game. That sounds much easier than it is because blame can vary from explicit to subtle and everyone’s blame sensitivity ears are set to eleven. Speak slowly, carefully, and factually when discussing the situation. You might wonder why everyone is pointing fingers, and the reason might well be you.
- Solve the problem. Keep everyone focused on solving the problem going forward. Use blameless statements of fact when discussing historical data. For example, say “when we start with less than 2.5x pipeline coverage, we almost always miss plan” as opposed to “when marketing fails on pipeline generation, we miss plan unless sales does their usual heroic job in pipeline conversion.”)
Then reset the pipeline discussion by constantly reminding everyone of these three facts:
- How do you make 16 quarters in a row? One at a time.
- How do you make one quarter? Start with sufficient pipeline coverage.
- And then convert it at your target conversion rate.
This reframes the problem into making one quarter — the right focus if you’ve missed three in a row.
- This will force a discussion of what “sufficient” means
- That is generally determined by inverting your historical week 3 pipeline conversion rates
- And adjusting them as required, for example, to account for the impacts of big deals or other one-time events
- This may in turn reveal a conversion rate problem, where actual conversion rates are either below targets and/or simply not viable to produce a sales model that hits the board’s target customer acquisition cost (CAC) ratio. For example, you generally can’t achieve a decent CAC ratio with a 20% conversion rate and 5x pipeline coverage requirement. In this case, you will need to balance your energy on improving both conversion rates and starting coverage. While conversion rates are largely a sales team issue, there is nevertheless plenty that marketing and alliances can do to help: marketing through targeting, tools, enablement, and training; alliances through delivering higher-quality opportunities that often convert at higher rates than either inbound or SDR outbound.
It also says you need to think about each and every quarter. This leads to three critical realizations:
- That you must also focus on future pipeline, but segmented into quarters, and not on some rolling basis
- That you need to forecast pipeline (e.g., for next quarter, if not also the one after that)
- That you need some mechanism for taking action when that forecast is below target
The last point should cause you to create some meeting or committee where the pipeline forecast is reviewed and the owners of each of the four to six pipeline sources (i.e., marketing, AE outbound, SDR outbound, alliances, community, PLG) can discuss and then take remedial measures.
- That body should be a team of senior people focused on a single goal: starting every quarter with sufficient pipeline coverage.
- It should be chaired by one person who must be seen as wearing two hats: one as their functional role (e.g., CMO) and the other as head of the pipeline task force. That person must be empowered to solve problems when they arise, even when they cross functions.
- Think: “OK, we’re forecasting 2.2x starting coverage for next quarter instead of 2.5x, which is a $2M gap. Who can do what to get us that $2M?”
- If that means shifting resources, they shift them (e.g., “I’ll defer hiring one SDR to free up $25K to spend on demandgen”).
- If that means asking for new resources, they ask (e.g., I’ll tell the CEO and CFO that if we can’t find $50K, then we think we’ve got no chance of hitting next quarter’s starting coverage goals).
- If that means rebalancing the go-to-market team, they do it. For example, “we’ve only got enough pipeline to support 8 AEs and we’ve got 12. If we cut two AEs, we can use that money to invest in marketing and SDRs to support the remaining 10.”
- Finally, if you need to focus on both pipeline coverage and conversion rates, then this same body, in part two of the meeting, can review progress on actions design to improve conversion.
Teamwork and alignment is not about behaving well in meetings or only politely backstabbing each other outside them. It’s about sitting down together to say, “well, we’re off plan, and what are we going to do about it?” And doing so without any sacred cows in the conversation. Just as no battle plan survives first contact with the enemy, no pipeline plan survives first contact with the market. That’s why you need this group and that’s what it means to align sales, marketing, alliances, and SDRs on pipeline goals. It’s the translation of the popular saying, “pipeline generation is a team sport.”
Notice that I never said to heavily focus on individual pipeline generation (“pipegen”) targets. Yes, you need them and you should set and track them, but we must remember the purpose of pipegen is to hit starting pipeline coverage goals. So just as we shouldn’t overly focus on other upstream metrics — from dials to alliances-meetings to MQLs — we shouldn’t overly focus on pipegen targets to the point where they become the end, not the means. While pipegen is certainly closer to starting coverage than MQLs or dials, it is nevertheless an enabler, in this case, one step removed.
Yes, tracking upstream metrics is important and for marketing I’d track both MQLs and pipegen (via oppty count, not dollars), but I’d neither pop champagne nor tie the CMO to the whipping post based on either MQLs or pipegen alone.
Don’t get me wrong — if your model’s correct, it should be impossible to consistently hit starting pipeline coverage targets while consistently failing on pipegen goals. But in any given quarter, maybe the AEs are short and marketing covers or marketing’s short and alliances covers. The point is that if the company hits the starting coverage goal, we’re happy with the pipeline machine and if we don’t, we’re not. Regardless of whether individual pipeline source X or Y hit their pipegen goals in a quarter. Ultimately, this point of view drives better teamwork because there’s no shame in forecasting a light result against target or shame in asking for help to cover it.
Finally, I’d note an odd situation I sometimes see that looks like this:
- Sales consistently achieves bookings targets, but just by a hair
- Marketing consistently underachieves pipeline targets
For example, sales consistently converts pipeline at 25% off 4x coverage and that 25% conversion rate is just enough to hit plan. But, because the CRO likes cushion, he forces the CMO to sign up for 5x coverage. Marketing then consistently fails to deliver that 5x coverage, delivering 4x coverage instead.
This is an unhealthy situation because sales is consistently succeeding while marketing is consistently failing. If you believe, as I do, that if sales is consistently hitting plan then, definitionally marketing has provided everything it needs to (from pipeline to messaging to enablement), then you can see how pathological this situation is. Sales is simply looking out for itself at the expense of marketing. That’s good for the company in the short term because you’re consistently hitting plan, but bad in the long term because there will be high turnover in the marketing department that should impede their ability to deliver sufficient pipeline in the future.
For more on this topic, please listen to our podcast episode of SaaS Talk with the Metrics Brothers entitled: Top-Down GTM Troubleshooting, Dave’s Method.