For a SaaS company, the important part of an AppExchange strategy is the order of a few decisions that are hard to reverse. Decide whether a listing adds anything your API integration doesn't, then pick the listing type, the billing path and the package design, and only then plan the security review and the launch. Most stalled launches made one of those choices late, after the build had already ruled it out.
The marketplace itself is now called AgentExchange. The Salesforce site says "Salesforce AppExchange is now AgentExchange," and the program terms state that "all references to AppExchange are now hereby replaced with AgentExchange," per the Salesforce Program Agreement. Appnigma's marketplace apps team builds native Salesforce apps for SaaS companies. The service includes "a native app, marketplace listing preparation, and review support" for each app. If you are a Salesforce admin answering the Trailhead quiz, the answer is A and B, deciding whether you want a free or paid solution and testing in a sandbox or Developer Edition org. The Trailhead unit Get Started with AgentExchange and our post on best practices for using AppExchange cover.
Updated October 2026. Checked against Salesforce's ISVforce Guide, the second-generation packaging guide, the ISV Track overview effective April 2026, and Trailhead. The earlier version was a list of general advice with no sources. It said little about listing types, billing, review timing or measurement, and it described Appnigma in terms our offering pages don't use. This update replaces it with the documented decisions, in the order they lock.
Which AppExchange decisions can't be undone later?
Five choices shape everything after them, and three of them are close to permanent. The table lists them in the order a SaaS team should make them, with what each one rules out.
| Decision | How permanent | What it rules out | Where Salesforce says so |
|---|---|---|---|
| Listing type (packaged, API or consultant) | Permanent | Switching type on the same listing | Select a Listing Type |
| Namespace | Permanent once packages ship | Renaming it, and any name another org already holds | Register a Namespace |
| Billing path | Hard to change after customers sign | Checkout for OEM apps and API listings | Checkout overview |
| Package generation | Convertible, with work | Nothing, if you start on 2GP | Use Managed Packages |
| Free or paid | Changeable | The review fee and revenue share, while free | How the Security Review Works |
The listing type rule is blunt. "You can't change the listing type after it's created," per Select a Listing Type. A namespace is the prefix that marks every component in your package. It "must be globally unique across all Salesforce orgs," per Register a Namespace, so register the one that matches your brand before anyone else does.
On package generation, Salesforce's guidance is "Going forward we recommend that everyone use managed 2GPs to create new apps," per Use Managed Packages. A first-generation package can now be converted, but starting on 2GP skips that project. Our managed package explainer covers the difference in more depth.
Packaged solution or API listing for a SaaS product
Most SaaS products already have a cloud backend and an OAuth integration that reads and writes Salesforce data. That makes the API listing tempting, because there is no package to build inside Salesforce. Salesforce defines it as "a solution that interacts with the Salesforce Platform by using REST API, SOAP API, or other Platform APIs," per Solution Types. The tradeoff shows up after launch, not before it.
| API listing | Packaged solution (managed package) | |
|---|---|---|
| Install from the listing | No | Yes |
| Security review | Required | Required |
| AgentExchange Checkout | Not available | Available |
| License Management App records | Not available | Yes |
| Push upgrades to customer orgs | Not applicable | Yes, after passing review |
| App Analytics usage data | Not available | Yes, after passing review |
| What you build in Salesforce | Nothing installed | Objects, UI, automation, Apex |
The install row comes from Installation Methods, which says "API solutions can't be installed directly from AgentExchange." Review applies to both, because packages and "Salesforce Platform API solutions" on the marketplace "must pass our security review," per How the Security Review Works. Checkout requires that "you must distribute your solution in a managed package," per the Checkout overview. The License Management App (LMA), the app in your partner org that tracks every customer's license, works because "you can register only managed packages," per Set Default Licensing.
Push upgrades, which update customer orgs without asking customers to install anything, are "only available to first- and second-generation managed packages that have passed the AgentExchange security review," per Push Upgrades. App Analytics has the same gate, as the measurement section below shows.
From our work with SaaS partners on this choice, the rule we use is simple. Pick the API listing when your product's value lives in your own app and Salesforce is a data source. Pick the managed package when customers need to see and act on your data inside Salesforce screens, when you want Checkout, or when you need usage data from inside customer orgs. If you are unsure whether to list at all, our post on whether listing a SaaS on AppExchange is worth it works through the costs.
How the billing path shapes what you build
Pricing on a listing is one of four models. Salesforce names them Free, Paid, Freemium and Paid Add-On Required, per Listing Approvals. How you collect the money is a separate choice, and Salesforce documents three paths.
AgentExchange Checkout. Customers pay through the listing. The share is 15% plus a $0.30 per transaction fee charged by Stripe, the payment partner, per Checkout revenue share. Your company must be based in the United States, the United Kingdom or a European Union country, per the Checkout overview. Checkout also isn't available for OEM apps.
Your own billing. You invoice customers yourself and report orders for revenue sharing through the Channel Order App. Salesforce's note is direct, "If you use AgentExchange Checkout to manage customer payments, don't use the COA," per the Channel Order App guide.
The Go-To-Market (GTM) app. Formerly the Partner Marketplace App, it has narrow fit. It supports only seat-based managed packages that are native to the Salesforce Platform, per GTM app prerequisites. The same page says "the GTM app is available to US-based customers only."
The detail that changes the build is feature gating. If you sell tiers, you will probably control features with the Feature Management App (FMA), which isn't preinstalled and is requested through a support case, per Install the FMA. With Checkout, "the license records in the License Management App are updated, but feature parameters aren't," per the Checkout FMA FAQ. So a tiered app sold through Checkout needs its own logic to switch features on after a purchase. Plan that before you design the package, not after the first customer upgrades and nothing changes.
Here is the Checkout math, worked from the published rate rather than any customer figure. Say a customer pays $12,000 a year by card in one annual charge. Salesforce's share is $1,800 plus $0.30. You keep $10,199.70. Billed monthly, that is 12 charges of $1,000, and the per-transaction fees add up to $3.60 a year. The fee barely matters. The 15% does. Our requirements for publishing a paid app post covers the agreements each path needs.
Plan the security review into the build, not after it
The review is a gate you schedule, and its prerequisites start before any code is submitted. Salesforce asks you to "have a partner recruitment representative confirm that you're enrolled in the ISV Partner Program and that you have a distribution agreement," per Submit for Security Review. New submissions "must be Lightning Ready," and "we can't accept an unmanaged or beta package," per How the Security Review Works and Required Materials.
On time, Trailhead says "a solution typically takes 4 to 5 weeks to get through the review process," and also that "most submissions pass on the second attempt," per Submit for Security Review on Trailhead. Put those two sentences together and a realistic plan holds two review cycles, roughly 8 to 10 weeks of review plus the time to fix findings in between. That is our arithmetic from Salesforce's own figures, not a promise Salesforce makes.
Paid solutions pay a fee for each attempt, which Trailhead lists in that same unit. "If you plan to distribute your solution for free, you don't pay the fee," but free solutions are still reviewed, per How the Security Review Works. Approval also isn't one and done. Trailhead says solutions are typically reviewed for security once a year. For those periodic re-reviews, "security review fees apply," per Periodic Re-Reviews.
Two habits keep review cost down after launch. Upgrades to a passed package don't send you through the full process again, and Salesforce advises you to "submit only major and minor versions, such as 1.0.0 and 1.1.0," per How the Security Review Works. Our posts on how long the security review takes and the AppExchange launch timeline go stage by stage.
Where the ISV partner program fits
Joining costs nothing up front. Salesforce describes the fee model as revenue sharing, and "a partner participates in revenue sharing with Salesforce only after they have reported their revenue for the first time," per Become a Partner. Your Partner Business Org (PBO) is the Salesforce org you run the partnership from. It "is provisioned when you join the Salesforce Partner Community" and should also be your Dev Hub, per the PBO reference.
The ISV Track effective April 2026 has five levels. They run Registered, Exploration, Build, Select and Summit. Commercial milestones move you up. Exploration means you are in "commercial conversations with Salesforce for their first paid app." Build means a signed distribution agreement. Select means you "have listed paid application(s) on the AgentExchange" and are distributing to customers, per the ISV Track overview PDF. The same document says tier evaluations happen quarterly. So a free app keeps you at the lower tiers, which matters if you were counting on benefits that start at Select.
How AgentExchange search ranks a listing
Salesforce publishes how its marketplace search works, which most listing advice ignores. "Keyword relevance is the most important factor, followed by semantic meaning, and trust score," per How Search Works. Among listing fields, the title and brief description weigh most, along with highlights and the publisher name. The same page says plainly, "Avoid keyword stuffing."
The trust score is the part that ties marketing to engineering. It "reflects how actively publishers maintain their solutions, including recent updates and new version releases," along with ratings and reviews. A package that ships a reviewed minor version every quarter is feeding its own search position, and one that hasn't changed in two years is losing ground it can't win back with listing copy.
What to measure after launch
Salesforce gives you two separate data sources, and which one you get depends on the listing type you chose at the start.
Marketplace Analytics covers the listing. It reports tile views and hovers, visitors, lead events and installs, per the Marketplace Analytics summary. It shows the 10 marketplace search terms that drive the most activity, but "search terms from external search engines aren't available," per Searches. Data updates once a day and has no API, only CSV export, per the Marketplace Analytics FAQ. Our Partner Console guide shows how to read those numbers without misjudging your funnel.
App Analytics covers what customers do inside your package. It is "available for first- and second-generation (1GP and 2GP) managed packages that passed security review and are registered to a License Management App," per the App Analytics overview. The data comes as package usage logs, monthly usage summaries and subscriber snapshots. An API listing gets none of this, so plan your own product telemetry if you go that way.
The retention rules decide your data pipeline. Summaries stay downloadable for 10 years, but "package usage log data is available to download for 45 days from the date that the log event occurred," per Download App Analytics Data. If churn analysis matters to you, schedule a download job from launch day, because a quarter you didn't save is gone. Salesforce also recommends "a 2-day query delay" so data from every instance finishes processing, per the App Analytics data flow.
Leads need setup too. They must arrive in "a standard Salesforce org, not a Developer Edition org," per Enable Lead Collection. Also, "no AgentExchange leads are sent to the org if reCAPTCHA is turned on," per AgentExchange Leads. Installs from your own installation URL create no lead at all, because the marketplace "isn't aware of the user's activity," per Lead Source Codes.
Mistakes that stall an AppExchange launch
- Creating the listing with the wrong type, then finding it can't be changed.
- Building a tiered app on Checkout without a way to turn features on after purchase.
- Writing code before a partner representative has confirmed the distribution agreement, then waiting on paperwork at submission time.
- Planning one review cycle when Trailhead says most submissions pass on the second.
- Sending installs through your own installation URL and wondering why the listing shows no leads.
- Leaving App Analytics logs undownloaded past 45 days and losing the usage history.
- Shipping no new versions after launch, which lowers the trust score search uses.
If you want a team to handle the build, the listing and the review for you, Appnigma's marketplace apps service does that. In that page's own words, "a listing supports discovery and evaluation, but it is not a promise of inbound leads," so the strategy above still decides whether the listing pays off.
Frequently Asked Questions
What is important to keep in mind when you develop an AppExchange strategy?
For a SaaS company, the listing type, billing path and review plan matter most, because they lock early. For admins taking the Trailhead quiz, the unit's answer is to decide free or paid and to test in a sandbox or Developer Edition org.
Is AppExchange now called AgentExchange?
Yes. Salesforce's site says "Salesforce AppExchange is now AgentExchange," and the program agreement replaces every reference to AppExchange with AgentExchange.
Can I change my listing type after I create it?
No. Salesforce says you can't change the listing type after it's created, so choose between a packaged solution and an API listing first.
Do free AppExchange apps need a security review?
Yes. Free solutions are still reviewed, but they don't pay the review fee.
Can Appnigma build and list our Salesforce app?
Yes. Appnigma's marketplace apps service covers the native app, listing preparation and review support. Salesforce controls review timing and approval.
About the author
Sunny Chauhan is the co-founder and CEO of Appnigma AI, which builds and maintains customer integrations and native Salesforce and HubSpot apps for B2B SaaS teams. Before Appnigma, he was on Salesforce's AppExchange team, where he worked with more than 300 SaaS partners. He has spent close to a decade on the Salesforce platform, including work at Zennify, and holds Salesforce certifications including Platform Developer II, Platform App Builder, Administrator, Data Cloud Consultant, and AI Associate.
Related Articles
- Is It Worth Listing Your SaaS on the Salesforce AppExchange?
- How Long It Takes to Get an App on AppExchange
- Requirements to Publish a Paid AppExchange App
- How Long the Salesforce Security Review Takes
- What the AgentExchange Partner Console Is For
- What Is a Managed Package in Salesforce?
- How to Get Your App Listed on AgentExchange
Sources
- Salesforce, Program Agreement
- Salesforce Developers, ISVforce Guide, Select a Listing Type
- Salesforce Developers, ISVforce Guide, Solution Types
- Salesforce Developers, ISVforce Guide, Installation Methods
- Salesforce Developers, ISVforce Guide, Use Managed Packages
- Salesforce Developers, First-Generation Packaging, Register a Namespace
- Salesforce Developers, Second-Generation Packaging, Push Upgrades
- Salesforce Developers, ISVforce Guide, AgentExchange Checkout Overview
- Salesforce Developers, ISVforce Guide, How Is Revenue Shared in AgentExchange Checkout?
- Salesforce Developers, ISVforce Guide, Checkout FAQ on the Feature Management App
- Salesforce Developers, ISVforce Guide, Channel Order App
- Salesforce Developers, ISVforce Guide, GTM App Considerations and Prerequisites
- Salesforce Developers, ISVforce Guide, Listing Approvals
- Salesforce Developers, ISVforce Guide, Set Default Licensing
- Salesforce Developers, Second-Generation Packaging, Install the Feature Management App
- Salesforce Developers, ISVforce Guide, How the AgentExchange Security Review Works
- Salesforce Developers, ISVforce Guide, Submit for Security Review
- Salesforce Developers, ISVforce Guide, Required Materials
- Salesforce Developers, ISVforce Guide, Periodic Re-Reviews
- Trailhead, Submit for Security Review
- Trailhead, Get Started with AgentExchange
- Salesforce, Become a Partner and FAQ
- Salesforce Developers, ISVforce Guide, Partner Business Org Reference
- Salesforce, AgentExchange ISV Track Overview (PDF)
- Salesforce Developers, ISVforce Guide, How Search Works
- Salesforce Developers, ISVforce Guide, Marketplace Analytics Summary
- Salesforce Developers, ISVforce Guide, Marketplace Analytics Searches
- Salesforce Developers, ISVforce Guide, Marketplace Analytics FAQ
- Salesforce Developers, ISVforce Guide, App Analytics
- Salesforce Developers, Second-Generation Packaging, Download App Analytics Data
- Salesforce Developers, Second-Generation Packaging, App Analytics Data Flow
- Salesforce Developers, ISVforce Guide, Enable Lead Collection
- Salesforce Developers, ISVforce Guide, AgentExchange Leads
- Salesforce Developers, ISVforce Guide, Lead Source Codes