Go-to-market guide · Legal, Product & Sales Ops
A shared playbook for how every new product, package or configuration gets defined, built, checked and released, so what reps can sell is exactly what the business agreed to sell.
The principle
If you can't configure it in Salesforce, we don't sell it.
Every product launches with the full set of configurations it's allowed to be sold in. Reps build deals inside that set without asking anyone. Anything outside it is an exception that crosses the moat to the product owner, and that should be rare: the goal is well under 1% of deals.
Everything sellable is a click away, priced and described. No waiting on Slack threads for "can we do this?"
Every configuration has an approved description and a trackable SKU, so contracts and revenue reporting stay consistent.
Decisions are made once, at launch, instead of deal by deal. Escalations become true exceptions.
How Salesforce sells a product today
Each step is a place where a launch can go wrong if it isn't planned. The guardrails in this guide map to these steps.
Production counts, November 2026. Every new product touches some of these, so a launch is never "just add a SKU".
The single-product model
Instead of a base product plus a pile of add-on SKUs, a package is one product the rep configures on the quote. The approach was proven for Executive Suite and is the recommended pattern for future launches.
The order form shows one line with a package price, not a price per component. Per-component pricing would mean going back to multi-product bundles, which adds significant work for Order Ops (amendments, microsites). For now, component prices live on the pricing sheet reps already use; Salesforce stays simple until the move to Revenue Cloud.
Try it
A working model of the rules discussed for Executive Suite. Change the options and watch the variant SKU, validation and description update the way they would on a quote. Prices are left out on purpose; limits shown are the proposed rules, pending the final configuration matrix.
SKU format and wording are illustrative. In Salesforce the description comes from rules that Legal owns (see Exceptions).
The launch path
A product moves to the next stage only when its gate is met. Most of the time goes into stages 1–3; the build itself is quick once the decisions are made.
What's being sold, to whom, and why. Tiers, terms, what's included, what it replaces, target customers, and how it fits drawdown and existing packages.
Every allowed option, the limits and dependencies between them (for example, max tripartite sessions by term), pricing logic, and any approval-only combinations such as very large deals. Legal pressure-tests it against scenarios before it's final.
Service description for each option, conditional notes (shown only when an option is selected), limits that need to appear in additional terms, and any restrictions such as one configuration per customer.
Product, configuration options, price rules, product rules, description logic, approval rules and rate-card entries — built from the matrix, never from Slack messages. Typically about a week once the matrix and wording are final.
Deal Desk quotes real scenarios; Order Ops runs an amendment, a renewal and an early upgrade; Finance confirms the SKU and revenue fields report correctly; Legal reviews generated order forms.
Deploy to production, update the handbook and pricing sheet, enable reps (what they can configure and what's an exception), and watch the first deals closely.
Due diligence before release
Use this before anything goes live. Ticks are saved in this browser only.
Who does what
| Step | Product owner | Legal | Sales Ops (Salesforce) | Deal Desk | Order Ops | Finance |
|---|---|---|---|---|---|---|
| Define the offer | A | C | I | C | I | C |
| Configuration matrix | R | C | C | C | C | I |
| Descriptions & terms | C | R | I | I | I | I |
| Sandbox build | I | I | R | I | I | I |
| Test & sign-off | A | R | C | R | R | R |
| Release & enable | A | I | R | C | I | I |
| Exceptions after launch | R | C | I | C | I | I |
R does the work · A owns the decision · C consulted · I kept informed
Exceptions and ownership
A configuration that can't be built in Salesforce goes to the product owner with a reason. If the same exception keeps coming up, it becomes a matrix change, not a habit.
Each customer has one configuration of a product at a time. A change is handled as an amendment (a negative amendment plus a new opportunity), not a second variant on the same account.
Some combinations are allowed but need sign-off, such as very large deals. They're defined in the matrix so they route automatically instead of by Slack.
Legal owns product descriptions but today has to send every wording change to Sales Ops, because descriptions are built into price rules. Three ways to give Legal direct control:
A table of descriptions per option and condition that Legal edits; the quote reads from it. Lowest moving parts.
Legal edits descriptions in the tool it already uses, and changes sync into Salesforce.
Legal keeps a structured list; a scheduled job loads it into Salesforce. Simple, but changes aren't instant.
Looking ahead
Salesforce is retiring CPQ, and the move to Revenue Cloud is on the roadmap. Everything in this guide carries over: the configuration matrix becomes the product's attributes and rules in Revenue Cloud's catalog, the variant SKU logic becomes standard, and Legal's descriptions plug into document generation.
Next steps
So the product owners fill in a consistent format.
All configurations, limits and pricing for Executive and Premier.
Scenario review of the matrix, then descriptions per option.
Align on the matrix; the build follows within about a week.