The metrics to recognise on sight, and what each one does to you. Three knowledge checks along the way, and 4 clips from a senior licensing analyst.
This is a taught session, not a talking head. The instructor works through analyst grade slides, and three times the video stops on a question with four options on screen. Pause, commit to an answer, and the next slide explains which option is right and why each of the others is wrong. 4 times in the session the frame splits and a senior licensing analyst gives the view from inside real SAP negotiations, and the instructor picks the clip apart when the slides return.
The full narration of this session, section by section, for reading and reference. Guest analyst clips are marked.
Welcome back. Session twenty, and this closes module four. We could spend five more sessions walking through the remaining products one at a time, and it would be out of date within a year, because the catalogue changes faster than any course can track. So we are going to do something more durable instead. Every metric in the Salesforce estate belongs to one of four families, and once you can place a product in about a minute, you no longer need to have studied it. So today: the four families, Revenue Cloud and the definition question underneath it, Commerce Cloud and the revenue share, and the three questions that identify any new line on sight. Three knowledge checks. Let's begin.
Five objectives. First, sort any metric into four families: people, capacity, consumption and business outcome, and the fourth is the dangerous one. Second, read Revenue Cloud correctly, because it is a seat line with a quiet dependency on who touches a quote. Third, handle a revenue share, where the licence is a percentage of your trading and success is priced automatically. Fourth, recognise a metric on sight using three questions that place any new Salesforce line within a minute. And fifth, hold the whole portfolio on one page listing every line, its metric, its direction and who owns it.
So, four families. People: users, roles, tiers, failing through over-assignment and dormant accounts. Capacity: cores, environments, storage, failing through sizing that nobody revisits. Consumption: credits, conversations, sends, failing through configuration nobody costs. And outcome: revenue, orders, contacts, which fails by charging you for succeeding. Let me explain why that fourth family deserves a different kind of attention from the other three.
Guest analyst clip.
Growth is the thing every business case in your organisation promises. So an outcome metric is the one line where the company delivering on its plan is the same event that raises your costs, and there is no inefficiency to point at afterwards.
Right, Revenue Cloud and CPQ, which is a seat line with a definition question underneath it. Who needs the licence, because quoting capability is often needed well beyond the sales team, so establish whether approvers, finance and support need it or only the authors. Does approval count as use, since an approver touching a quote may require licensing, and you want that boundary in writing before you size the population. Is billing a separate line, because quote to cash spans several products with separate metrics. And what about the platform layer, since CPQ objects can pull users into higher licence types, which interacts with the Platform population from session eight. This is a people metric with an unusually wide population, and the count grows through process design rather than through hiring, which puts it halfway toward being a consumption line.
First knowledge check. Which metric family charges you more when the business performs well? A, people. B, capacity. C, consumption. D, business outcome. Pause here and pick an answer before you continue.
D. An outcome metric ties the licence directly to trading performance, so a good year raises the bill without anybody deciding anything, and unlike the other three there is no waste to remove and no efficiency to find. A rises with headcount, which is a decision. B rises with deployment, also a decision. C rises with configuration, which is a decision made by somebody who did not realise they were making one, and that is bad enough. Only D charges you for the result you were actually trying to produce.
Commerce Cloud then, which is the clearest outcome metric in the portfolio. It is priced against trading volume, commonly a share of the value transacted through the platform. So the licence scales with success, and a strong season raises the fee automatically and immediately. There is no efficiency lever, meaning you cannot optimise your way down, and the only variables are rate and structure. Which makes the tiers the lever: rate bands, thresholds, and where they sit relative to your forecast. And the floor matters, because a minimum commitment protects them in a bad year, so negotiate it knowing that is what it is for. Let me set out what to actually ask for.
Guest analyst clip.
Four things, then. Declining rate bands, because the percentage should fall as volume rises and a flat rate applied to growth is punishing. What counts as transacted value, so returns, cancellations, tax and shipping, each of which is worth arguing about separately.
The minimum commitment, which is what you owe in a poor year and is the risk sitting on your side of the table. And channel scope, meaning which sales channels flow through the metric and what happens when you add one, because adding a channel can move a large volume of trading inside the metric without anybody intending it.
Second knowledge check. On a revenue share model, what is the most valuable structural ask? A, a lower flat percentage. B, declining rate bands as volume grows. C, a longer term at the same rate. D, payment terms extended to sixty days. Pause here before you continue.
B. Bands change the shape of the curve rather than shifting it down, so they protect you precisely in the scenario your business is working toward, which a flat reduction does not. A helps at every volume and helps least where it matters most, and it is the ask most buyers lead with. C locks a rate that may be wrong for three years and gives away the renewal. And D is a cash flow improvement rather than a licensing one, and trading rate structure for it is a poor exchange.
A word on the long tail. Industry clouds bundle differently, as vertical packages with their own objects and sometimes their own metric. Field Service adds its own populations: technicians, contractors and dispatchers, each with a different licence shape. Acquired products keep their models, so anything Salesforce buys arrives with the metric it already had, which is why the catalogue is not internally consistent. The catalogue outpaces any course, which is exactly why the four families matter more than any list of product names. And so you place it, then price it. Let me give you the three questions that do the placing.
Guest analyst clip.
Identify the family first, and the right questions follow automatically. That is the whole method, and it is worth more than memorising a catalogue that will be different next year.
So to state them plainly. What makes this number go up: hiring, deploying, configuring or trading, and that answer names the family. Who can make it go up, and do they know that they can, which is the governance question. What makes it go down, and if the honest answer is nothing, you have an accumulating line and it needs a rule attached. Then ask the standard four we have used all course: peak or average, what counts, when it is measured, and the rate above the commitment. And write the answers on the order form rather than in an email, because definitions that live in documentation can be reinterpreted and definitions in your contract cannot.
Five failures. A new product bought on the old mental model, so assuming a seat metric because every previous line was one. Outcome metrics sized on today's trading, meaning a commitment written against a year the business fully intends to beat. No portfolio view, so nine products, nine metrics, nine separate conversations and no single page. Each line owned by its own department, so nobody sees that four of them rise together when the company grows. And definitions left in documentation, which across a portfolio this large is a great deal of surface area you do not control.
Last knowledge check. A new Salesforce product is proposed. What is the first question? A, what does it cost per user. B, what makes the number go up, and what makes it go down. C, which competitors offer the same thing. D, can it be added to the existing agreement. Pause here and pick an answer before you continue.
B. That pair of questions identifies the family, the growth mechanism and whether the line is reversible, and everything else you need follows from the answers. A assumes a per user model before establishing that there is one, which is the single most common error across this entire portfolio. C is a procurement question that arrives later and matters less than the structure. And D is worth asking, and it is about packaging, which you cannot judge until you understand what it is you are packaging. Let me describe the page that holds all of this together.
Guest analyst clip.
One page, every line, five columns. The product and its metric, named plainly, in the terms the contract uses rather than the marketing name. The family: people, capacity, consumption or outcome, one word, and it predicts the failure mode. Direction of travel: rising, flat or reducible, and most estates discover more rising lines than they expected. The owner, one name per line, where blank cells are your priority list rather than an administrative gap. And the renewal date, because lines that renew together can be negotiated together, and in most organisations they are not, purely because nobody has ever seen them side by side.
Three sentences. Every line in the Salesforce catalogue belongs to one of four families, people, capacity, consumption or business outcome, and once you can place a product in a minute you no longer need to have studied it, because the family predicts how it will fail. Outcome metrics deserve particular respect because they price your success rather than your waste, so on a revenue share the structure matters more than the rate, and declining bands protect you exactly in the scenario your business is working toward. And hold one portfolio page with every line, its metric, its family, its direction and its owner. That closes module four.
Homework before session twenty one, about two hours, and this one becomes a permanent artefact. One, list every Salesforce line you hold, from the order forms, including anything bundled into another product. Two, assign a family to each: people, capacity, consumption or outcome, one word per line, no exceptions. Three, mark the direction, rising, flat or reducible, and be honest about which ones only ever rise. Four, name an owner per line, and the blanks are the finding, and there will be blanks. And five, add the renewal dates, then look for lines that could be brought together into a single negotiation.
Five guides, all on redresscompliance dot com. Salesforce Commerce Cloud pricing covers the trading value metric, the bands and the minimum commitment. Revenue Cloud and CPQ licensing sets out who needs a licence and where the population turns out to be wider than expected. The CPQ and Billing licensing playbook covers quote to cash across several products and several metrics. Salesforce Industries Cloud licensing explains how the vertical packages are built and where they differ. And Salesforce add ons pricing walks the long tail of the catalogue line by line.
That is session twenty, and module four is complete. The thing to take away is that you do not need to know the catalogue, you need to know the four families, and then any product anybody puts in front of you becomes a set of questions you already have. Next time we open module five on the agreement itself, starting with the order form in detail: term, ramp, co-termination, auto renewal and the uplift clause. See you then.