Salesforce Go for Revenue Cloud Series, Episode 1
Setting up a new Revenue Cloud org has always meant a long list of setup tasks before anyone can create a single quote. Salesforce Go changes that. In the first episode of our Salesforce Go for Revenue Cloud Series, Khaled El Halabieh walks through how Salesforce Go for Revenue Cloud Initial Setup turns most of that foundation work into a one-click setup, and where you still need to roll up your sleeves.
What we heard at Dreamforce 2026
Dreamforce 2026 was an exciting one for the Revenue Cloud community. Two themes stood out for teams like ours.
1. Meet sellers where they are: The front end is no longer just the Salesforce UI. Pricing, quoting, and approval logic now show up in the tools sellers already use, including Slack, Claude, and other AI assistants.
2. Speed of delivery through accelerators: Salesforce is shipping accelerators through Salesforce Go feature sets and templates. The one generating the most buzz is the CPQ-to-Revenue Cloud Migration Assistant, expected later this year.
That second theme is the inspiration for this series. Each episode looks at one accelerator and what it means for a real implementation.
What is Salesforce Go?
Salesforce Go is a guided setup experience inside Setup, organized by business outcome rather than by setup page. Instead of hunting through a dozen settings screens, you find a feature, check what is already in place, and turn it on.
One-click enablement: Features and feature sets turn on together, and the automated steps run for you.
Readiness checks: Go flags prerequisites before you turn anything on, and skips steps your org has already completed.
Platform-wide, not Revenue Cloud-only: Agentforce, Field Service, and Partner Cloud all have their own entries.
Revenue Cloud pillar: Foundation setup comes first, followed by feature sets such as Manage Billing and Dunning.
This episode focuses on that foundation: Revenue Cloud Initial Setup.
The manual path: 10 steps before your first quote
Today, getting Revenue Cloud to the point of a working quote requires a manual sequence of permission, setting, and procedural tasks. Here is how the documented path maps to what Salesforce Go covers.
Manual step | Covered by Go? | What it involves |
1. Assign permission set licenses | Partial | Revenue Cloud PSLs for admins and users |
2. Assign permission sets | Partial | Admin, pricing, catalog and quoting permissions |
3. Enable Revenue Settings | Yes | Core toggles in Setup > Revenue Settings |
4. Turn on Salesforce Pricing | Yes | Pricing engine, context definitions, activated price book |
5. Create or clone pricing procedures | Yes | Default pricing procedure ready to use |
6. Connect procedures in Pricing Setup | Yes | Default procedure assigned |
7. Update page layouts | No | Quote, Quote Line and Order layouts and components |
8. Catalog, categories, selling models | No | Your product and commercial model |
9. Create your first product | No | Product, selling model options, price book entries |
10. Create and test a quote | No | End-to-end validation |
The pattern is clear. Salesforce Go handles the platform plumbing. The parts that reflect your business, such as catalog, products, and layouts, stay with your team.
Demo: running Revenue Cloud Initial Setup
In the following video, Khaled walks through the full flow in a live org.
What to watch out for
Salesforce Go gives you a working foundation fast, but it is a starting point, not a finished implementation. Plan for these five realities.
Limitation | Impact |
Not everything is automated | Manual steps remain. Use Go’s own list as a checklist of what it does and doesn’t do. |
Defaults, not your design | Go creates default procedures. Custom pricing logic and settings still need to be designed and built. |
Runs org by org | Plan how configuration moves across your sandboxes and into production. |
No data or migration | Products, prices, assets and CPQ data still need a migration or build plan. |
License-gated | Features stay locked until users hold the right Revenue Cloud licenses. |
The takeaway: let Go handle the repeatable foundation, and spend your delivery time on the design decisions that differentiate your revenue model.
About the author
Khaled El Halabieh is a Principal Technical Architect at Stratus Carta. He has spent 10 years in the Salesforce ecosystem, working across Revenue Cloud and Steelbrick CPQ (Quote-to-Cash). Before joining Stratus Carta, he spent three years on the Revenue Cloud Practice Lead team at Salesforce, focused on delivery excellence. Connect with Khaled on LinkedIn to talk Revenue Cloud, Dreamforce.
About Stratus Carta
Planning a Revenue Cloud rollout, or weighing your move from CPQ? Stratus Carta’s team includes former Salesforce and Vlocity practitioners who work closely with Salesforce product teams. We can help you get from foundation to first quote, and from first quote to a design that fits your business. Reach out to us on LinkedIn.
