Salesforce ISV OEM licensing—the commercial structure that AppExchange ISVs use to embed Salesforce capability inside their own products—is one of the least transparent dimensions of the Salesforce commercial surface. The OEM license, sometimes called the Embedded license, gives an ISV the right to resell a Salesforce-powered application to its own end customers, with the underlying Salesforce platform abstracted behind the ISV's own product branding. The commercial structure is meaningfully different from the standard end-customer Salesforce contract, and the negotiation discipline is meaningfully different too. The ISVs that build commercially successful OEM-embedded products consistently negotiate OEM commitments that materially outperform the standard ISV defaults; the ISVs that don't build the disciplined negotiation posture overpay across the commitment term and frequently find their unit economics constrained by the underlying Salesforce cost structure.
This article is written for the ISV-side buyer—the ISV executive, the product leader, or the procurement leader who is negotiating the OEM commitment with Salesforce. The framing is buyer-side and vendor-neutral. The OEM commercial structure is not particularly transparent, but the structural dimensions of the commitment can be understood, scoped, and negotiated with the same discipline that applies to the standard end-customer Salesforce contract. The disciplined ISV captures meaningful commercial outcomes across the OEM commitment, with material implications for the ISV's product economics and the broader business.
What the Salesforce ISV OEM license actually includes
The OEM license gives the ISV the right to provision a Salesforce-powered application to end customers, with the underlying Salesforce platform abstracted behind the ISV's own product. The license includes a defined subset of the Salesforce capability surface—typically the Sales Cloud or Service Cloud equivalent, plus a configurable set of platform capabilities. The license does not include the full Salesforce capability surface; the ISV has to negotiate which capabilities are included in the embedded commitment.
The OEM license has three structural components. The embedded capability set defines which Salesforce capabilities the ISV's product can use. The standard embedded set typically includes the Sales Cloud or Service Cloud core capability, the platform automation surface (Flow, Process Builder equivalent), the standard objects, and the API access. The expanded embedded set can include additional capabilities such as Einstein, the Marketing Cloud-equivalent capability, the data layer capability, or specialized industry-vertical capability. The per-user pricing defines the commercial cost per end-user-month, with volume tiers that scale with the ISV's deployed user base. The volume commitment structure defines the minimum committed end-user volume across the commitment term, with the per-user pricing scaling against the committed volume.
| OEM Component | Standard ISV default | Disciplined ISV outcome |
|---|---|---|
| Per-user-month price | $8-$18 | $4.50-$12 |
| Volume commitment | 2-3 year, 80-100% | 3-5 year, 50-75% |
| Volume tier scaling | Static | Tiered with thresholds |
| Capability expansion | Renegotiation | Pre-agreed pricing |
| End-customer migration | Restricted | Negotiated portability |
The embedded capability set is the most consequential dimension
The single most consequential dimension in the OEM commercial discussion is the embedded capability set. The standard embedded set covers the Sales Cloud or Service Cloud-equivalent capability, but the ISV's product frequently requires additional capabilities—Einstein for AI-powered features, Data Cloud for unified customer profile, Marketing Cloud for messaging surface, or specialized industry-vertical capability. Each additional capability has a commercial cost, and the disciplined ISV scopes the embedded capability set against the product's operational requirement rather than against the default embedded surface.
The disciplined approach is to document the specific capabilities the ISV's product actually requires, with the operational use case for each capability, and to scope the embedded capability set against that operational specification. The maximum addressable embedded capability set produces a commercial cost that frequently constrains the ISV's product economics; the operational specification produces a commercial cost that aligns with the product's unit economics.
The volume commitment structure
The volume commitment structure is the second most consequential dimension in the OEM commercial discussion. The standard ISV default commits to a static end-user volume across the commitment term, with the per-user pricing scaling against the committed volume. The disciplined ISV negotiates a tiered volume commitment structure, with the per-user pricing stepping down at pre-agreed volume thresholds, and with explicit protections against the volume-commitment exposure when the ISV's product adoption deviates from the original assumptions.
The volume commitment exposure is the most common commercial pitfall in OEM commitments. The ISV that commits to a static volume of 50,000 end-users across a 3-year term, but only achieves 25,000 deployed end-users, frequently finds itself paying the committed volume rather than the deployed volume. The disciplined volume commitment structure includes protections against the volume-commitment exposure, with explicit mechanisms for scope-down if the deployed volume falls short of the original assumptions.
The capability expansion mechanics
The capability expansion mechanics are the third dimension that frequently surfaces commercial exposure in the OEM commitment. The standard ISV default treats capability expansion as a renegotiation event, with the expansion pricing established at the moment of expansion rather than at the moment of original commitment. The disciplined ISV negotiates the capability expansion mechanics at the moment of original commitment, with pre-agreed expansion pricing for the capabilities that the ISV's product roadmap is likely to require in the commitment term.
The disciplined capability expansion mechanics include the expansion pricing for the specific capabilities the product roadmap targets, the expansion timeline that the ISV can exercise, and the protections against the expansion-moment commercial exposure that the renegotiation event would otherwise expose the ISV to.
The end-customer migration provisions
The end-customer migration provisions are the fourth dimension of the OEM commercial structure that deserves negotiation attention. The standard ISV default restricts the end-customer migration to a Salesforce-standard contract if the ISV's product engagement terminates. The restriction can be commercially material to the ISV's end customers, who may have invested meaningfully in the ISV's product configuration and may not have a clean exit path from the underlying Salesforce platform.
The disciplined ISV negotiates the end-customer migration provisions, with explicit portability mechanisms for the end customer's data and configuration, and with explicit commercial mechanisms for the end customer's continuation on Salesforce if the ISV's product engagement terminates. The end-customer migration provisions protect both the ISV and the ISV's end customers from the commercial exposure that the restricted migration would otherwise produce.
The five levers that move the OEM commitment
1. Scope the embedded capability set against operational requirement
The embedded capability set should be scoped against the product's operational requirement, with explicit documentation of the capabilities the product actually requires. The default embedded surface frequently includes capabilities the product does not consume, producing a commercial cost that constrains the product economics. The disciplined scoping captures 25-40% reductions in the embedded commercial cost without operational impact.
2. Negotiate the volume commitment structure with tier thresholds and scope-down protections
The volume commitment structure should include tier thresholds at which the per-user pricing steps down, and scope-down protections that prevent the volume-commitment exposure when deployed volume falls short of the original assumptions. The disciplined volume commitment structure captures 20-35% reductions in the volume-commitment exposure across the commitment term.
3. Pre-negotiate the capability expansion mechanics
The capability expansion mechanics should be pre-negotiated at the moment of original commitment, with explicit pricing for the capabilities the product roadmap targets. The disciplined pre-negotiation prevents the renegotiation-event commercial exposure that the standard default would otherwise produce, and produces 15-25% reductions in the capability expansion cost across the commitment term.
4. Negotiate the end-customer migration provisions
The end-customer migration provisions should be negotiated with explicit portability mechanisms and commercial continuation provisions. The disciplined provisions protect the ISV and the ISV's end customers from the migration-restriction exposure, and produce strategic value beyond the immediate commercial outcome.
5. Coordinate the OEM commitment with the broader ISV partnership
The OEM commitment should be coordinated with the broader ISV partnership commitments—AppExchange listing, partner co-marketing, partner enablement. The bundled negotiation captures the leverage that aligns the OEM commitment with the broader partnership, and prevents the negotiation-leverage dilution that occurs when the OEM commitment is negotiated as a discrete commercial discussion.
The pitfalls that show up in OEM commitments
Six patterns appear repeatedly in OEM commitments. First, the embedded capability set is scoped at the default embedded surface rather than against the product's operational requirement. Second, the volume commitment structure is static rather than tiered, exposing the ISV to volume-commitment exposure when deployed volume falls short. Third, the capability expansion mechanics are not pre-negotiated, exposing the ISV to renegotiation-event commercial exposure. Fourth, the end-customer migration provisions are restrictive, producing the strategic exposure for the ISV's end customers. Fifth, the OEM commitment is negotiated as a discrete commercial discussion, dropping the volume leverage that would have applied in a coordinated negotiation with the broader ISV partnership. Sixth, the renewal mechanics are silent on the OEM commitment, exposing the ISV to discretionary repricing at the renewal moment.
What a well-negotiated OEM commitment looks like
A well-negotiated OEM commitment has seven features. The embedded capability set is scoped against the product's operational requirement. The volume commitment structure has tier thresholds and scope-down protections. The capability expansion mechanics are pre-negotiated with explicit pricing. The end-customer migration provisions include portability mechanisms and commercial continuation provisions. The OEM commitment is coordinated with the broader ISV partnership commitments. The renewal mechanics specify the OEM commitment and the protections against discretionary repricing. And the OEM commitment includes the ISV's protections against the operational and commercial exposure that the standard ISV defaults would otherwise produce.
Benchmark outcomes by ISV scale
For a mid-sized ISV with 10,000-50,000 deployed end-users, the disciplined OEM commitment typically lands at $6.50-$10.50 per end-user-month, against the standard default of $10-$16 per end-user-month. The annual commercial commitment lands at $780K-$6.3M, against the standard default of $1.2M-$9.6M for equivalent deployed volume.
For a large ISV with 100,000+ deployed end-users, the disciplined OEM commitment typically lands at $4.50-$8 per end-user-month, against the standard default of $8-$13 per end-user-month. The annual commercial commitment lands at $5.4M-$32M, against the standard default of $9.6M-$52M for equivalent deployed volume.
The renewal data that wins
The single most valuable artifact for an OEM renewal is the deployed-volume and capability-consumption report that captures the actual deployed end-user volume, the actual capability consumption against the embedded capability set, and the broader operational outcomes the OEM commitment has produced. The report establishes the operational baseline for the next renewal conversation and supports the right-sizing of the embedded capability set, the volume commitment structure, and the capability expansion mechanics at the renewal moment.
Where to begin
If your OEM commitment is in scoping, the most useful first step is a capability-by-capability operational specification. Document the specific capabilities the product actually requires, with the operational use case for each capability. The specification establishes the foundation for the embedded capability set scoping and the broader commercial commitment. If your OEM commitment is already in production, the most useful first step is a capability-by-capability consumption analysis that establishes the right-sizing opportunities for the next renewal conversation.
The strategic frame
The Salesforce ISV OEM commitment is a strategic commercial structure that has material implications for the ISV's product economics and the broader business. The commitment deserves the same scope discipline that applies to every other Salesforce commercial discussion, with the multi-dimensional structure—embedded capability set, per-user pricing, volume commitment, capability expansion, end-customer migration—warranting careful negotiation across each dimension. ISVs that treat the OEM commitment as a strategic commercial decision—with disciplined scoping and measured commercial outcomes—consistently outperform ISVs that treat the OEM commitment as a default commercial structure bundled into the broader Salesforce partnership.