Revenue Management Intelligence connects Agentforce Revenue Management, Data 360, Tableau Next and Agentforce to give leaders a live view of revenue performance. Instead of waiting for Finance or Revenue Operations to assemble a monthly report, teams can see what is happening across pricing, subscriptions, orders and billing using data generated by the revenue process itself.
The dashboards help users find stalled orders, monitor recurring revenue, investigate billing issues and understand pricing behavior. They can then drill into the records behind a metric or ask Agentforce a direct question in natural language.
The intelligence is only reliable when the revenue data underneath it is connected, governed and current.
Most revenue reporting explains yesterday
The first question I ask about any dashboard is: what decision does it help someone make?
Many revenue reports are built after the event. Data is exported from several systems, reconciled in spreadsheets and presented during a monthly meeting. By the time the report reaches leadership, the conditions behind it may have changed.
An order has been stalled for another week. A draft invoice is still waiting to be posted. A customer has moved further into arrears. A discount pattern has continued across another group of deals. The report may be accurate for the period it covers, but it is no longer current enough to guide the next action.
Revenue Management Intelligence uses data produced by the revenue process and presents it through dashboards designed around live operational and commercial questions. Mike Aaron described it as a series of analytical dashboards built to improve subscription performance, order management, billing visibility and pricing decisions.
The important difference is that users can move from the metric into the Salesforce records behind it. They can see the signal, understand what created it and decide what needs to happen next.
What Revenue Management Intelligence combines
Revenue Management Intelligence brings together four connected capabilities.
Agentforce Revenue Management
Agentforce Revenue Management provides the transactional foundation. It holds information about products, prices, quotes, contracts, orders, subscriptions, invoices and billing activity. Because these transactions are connected within the revenue process, the intelligence layer can examine what is happening without relying on a separate monthly data collection exercise.
Data 360
Data 360 provides the trusted data foundation. It connects revenue information with customer and operational data from other sources. It also helps maintain consistent identities and definitions across the business. The executive dashboard, operational console and Agentforce response should all use the same governed information.
Tableau Next
Tableau Next presents the information through interactive dashboards. Users can filter by account, product, date, country or business area. They can select a metric and inspect the records contributing to it. Mike explained that revenue data flows into the data foundation through data streams, where Tableau Next can support detailed analysis and drill-down views. The dashboards can also be adapted to reflect the organization’s own measures and operating structure.
Agentforce
Agentforce gives users a natural-language way to question the data. During the webinar, Mike asked:
Agentforce searched the relevant orchestration records and returned the orders on the page for further investigation. The user does not need to know the name of every report, field or object before asking a useful business question.
Four views of revenue performance
Revenue Management Intelligence includes four main analytical areas. Each supports a different decision within the revenue process.
Pricing Analytics
Pricing Analytics helps leaders understand how price, discount, volume, cost and margin affect performance. A CFO, CRO or pricing leader can see current revenue, cost and margin, then analyze the results by product, customer, market or industry.
During the webinar, Justin identified a product receiving unusually high discounts. He then drilled into the accounts behind those discounts to assess whether the concessions were supported by wider customer value. This helps teams answer questions such as:
- Which products generate the strongest margins?
- Where is discounting increasing?
- Which customers receive the largest concessions?
- Are volume increases compensating for lower prices?
The dashboard provides a route into the commercial behavior behind the headline number.
Subscription Revenue Analytics
Subscription Revenue Analytics gives Sales, Finance and Product teams a view of recurring revenue health. It can show Monthly Recurring Revenue, active subscriptions, bookings, renewals, customer growth and churn.
Mike explained that users can examine how pricing supported the original sale or renewal, then assess whether that pricing helped retain the customer. The data can also be viewed by account or product, helping leaders decide where to invest.
Order Analytics
Order Analytics shows what happens between the accepted sale and the start of billing. A Billing Executive can see:
- how many orders progressed
- which orders failed
- which are in jeopardy
- where they are waiting in the orchestration process
- which delays may prevent billing
Users can filter the data by account, product, start date or order status and inspect the records behind each stage. This connects an operational delay with its financial consequence. An order in jeopardy may prevent the business from billing against a scheduled milestone. In one webinar example, the delay could have affected £5 million in billing.
Billing Analytics
Billing Analytics gives Finance and Billing teams a current view of invoice and collection performance. It can include:
- Annual and Monthly Recurring Revenue
- generated and draft invoices
- failed invoice runs
- unbilled orders
- aging balances
- Days Sales Outstanding
- invoice-run performance
Users can filter by account, product, region or time period. They can then move into the invoices or accounts contributing to the result. During the demonstration, Justin used the dashboard to examine recurring revenue, overdue balances, unbilled orders and invoice health. He also asked Agentforce to calculate the value and average size of invoices generated during a selected month.
Executives and operational teams need different views
A CFO and a Billing administrator may use the same underlying data, but they need different experiences. The executive wants to know whether revenue, margin, billing and cash collection are moving in the right direction. The administrator needs to know which invoice run failed, why an invoice remains in draft and what action is required.
The Billing Operations Console provides that detailed operational view. Mike described it as a one-stop shop for invoice operations in Salesforce. It can show scheduled invoice runs, credit memos, draft invoices, processing errors and recent billing activity. Users can open an error and work on the underlying issue.
The same trusted data supports both perspectives: leadership sees revenue health, and operational teams see the exceptions that need attention.
The dashboard should lead to action
Revenue Management Intelligence becomes useful when the user can move from a signal into the next action. That might mean:
- opening a failed order
- investigating unusual discounting
- identifying renewals requiring attention
- finding invoices behind an aging balance
- sharing a record with a colleague
- correcting a billing error
- starting a targeted collections action
Agentforce reduces the effort required to move through that process. A user can ask for all invoices produced during a period, request a list of unactivated orders or investigate the records behind a billing problem. The response remains connected to the Salesforce data that produced the answer.
That connection matters. The insight does not sit in a separate report waiting for somebody to translate it back into operational work.
Trusted data determines whether the intelligence is useful
A polished dashboard cannot repair weak revenue data. If products are duplicated, contract terms are incomplete or invoice statuses are inconsistent, the dashboard will reproduce those problems.
Revenue Management Intelligence depends on:
- a controlled product catalog
- consistent pricing and discount rules
- accurate account and contract information
- connected order and billing records
- agreed metric definitions
- clear ownership and governance
A system becomes trusted when users can understand where the data came from, how the metric was calculated and which process owns it. They should be able to move from a top-level number into the supporting records and see why the number is true. That traceability is what separates revenue intelligence from a visually attractive report.
What changes for revenue leaders
Revenue Management Intelligence allows leaders to manage the business closer to the point where revenue activity occurs.
- A CFO can examine billing health without waiting for a monthly spreadsheet.
- A CRO can connect subscription growth with account and product performance.
- A pricing leader can see where discounts are affecting margin.
- Revenue Operations can identify stalled orders before they delay billing.
- Billing teams can investigate failed runs and outstanding exceptions in one place.
The same data supports different decisions across the organization. That is the value of connecting Agentforce Revenue Management, Data 360, Tableau Next and Agentforce: one governed view of revenue performance, with experiences designed around the people responsible for acting on it.
- Revenue Management Intelligence uses current revenue data instead of a manually assembled monthly report.
- Agentforce Revenue Management provides the transactions across pricing, subscriptions, orders and billing.
- Data 360 connects and governs the information.
- Tableau Next provides interactive dashboards and drill-down analysis.
- Agentforce lets users question the data in natural language.
- The dashboards support both executive decisions and operational work.
- The intelligence is only reliable when the underlying revenue data is controlled and trusted.
Related questions
What tools power Revenue Management Intelligence? +
Agentforce Revenue Management provides the revenue transactions, Data 360 provides the trusted data foundation and Tableau Next presents the dashboards. Agentforce helps users question the information and support follow-up actions.
How is it different from a traditional BI dashboard? +
A traditional dashboard may depend on scheduled extracts and sit downstream of the operating process. Revenue Management Intelligence remains connected to Salesforce revenue records, allowing users to inspect and act on the underlying transactions.
Which dashboards are included? +
The main areas are Pricing Analytics, Subscription Revenue Analytics, Order Analytics and Billing Analytics. The Billing Operations Console provides a detailed operational view for teams managing invoice activity.
How does Agentforce work with the dashboards? +
Users can ask questions in natural language, such as requesting unactivated orders or invoices generated during a period. Agentforce searches the connected Salesforce data and returns the relevant records or answer.
What needs to be in place first? +
The business needs reliable product, pricing, contract, order and billing data. Metric definitions, data ownership and governance should also be agreed before leaders rely on the dashboards.
Get a live, trusted view of revenue performance.
Start with a Revenue Infrastructure Review and leave with a prioritized roadmap to the data foundation behind Revenue Management Intelligence.
Book a Revenue Infrastructure Review