The CPQ migration business case: a CFO-ready model with published numbers
A CPQ business case has five lines — licence, implementation, admin, integration upkeep, and the cost of the status quo — over three years. At 50 users, Kugamon runs about $158K over three years against about $840K for Revenue Cloud Advanced, using Salesforce’s published licence price and labelled estimates for what it does not publish. This page gives you the model, the sources, the risks and the sentence each executive needs to hear.
The three questions you will get
- The CFO asks “what does staying cost?”Licence continues; no new features; documentation retired to a PDF; admin time rises as the product ages. Zero is not the number.
- The CFO asks “why not Salesforce’s own successor?”$150–$200 per user per month published, a new data model, a 12–18 month rebuild in practice, implementation not published.
- The CFO asks “what is the risk?”The install base. Every renewal after go-live depends on it. The parallel run is the control.
The five lines
| Line | What goes in it | Where the number comes from |
|---|---|---|
| 1. Licence | Per user per month × users × 36. | Published for Kugamon ($65–$125) and Revenue Cloud Advanced ($150–$200); not published for Conga, DealHub, Nue. |
| 2. Implementation | One-time: configuration, data migration, training. | Published for Kugamon ($30K one-year, $25K multi-year); a labelled estimate for everyone else. |
| 3. Admin | Hours per month to run it × loaded rate × 36. | Your number; the calculator’s defaults are estimates. |
| 4. Integration upkeep | Each system that reads quote objects, re-tested on every release. | Count them; roughly a day per integration per release. |
| 5. Status quo | What staying costs: current licence, rising admin time, the risk of a frozen product. | Your current invoice plus the admin trend. |
Lines 1 and 2 are where published numbers exist and where vendors differ most. Lines 3–5 are yours. The TCO page explains each line; the calculator does the arithmetic.
The model at 50 users
Three-year totals from the calculator at 50 users. Solid segments are published prices; hatched are estimates, and the CFO will want to know which is which.
Change the user count and term in the calculator and paste the link into the business case; the view is in the URL.
The cost of staying
Staying on Salesforce CPQ is a legitimate option and the business case must price it honestly. The licence continues at your contract rate. Nothing new arrives; Salesforce describes a maintenance phase with support and critical fixes (Salesforce). The online documentation was retired in July 2026 for a single PDF (KB), so admin time rises as questions get harder to answer. Put a number on that trend — even one extra admin day a month is $10–15K a year — and the status-quo line stops being zero. There is no deadline: Salesforce says no end-of-life date has been announced and existing customers can renew.
What the CFO, CRO and CIO each need to hear
| Executive | The sentence | The evidence to bring |
|---|---|---|
| CFO | “The three-year cost is $X against $Y, and the implementation fee is fixed in the contract.” | The calculator link; the AppExchange pricing page; the vendor’s written fee. |
| CRO | “Reps quote in the same Salesforce screens; go-live is 4–8 weeks with one quote cycle in parallel.” | The timeline; the parallel-run procedure. |
| CIO | “Every object stays in our org on standard Products and Price Books; nothing to export if we ever leave.” | The five-question native test; the object mapper. |
| RevOps | “Our admin runs it; pricing changes take minutes, not tickets.” | A demo of a price change; the team page. |
The risk register
A business case without risks reads as a pitch. Bring the twelve from the risks page and name the three the CFO will ask about:
- Incomplete install base. Control: reconcile counts and value per account before cutover; migrate in one pass.
- Pricing drift. Control: one quote cycle in parallel, totals compared line by line.
- Timeline compression. Control: the cutover date is set after the parallel run passes, not before; there is no end-of-life deadline forcing it.
The one-page summary
Structure the summary page in this order; it answers the questions in the order they are asked.
- Decision requested
Approve migration from <current CPQ> to <target> at <users> users on a <term> contract.
- Three-year cost
Target: $X (licence $A published, implementation $B fixed, admin $C estimate). Alternative: $Y. Staying: $Z.
- Timeline
<weeks> from contract to go-live; one quote cycle in parallel; cutover on a date set after the parallel run passes.
- What changes for whom
Reps: same Salesforce screens. Admin: owns pricing. Finance: renewals automated.
- Risks and controls
Three risks, three controls, one owner each.
- Sources
The vendor’s published price page, the written fee, the calculator link, this site’s methodology page.
What Salesforce admins say on AppExchange
Quoted verbatim from the Kugamon listing on AppExchange. Reviewer names and dates as published there. Read all 134, including the critical ones →
★★★★★A new bar for RevOps
“As someone who has set up Salesforce CPQ before, I found Kugamon to be much more straightforward and easier to use. It took us just a few weeks to get going, rather than the few months or even years required by other systems.”
★★★★★Depth and Details
“They came well-prepared, asked the right questions, and provided genuinely useful guidance that helped us move forward with confidence. It’s rare to find a partner who engages with this level of thoroughness at such an early stage.”
★★★★★Great Product and Company!
“Kuldip and the team are super responsive, easy to work with, and are always innovating on the product. There are lots of great features, and what’s not available Kugamon provide ways to help us extend its functionalities.”
Five cost lines over three years — licence, implementation, admin, integration upkeep and the cost of staying — for each option, using published prices where they exist and labelled estimates where they do not, plus a risk register with a control for each risk and a one-page summary in the order executives ask. The calculator does the arithmetic.
Kugamon about $158K (licence and implementation published; admin estimated). Revenue Cloud Advanced about $840K (licence published at $200 per user per month, Salesforce; implementation and admin estimated). Conga, DealHub and Nue publish no prices, so every figure for them is an estimate: roughly $555K, $399K and $342K. Basis: TCO page.
The licence continues; no new features arrive (Salesforce); the documentation is now a single PDF (KB); admin time rises. There is no deadline, so the case for moving is the trend in those costs, not a date.
Published prices, your team size
Three-year totals for 1, 2 or 3-year terms at any user count. Every estimate is labelled.