What you’ll find in this blog:
- Salesforce innovation is now focused on Agentforce Revenue Management, a native platform that offers improved performance, tighter integration, and a future-ready architecture compared to CPQ.
- Agentforce Revenue Management connects quoting, contracts, billing, and fulfilment on a single data model, enabling a more unified revenue lifecycle.
- Organisations can adopt capabilities such as Contract Lifecycle Management or Dynamic Revenue Orchestration independently, allowing a phased approach rather than a full migration.
- Exploring the transition now positions organisations to take advantage of ongoing innovation and AI-driven revenue operations.
If you have been running Salesforce CPQ for a few years, it has likely served you well. It brought structure to your quoting process, enforced pricing rules, and gave your sales team a guided path from opportunity to quote. However, the landscape is shifting, and Salesforce’s investment is now firmly focused on Agentforce Revenue Management.
So what does this mean for CPQ customers, and why should you care?
A Platform Built on Core, Not a Managed Package
The most fundamental difference between Salesforce CPQ and Agentforce Revenue Management is architectural. CPQ runs as a managed package on top of Salesforce, which has always introduced constraints such as governor limits, upgrade dependencies, and limitations around customisation and calculations. ARM is built natively on the Salesforce core platform, using standard objects rather than package objects. This enables tighter integration with the rest of your organisation, improved performance, and a future-ready foundation that evolves with each Salesforce release rather than lagging behind.
For teams that have spent years managing workarounds and technical debt within CPQ, this shift alone is significant.
The Benefits of Making the Move
A Unified Revenue Lifecycle
CPQ has always been just one piece of a broader puzzle. Billing, contracts, order management, and revenue recognition often required separate tools or significant integration effort. Agentforce Revenue Management brings these capabilities together on a single platform with a shared data model, allowing the quote your representative creates to flow seamlessly through to contract, order, fulfilment, and invoice without data gaps or reconciliation challenges.
API-First Architecture
Every revenue process in Agentforce Revenue Management is exposed as an API. This makes it much simpler to connect your quoting and pricing engine to e-commerce portals, partner channels, or customer self-service experiences. If you have previously struggled to align CPQ pricing with an external system, you will recognise how significant this improvement is.
Scalability for Complex Configurations
The new Advanced Configurator introduces constraint-based configuration, replacing the rigid if-then rule logic that CPQ relied on. Instead of maintaining thousands of product and price rules that become increasingly fragile as your catalogue grows, you define relationships and allow the solver engine to determine valid configurations automatically. This represents a fundamentally more scalable approach to managing product complexity.
You Do Not Have to Adopt Everything at Once
One of the most compelling aspects of Agentforce Revenue Management is its composability. You can begin with the capabilities that address your most pressing challenges and expand over time.
Take Contract Lifecycle Management as an example. Many CPQ customers currently rely on third-party tools to manage contract generation, redlining, approvals, and e-signatures. With Agentforce Revenue Management, CLM is native. You can generate contracts directly from approved quotes, manage clause libraries, automate approval workflows, and handle e-signatures without leaving Salesforce. Legal teams can maintain pre-approved templates and clause libraries, while AI-driven clause generation helps accelerate drafting. According to KPMG, up to 40 percent of a contract’s value can be lost due to CLM inefficiencies. For organisations where the contract stage is a bottleneck in the deal cycle, adopting CLM alone could deliver immediate and measurable value.
Similarly, Dynamic Revenue Orchestration is another capability that can be leveraged independently. DRO provides a visual design canvas to map how commercial orders are broken down into fulfilment tasks, billing schedules, and downstream system hand-offs. If your current post-sale process involves manual order management or inefficient integrations between CPQ and your ERP system, DRO can streamline the entire workflow without requiring you to reimplement your quoting process from the beginning.
The key point is that migration does not need to be a greenfield project. You can adopt specific modules where the return on investment is clearest and build from there.
Looking Ahead
Salesforce has made it clear that Agentforce Revenue Management represents the future of revenue operations on the platform. CPQ is not disappearing immediately, but the pace of innovation is clearly aligned with the new architecture. Each major release is introducing new capabilities to Agentforce Revenue Management, including enhanced pricing formulas, multi-order creation, and deeper Agentforce AI integration, while CPQ’s roadmap is largely focused on maintenance. If you are currently planning CPQ enhancements or encountering limitations with your existing setup, now is an appropriate time to evaluate whether those efforts would be better directed towards Agentforce Revenue Management instead.
Organisations that begin exploring this transition now will be best positioned to take advantage of AI-driven revenue operations as the platform continues to mature.