Preparing for Your Revenue Cloud Implementation Posted by
Greg ParashisThe short answer: The most successful Revenue Cloud implementations start before discovery, with business rules already written down. Before kickoff, document seven things: your product catalog rules, the factors that change price, mid-term amendment behavior, your approval matrix, every sales channel, your quote document requirements, and your renewal pricing policy.
Salesforce has renamed its revenue platform more than once, most recently moving from Agentforce Revenue Management back to Revenue Cloud. The name on the product has changed, but the fundamentals of a good implementation have not. The teams that get the most out of Revenue Cloud are the ones who show up to discovery with their business rules already documented.
Here is what to gather before your kickoff, and why it matters.
1. Your product catalog, including the rules behind it
Revenue Cloud’s catalog is the foundation everything else builds on: quoting, pricing, contracts, orders, and billing all pull from the same product data. Before discovery, document not just what you sell but how it is packaged. Are there prerequisites to buying certain products? Are any products mutually exclusive? Can everything be sold a la carte, or are some items only available inside a bundle?
If these rules live in your sales reps’ heads rather than on paper, discovery is the wrong time to discover that.
2. How pricing actually works
List every factor that changes a price. Does a longer subscription term earn an automatic discount? Does higher volume unlock lower unit pricing? Is an add-on cheaper when it is purchased alongside a bundle rather than separately? Revenue Cloud can support tiered, volume-based, and commitment pricing, but it needs your specific rules, not general assumptions about how they should work.
3. How amendments behave mid-term
When a customer adds a product halfway through their contract, what happens? Does the new item prorate? Does it co-term with the existing agreement, or run on its own schedule? Amendment and renewal behavior are controlled by the same catalog and pricing setup, so gaps here surface later as billing errors.
4. Your approval matrix
Map out what requires approval and who approves it. Discounts above a certain percentage, terms shorter than a set length, and specific products that always need sign-off regardless of discount are all common triggers. Name the approver for each scenario. A vague answer like “sales leadership” during discovery usually means more workshop time later to pin down the actual chain.
5. Every channel your sales come through
Do all quotes run through an internal sales rep, or do you also sell through ecommerce (business-to-consumer) or reseller channels? Each channel may need its own pricing rules, approval paths, or quote outputs, so your implementation partner needs the full picture of how deals reach your business.
6. What your quote documents need to produce
Bring a copy of the quote form you present to customers today. Be ready to talk through what is dynamic versus static: do the legal clauses change based on which products are on the quote? Does the layout differ by product line or customer segment? This is one of the most concrete artifacts you can hand over, and it saves real time in design sessions.
7. Your renewal pricing policy
When a contract renews, do you carry forward the customer’s existing price, or move them to current list price? If you use current price, are there standard uplifts applied, and how are they calculated? Renewal logic touches both your pricing model and your customer relationships, so it is worth getting precise here.
Your pre-discovery checklist at a glance
Item What to bring What happens without it Product catalog What you sell, how it is bundled, prerequisites, exclusions, and what can be sold a la carte Packaging rules surface mid-discovery from reps’ memory Pricing Every factor that changes a price: term, volume, commitment, and bundle discounts Configuration built on assumptions instead of your rules Amendments Proration and co-terming behavior for mid-term changes Billing errors after go-live Approval matrix Each approval trigger and the named approver for it Extra workshops to pin down the approval chain Sales channels Internal sales, ecommerce, and reseller paths Missing pricing, approvals, or quote outputs for a channel Quote documents Your current quote form, with dynamic versus static content marked Longer design sessions Renewal pricing Carry-forward versus current list price, and how uplifts are calculated Renewals priced in ways customers do not expect
Why this preparation pays off
None of this requires new tooling or a formal audit. It is information your team already has, just scattered across spreadsheets, sales playbooks, and institutional memory. Pulling it together before discovery means your implementation partner spends that time on meaningful design conversations instead of chasing down basic facts about your business, and it puts you on a faster path to a system that actually reflects how you sell. For how the end of Salesforce CPQ changes the scope of a quoting project, see CPQ implementation in 2026.
CloudMasonry’s revenue platform practice handles Revenue Cloud implementations from scoping through hypercare, and if you are moving off legacy CPQ, our migration guide covers that path. Contact us to talk through what to prepare before your kickoff.
Frequently Asked Questions
What should we prepare before a Revenue Cloud implementation?
Document your product catalog and packaging rules, every factor that changes a price, how amendments behave mid-term, your approval matrix with named approvers, every sales channel, your current quote documents, and your renewal pricing policy.
Is Revenue Cloud the same product as Agentforce Revenue Management?
Yes. Salesforce renamed Revenue Cloud to Agentforce Revenue Management in 2025, then returned to the Revenue Cloud name in 2026. The platform is the same, and so are the fundamentals of a good implementation.
Do we need new tools or a formal audit to prepare for discovery?
No. Most of this information already exists in spreadsheets, sales playbooks, and institutional memory. The work is gathering it in one place before kickoff so discovery time goes to design decisions.
Why do amendment and renewal rules matter so early in the project?
Amendment and renewal behavior are controlled by the same catalog and pricing setup as new quotes. Gaps found late tend to surface as billing errors or renewal pricing that surprises customers.
Greg ParashisThe short answer: The most successful Revenue Cloud implementations start before discovery, with business rules already written down. Before kickoff, document seven things: your product catalog rules, the factors that change price, mid-term amendment behavior, your approval matrix, every sales channel, your quote document requirements, and your renewal pricing policy.
Salesforce has renamed its revenue platform more than once, most recently moving from Agentforce Revenue Management back to Revenue Cloud. The name on the product has changed, but the fundamentals of a good implementation have not. The teams that get the most out of Revenue Cloud are the ones who show up to discovery with their business rules already documented.
Here is what to gather before your kickoff, and why it matters.
1. Your product catalog, including the rules behind it
Revenue Cloud’s catalog is the foundation everything else builds on: quoting, pricing, contracts, orders, and billing all pull from the same product data. Before discovery, document not just what you sell but how it is packaged. Are there prerequisites to buying certain products? Are any products mutually exclusive? Can everything be sold a la carte, or are some items only available inside a bundle?
If these rules live in your sales reps’ heads rather than on paper, discovery is the wrong time to discover that.
2. How pricing actually works
List every factor that changes a price. Does a longer subscription term earn an automatic discount? Does higher volume unlock lower unit pricing? Is an add-on cheaper when it is purchased alongside a bundle rather than separately? Revenue Cloud can support tiered, volume-based, and commitment pricing, but it needs your specific rules, not general assumptions about how they should work.
3. How amendments behave mid-term
When a customer adds a product halfway through their contract, what happens? Does the new item prorate? Does it co-term with the existing agreement, or run on its own schedule? Amendment and renewal behavior are controlled by the same catalog and pricing setup, so gaps here surface later as billing errors.
4. Your approval matrix
Map out what requires approval and who approves it. Discounts above a certain percentage, terms shorter than a set length, and specific products that always need sign-off regardless of discount are all common triggers. Name the approver for each scenario. A vague answer like “sales leadership” during discovery usually means more workshop time later to pin down the actual chain.
5. Every channel your sales come through
Do all quotes run through an internal sales rep, or do you also sell through ecommerce (business-to-consumer) or reseller channels? Each channel may need its own pricing rules, approval paths, or quote outputs, so your implementation partner needs the full picture of how deals reach your business.
6. What your quote documents need to produce
Bring a copy of the quote form you present to customers today. Be ready to talk through what is dynamic versus static: do the legal clauses change based on which products are on the quote? Does the layout differ by product line or customer segment? This is one of the most concrete artifacts you can hand over, and it saves real time in design sessions.
7. Your renewal pricing policy
When a contract renews, do you carry forward the customer’s existing price, or move them to current list price? If you use current price, are there standard uplifts applied, and how are they calculated? Renewal logic touches both your pricing model and your customer relationships, so it is worth getting precise here.
Your pre-discovery checklist at a glance
| Item | What to bring | What happens without it |
|---|---|---|
| Product catalog | What you sell, how it is bundled, prerequisites, exclusions, and what can be sold a la carte | Packaging rules surface mid-discovery from reps’ memory |
| Pricing | Every factor that changes a price: term, volume, commitment, and bundle discounts | Configuration built on assumptions instead of your rules |
| Amendments | Proration and co-terming behavior for mid-term changes | Billing errors after go-live |
| Approval matrix | Each approval trigger and the named approver for it | Extra workshops to pin down the approval chain |
| Sales channels | Internal sales, ecommerce, and reseller paths | Missing pricing, approvals, or quote outputs for a channel |
| Quote documents | Your current quote form, with dynamic versus static content marked | Longer design sessions |
| Renewal pricing | Carry-forward versus current list price, and how uplifts are calculated | Renewals priced in ways customers do not expect |
Why this preparation pays off
None of this requires new tooling or a formal audit. It is information your team already has, just scattered across spreadsheets, sales playbooks, and institutional memory. Pulling it together before discovery means your implementation partner spends that time on meaningful design conversations instead of chasing down basic facts about your business, and it puts you on a faster path to a system that actually reflects how you sell. For how the end of Salesforce CPQ changes the scope of a quoting project, see CPQ implementation in 2026.
CloudMasonry’s revenue platform practice handles Revenue Cloud implementations from scoping through hypercare, and if you are moving off legacy CPQ, our migration guide covers that path. Contact us to talk through what to prepare before your kickoff.
Frequently Asked Questions
What should we prepare before a Revenue Cloud implementation?
Document your product catalog and packaging rules, every factor that changes a price, how amendments behave mid-term, your approval matrix with named approvers, every sales channel, your current quote documents, and your renewal pricing policy.
Is Revenue Cloud the same product as Agentforce Revenue Management?
Yes. Salesforce renamed Revenue Cloud to Agentforce Revenue Management in 2025, then returned to the Revenue Cloud name in 2026. The platform is the same, and so are the fundamentals of a good implementation.
Do we need new tools or a formal audit to prepare for discovery?
No. Most of this information already exists in spreadsheets, sales playbooks, and institutional memory. The work is gathering it in one place before kickoff so discovery time goes to design decisions.
Why do amendment and renewal rules matter so early in the project?
Amendment and renewal behavior are controlled by the same catalog and pricing setup as new quotes. Gaps found late tend to surface as billing errors or renewal pricing that surprises customers.
Client Success Stories
Cappstone
A commercial cleaning and facility maintenance company serving 950+ businesses. Read how CloudMasonry migrated quoting, contracts, and vendor management from Salesforce CPQ to Revenue Cloud Advanced.
ZELUS
A 3D scanning and reality capture company. Read how CloudMasonry rebuilt eight years of Excel pricing logic in Salesforce Revenue Cloud Advanced.
One Identity
A cybersecurity company specializing in unified identity security. Read how CloudMasonry is carving out a dedicated Salesforce environment and migrating legacy CPQ to Revenue Cloud Advanced.
Brava Roof Tile
A premium composite roofing manufacturer. Read how a Salesforce CPQ transformation reduced waste, improved processes, and set their quoting up to scale.