Go-to-market guide · Legal, Product & Sales Ops

From idea to sellable:
launching a product in Salesforce with guardrails

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.

Configured catalog Allowed tiers, terms, quantities, limits Pricing and descriptions built in Reps self-serve · normal approvals Product owner exception review Rep builds a deal Rare exception: outside the catalog → product owner review
For reps

Faster deals

Everything sellable is a click away, priced and described. No waiting on Slack threads for "can we do this?"

For Legal & Finance

Predictable terms

Every configuration has an approved description and a trackable SKU, so contracts and revenue reporting stay consistent.

For product owners

Fewer escalations

Decisions are made once, at launch, instead of deal by deal. Escalations become true exceptions.

The GA rule

Due diligence happens before general availability, not after

A product is generally available only when it ships with its complete, approved set of configurations. The work of deciding what can be sold, how it's described and how it's priced is done once, up front, by the people who own it.

Before GA, every launch must have
  • A complete configuration matrix: every option, limit and dependency it will ever be sold with
  • Approved wording from Legal for every option and condition
  • Pricing and discount guardrails, including drawdown rate cards
  • Approval-only paths defined for the rare cases that need sign-off
  • Tested quoting, amendment, renewal and reporting
  • Signed off by Product, Legal, Deal Desk, Order Ops and Finance
After GA
  • No customer-specific configurations. If it isn't in the catalog, it isn't sold
  • A new configuration means a new version of the matrix, through the same review, so it's available to every customer
  • Exceptions go to the product owner with a reason. Repeated exceptions become matrix changes, not habits
  • The first 30 days are reviewed and lessons folded back into the matrix

How Salesforce sells a product today

Eight steps from catalog to renewal

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.

1
ProductThe SKU in the catalog, with its configuration options
2
Price bookList price for each product and currency
3
Deal calcDeal terms agreed and approved in Winston
4
QuoteRep adds the product and picks options
5
RulesPrice rules calculate; product rules block invalid choices
6
ApprovalsDiscounts, terms and special products routed for sign-off
7
Order formGenerated with the line descriptions and terms
8
Order → contractBilling, amendments and renewals
0
active products in the catalog
0
price rules calculating prices and descriptions
0
product rules validating selections
0
active approval rules

Production counts, November 2026. Every new product touches some of these, so a launch is never "just add a SKU".

The single-product model

One product, many configurations

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.

What the rep sees

  • Options on the product itself: tier, coaching term, and quantities for chemistry calls, tripartite sessions, 360s and team debriefs
  • Price calculated from the options selected, as one package price
  • Invalid combinations blocked with a clear message (for example, too many tripartite sessions for a 6-month term)
  • Description written for them, matching exactly what was selected

Why it's better behind the scenes

  • Amendments, renewals and early upgrades stay simple: one line to change, not a bundle
  • Variant SKU: the same configuration always produces the same code, so Finance can track what's selling and spot trends
  • Fits drawdown: the product appears on the rate card like any other drawable product
  • Works with service packages such as a client delivery director assignment

The trade-off, decided

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

Configure an Executive Suite package

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.

2
Up to 3 on a 12-month term
1
Limit: 1 per licence term
0

Variant SKU

Order form description

SKU format and wording are illustrative. In Salesforce the description comes from rules that Legal owns (see Exceptions).

The launch path

Six stages, each with a gate

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.

1
Product owner

Define the offer

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.

Gate: a one-page offer summary that Sales leadership, Legal and Finance have seen.
2
Product owner + Legal

Build the configuration matrix

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.

Gate: a completed matrix on the Sales Ops template, with no "it depends" cells.
3
Legal

Write descriptions and terms

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.

Gate: approved wording for every option and for each condition that changes the wording.
4
Sales Ops

Build in the sandbox

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.

Gate: every row of the matrix can be quoted in the sandbox, and every blocked combination is blocked.
5
Deal Desk · Order Ops · Finance · Legal

GA readiness review

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.

Gate: written sign-off from each team, logged against the launch. No sign-off, no GA.
6
Everyone

Release and enable

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.

Gate: first 30 days reviewed: exceptions, errors and questions folded back into the matrix.

Due diligence before release

The release checklist

Use this before anything goes live. Ticks are saved in this browser only.

Who does what

Roles for every launch

StepProduct ownerLegalSales Ops (Salesforce)Deal DeskOrder OpsFinance
Define the offerACICIC
Configuration matrixRCCCCI
Descriptions & termsCRIIII
Sandbox buildIIRIII
Test & sign-offARCRRR
Release & enableAIRCII
Exceptions after launchRCICII

R does the work · A owns the decision · C consulted · I kept informed

Exceptions and ownership

What happens outside the catalog

Crossing the moat

Exception requests

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.

One customer, one configuration

Changing a live deal

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.

Approval-only

Built-in exceptions

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-owned descriptions

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:

Option A

Description records in Salesforce

A table of descriptions per option and condition that Legal edits; the quote reads from it. Lowest moving parts.

Option B

A panel in Winston

Legal edits descriptions in the tool it already uses, and changes sync into Salesforce. See the demo →

Option C

Maintained list with a daily load

Legal keeps a structured list; a scheduled job loads it into Salesforce. Simple, but changes aren't instant.

Looking ahead

Built to carry over to Revenue Cloud

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.

What that means for launches now

  • Keep each launch on the single-product pattern
  • Keep every decision in the matrix, not in custom code or one-off rules
  • Avoid stopgaps that add complexity; they make the migration slower

Next steps

Getting Executive Suite through the path

Sales Ops

Send the matrix template

So the product owners fill in a consistent format.

Product owners

Complete the matrix

All configurations, limits and pricing for Executive and Premier.

Legal

Pressure-test & write

Scenario review of the matrix, then descriptions per option.

Everyone

Review the week of 30 Nov

Align on the matrix; the build follows within about a week.