This agenda is part of the annual client advisory meeting agenda, which offers a short insert for the same trigger. Use this page when the CPQ replacement deserves its own half hour. Companion agendas cover a license true-up and a laboratory system replacement.
Who sits at the table for a quoting-system decision
Four seats are enough. Each person answers the blocks they know first-hand, so the meeting does not depend on one person guessing.
| Seat | Why this person | Answers blocks |
|---|---|---|
| CRO or CFO | Signs off on discount policy and decides what happens to the legacy quoting data | 1, 4, 5 |
| RevOps lead | Knows which approval chains exist and when each one started | 2, 3 |
| Salesforce administrator | Knows the approval objects, field history settings and what the migration copies | 2, 3, 4 |
| You, the RevOps consultant | Keeps time and writes the decision down | All |
Leave the new CPQ vendor and the systems integrator out of this one. Send the invite with one line: "Half an hour on where deal exceptions were approved, before the old quoting tool is retired. Descriptions only; nothing is exported."
The five blocks on one page
Illustrative. A RevOps consultant is moving a fictional 340-person industrial software company off Salesforce CPQ. Quotes go back to 2017, and the new tool will import open quotes and the product catalog only.
| Time | Block | The question | Who answers |
|---|---|---|---|
| 0-5 min | Cutover | When does the new quoting tool go live, and when do Salesforce CPQ licenses end? | CRO or CFO |
| 5-12 min | Approval map | Which approval types exist (discount, payment terms, legal), and since when? | RevOps lead |
| 12-18 min | The full record | Are rejected and recalled requests kept, and do approver comments move with the quote? | Salesforce administrator |
| 18-24 min | Ownership | Who owns the old CPQ data after go-live, and is any of it restricted by customer contracts? | CRO or CFO and administrator |
| 24-30 min | Decision | Does the company want to hear how licensing approved business data works, and who would lead it? | CRO or CFO |
Each block: what to ask and what a strong answer sounds like
Minutes 0-5: cutover
A strong answer has two dates: "Go-live is the first of next quarter, and our CPQ renewal lapses four months after that." The second date matters more, because that is when the approval layer becomes hard to reach. Salesforce describes CPQ as end of sale, not end of life, so some companies have a plan but no date. If that is the case here, say so and move on; the decision in block five will probably be a dated revisit.
Minutes 5-12: approval map
A strong answer names the chains and their start years: "Discounts over 15% go to the regional VP, then finance, since 2018. Nonstandard payment terms have gone to the controller since 2020. Legal redlines are tracked separately." Probe gently for exceptions that were approved outside the system, by email or in a chat thread. Those are worth noting, but they are a separate store with separate owners.
Minutes 12-18: the full record
This is where the answer to "where are the exceptions?" is usually found. A signed contract shows the final price; the context sits in the approval history. Salesforce's classic Approval History records statuses such as Submitted, Approved, Rejected, Reassigned and Recalled, and CPQ's Advanced Approvals creates an approval record for each approver who received a request, each with its own status. A strong answer: "We keep every request, including rejections, and approvers must leave a comment above 20%." A weak but useful answer: "Only approved records, and comments are optional." Ask also whether field history tracking was on for discount fields: with Field Audit Trail off, Salesforce keeps field history for up to 18 months, and tracking starts only from the day it was enabled.
Minutes 18-24: ownership
A strong answer names a person and a plan: "The CFO owns the org after go-live. We will keep it read-only for a year, then decide." Listen for customer contracts that limit how quote data can be used, and for a reseller or channel partner whose quotes sit in the same org. Both are rights questions for later review, not reasons to stop the meeting.
Minutes 24-30: decision
Before asking for a decision, state three facts. SourceX licenses approved business data directly from companies for AI training and evaluation, and manages agreement, rights review, data preparation, delivery and payout. You are a SourceX referral partner and may receive a reward if a qualifying license completes, funded separately by SourceX and never deducted from the company's payout. The CPQ project does not depend on the answer.
Three answers that change the plan mid-meeting
| What you hear | What it means | What you do |
|---|---|---|
| "The old org is already archived to cold storage." | The records may exist but access is now a project | Ask who holds the archive, then go straight to block five |
| "Approvals were turned off in 2022; everyone just emails finance." | The system holds only part of the trail | Note the years with system approvals and the email period separately |
| "We use a reseller for most quotes." | Some records may belong to or be restricted by a third party | Record the reseller's role for the rights review and continue |
What the meeting decides, and what stays open
The half hour ends with one of three outcomes written in the notes, each with a name and a date.
- Introduce now. Approval records exist across several years, the CRO or CFO opts in as sponsor and names the CEO, who can authorize a licensing discussion, as the authorized contact. Send the annotated CPQ replacement introduction email the same week.
- Revisit by a date. The cutover date or the approval scope is unknown. Set the follow-up before the CPQ licenses end.
- Stop. The owner declines, the records are gone, or the company is below the size baseline.
For "introduce now", the company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Sign the Channel Partner Agreement before submitting; attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application.
What nobody can settle in this room: whether customer names and pricing can be de-identified, whether contracts allow licensing, whether there is demand for this kind of record, and what any offer would be. SourceX assesses those with the company. The Salesforce system page covers export routes, the sell-side kickoff agenda shows a different event-driven meeting, and the ERP replacement guide covers the finance-side equivalent.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If the meeting ended on "introduce now", register as a partner, check the company against who qualifies and read the program terms before the CPQ licenses lapse.