The numbers should not make sense. Global software spend is growing at 15% this year – the fastest pace in a decade, pushing the market from $1.2 trillion to $1.4 trillion according to Gartner. And yet, roughly half of SaaS companies are contracting, losing customers, or watching growth flatline. For revenue operations professionals, this contradiction is not a paradox to puzzle over. It is a strategic map. The money is moving, and your job is to know exactly where it is going.
The Great Software Bifurcation
What looks like a thriving software market on the surface is actually a tale of two very different realities. Spend is concentrating. Buyers are not cutting software budgets – they are cutting vendor count. Enterprises that once ran 40 to 60 SaaS tools are consolidating around a tighter stack of platforms that demonstrate clear, measurable ROI. The companies winning in this environment share a common trait: they are either deeply integrated into a buyer’s workflow or they are driving outcomes that are directly tied to revenue.
For RevOps leaders, this shift demands a ruthless audit of the tools in your own stack. Every platform that sits between your CRM data and a revenue outcome needs to justify its existence – not with feature lists, but with pipeline influence, deal velocity, or churn reduction metrics. If a tool cannot answer the question “what did this do for revenue this quarter,” it is a consolidation target. Keep up with the latest shifts in the space through CRM News to track which vendors are gaining ground and which are quietly losing it.
Outbound Is Not Dead – It Just Got a New Engine
One of the more persistent myths circulating in GTM circles over the past two years has been the death of outbound. The reality, as operators like Sam Blond – who led outbound at Brex, Zenefits, and EchoSign before founding the AI-native revenue platform Monaco – are demonstrating, is more nuanced. Outbound is not dead. The version of outbound that relied on high-volume, low-relevance sequences is dead.
AI has restructured the economics of outbound fundamentally. What previously required a team of eight SDRs to research, personalise, and sequence can now be handled by a fraction of that headcount with AI agents running in production. The implications for RevOps are significant:
- Sequence quality now matters more than sequence volume – AI can produce personalisation at scale, so generic outreach has no excuse
- SDR roles are shifting toward orchestration and oversight of AI-driven prospecting workflows
- Attribution models need to account for AI-assisted touchpoints that do not map cleanly to traditional source categories
- CRM hygiene becomes more critical, not less – AI agents are only as good as the data they are trained on and pull from
If your RevOps function has not yet evaluated AI-native sales platforms, now is the time. You can browse vendor options and comparisons in our CRM Tools Directory to see how the new generation of outbound tools stacks up against legacy sequencing platforms.
CRM Security Is a RevOps Problem Now
A vulnerability disclosed on July 5th in Apache Camel’s Salesforce integration – CVE-2026-49099 – is a reminder that RevOps teams cannot treat platform security as someone else’s problem. The flaw allows HTTP clients to inject SOQL and SOSL queries, override target SObjects, and redirect Apex REST calls through non-Camel-prefixed Exchange header constants. In plain terms, it is a vector that could expose or manipulate CRM data at the query level.
Affected versions include Apache Camel 4.0.0 before 4.14.8 and 4.15.0 before 4.18.3. Teams using these versions for Salesforce integrations should patch immediately.
This matters to RevOps beyond the IT ticket it generates. Data integrity in your CRM is the foundation of every revenue forecast, territory assignment, and pipeline report your leadership team relies on. A compromised or corrupted data layer does not just create a security incident – it creates bad decisions. RevOps leaders should be in the room when integration security is reviewed, not waiting for a breach to surface in a board meeting.
What Winning RevOps Functions Are Doing Differently
The companies growing into that 15% spend increase share operational traits that are worth benchmarking against. They are treating their CRM not as a system of record but as a system of action – connecting data, signals, and workflows into a continuous revenue motion. They are investing in data infrastructure alongside tooling, recognising that raw Salesforce data piped through modern analytics layers – such as Polars-based adapters now appearing in the Python ecosystem – gives analysts far faster query performance on large datasets.
They are also measuring RevOps through a tighter set of leading indicators: pipeline coverage ratios, time-to-first-meaningful-engagement, forecast accuracy at the rep level, and expansion revenue as a percentage of new ARR. Lagging metrics alone no longer cut it in a market where half the competition is quietly shrinking.
The bifurcation in SaaS is not going to reverse. If anything, AI is accelerating the gap between operators who use data to drive decisions and those who still rely on gut feel and spreadsheets. For a practical starting point on building tighter RevOps processes, explore our CRM Guides – the fundamentals still matter, and they matter more when the margin for operational error keeps shrinking.