Why strong functions can still add up to a missed number.
Every GTM executive has two jobs. The first is running their function: the CMO is accountable for brand and demand creation, the CRO for revenue, Customer Success for customer outcomes and retention, and RevOps for the systems, processes and data underneath it all.
The second rarely appears in anyone’s mandate. It’s making the whole GTM organization more effective. Sometimes that means changing your own team’s priorities to support a decision the leadership team has made together. As SaaS companies scale, the second job has a bigger impact on whether the business hits its number.
Functional success doesn't always translate into business success
As organizations grow, GTM functions become more specialized. Teams develop their own operating processes, performance metrics, budgets and priorities. That specialization is necessary. But it also introduces a challenge: individual functions can perform well while the broader revenue organization underperforms.
Marketing may be exceeding its pipeline targets while Sales struggles with conversion. Sales may be closing new business while Customer Success is seeing declining adoption or retention. RevOps may have reliable data showing where performance is breaking down, but lack the authority to drive the decisions needed to address it.
Each function can point to legitimate accomplishments. Yet the company is still missing its revenue objectives. The problem is where performance gets optimized. Each function tunes its own numbers, while the outcomes that matter most depend on how the functions work together.
Turf protection isn’t always the cause. Executives are usually doing exactly what their goals, budgets and incentives tell them to do. When those commitments conflict, collaboration won't resolve it. The leadership team must decide which outcome is priority and reset functional expectations to match.
“A successful GTM organization isn’t the sum of successful departments. It’s the result of how effectively those departments operate as one system.”
The hardest decisions rarely belong to one function
Consider a SaaS company that's falling short of its enterprise revenue target. Marketing believes the issue is insufficient investment in demand creation. Sales believes the existing pipeline isn't converting because the opportunities aren't well qualified. Customer Success has evidence that certain customer segments achieve substantially better outcomes, suggesting the company may be pursuing the wrong accounts. RevOps can quantify the conversion gaps. Each has a point.
Regardless of reporting structure, resolving cross-functional GTM issues requires collaboration between leaders, not direction from a single functional executive. Whether that works depends on the relationships between those leaders, their understanding of each other's functions and whether they share a common view of performance. When those conditions exist, they bring forward evidence rather than competing narratives, agree on the underlying problem and develop one coordinated plan. Without them, each leader returns to their function with a separate improvement plan, the issue cycles and GTM performance continues to suffer.
The solution may require Marketing to change targeting, Sales to adjust qualification practices, Customer Success to contribute customer insight and RevOps to establish a shared measurement approach. No single executive can deliver that outcome independently. That's the second job: committing your function's resources to a decision that serves the business.
Collective accountability doesn't mean shared ownership of everything
Not every decision needs the whole GTM leadership team. Functional executives need the authority to run their own organizations, make decisions and deliver on their commitments.
Some decisions affect more than one function, though. Examples include how much to invest in each customer segment, how to split resources between new customers and expansion, where to focus when there’s enough pipeline but conversion is dropping, and how to respond when a product launch doesn’t deliver. The leadership team should work through these decisions together, with the right information and a clear view of how each option affects the rest of the business. There still needs to be a clear decision owner, so the discussion results in a decision rather than another round of debate.
Once the decision is made, each affected executive has to put it into practice in their own function by changing priorities, moving resources and adjusting plans. That’s how collective accountability turns into coordinated execution.
Alignment is tested after the decision
It's easy for an executive team to agree on a strategic direction. The harder work begins when that decision requires changes across functions. Perhaps the business has decided to accelerate its enterprise growth motion. Product Marketing needs to strengthen positioning and enablement. Marketing needs to redirect investment. Sales needs different skills and coverage. Customer Success needs to prepare for more complex implementations and customer expectations. RevOps needs to adapt the funnel model and reporting.
The leadership team may agree entirely with the strategy. But if each function continues operating against its previous priorities, little changes. The test is whether resources have moved, conflicting commitments have been resolved, each leader understands their dependencies and there's a shared view of progress and risk. Most importantly, the changes need to show up in business results.
What makes the second job workable
Good intentions don't survive conflicting incentives. Executives need to be willing to make trade-offs for the broader business, but that commitment also needs to be supported by how the organization operates. Four things help.
Relationships. Make time for your GTM peers outside the regular leadership meetings. Get to know what they’re accountable for and where their teams are under pressure. When a decision means asking a peer to change priorities, it helps if you already understand what you’re asking them to give up.
Shared definitions. One funnel and one set of stage definitions that every function reports against. When each function reports its own version of the truth, cross-functional conversations become arguments about the numbers.
Explicit decision rights. Agree which decisions each executive owns, which require input from peers and which need CEO involvement. The most damaging delays often come from decisions that sit between functions, with no clear owner.
A cadence built for cross-functional calls. A regular forum, separate from functional reviews, where the leadership team looks at the full funnel together, surfaces dependencies and makes trade-offs.
None of this works if executives are still rewarded exclusively for optimizing their own functions. Shared business outcomes need to be reflected in how leadership performance is evaluated.
The leadership team can become the constraint
If your GTM leaders are hitting their numbers and the business is still missing its revenue target, look at how the leadership team makes decisions across functions before looking inside any one of them.
As a SaaS business scales, complexity increases. More products, customer segments, geographic markets and revenue motions create more dependencies between functions. Companies naturally respond by investing in functional leadership, talent, systems and processes. Those investments matter. But there's a point where improving the individual parts of the GTM organization produces diminishing returns if the executive team isn't equally effective at operating across them.
At that point, how well the leadership team works across functions matters more than how strong each function is. The companies that navigate this well recognize that every GTM executive has two responsibilities: to lead their own function exceptionally well, and to contribute to the performance of the broader GTM organization.
The first builds strong functions. The second builds a business that can scale.
Acton Hunter helps B2B SaaS companies align GTM strategy, leadership priorities and execution to build more predictable revenue growth.
Explore our approach to Pipeline Confidence →