Salesforce CPQ optimisation and revenue platform planning

Separate the quoting problem from the product decision

A complex quote can fail because product rules conflict, discount approval is unclear or the accepted offer cannot be turned into an order. Emerge begins with those commercial decisions rather than assuming that a new quoting product will resolve them. We support assessment and improvement of installed Salesforce CPQ estates and a deliberate plan for the next revenue platform.

Salesforce’s current revenue portfolio is marketed as Agentforce Revenue Management, formerly Revenue Cloud. Existing Salesforce CPQ implementations and the current revenue products should not be treated as interchangeable configurations. We confirm the installed package, contract, supported features and available commercial options with the customer before proposing an optimisation or migration. This page does not position the legacy CPQ package as the default net-new purchase.

Reconstruct the commercial model

The first deliverable is a map of what the organisation sells and how it becomes a valid offer. Products, bundles, options, quantities, terms and eligibility rules must reflect the actual business. A rule that exists only because of an old workaround is separated from a rule required by the commercial model.

Pricing authority is explicit. List prices, contracted rates, volume adjustments, discretionary discounts and taxes may come from different sources. We establish the order in which those decisions apply and who can approve an exception. A calculation that produces a number is not enough; the business must be able to explain why that price is valid.

The assessment includes amendments, renewals and cancellations where they matter to the installed estate. A new-sale demonstration often hides the complexity of changing an existing subscription or contract. Representative historical examples show which behaviours the future platform must preserve and which can be redesigned.

An illustrative quote-to-order workflow

A salesperson selects the authorised customer and opportunity context, then configures an offer using the agreed catalogue. Validation identifies incompatible choices or missing information before a document reaches the buyer. Pricing uses the approved source and records the relevant term and currency assumptions.

An exception follows a defined approval threshold with the information needed to make the decision. Approval applies to a particular quote version; a material change requires the appropriate re-evaluation. The generated document reflects that accepted version and the organisation’s reviewed commercial terms.

When the buyer accepts, the handover creates or updates the destination order through a controlled interface. A stable reference connects opportunity, quote, signed document and accepted order. The process verifies the destination’s business state rather than assuming that a successful API submission established an order ready for fulfilment or billing.

Decide between repair and transition using evidence

An installed estate may benefit from simplifying rules, repairing integration, improving test coverage or removing unused customisation. A transition may be justified by a changed business model, unsupported requirements or the cost of maintaining the existing design. We compare those options against real quote scenarios and the customer’s commercial arrangements.

A migration is not a field-by-field copy of the old package. Product modelling, calculation behaviour, approvals, contract records and downstream interfaces can differ. We identify which historical information must remain available and which active agreements need operational continuity. The plan records the treatment of open quotes and in-flight commercial approvals at cutover.

Current product naming is kept separate from licensing assumptions. A page describing a feature does not prove that it is included in the customer’s agreement or available in the intended configuration. The solution scope names the verified product and entitlement, and any unresolved commercial dependency remains visible before implementation starts.

Build a commercial regression set

Acceptance uses approved examples covering common and difficult deals. The set includes bundles, incompatible options, quantity changes, discounts, multiple currencies where relevant, amendments and renewals. Expected outputs are reviewed by commercial owners rather than copied blindly from a potentially incorrect legacy calculation.

Tests follow approvals, document generation and the destination handover. They include a changed quote after approval, a rejected order, a duplicated callback and a partially completed transaction. Finance and operations reconcile the accepted commercial values and identifiers before the release is considered ready.

The rollout may begin with one product family or sales motion. Parallel comparison can expose differences without immediately replacing every quoting path. The release plan distinguishes reversible configuration changes from commercial records that require a controlled correction or reconciliation.

Own the rules after launch

Emerge hands over the catalogue decisions, rule inventory, approval map, regression examples and integration contracts. Named owners approve pricing changes and maintain the scenarios used for future releases. The operating review examines repeated exceptions, quote rejection reasons and the cost of customisation.

The result is a quoting process the organisation can explain and a platform decision supported by its actual revenue model, with a clear route from today’s installed estate to the next justified increment.