Auditing a Salesforce CPQ Nobody Enjoyed Using, Then Rebuilding the Quote Page Role by Role

The problem

The play

1. 1
   Scope the audit as twelve areas with time boxes, then execute against it
2. 2
   Census the fields instead of asserting bloat

   Every custom field on the five key objects was counted and measured for population rate, producing a hard number per object rather than an opinion.

3. 3
   Trace the ARR chain end to end and name the competing definitions

   The audit followed the actual path, a price rule calculates year-one recurring revenue on the quote, a CPQ handler writes it to the opportunity when a quote is created or updated as primary.

4. 4
   Find the silent failures in the automation layer

   The most urgent finding was not a missing feature. Several after-save record-triggered handler flows had no fault paths, so a single failed step aborted the entire flow and every downstream update went uncompleted with no error surfaced to anyone.

5. 5
   Inventory the price rules by what they are for

   All thirty-three live price rules were grouped by purpose, discount, ARR calculation, recurring-revenue calculation, historical price population, uplift, segment.

6. 6
   Treat permissions and the calculation user as a real risk

   License and permission-set assignment was reviewed and came back clean, but the audit recommended moving CPQ calculations off a named standard user and onto an integration user, so that a departure does not break quoting, and so standard users are not granted the elevated permissions the calculation path needs.

7. 7
   Reconstruct the amendment and renewal lifecycle

What it moved

From a LeanScale case studyRead the full case study →