Most teams find the Salesforce ISV Partner Program the way they find most things in the Salesforce ecosystem: mid-deal. A prospect asks if you're listed on AppExchange. A customer wants your product managed inside their org instead of bolted on. Suddenly you're reading fee tables and tier names that don't map to any decision you're actually trying to make.
Salesforce's partner tiers are the levels Salesforce assigns to its consulting partners based on certifications, delivered projects, and customer satisfaction, and as of 2026, there are only two: Select and Summit.
MagicFuse went through this same reassessment under the new system and holds Summit status, so this isn't a recap written from the outside. It's what the change actually looks like from inside the tier Salesforce built the new system around, from a team that was measured against it directly.
This guide covers what changed, what Select and Summit each signal, what happened to the tiers you might still see referenced elsewhere, and where tier stops being useful information for you as a buyer.
Key Takeaways
- Salesforce relaunched its ISV track around AgentExchange in April 2026, adding two partnership paths: Extend and Enhance for apps and integrations, and Build and Bundle for platform-native products.
- ISV partners move through five journey-stage tiers: Registered, Exploration, Build, Select, and Summit, reviewed quarterly based on commercial progress rather than a point score.
- Joining the Salesforce Partner Community is free. Building and listing an app isn't: expect a Security Review fee for paid apps, an annual listing fee, and a revenue share of 15% (ISVforce) or 25% (OEM).
- The biggest cost most ISVs underestimate isn't a Salesforce fee at all. It's building and maintaining a managed package that meets Salesforce's coding and security standards.
- A Security Review is mandatory before any paid app can list, and it trips up a lot of first-time submissions on preventable issues like missing access checks.
- Becoming an ISV partner, passing Security Review, and getting AppExchange-listed are three separate milestones, and conflating them is the most common reason teams misjudge their timeline.
What Is the Salesforce ISV Partner Program?
The Salesforce ISV Partner Program lets independent software vendors, companies building their own product rather than delivering implementation services, build on the Salesforce platform and distribute through AppExchange and AgentExchange. In return, Salesforce takes a percentage of what your app earns. Whether your app extends a specific Salesforce cloud or one of Salesforce's other products, the program itself works the same way.
That's a different relationship than the one most people picture when they hear "Salesforce partner." A consulting partner gets paid by clients to implement Salesforce for them. An ISV partner builds a product once and sells it to many Salesforce customers, the way you'd sell software through any other marketplace.
ISVforce vs. OEM: The Two Commercialization Paths
Salesforce splits ISV distribution into two models. Under ISVforce, you sell your app to companies that already use Salesforce, and Salesforce takes 15% of your app's revenue. Under OEM, you bundle Salesforce licensing inside your own product and sell to customers who may never have touched Salesforce before, and the revenue share rises to 25% of the combined solution's revenue.
Which one fits depends on your buyer. If your customers are already running Salesforce and you're extending what they have, ISVforce is the simpler path. If you're selling a standalone product to a market that doesn't know or care that Salesforce powers it, OEM is built for that.
What ISV Partners Keep Control Of
Unlike a reseller relationship, becoming an ISV partner doesn't hand Salesforce your go-to-market. You set your own pricing, run your own sales and marketing, and decide who you sell to. Salesforce provides the platform, the marketplace, and a share of the customer relationship through co-selling, but the product and the sales motion stay yours.
Salesforce ISV Partner Program at a Glance
What's the Difference Between an ISV, a Consulting Partner, a Reseller, and an MSP?
Salesforce recognizes several kinds of partners, and it's worth knowing where ISV sits among them before you decide this is the right track.
Consulting Partners
Consulting partners, sometimes grouped with system integrators, join the Salesforce Consulting Partner Program to handle Salesforce implementations and deliver Salesforce solutions for their clients. Their work spans everything from a first rollout to complex projects across Sales Cloud, Service Cloud, and Marketing Cloud, and their tier depends on certifications, successful Salesforce projects, and customer success, not a product they've shipped.
Reseller Partners
Reseller partners help customers purchase Salesforce licenses, often bundled with their own services. They're closer to a distribution channel than a product business.
Managed Service Providers
Managed Service Providers pick up where implementation ends, running ongoing support, monitoring, and administration for a Salesforce org after go-live.
Where ISV Partners Differ
An ISV partner builds solutions once and distributes them to many customers through a partner-based AppExchange or AgentExchange listing, rather than delivering a service to one customer at a time. That's different from how other partners earn revenue, and it's why the tiers, the fees, and the whole evaluation model look nothing alike. Salesforce structures its ISV partnerships around this distinction for exactly that reason: if your team is building software, not delivering projects, the ISV track is the one built for you.
What Changed in the Salesforce ISV Partner Program in 2026?
This is the part most existing guides on this topic miss, because it's genuinely new. In April 2026, Salesforce relaunched its ISV framework as the AgentExchange ISV Track, and the program's own marketing has shifted noticeably since.
The April 2026 AgentExchange ISV Track Relaunch
Salesforce's current Become an ISV Partner page no longer leads with the old AppExchange-only framing. It's built around Agentforce and AgentExchange, and it positions the program as reaching Salesforce's roughly 21 million customers, a figure Salesforce states directly on that page.
Two New Partnership Paths: Extend and Enhance vs. Build and Bundle
The relaunch introduces two named paths instead of a single generic ISV track. Extend and Enhance is for apps and integrations that surface inside Agentforce Builder and Slack and reach existing Salesforce customers. Build and Bundle is for platform-native products aimed at a broader market, including customers who don't already run Salesforce, with full control over your own sales and marketing.
Quarterly Tier Reviews, Not Annual
Salesforce now evaluates ISV tier progress every quarter instead of once a year. That's a meaningful shift: an ISV that lands a big deal or ships a major release doesn't have to wait a full year to move up, and Salesforce can also move a partner down faster if commercial activity stalls.
What Are the Salesforce ISV Partner Tiers?
Registered, Exploration, Build, Select, and Summit
Salesforce assigns ISV partners to one of five tiers based on where they sit in the partner journey, not a scored checklist:
- Registered. You've created a partner account, but there's no commercial relationship with Salesforce yet.
- Exploration. You're in active conversations with Salesforce about your product.
- Build. You've signed a Partner Distribution Agreement and you're actively building.
- Select. You have at least one paid app live on AppExchange or AgentExchange.
- Summit. A strategic, high-revenue partnership, typically by invitation.
How Salesforce Evaluates Tier Progress Now
Since Salesforce replaced its older points-based system, tiers reflect the commercial stage of the relationship (revenue, strategic alignment, and business growth) reviewed quarterly, rather than a running score of activities completed. In practice, that means the fastest way up isn't collecting badges, it's shipping a listed, paying product.
How Do You Join the Salesforce Partner Community and Become an ISV?
Here's a step-by-step guide to how it actually works. The steps themselves are straightforward, and getting through each one cleanly is where teams lose time.
- Apply to the Salesforce Partner Community. There's no enrollment fee.
- Complete Salesforce's application and partner review process, which may include a due-diligence step depending on your product and market.
- Get approved into the Registered ISV tier and set up a Partner Business Org.
- Build your managed package to Salesforce's coding and security standards.
- Sign the Partner Distribution Agreement, the partnership agreement that sits under Salesforce's broader Partner Program Agreement, and submit your app for Security Review.
- Pass review, complete your AppExchange or AgentExchange listing, and go live.
The Three Gates People Confuse
Teams planning a launch timeline often treat "becoming an ISV partner," "passing Security Review," and "getting listed on AppExchange" as one milestone. They're three separate ones. You can be a Registered ISV partner with zero code written. You can pass Security Review and still have listing work left to do. Salesforce structures its ISV partner program around all three stages of that Salesforce journey, and treating them as one step is the most common planning mistake we see.
How Much Does It Cost to Become a Salesforce ISV Partner?
Salesforce's Direct Fees
Signing up for the Partner Community costs nothing. Beyond that, expect a Security Review fee for paid apps (commonly cited around $999 per submission, and it applies again if you have to resubmit), an annual AppExchange listing fee (roughly $150), and the ongoing revenue share of 15% under ISVforce or 25% under OEM. Confirm current figures directly with your Salesforce Partner Account Manager before budgeting, since Salesforce updates program pricing from time to time.
The Real Cost: Building and Maintaining the Managed Package
The Salesforce fees are rarely the expensive part. Building a production-grade managed package, one that passes governor limits, handles CRUD and field-level security correctly, and clears Security Review, is specialist engineering work. Traditional development timelines for a first listing commonly run 6 to 12 months, longer if the first Security Review submission doesn't pass.
What a 15% Revenue Share Actually Costs at Scale
Run the math on your own numbers before you commit to a model. Say your app generates $2,000,000 in net revenue through ISVforce in a year. At 15%, that's $300,000 paid to Salesforce, leaving $1,700,000. Under OEM's 25% share on the same revenue, you'd pay $500,000 and keep $1,500,000. The difference isn't trivial, and it's the clearest reason to get the ISVforce-versus-OEM decision right before you build, not after.
ISVforce vs. OEM: Which Revenue-Sharing Model Fits Your Product?
If your buyer already has a Salesforce login and you're adding capability they don't have today, ISVforce keeps things simple: lower revenue share, a customer base that already understands the platform, and a shorter explanation in every sales call.
If you're selling to a global market where most buyers have never heard of Salesforce, OEM lets you bundle the license invisibly inside your own product and price accordingly. The higher revenue share buys you a market Salesforce alone wouldn't reach.
What Benefits Do Salesforce ISV Partners Get?
Reach and Marketing
Listed apps can reach Salesforce's customer base directly through AppExchange and AgentExchange, and Salesforce offers co-marketing opportunities and marketing development funds to partners who qualify.
Technical Resources
Partners get access to resources like developer tools, APIs, demo orgs for building and testing, and technical consultations with Salesforce's own teams, plus early access to new platform capabilities before general release.
Financial Incentives
Higher tiers unlock additional financial incentives tied to performance, on top of the standard revenue-share model.
Support
ISV partners get dedicated technical support services, and at Summit tier, a Partner Account Manager and closer account management, the kind of support that helps keep customer satisfaction high once your app is live.
Why Does Salesforce Security Review Trip Up First-Time ISVs?
The Most Common Reasons Apps Fail Review
The failures that come up again and again aren't exotic. Missing CRUD and field-level security enforcement, cross-site scripting gaps, hardcoded record IDs, and sharing-model violations account for most first-time rejections. None of these are hard problems once you know to look for them. They're just the kind of thing a team building its first managed package hasn't hit yet.
What Security Review Actually Checks For
Security Review audits how your app handles data access, authentication, and injection risks inside a multi-tenant environment where your code runs alongside every other customer's data. It's a code-level review, not a business check, and it exists because your app runs inside a customer's live Salesforce environment, alongside their own data. That's exactly why AppExchange development rewards teams who've been through the process before: they know what the reviewers are actually looking for, not just what the public checklist says.
Where Do ISV Apps Get Distributed on Salesforce?
AppExchange remains the primary marketplace for Salesforce apps, and it's more embedded in customer behavior than most teams assume: 91% of Salesforce customers have installed at least one AppExchange app, up from 79% in 2016. AgentExchange is the newer layer built around Agentforce, where agent-ready apps and integrations surface directly inside Agentforce Builder and Slack.
The two aren't competing marketplaces so much as two doors into the same customer base. Where your app lists, and how it's positioned, depends on whether you're extending an existing Salesforce workflow or building something Agentforce-native from the start.
Should You Build It Yourself, Hire a Done-for-You Builder, or Work With a Salesforce Delivery Partner?
Each path is genuinely right for a different situation, and the right one depends on your business goals, your timeline, and how complex the build really is. Being honest about the tradeoffs will save you more time than any single tip in this guide.
Building in-house works if you already have Salesforce engineers on staff who understand Apex, managed packaging, and governor limits. It's the slowest path to a first hire, but you keep everything in-house long term.
A done-for-you AI-assisted builder can get a simple app packaged fast, sometimes in weeks rather than months. That speed usually comes with less flexibility for complex data models or custom Security Review remediation, so it fits best for straightforward, well-scoped apps.
A Salesforce delivery partner sits between the two: faster than hiring and onboarding an in-house team, but with the packaging judgment and Security Review experience a fast, templated build can't always match, especially once your app's data model or integrations get more complex. That's the overlap between Salesforce custom development and broader Salesforce consulting work, and it's the right call when the app is core to your product, not a side project.
How MagicFuse Helps ISVs Get to AppExchange
As a certified Salesforce partner, MagicFuse's Salesforce ISV team has taken managed packages through Salesforce Security Review for ISVs including Elements.cloud, Atamis, Riptide, Limio, ID-Pal, and Surfly, across multiple industries from subscription commerce to identity verification. We currently support 15+ ISV products on the platform, and we've also shipped 3 AppExchange products of our own, so we've sat on both sides of the review process: as the team submitting an app, and as the team helping a client fix one that stalled.
That combination matters for a program this specific. Our Salesforce team holds 270+ certifications across 80+ certified Salesforce consultants, and the proven expertise behind those success stories comes from 12+ years of delivering solutions in the Salesforce ecosystem, long enough to have seen the tier system, the fee structure, and the review criteria change more than once.
If you're weighing whether to build in-house, hire a done-for-you shop, or bring in a delivery partner, contact us and we'll look at your product and tell you honestly which path actually drives business growth for you, even if that's not us. Read more about how we hire and staff AppExchange developers for ISV teams.
FAQs
- What Is a Salesforce ISV Partner?
A Salesforce ISV partner is a company that builds, markets, and sells its own application on the Salesforce platform under Salesforce's ISV partnership program, distributing it through AppExchange or AgentExchange in exchange for a share of the app's revenue.
- What's the Difference Between an ISV and an OEM Partner?
ISVforce and OEM are both paths inside the same ISV program, not separate partner types. ISVforce sells to customers who already use Salesforce at a 15% revenue share. OEM bundles Salesforce licensing inside your own product for a broader market at a 25% revenue share.
- How Much Does It Cost to Become a Salesforce ISV?
Joining the Partner Community is free. Beyond that, budget for a Security Review fee on paid apps, an annual listing fee, a revenue share of 15% to 25%, and the cost of building a managed package that meets Salesforce's standards, which is usually the largest line item.
- Is There a Fee to Join the Salesforce Partner Community?
No. Signing up for the Salesforce Partner Community has no enrollment fee. The costs start once you build and submit an app for Security Review and listing.
- How Long Does Salesforce Security Review Take?
A first review typically takes several weeks, and a resubmission after a failed review commonly adds 2 to 3 more. Teams that get it right the first time usually do so because someone on the build team has been through the process before.
- What's the Difference Between AppExchange and AgentExchange?
AppExchange is Salesforce's established app marketplace. AgentExchange is the newer marketplace built around Agentforce, where agent-ready apps and integrations surface inside Agentforce Builder and Slack. Both sit under the same ISV Partner Program.
- Do You Need an In-House Salesforce Development Team to Become an ISV?
No, but you need that expertise somewhere: on staff, through a done-for-you builder, or through a Salesforce delivery partner. What you can't skip is the packaging and Security Review knowledge itself.
- How Are Salesforce ISV Partner Tiers Evaluated?
Salesforce reviews ISV tiers quarterly based on where a partner sits in the commercial journey, from Registered through Summit, rather than a points-based scorecard.
