Your First Quote in Revenue Cloud: Seven Setup Decisions That Prevent Rework
Quick Question
What should you decide before building your first quote in Revenue Cloud?
Seven things: how the product is structured, the rules for each component, how each product is sold, where prices live, how reps find products, which attributes drive the configuration, and how you will test the quote. Deciding these first saves you from rebuilding the product later.
Your first quote shows you how your setup behaves. If a component is optional when it should be required, a price comes up as zero, or a rep can’t find a product, the cause is usually a setup choice that nobody made on purpose.
This checklist covers seven of those choices. The examples use one product: a configurable rack server with a processor, memory, hard drive, network adapter, and warranty. The screenshots come from our walkthrough, where we build this server in a Revenue Cloud demo org and take it through the quote.
1. Decide what is a bundle and what is a Standalone product
If customers choose the parts of what they buy, you are selling a bundle: a parent product with components grouped under it. Here, the server is the parent. Processor, memory capacity, hard drive, network adapter, and warranty and support are the component groups, and each group holds its options.
Sketch the parent, the groups, and the options on paper before you build. Changing the structure after you have added pricing and rules means reworking all of it.
Bundle structure for the rack server: one parent product with five component groups.
2. Set the rules for each component
Each component needs its own rules. For every group, decide:
- Is the component required?
- Is it included by default?
- Can the rep change the quantity?
- Is the price included in the parent?
- Does the quantity scale with the parent (proportional), stay fixed (constant), or not scale (none)?
- What are the minimum and maximum quantities, and how many options can a customer pick from the group?
For the memory group, 8 GB might be included by default, with 16 GB and 32 GB as alternatives. Write the rules in a table first, with columns for component, required, default, and quantity range. Then you can compare the table to what the system does.
Cardinality settings for a memory option, including the quantity scaling method.
3. Pick a selling model for every product
A product selling model says how a product is sold, such as one time or on a recurring term. Pricing attaches to the selling model, so choose one for each product.
In the example, the server hardware sells one time and the warranty sells on an annual term. Mixed bundles like this are common, and the configurator shows one-time and recurring totals separately. Choose the models early, since your price books are built around them.
4. Decide where prices live
Prices live in price books. Each price book entry ties a product and a selling model to a list price. Before you load prices, decide:
- Will you use only the standard price book, or separate ones by region, segment, or channel?
- Who owns price changes, and who reviews them?
- Will the bundle parent carry a price, or will the price come from its components?
Either approach works for the parent. Pick one on purpose so the quote total doesn’t surprise anyone.
Price Books and Product Selling Model Option on the product record. The standard price book entry uses the One-Time selling model.
5. Organize catalogs and categories around how reps search
Catalogs and categories control how reps browse, and search settings control what they find. In the example, a hardware catalog has categories for memory, PCIe, power supplies, processors, servers, and solid state drives. Services and software each have their own catalog.
Decide three things:
- How many catalogs you need, and what goes in each.
- Which product fields reps can search and filter on, such as product name and product type.
- When the search index gets rebuilt. Rebuild it after you change product or search settings so results match the catalog.
Then ask someone who didn’t build the catalog to find a specific product.
Browsing the hardware catalog from a quote, with categories on the left.
6. Choose the attributes that drive the configuration
Attributes capture the details that change what the customer gets, such as memory size, warranty duration, and server configuration. Use picklists so the values stay consistent. Define an attribute once and let products inherit it.
Decide which attributes the configurator must collect, which are for information only, and which values are allowed. Free-text attributes lead to several spellings of the same value.
Inherited attributes on the server product: Server Configuration and Warranty Duration (Years), both picklists.
7. Plan how you will test the quote
Treat the first quote as a test script. Create a test quote and run the same cases after every change:
- Add the bundle and open the configurator.
- Change the defaults, such as memory size and warranty term.
- Check that product validation catches combinations that shouldn’t be allowed.
- Confirm the quote lines and totals match what you expected, with instant pricing on and after a manual price update.
- Apply a discount and follow the quote through review and approval. In the walkthrough, the quote shows In Review once a 15% discount is on.
- Create an order from the approved quote and check that the lines, discount, and tax carried over.
Write down the expected totals before you start. If you plan to use an agent to create quotes, run the same cases through it and compare the results to your manual quote.
The configurator for the server, with product validation on and totals by billing frequency.
Quote line items after configuration: 17 lines and a grand total of USD 19,518.
How these decisions connect to the readiness questions
In Agentforce Revenue Management: Why B2B Revenue Teams Need an AI-Ready Foundation, we listed eight questions to answer before implementation. The seven decisions above are where several of those questions get answered in practice.
| Setup decision | Readiness question it helps answer |
|---|---|
| 1. Bundle structure | Is the product catalog clean, structured, and maintainable? |
| 2. Component rules | Is there CPQ technical debt that will conflict with the new system? |
| 3. Selling models | Is billing logic tied to contracts and orders, or re-entered by hand? |
| 4. Price books | Are pricing and discount rules documented and consistently applied? |
| 5. Catalogs and search | Is the product catalog clean, structured, and maintainable? |
| 6. Attributes | Is account and transactional data reliable enough to trust? |
| 7. Quote testing | Are approval workflows defined and actually followed? |
The other two questions, about contract templates and connected systems, go beyond the first quote. They are the next step once the quote behaves the way you designed it.
FAQs
Do we need to design the whole catalog before building the first quote?
No. Start with one representative bundle and make the seven decisions for it. What you learn will shape the rest of the catalog.
Can we reuse product data from Salesforce CPQ?
Some of it. Products and price book records can often be reused. Configuration logic needs a case-by-case review, because some of it is platform-based and some is specific to CPQ.
Who should help make these decisions?
The admin or architect who will build the setup, plus someone from sales operations, someone from finance, and the product owner. Each decision affects at least two of those groups.
Related Blogs
Recent Blogs

Your First Quote in Revenue Cloud: Seven Setup Decisions That Prevent Rework
Three things slow every Salesforce team down — regardless of size or setup. Here’s what they are, and what mindZolt built to fix each one.

10 Days. 6 Cities. Then Dreamforce. Here’s What We Brought Back.
From six cities on the Road to Dreamforce to a week of Salesforce AI announcements, here’s what mindZvue brought back—and where mindZolt fits into everyday Salesforce work.

The Dreamforce 2026 Guide Nobody Else Can Write
The only Dreamforce 2026 guide built from years of showing up — real mindZvue stories, first-timer tips, and what’s actually coming in San Francisco, September 15–17