What Is Revenue Under Management?
Revenue Under Management (RUM) is a commercial metric that quantifies the total volume of revenue flowing through a governed pricing, quoting, or commercial management system during a defined measurement period. It does not represent a company's total earnings—only the portion actively managed by structured software or process controls.
A practical example: a distributor with $1.2B in annual revenue routes $900M through its pricing and CPQ (configure, price, quote) platform. That $900M is the company's RUM. The remaining $300M, processed outside the governed system, is excluded.
One important caution: RUM is not a standardized metric. Its meaning shifts meaningfully across B2B pricing software, property management, marketplace payments, and SaaS customer success. Readers should confirm which definition applies before using the term in contracts or vendor comparisons.
How Revenue Under Management Works
RUM is calculated through four sequential steps:
- Define the revenue perimeter. Identify which product lines, channels, and transaction types fall within the governed system. Unmanaged revenue is explicitly excluded. This boundary is contractually significant when RUM serves as the basis for a vendor licensing fee—ambiguity here creates real legal and financial risk.
- Aggregate governed transactions. The pricing or CPQ platform captures every quote, order, contract, or invoice that passes through its workflows. Integration gaps with ERP or CRM systems cause RUM to be understated, since transactions not captured by the platform are invisible to the calculation.
- Calculate managed volume. RUM equals the sum of revenue from governed transactions over the measurement period. Trailing twelve months (TTM) is the most common window, and gross revenue is the typical basis—though neither is universal.
- Apply the metric. Vendors use RUM as the basis for value-based licensing, where fees scale with managed revenue volume rather than seat count. Organizations use it internally as a governance coverage ratio: RUM ÷ Total Revenue. For the distributor above, $900M ÷ $1.2B = 75% coverage.
RUM is a flow metric—it measures transactions passing through a system over time—not a stock metric measuring assets held at a point in time.
Revenue Under Management vs. Assets Under Management (AUM)
AUM is the term most commonly confused with RUM because both share the "\\\_ Under Management" naming convention. The differences are fundamental.
DimensionRevenue Under ManagementAssets Under ManagementWhat it measuresRevenue transactions governed by a commercial systemCapital assets held in custody on behalf of clientsStandardizationNo universal standard; definition varies by vendor and industryFormally defined by SEC and FINRA regulationsPrimary usersPricing teams, enterprise software buyers, SaaS vendorsInvestment advisers, asset managers, regulators
Use RUM when measuring revenue actively governed by a pricing or commercial system; use AUM when measuring capital assets held in custody under a regulatory framework.
Revenue Under Management in B2B and Enterprise Pricing
RUM is most relevant in complex B2B environments—manufacturers, distributors, and consumer goods companies managing thousands of SKUs, multiple channels, and tiered customer agreements. In these settings, RUM quantifies how much of an organization's revenue is subject to governed pricing logic—approved price lists, discount guardrails, rebate rules—rather than ad hoc negotiation.
Consider an industrial manufacturer that onboards its distributor pricing network to a price optimization platform region by region. As each region is added, more revenue flows through governed workflows and RUM expands. The governance coverage ratio becomes a meaningful operational signal: a low ratio indicates margin exposure from unmanaged discounting; a rising ratio reflects increasing pricing discipline across the organization.
RUM also functions here as a vendor licensing basis. The software fee scales with governed revenue volume rather than user count, aligning vendor incentives with the client's adoption and revenue growth.
Limitations and Strategic Risks
RUM is a useful metric, but buyers should approach it with specific risks in mind:
- No standardized definition. RUM means different things across industries and vendors, creating contract interpretation risk. Require a precise written definition of included and excluded revenue before signing any agreement.
- Fee growth without proportional value. Under value-based licensing, the vendor fee grows with revenue growth even if the software's marginal contribution diminishes. Negotiate rate reductions or fee caps at scale to protect against this misalignment.
- Understated RUM from integration gaps. If the platform does not capture all governed transactions, RUM underrepresents true scope. Address this with data completeness audits and clear ERP integration requirements upfront.
- Gameable perimeter. Organizations may narrow the defined scope to reduce licensing fees. Include audit rights in vendor agreements to preserve integrity of the metric.
Comparing RUM figures across vendors is unreliable without normalized, explicitly documented perimeter definitions.
Related Terms: Assets Under Management (AUM) | Gross Merchandise Value (GMV) | Annual Recurring Revenue (ARR) | Price Optimization
