The hardest part of AppExchange app development isn't writing Apex. It is getting a managed package through security review in as few rounds as possible, making first-release decisions that Salesforce locks for good, and keeping one package working in thousands of customer orgs you never see. Each of those costs weeks when it goes wrong, and none of them shows up in a feature estimate.
For a SaaS company, the question behind "what are the challenges?" is usually a planning one. Sales wants an install date, product wants the integration inside Salesforce, and nobody on the team has shipped a managed package before. Appnigma's marketplace apps team builds native Salesforce apps for SaaS companies and covers "a native app, marketplace listing preparation, and review support." If you want the full build sequence rather than the risks, our AppExchange app development guide walks through it step by step.
Updated October 2026. Checked against Salesforce's ISVforce Guide, the second-generation packaging (2GP) developer guide, the Apex Developer Guide and Trailhead. The earlier version of this post gave a first-attempt failure rate, a review length longer than Salesforce's own estimate, and an industry build-cost range. Salesforce publishes none of those figures. It also described Appnigma features that no longer exist. This update replaces them with what Salesforce documents and adds the post-release rules most guides skip.
Which challenges cost a SaaS team the most time
Most AppExchange (now AgentExchange) delays trace back to six areas. The table ranks them by how much schedule they can cost, with the rule Salesforce actually sets for each.
| Challenge | What Salesforce sets | What it costs you | How to de-risk it |
|---|---|---|---|
| Security review rounds | Initial review takes "approximately 4 to 6 weeks" | A failed round adds a new verification and retest cycle | Scan with Code Analyzer and fix CRUD/FLS before you submit |
| First-release lock-in | Manageability rules fail any version that breaks them | Wrong field types and global Apex stay with you for the life of the package | Review the data model and every global before promoting |
| Customer org variance | Editions, enabled features and limits differ per org | Installs fail on a missing dependency, or code hits shared limits | Test in Professional and Enterprise Edition orgs from Environment Hub |
| Release cadence | Three Salesforce releases a year, each with a preview window | Regression work three times a year, forever | Test against preview in each window and budget it |
| Upgrade adoption | Customers install upgrades themselves unless you push | Several versions in the field at once | Pass review early so push upgrades are available |
| Distribution | A listing is a catalog entry, not a channel | Installs don't arrive by themselves | Plan the sales motion before the listing goes live |
Security review rounds and first-release lock-in are where SaaS teams most often lose a quarter. The review figure comes from Act on Security Review Results and the manageability rule from Manageability Rules and Ancestry.
Why the security review is the biggest schedule risk
Salesforce times an initial review at "approximately 4 to 6 weeks after you submit," per Act on Security Review Results. It publishes no pass rate. The often-quoted 50 percent failure rate has no Salesforce source, and this page used to repeat it. What Salesforce does say is blunter. "Applicants who don't test beforehand rarely pass and must resubmit," per How the AgentExchange Security Review Works, and the Trailhead unit Submit Your Solution for Security Review notes that "Most submissions pass on the second attempt."
The schedule cost of a failure is easy to work out from Salesforce's own stage estimates. Verification takes 1 to 2 weeks and the first test 3 to 4 weeks. A remediated resubmission goes back through verification and then a 2 to 3 week retest. So a package that fails once on real findings spends roughly 7 to 11 weeks in review plus your fix time, against 4 to 6 weeks for a clean pass. That is a 3 to 5 week slip on the date sales already promised. Appnigma's Warmly project took eight weeks from kickoff to AppExchange launch. That figure includes "six weeks of Salesforce security review." The marketplace apps page labels that "a project example, not a guaranteed schedule," because review timing is set by Salesforce.
Money follows the same pattern. "There's no charge to resubmit a returned submission," while "there's a fee to retest a remediated solution," per AgentExchange Security Review Stages. A returned submission is one sent back for missing items, such as expired test org credentials. Free solutions pay no review fee at all.
What reviewers find most often
Salesforce's Top 20 vulnerabilities blog ranks findings by how often they appear. The top four are missing CRUD/FLS enforcement (checking a user's object and field permissions before reading or writing data), insecure software versions, sharing violations and insecure storage of secrets. CRUD/FLS leads "by a significant margin."
Two details trip up teams that learned Apex from older posts. "WITH SECURITY_ENFORCED isn't allowed in AppExchange packages," per Salesforce's CRUD/FLS secure coding guide, so use WITH USER_MODE or Security.stripInaccessible() instead. And secrets such as an API key "must be stored in Managed Protected Custom Metadata Types," per Storing Sensitive Data, not in a custom setting a customer admin can read.
Declarative builds don't sidestep the review either. The same Top 20 list counts flows running in system mode without sharing as a sharing violation. If your package calls your own backend, reviewers test that too. Salesforce asks for a DAST scan of external endpoints (a dynamic scan of the running service, with tools such as ZAP or Burp Suite) and for login credentials to any external component, per the Source Code Scanner page. For a SaaS company, that puts part of your core product in scope. Our security review timeline post breaks down each stage week by week.
Decisions you can't undo after the first release
This is the challenge competitors rarely mention, and the one that costs the most over the life of an app. Once you promote a 2GP package version to released, "you can't reverse the promotion," per Get Ready to Promote and Release. From then on, Salesforce's manageability rules decide what you may change. "If you attempt to make a change that would break a manageability rule ... your package version creation fails," per Manageability Rules and Ancestry.
In practice these are the commitments a first release makes for you:
- Namespace. "After you associate a namespace with an org, you can't change it or reuse it," per Register a Namespace. It appears in every API name customers see.
- Field definitions. After release, nobody can change a packaged field's Data Type or Field Name, per Packageable Components. The External ID and Unique settings lock the same way. Labels and formulas stay editable for you.
- Global Apex. Salesforce says you "generally can't change the API shape of
globalApex after it's released," per Best Practices for Global Apex in Managed Packages. You can't delete or rename a global class or method, or change its signature. Salesforce recommendsglobal"only when necessary." - Removed components. Removing components "requires approval from Salesforce," and most removed metadata stays in customer orgs "marked as deprecated," per Remove Metadata Components.
The pattern for a SaaS team is simple. Treat global Apex as a public API with a support promise, and keep it out of the package until a customer or an extension package truly needs it. Model fields for the data you will hold in two years, not for the first demo. A wrong field type found after release usually means a new field, a data migration in every customer org, and a deprecated field that customers keep seeing.
Your package runs in orgs you don't control
Your test org is clean. A customer's org has years of validation rules, triggers, other managed packages and an edition you may not have tested. That variance produces two kinds of failure.
The first is an install that never starts. A hard reference to an optional feature becomes an install requirement. Salesforce's own example is a page that uses the currency ISO code, which means "Any organization that wants to install this package must have multicurrency enabled," per Understanding Dependencies. Salesforce documents two ways out. You can use dynamic Apex to check a feature before referencing it, or ship a base package plus an extension package. Anything the extension calls in the base must be global, which brings back the lock-in rules above.
The second is a package that installs but behaves differently. Professional Edition is the common surprise for SaaS teams selling to mid-market customers. "API access isn't normally supported in Group and Professional Edition orgs," and becomes available only after your app passes review, with Bulk API 2.0 remaining unavailable, per API Access in Group and Professional Edition. If your integration syncs data through your backend, that rule can decide whether a PE customer can use it at launch.
Governor limits change with review status too. Certified managed packages "get their own set of limits for most per-transaction limits," per Execution Governors and Limits. CPU time and heap size stay shared with everything else in the transaction, so a customer's heavy triggers still count against you. Our post on governor limits for managed packages covers the arithmetic.
What keeps costing you after launch
Salesforce ships three major releases a year, and each has a preview window when sandboxes run the new version first. The next one runs January 10 to February 20, 2027 for Spring '27, per Target a Specific Release. Summer '27 follows from May 9 to June 12, 2027. You can build package versions against preview during each window. That is the moment to rerun your regression suite, not after customers report a break.
Getting fixes to customers is the second ongoing cost. An upgrade is an install, and customers install it when they choose. Push upgrades let you upgrade customer orgs yourself, but they are "only available to first- and second-generation managed packages that have passed the AgentExchange security review," and you enable them by logging a case, per Push Upgrade. Salesforce also suggests it "might be better to wait 3-4 weeks after a major Salesforce release before you push major upgrades," per its push upgrade best practices. Without pushes, expect several versions in the field at once and plan support for each.
Then there is the review itself, again. New package versions don't go through the full review, but Salesforce runs periodic re-reviews where "security review fees apply," per Periodic Re-Reviews. Plan for that cost from the start. On Appnigma's marketplace apps projects, upgrades and ongoing fixes "can be covered by a separate maintenance retainer" agreed before the build begins.
Does an AppExchange listing bring customers?
Not by itself. Salesforce documents what a listing does, which is to capture leads from people who opt in and create a license record when someone installs. It makes no promise of installs. Appnigma's marketplace apps page says it the same way. "A listing supports discovery and evaluation, but it is not a promise of inbound leads."
For most SaaS companies the listing earns its keep in the sales cycle. A Salesforce customer's admin can evaluate a reviewed, installable package, and the review result answers security questions procurement would otherwise ask. Our post on whether listing on AppExchange is worth it weighs that against an API integration with no package.
Mistakes that turn a challenge into a missed quarter
- Starting tests at the end. A beta version "must pass a 75% code coverage requirement before it can be promoted," per Get Ready to Promote. Teams find this the week they planned to submit.
- Installing a beta in a customer sandbox you will upgrade later. Salesforce warns that "you can't upgrade a beta package version," per Install and Uninstall 2GP.
- Building in a Dev Hub you don't own. Salesforce says "All Salesforce ISV and OEM partners should designate their PBO as their Dev Hub org," per Partner Business Org. If an agency builds the package, make sure it lives in your Partner Business Org (PBO), under your namespace.
- Starting a new app on first-generation packaging. Salesforce's developer blog put it plainly in 2024: "As of 2024, nobody should create any new 1GPs," per Get Started with Modern AppExchange Development.
- Leaving the backend out of review prep. The DAST scan and external credentials are part of the submission, so your own service needs to be ready for testing too.
Frequently Asked Questions
What is the hardest part of building an AppExchange app?
For most SaaS teams it is the security review, because each failed round adds roughly 3 to 5 weeks to the launch. The second is first-release lock-in, since field types, global Apex and the namespace can't change once a version is released.
Do half of AppExchange apps fail security review the first time?
Salesforce publishes no pass rate, so that figure has no official source. Its documentation says applicants who don't test beforehand "rarely pass," and Trailhead says most submissions pass on the second attempt.
How long does the AppExchange security review take?
Salesforce says "approximately 4 to 6 weeks" for an initial review. A failed round adds a new verification and retest, roughly 7 to 11 weeks in total plus your fix time.
What can't you change after releasing a managed package?
The namespace, API names, packaged field Data Type and Field Name, and any global Apex class or method signature. Removing components needs Salesforce's approval and usually leaves them deprecated in customer orgs.
Can Appnigma handle these challenges for us?
Yes. Appnigma's marketplace apps team, built by ex-Salesforce engineers, delivers the native app, listing preparation and review support. Ongoing maintenance is available as a separate retainer.
Related Articles
- Salesforce AppExchange app development, the complete guide
- How long the Salesforce security review takes
- How long it takes to get an app on AppExchange
- Is it worth listing your SaaS on AppExchange?
- Salesforce governor limits for managed packages
Sources
- Act on Security Review Results, ISVforce Guide
- How the AgentExchange Security Review Works, ISVforce Guide
- AgentExchange Security Review Stages, ISVforce Guide
- The Top 20 Vulnerabilities Found in the AppExchange Security Review, Salesforce Developers Blog
- Protect Against CRUD and FLS Vulnerabilities, Secure Coding Guide
- Storing Sensitive Data, Secure Coding Guide
- Source Code Scanner and DAST, ISVforce Guide
- Manageability Rules and Ancestry, 2GP Developer Guide
- Packageable Components, 2GP Developer Guide
- Best Practices for Global Apex in Managed Packages, Apex Developer Guide
- Remove Metadata Components, 2GP Developer Guide
- API Access in Group and Professional Edition, ISVforce Guide
- Execution Governors and Limits, Apex Developer Guide
- Target a Specific Release, 2GP Developer Guide
- Push Upgrade, 2GP Developer Guide
- Periodic Re-Reviews, ISVforce Guide
- Get Started with Modern AppExchange Development, Salesforce Developers Blog
- Submit Your Solution for Security Review, Trailhead