In the previous article, we explored a revenue optimization problem that is surprisingly common: your CRM may be working, your CPQ may be working, your pricing platform may be working, and your compensation system may be working; yet the revenue process between them is still creating friction.
That raises the obvious next question: How do you actually find the gaps?
The answer is not to start with a list of applications and ask whether each one is functioning correctly. That approach tends to recreate the same siloed thinking that caused the problem in the first place.
Instead, follow revenue. Take a real opportunity and trace what has to happen from territory and account planning through CRM, pricing, quoting, approvals, booking, compensation, reporting, and the next planning cycle. At every transition, look for the places where information stops, changes, gets recreated, requires manual intervention, or arrives too late to influence the next decision.
Those transitions are where revenue process gaps tend to hide. And once you start looking for them systematically, you can begin separating minor administrative annoyances from the issues actually affecting seller productivity, margins, forecasting, and growth.
Let’s dig a little deeper.
Most organizations have a system that works like this: CRM sends data to CPQ. CPQ connects with ERP. ERP provides transactions to the sales compensation platform. Pricing integrates with one or more of those systems. Data eventually reaches an analytics environment.
While this structure may seem to support a connected data flow, that’s rarely the case in practice. The average organization manages 957 applications, but only 27% of them are connected.
CRM and CPQ systems may be somewhat connected, but in actuality, sellers still copy information between the two. Pricing may technically feed CPQ while part of the price-setting process still happens in spreadsheets. Closed-won transactions may automatically reach the compensation system, but Sales Operations may spend days resolving account assignments and crediting exceptions before payouts are accurate.
So don't begin an assessment by asking, "What systems do we have?" Begin with: What has to happen for us to turn an opportunity into profitable revenue? Then work through that process in sequence.
The Integrated Revenue Optimization approach looks across the connected revenue lifecycle rather than treating planning, pricing, CPQ, and sales compensation as isolated functions. CRM opportunity data serves as an important backbone because account, territory, pricing, quote, booking, and forecasting information all intersect there.
That broader view lets you find gaps that aren't visible when you evaluate systems independently.
You do not need every revenue function to operate in one piece of software. You need them to operate from a shared understanding of the business.
Imagine a pricing change being published and immediately becoming an enforceable guardrail during quoting. Sellers see the right economics while building the deal. Actual customer responses then flow back to pricing so the next update reflects real market behavior.
- Imagine a territory change automatically updating account ownership, quote routing, crediting, and compensation rather than creating four separate administrative tasks.
- Imagine quota planning using not just last year's revenue, but actual account potential, whitespace, pricing realization, seller capacity, and conversion behavior.
- Imagine the sales compensation plan reinforcing the same margin and product strategy sellers see during the deal.
- And imagine leadership being able to move from a revenue number to the underlying pricing, quoting, coverage, and seller behavior that produced it.
That is what revenue optimization looks like when the revenue stack begins functioning as a system rather than a collection of applications.
You don't need a months-long transformation initiative to begin looking for these issues.
If several of those questions are difficult to answer, you probably don't have one isolated system problem. You have a revenue process opportunity.
When organizations discover friction across the revenue stack, it is tempting to jump straight to technology. But instead, it’s often best to start with the revenue lifecycle. Understand where information stops, where decisions conflict, where people compensate for the systems, and where those gaps have measurable business consequences. Then determine which changes will produce the greatest return.
That may mean new technology. Or, it may mean getting significantly more value out of the technology you already own. Either way, you'll be solving the actual problem instead of the most visible symptom. Because once you know where your revenue process is breaking, revenue optimization becomes much less abstract.
You have a map of the gaps, an understanding of what they cost, and a clearer path toward connecting the revenue engine around the way your business actually works.