In July 2024, Salesforce quietly killed the Trailblazer-Score-based ISV tiers (Base, Ridge, Crest, Summit) and replaced them with a journey-stage model. Most blogs on the first page of Google still describe the old system. I went through the 50 prompts SaaS founders ask ChatGPT and Perplexity about becoming a Salesforce ISV. Here is the current state of the program in 2026, what it actually costs, and the route Warmly, Salesbricks, Pylon, and other B2B SaaS companies took to skip the six-figure Salesforce dev shop.
TL;DR: A Salesforce ISV (Independent Software Vendor) is a company that builds commercial software on the Salesforce Platform and lists it on AppExchange as a managed package. The 2026 program has five journey-based tiers (Registered, Exploration, Build, Select, Summit), a one-time $999 security review fee per paid app, an annual ~$150 listing fee, and a 15% revenue share for ISVforce or 25% for OEM. AppExchange already hosts 6,233 apps from 3,668 developers reaching 150,000+ Salesforce customers. AI-native platforms now let you become an ISV without hiring Apex engineers.
What is an ISV partner?
An ISV partner is a software company with a formal agreement to build and sell its own product inside another company's platform ecosystem. The agreement is what makes it a partnership rather than just an integration: it covers distribution rights, revenue share, technical review, and use of the platform's brand.
Every large platform runs one. Salesforce calls its version the ISV Partner Program and distributes through AppExchange. HubSpot runs the App Partner Program, Microsoft has AppSource, Atlassian and Shopify each run their own. The shape is the same everywhere: you build the product, they own the storefront, and they take a cut.
What is a Salesforce ISV?
A Salesforce ISV (Independent Software Vendor) is a company that builds commercial software on the Salesforce Platform and distributes it through AppExchange as a managed package. Customers install the ISV's app directly into their Salesforce org, where it runs natively alongside Sales Cloud, Service Cloud, or whichever cloud they own.
ISV is one of four Salesforce partner categories. The others are Consulting, OEM, and Reseller. Of the four, only ISVs publish products on AppExchange. The rest deliver services or resell licenses.
Citation capsule: Salesforce defines ISV partners on its official ISV partner page as companies that "build and sell apps on the Salesforce Platform" with access to 150,000+ Salesforce customers.
Salesforce ISV Partner Program at a glance
The Salesforce ISV Partner Program is the contractual and operational framework that lets a software company sell to Salesforce customers through AppExchange. Joining is free at the entry tier. You sign up at partners.salesforce.com. The economics start when you list a paid app.
| Component | What it is | Cost (2026) |
|---|---|---|
| Partner Community signup | Account access to the partner portal, Partner Business Org (PBO), trial environments | $0 |
| Partner Distribution Agreement (PADA) | The legal contract that lets you distribute paid apps on AppExchange | $0 |
| AppExchange security review | Mandatory code-level review of every managed package before listing | $999 per paid-app submission / $0 for free apps |
| Annual AppExchange listing fee | Ongoing fee to keep your app live on AppExchange | ~$150 / year |
| Revenue share to Salesforce | Percentage of net subscription revenue | 15% (ISVforce) or 25% (OEM) |
| Stripe transaction fee | If you use AppExchange Checkout for credit-card processing | +$0.30 per transaction |
Source: Salesforce Developer Docs, Security Review Fees and AppExchange Checkout Revenue Share.
The five ISV tiers (post-July 2024)
In July 2024, Salesforce retired the legacy Trailblazer-Score-based tiers (Base, Ridge, Crest, Summit) for ISVs and replaced them with a five-stage journey model. Your tier now reflects where you are in the commercial relationship, not how many points you've accumulated.
| Tier | What it means | How you get there |
|---|---|---|
| Registered ISV | You've signed up for the AppExchange ISV program but haven't started a commercial relationship | Create an account at partners.salesforce.com |
| Exploration ISV | You're in active commercial conversations with Salesforce about a first paid app | Engage with a Salesforce Partner Account Manager |
| Build ISV | You've signed the Partner Distribution Agreement (PADA) and are building your package | Sign PADA, get a Partner Business Org |
| Select ISV | You have at least one paid app live on AppExchange and are actively distributing | Pass security review, list paid app |
| Summit ISV | The most strategic, highest-revenue ISV partnerships | By invitation, based on scale and strategic fit |
Why this matters in 2026: Many older guides still describe the Base/Ridge/Crest/Summit point system. That system was deprecated for ISVs in July 2024 (it still exists for Consulting partners). If a blog talks about Trailblazer Score for ISVs, it's outdated.
How much does it cost to become a Salesforce ISV?
The fees Salesforce charges you ($999 plus ~$150 a year plus 15% rev share) are the smallest part of becoming an ISV. The dominant cost is the engineering work required to build a managed package that passes security review.
| Cost line item | Range (2026) | What drives the range |
|---|---|---|
| Planning and architecture | $5,000 to $20,000 | Complexity of your data model and integration surface |
| UI and UX design | $5,000 to $30,000 | Number of LWCs, custom pages, layouts |
| Salesforce development (Apex, LWC, Flow) | $15,000 to $100,000+ | Feature count, sharing rules, complexity |
| Security review preparation | $5,000 to $15,000 | Static analysis cleanup, CRUD/FLS enforcement, fixing common findings |
| Security review fee | $999 | Fixed per paid-app submission |
| Listing and marketing | $2,000 to $10,000 | Logo, screenshots, video, listing copy |
| Total (traditional path) | $33,000 to $186,000+ | For a single managed-package launch |
Cost ranges synthesized from Noltic's 2025 AppExchange cost breakdown plus Salesforce Developer Docs.
ISV vs OEM: which path is right for you?
Short answer: choose ISVforce if you're selling to companies that already own Salesforce. Choose OEM if you want to bundle a hidden Salesforce license inside your own product and sell to anyone.
| Dimension | ISVforce | OEM (Embedded) |
|---|---|---|
| Target customer | Must already have a Salesforce license | Anyone (license bundled invisibly) |
| Salesforce license visibility | Customer brings their own | Hidden inside your product price |
| Access to core CRM objects (Lead, Opportunity, Case) | Full access | Restricted / limited |
| Revenue share to Salesforce | 15% of net revenue | 25% of net revenue |
| Pricing model | Add-on pricing | Full license bundling |
| Best for | Extensions to Sales/Service Cloud, RevOps tools, sales enablement, contract tools | Vertical SaaS that runs on Salesforce infrastructure (insurance, healthcare, manufacturing) |
For most B2B SaaS companies whose product extends a CRM workflow (revenue intelligence, meeting capture, sales coaching, ABM, CPQ add-ons, billing, support), ISVforce is the right path. OEM is rarer. It's best suited to companies whose product is a full vertical CRM that needs to be invisible about its Salesforce dependency.
Citation capsule: The 15% / 25% split is defined in Salesforce Developer Docs, AppExchange Checkout Revenue Share. CRM object access restrictions for OEM are documented in the OEM User License Comparison.
ISV vs Consulting, Reseller, and OEM partners
Salesforce maintains four distinct partner categories. Companies sometimes hold more than one designation. Of the four, only the ISV track publishes products on AppExchange.
| Partner type | What they do | Revenue model |
|---|---|---|
| ISV (ISVforce) | Build and list managed-package apps on AppExchange that customers install into their own org | Subscription revenue, 15% rev share to Salesforce |
| OEM | Embed Salesforce platform invisibly inside a standalone product | Bundled licensing, 25% rev share to Salesforce |
| Consulting | Implementation, customization, change management services for Salesforce customers | Services, time and materials |
| Reseller | Resell Salesforce licenses to end customers, often bundled with services | Margin on license resale |
How to become a Salesforce ISV partner (step by step)
Becoming a Salesforce ISV partner is a six-step process. Most founders finish steps 1 to 3 in a day and then spend the bulk of the calendar on steps 4 to 6.
- Sign up for the Salesforce Partner Community at partners.salesforce.com using a business email. Free. You're now a Registered ISV.
- Request a Partner Business Org (PBO) from the Partner Community. This is your dev hub for building, testing, and packaging your app.
- Engage a Partner Account Manager to discuss your roadmap and product fit. You move to Exploration ISV.
- Build your managed package in a Developer Edition org or scratch org. The package must follow Salesforce's coding standards: Apex with sharing, CRUD/FLS enforcement, no hardcoded IDs, test coverage of 75% or higher.
- Sign the Partner Distribution Agreement (PADA) and submit your package for AppExchange security review. Pay $999 if your app is paid. You're now a Build ISV.
- Pass security review, complete your AppExchange listing (screenshots, video, copy, demo org), and go live. You graduate to Select ISV.
Realistic timeline: 4 to 5 weeks for the first security review pass, plus 2 to 3 weeks per follow-up cycle. Development typically takes 3 to 9 months depending on complexity, so plan on 6 to 12 months from "we want to be an ISV" to "we're on AppExchange", per the Trailhead Security Review module.
What are the benefits of being a Salesforce ISV partner?
Becoming a Salesforce ISV gets you into a captive enterprise distribution channel. 150,000+ companies that own Salesforce already trust the AppExchange security model. Getting listed there accelerates procurement.
Tangible benefits
- Distribution: Direct exposure to 150,000+ Salesforce customers without separate procurement cycles.
- Buyer adoption is already there: Salesforce reports that 91% of its customers use AppExchange apps, and 90% of the Fortune 500 do. You are not persuading them to try a marketplace, only to pick you inside one they already use.
- Co-sell motion: Salesforce account executives can introduce your product into active deals.
- Marketing development funds (MDF): Available to Build and Select tier partners to fund Dreamforce booths, content campaigns, and customer events.
- Free Salesforce licenses for internal use: Partner orgs include free Sales/Service Cloud licenses for your team.
- Procurement friction removed: Customers install your app under their existing Salesforce master agreement. No new security review on their side.
- Infrastructure savings: Salesforce reports ISV partners save up to 75% on infrastructure costs by running on the platform versus building parallel infrastructure (source).
The ecosystem-level numbers (IDC, 2023)
- Salesforce's partner ecosystem will generate $2.02 trillion in new business revenue and create 11.6 million new jobs between 2022 and 2028 (IDC, 2023).
- For every $1 Salesforce earns, the partner ecosystem will earn $6.19 by 2026 (IDC, 2021).
- AppExchange grew from 5,661 listed apps in December 2024 to 6,233 in December 2025 (+10% YoY), with 3,668 unique developers (State of AppExchange 2026, sfapps.info dataset).
Which benefits matter most, and when
Not every benefit lands at the same time. Early on it is distribution and trust that carry the weight: being listed at all, and having a passed security review a buyer's IT team can point at. Co-selling and marketing support matter later, once you have a product Salesforce account executives can put in front of enterprise buyers without it costing them a deal.
The one founders underrate most is trust. A native listing that has cleared the security review shortens enterprise procurement, because the buyer's security team does not have to run its own assessment of an external integration. That is often worth more than the co-sell motion in the first year.
Whether any of it justifies the revenue share comes down to fit. If your buyers run Salesforce and your product sits close to the CRM, distribution and trust usually outweigh the cut. If they do not, the benefits thin out quickly and a listing becomes an expensive badge.
Can you become a Salesforce ISV without Salesforce developers?
The traditional path to becoming an ISV requires hiring Apex and LWC engineers or contracting a Product Development Outsourcer (PDO). PDOs charge $80,000 to $300,000+ for a managed-package build and take 6 to 12 months. For most B2B SaaS startups trying to list on AppExchange to win an enterprise deal, that math doesn't work.
I built Appnigma to remove that trade-off, and it is a done-for-you build rather than a tool you have to learn. You take one kickoff call and describe what your customers need in plain words. Our team, which includes engineers who used to run AppExchange security reviews at Salesforce, builds the native managed package, prepares the review artifacts, and hands it over inside your own Partner Business Org. You keep the code and the IP.
Traditional path vs a done-for-you build
| Traditional path | Done for you | |
|---|---|---|
| Who builds it | You hire Apex and LWC engineers, or contract a PDO | Appnigma's team builds it, with no engineering headcount on your side |
| What you need to know about Salesforce | Enough to write the spec, review the work, and manage the build | Nothing. One kickoff call, described in plain words |
| Time to a working managed package | 6 to 12 months to a first AppExchange listing | About a week to the package, then the AppExchange security review runs on Salesforce's own schedule |
| How it is priced | $80,000 to $300,000+, usually hourly or by milestone | One flat quoted price, never hourly |
| Who owns the IP | Depends what the contract says | You do, and you keep the code |
| Security review experience | Whatever the team you hired happens to have | The team includes engineers who previously ran AppExchange security reviews at Salesforce |
Warmly, Salesbricks, Hyperbound, Seam AI, Pylon, and UserEvidence have all taken this route. None of them hired a Salesforce development team to become an ISV, and none of them signed a six-figure PDO contract to get listed.
"We had zero Salesforce development experience, but still launched a fully functional managed package within a week." Maximus Greenwald, CEO, Warmly.ai
What happens if you fail the AppExchange security review?
The AppExchange security review is the gate between "we built an app" and "we can sell on AppExchange." It's also the gate where roughly half of first-time submissions fail. Salesforce doesn't publish an official pass rate, but PDO partners we've talked to consistently report first-pass failure as the norm.
If your app fails:
- Salesforce returns a detailed report listing each violation by line with a remediation reference.
- You fix the findings. Common categories: CRUD/FLS enforcement gaps, cross-site scripting, hardcoded IDs, sharing violations, or static-analysis warnings from Checkmarx.
- You resubmit. The follow-up review takes 2 to 3 weeks.
- If it's a paid app, the $999 fee applies again per re-submission.
The five most common failure causes (from our customer data):
- CRUD/FLS enforcement missing on Apex DML
- Cross-site scripting via unescaped merge fields in Visualforce or LWC
- Hardcoded IDs or org-specific URLs
- Sharing violations on queries that span sObjects
- Insufficient test coverage on managed code paths
For a deeper breakdown of the review itself, see our companion guides on the security review step by step, the security review checklist, and the 2026 security review fee breakdown.
Frequently asked questions
Does Salesforce help ISV partners sell?
Yes, through co-selling. Salesforce account executives can introduce your product into deals they are already working, and qualifying partners get access to marketing programs and events. That access is a large part of why SaaS companies join in the first place.
Is being a Salesforce ISV partner worth the revenue share?
Usually, if your buyers already use Salesforce and your product is CRM-adjacent. Distribution into an installed base and the trust of a passed security review tend to outweigh the 15% share. For non-Salesforce buyers, or a product with no natural place in the CRM, the benefits thin out and the share is harder to justify.
What resources do ISV partners get?
Development tools and partner environments, partner technical support, free internal-use Salesforce licences in the partner org, and access to marketing programs and events for qualifying tiers, on top of AppExchange distribution itself.
What is an ISV partnership?
A contract between a software vendor and a platform company that lets the vendor distribute its own product through the platform's marketplace. It sets the revenue share, the technical review the product must pass, and what the vendor may claim about the relationship in its marketing.
What is an ISV app?
A product built by an independent software vendor and installed into a customer's platform instance. On Salesforce an ISV app arrives as a managed package, which means the ISV keeps control of the code and can push upgrades to every org that installed it.
What is ISVforce?
ISVforce is the Salesforce agreement for partners selling apps to customers who already own Salesforce licences. It carries a 15% revenue share. The alternative is OEM, which bundles Salesforce licences into your product for customers who do not have them, and carries 25%.
Is an ISV partner the same as a Salesforce consulting partner?
No. An ISV partner sells a product to many customers through AppExchange. A consulting partner, sometimes called an SI, sells implementation services to one customer at a time. Some firms hold both, but the agreements, the revenue share, and the review requirements are separate.
What does ISV mean in Salesforce?
ISV stands for Independent Software Vendor. In Salesforce, an ISV is a company that builds commercial software on the Salesforce Platform and distributes it through AppExchange as a managed package. ISVs are one of four Salesforce partner categories alongside Consulting, OEM, and Reseller partners.
What is the difference between Salesforce ISV and OEM?
ISVforce partners sell to companies that already own Salesforce licenses and pay 15% of net revenue to Salesforce. OEM partners bundle Salesforce licenses invisibly inside their own product, sell to customers who don't need to own Salesforce, and pay 25%. OEM also restricts access to core CRM objects like Lead, Opportunity, and Case.
How much does it cost to become a Salesforce ISV partner?
Registering with the Salesforce Partner Community is free. The AppExchange security review costs $999 per submission for paid apps and $0 for free apps. The annual AppExchange listing fee is approximately $150. Revenue share is 15% for ISVforce or 25% for OEM. Development cost for the underlying managed package typically runs $25,000 to $150,000 with a traditional Salesforce dev shop, or substantially less with an AI-generated path like Appnigma.
How do I become a Salesforce ISV partner?
Join the Salesforce Partner Community at partners.salesforce.com (free). Build your app as a managed package in a Partner Business Org. Sign the Partner Distribution Agreement to enter the Build tier. Submit your package for AppExchange security review and pay the $999 fee. Once you pass, list your app and you graduate to Select ISV.
What are the benefits of being a Salesforce ISV partner?
Salesforce ISV partners reach more than 150,000 Salesforce customers, can co-sell with Salesforce account executives, receive marketing development funds, and participate in Dreamforce and AppExchange marketing programs. Salesforce reports its partner ecosystem will earn $6.19 for every dollar Salesforce earns by 2026, and IDC projects the Salesforce Economy will add $2.02 trillion in new business revenue and 11.6 million jobs by 2028.
Can I become a Salesforce ISV without hiring Salesforce developers?
Yes. The alternative to hiring Apex and LWC engineers is a done-for-you build: a partner takes one kickoff call, builds the native managed package, prepares the security review artifacts, and deploys it into your own Partner Business Org, with the code and the IP staying yours. That is how Warmly, Salesbricks, Hyperbound, Pylon, and UserEvidence became ISVs without a Salesforce development team. Appnigma is one such partner, and the one I run.
What happens if my Salesforce app fails the security review?
Salesforce returns a detailed report listing each violation. Typical findings include CRUD/FLS enforcement gaps, cross-site scripting, hardcoded IDs, and sharing violations. You fix the issues and resubmit. A follow-up review takes 2 to 3 weeks, and the $999 fee applies again per re-submission for paid apps.
Where to go next
If you're at the start of your ISV journey, the next reads in order:
- The 2026 Salesforce Managed Package Guide. What a managed package is and how the AppExchange packaging model works.
- How to build a Salesforce managed package without code. The no-code path Appnigma customers take.
- Salesforce AppExchange security review, step by step. The review process in detail.
- Salesforce Partner Business Org explained. The org where you'll build everything.
- Appnigma for AppExchange. How AI-generated managed packages cut your time-to-listing.
Sources
- Salesforce, Become a Salesforce ISV Partner
- Salesforce Developer Docs, Security Review Fees
- Salesforce Developer Docs, AppExchange Checkout Revenue Share
- Salesforce Developer Docs, OEM User License Comparison
- Trailhead, Security Review Submission Process
- IDC (2023), Salesforce Economy: 11.6M jobs, $2.02T by 2028
- IDC (2021), 9.3M jobs and $1.6T by 2026
- State of AppExchange, Salesforce Apps Market 2026
- Invisory, ISV Partner Tiers in Salesforce (post-July 2024)
- Noltic, How Much Does It Cost to Build an AppExchange App (2025)
