
Most go-to-market strategies fail because companies never get specific enough about how they'll reach their goal. The numbers go in, the targets get blessed by the board, and then everyone disperses to execute against a plan that nobody has stress-tested.
Then reps ramp slower than assumed. The product release slips. CS doesn't have the data to target expansion accounts. And by Q3, the postmortem is already writing itself.
In a recent RevOps Co-op webinar, Matthew Volm sat down with Steve Busby, Founder and Lead Partner at Revenue Operations Associates, to work through what a genuinely comprehensive go-to-market (GTM) strategy looks like — not the buzzword version, but the one that includes the connective tissue most plans leave out. Busby brings a distinctive vantage point to the conversation: he spent the bulk of his career as CEO of a $100 million data analytics company before moving into advisory work, where he has since assessed the GTM motions of hundreds of companies against what "best in class" actually looks like.
A poll conducted at the start of the session asked attendees to name their most pressing GTM challenge. The results were telling: "not covered at all" and "covered a little bit" dominated the room when asked how well current plans address the specifics of how goals will be achieved. Almost nobody said "fully covered." That gap — between target-setting and executable strategy — was the subject of everything that followed.
Busby opened by naming something that most practitioners already suspect but rarely say out loud: a truly holistic go-to-market strategy is essentially nonexistent in the wild.
"A complete go-to-market strategy to us at least is a unicorn. We have not seen it yet. If your company has it, please call me afterwards and I'd love to see it." — Steve Busby
What's missing, he argued, is breadth. Most GTM plans are built for new logo acquisition — the left side of the bow tie — and treat everything else as secondary. They don't cover product, talent, rep ramp, marketing to existing customers, or the full customer lifecycle in any meaningful way. They also tend to be organized around outcomes rather than the operating dependencies that actually determine whether those outcomes are achievable.
The analogy Busby returned to throughout the session is worth sitting with. A complete GTM plan is like a detailed architectural drawing for a building — not just the rooms and walls, but the electrical wiring, plumbing, and load-bearing systems that make the structure functional. Everyone from the roofer to the electrician needs that master plan to do their job in context. A plan that only shows the rooms and says "figure out the rest" isn't actually a plan.
There's a second layer to this analogy that matters for the AI moment we're in. Busby noted that deploying AI effectively requires a context layer specific to your company — the same thing a GTM strategy is supposed to provide for every human working in marketing, sales, CS, product, and finance. If that strategic foundation doesn't exist, neither AI nor people will have what they need to execute with precision. This connects directly to the data readiness challenge that Episode 107: AI Can't Fix What Your Business Can't Define covers in depth.
One of the more provocative claims in the session is worth pulling out explicitly: Busby argued that RevOps strategy and GTM strategy are, in a meaningful sense, the same thing.
"If you agree with the principle that revenue operations is sort of how you execute your go-to-market strategy, RevOps strategy is go-to-market strategy. I think they are the same thing." — Steve Busby
The practical implication for RevOps teams is significant. The skills that make a strong RevOps professional — systems thinking, data fluency, cross-functional diagnosis, the ability to translate strategic goals into operating requirements — are exactly what companies are now hiring for under labels like "GTM engineer" and "GTM architect." The mandate is evolving, and there's a window to claim it.
Volm reinforced the point: the work RevOps practitioners are already doing day-to-day is directly connected to the challenges companies face at the strategic level. The gap isn't skill — it's scope. Many RevOps teams are operating inside a narrow definition of their role when the actual problems they're positioned to solve are bigger. For more on how RevOps professionals can expand their influence at the executive level, Episode 99: What Executives Actually Want From RevOps is worth a listen.
The most practical section of the session was also the most uncomfortable: what Busby calls "the reality math" — the simple but rarely performed arithmetic that connects top-down targets to operating capacity.
The example he walked through was straightforward. If the goal is $5 million in incremental revenue, and average contract value is $50,000, the team needs 100 new clients. If the historical conversion rate is 25%, that requires 400 sales-qualified opportunities in the pipeline. If the company has five reps who each close roughly one new client per month, the math doesn't work — and that becomes visible immediately once someone writes it down.
"In order to hit this, we're gonna need 100 new clients over the course of the year. You know, our high water mark is 63. We're coming in with the same resources." — Steve Busby
The point isn't that ambitious targets are wrong. It's that the gap between current capacity and required output has to be named, quantified, and addressed before the year starts — not explained away in Q3. If the gap will be closed by newly ramped reps, that assumption needs to be surfaced and vetted. If conversion rates are expected to improve because of a new tool or process, that's an assumption too, and someone needs to own it.
Busby's advice for RevOps practitioners navigating top-down targets they didn't set: don't push back on the number, do the math. Facts presented objectively to a senior leader carry more weight than opinions, and they create an opening for a productive conversation about what would actually need to change. The worst outcome is arriving at Q3 with explanations nobody wanted to hear. Episode 101: RevOps Should Build for Itself First covers related territory on how RevOps can position itself as a credible strategic voice rather than a reactive one.
An audience member during the session raised a question that cuts to the heart of most GTM strategies: beyond upsell, what does "going to market" with existing customers actually look like?
Busby's answer started with a decomposition exercise. If the revenue target is $5 million in growth, break it into components: new logo revenue, expansion revenue, price increase contribution, and churn impact (positive or negative). Once that breakdown is on paper, it becomes immediately visible that some portion — often 30 to 40 percent — is expected to come from the right side of the bow tie. At that point, the follow-on question writes itself: are we spending 30 to 40 percent of our resources, attention, and marketing budget on that side?
"Typically, there's a deer in the headlight — don't think so. But that's the gap, right?" — Steve Busby
The specific point about marketing budget allocation landed as one of the session's sharpest insights. If CS is responsible for a significant share of revenue growth through expansion and retention, but marketing allocates nearly all of its campaign budget and creative resources to new logo acquisition, there's a structural misalignment hiding in plain sight. The GTM plan is a vehicle to surface it, name it, and make a decision about whether to close it.
Volm added that the tools and processes that work on the new business side — pipeline tracking, win rate measurement, renewal forecasting — translate directly to the customer side. Teams don't need to build from scratch; they need to apply familiar frameworks to an underserved motion. This theme runs through Episode 54: Delivering Customer Value and the Evidence of Impact as well.
One of the most underappreciated problems in GTM execution is the gap between what sales promises during a deal and what CS is equipped to deliver afterward. Busby framed this as both a common failure mode and a significant opportunity for RevOps practitioners.
The sequence is familiar: sales closes a deal by quantifying value, the customer commits based on expected return on investment (ROI), and the account transfers to CS — where the documented promises often don't follow. CS is then operating without a clear mandate, trying to demonstrate value that was never precisely defined, and struggling to make the case for renewal when it comes up.
"Sales is making promises, right? They're doing whatever they can to close deals. Can we quantify that — that's value, right? That the customer is saying, 'Great, I want those values. I'll put a price on those values. I'll decide to transact.' But putting a great — there's ROI, right? Those values can be quantified." — Steve Busby
The opportunity Busby named is building the mechanism that transfers that value definition — cleanly, specifically, and in a way that CS can track and report on through the customer lifecycle. When that works, it drives QBR conversations grounded in evidence rather than sentiment, and it creates a defensible foundation for price increases and expansion discussions. This connects to the broader theme of building a better funnel for growth and success teams, where the right side of the bow tie gets the same operational rigor as the left.
The second half of the session moved through a component-by-component framework for what a comprehensive GTM plan should actually include. Most plans, Busby noted, have the basics: objectives, revenue targets, and a new logo motion. What they consistently lack are the elements that determine whether the basics can actually execute.
Market segments and ICP clarity. This seems foundational — and it is — but Busby was direct about how often it fails in practice. When CS, sales, marketing, and product are each asked to define the ideal customer profile (ICP), they rarely give the same answer. That misalignment is a structural drag on every motion the company runs. Episode 32: Perfect Your ICP covers how to get sharper here.
Value proposition rigor. The temptation when pipeline is weak is to invest in sales productivity — more coaching, better sequences, tighter process. Busby's counterpoint was pointed: "Much rather would have a great product and an average sales force than a crappy product and a great sales force." Before optimizing the sales machine, the GTM plan should include a clear-eyed assessment of whether the value proposition itself is differentiated and competitively durable.
Pricing. Often treated as a finance decision rather than a GTM decision, pricing should be front and center in any comprehensive plan. The key question isn't just whether to adjust prices — it's what the downstream effects on retention and churn will be, who owns those assumptions, and who will track them against actuals.
Onboarding, retention, and expansion. This is where the bow tie opens to the right, and where most plans are weakest. The plan should specify how expansion revenue will be generated — not just that it will be — and should include a view on which customer segments merit white-glove service versus more automated engagement.
Tech stack and data quality. Busby described the typical commercial tech stack as a "Franken mess" — built through a series of point-in-time decisions rather than architected against a coherent strategy. The GTM plan is the right place to flag whether the current stack is aligned with execution needs, and to name data quality as a risk to AI-driven initiatives if it isn't sufficient. Data Management in RevOps: What to Fix First and What Can Wait offers a practical starting point for teams working through this.
Key dependencies — HR, product, finance. This is where the conversation consistently surprised attendees who think of GTM as a sales and marketing domain. If hiring is two months delayed because of HR turnover, that's a GTM dependency. If a product release ships buggy, that affects new logo close rates and renewal assumptions simultaneously. If finance hasn't reconciled the operating budget with the headcount the GTM plan assumes, there's a gap that will surface eventually — better to surface it now.
KPIs and accountability. The plan should specify not just which metrics will be tracked, but what happens when they miss. Pre-agreeing on response protocols for performance gaps — rather than negotiating them after the fact — removes a significant source of organizational friction.
The through-line of the session's practical advice is something Busby named explicitly: "bold clarity." The RevOps practitioner who wants to operate at a strategic level needs to be the person who documents the assumptions underlying the GTM plan, secures stakeholder sign-off on those assumptions, and then manages the ongoing comparison between assumptions and actuals.
This is not a comfortable role — it requires surfacing things people would sometimes prefer not to see. But the alternative is worse.
"The worst thing you can do is say, 'Great, we got some crazy top-down order. We'll give it our best.' And then, you know, halfway through the year start coming up with why we're behind." — Steve Busby
The posture Busby recommended — come with facts, not opinions; ask for a conversation rather than a confrontation; frame everything in terms of wanting the team to win — is a template for how RevOps practitioners can earn and hold strategic credibility. For more on how to develop and exercise that kind of organizational influence, Episode 74: Influence Without Authority: The RevOps Way is directly on point.
The underlying current across this session is the same throughout: the work of building a real GTM strategy isn't glamorous, and it's definitely not finished once the revenue target gets blessed. It's the ongoing, unglamorous job of surfacing the assumptions everyone else prefers to leave implicit — and holding the organization accountable to them. That's the work, and it's RevOps work.
Check out our blog, join our community and subscribe to our YouTube Channel for more insights.