Moving from spreadsheet quoting to a Salesforce-native CPQ
Spreadsheet quoting works until it does not: no approval trail, no install base, no automatic renewals, and a “real” price list that lives on one laptop. A Salesforce-native CPQ turns the spreadsheet’s columns into Price Book Entries and its rows into quote lines your admin owns. Preparation is the work; the implementation is typically 4–8 weeks.
Is it time?
- Under ten reps, one price list, no renewalsA spreadsheet is fine — revisit when any of those changes
- Discounts need approval and nobody can find the last quoteA native CPQ fits — quotes, approvals and renewals as Salesforce records
- You already sell subscriptions from a spreadsheetMove now — every renewal you miss is unrecoverable
What the spreadsheet is missing
The spreadsheet is not the problem. What it cannot do is.
| Capability | In a spreadsheet | In a native CPQ |
|---|---|---|
| Price list | A tab someone maintains; forks appear. | Price Book Entries in Salesforce, one source. |
| Approval | An email thread. | Threshold-based routing with an audit trail. |
| Quote document | Copy-pasted into Word. | Generated from the quote record. |
| Install base | Nobody knows what each customer owns. | Subscription records with start and end dates. |
| Renewals | A calendar reminder, if that. | Renewal opportunities created automatically. |
| Reporting | Export and pivot. | Standard Salesforce reports on standard objects. |
What to prepare before you start
- Clean the product list
One row per sellable thing, with a SKU-like code, a list price and a unit. This becomes Product2 and Price Book Entries.
- Write down the discount rules
Who can give what, up to what percentage, and who approves beyond that. Three rules is normal; thirty means you have been improvising.
- List every active customer contract
Product, quantity, price, start and end date. This is the install base; it is the one thing you cannot rebuild later.
- Pick one quote template
The one reps actually send. Everything else is a variant you can add afterwards.
Where your data will live
The implementation, step by step
- Load products and price books
From the cleaned list. Validate twenty random prices.
- Configure discounts and approvals
From the written rules.
- Load the install base
Every active contract as a subscription record.
- Run one quote cycle in parallel
Reps quote in both for two weeks; compare totals.
What it costs
Kugamon CPQ is $65 per user per month, billed annually with a 10-user minimum, as published on the AppExchange. Implementation is a fixed $30,000 on a one-year term or $25,000 on two or three years. There is no SI, no data model to redesign, and no licence for the spreadsheet you are leaving. Full editions: Kugamon pricing.
Not necessarily. Under ten reps with one price list and no renewals, a spreadsheet is fine. The tipping point is usually the first missed renewal or the first discount nobody can explain.
With Kugamon, typically 4–8 weeks. Most of that is preparation — cleaning the product list, writing down discount rules, and listing active contracts — rather than configuration.
$65 per user per month for CPQ (billed annually, 10-user minimum) plus a fixed implementation fee of $30,000 on a one-year term or $25,000 on two or three years (AppExchange).
You can keep it as a reference, but the Price Book in Salesforce becomes the source of truth. Running both is how forks reappear.
See your migration plan
Published timelines by source platform, a fixed implementation fee, and a calculator that labels every estimate.