Custom Salesforce app development pays off for a SaaS company when enough of your customers run Salesforce that your product has to work inside their org, not just sync with it. The usual triggers are enterprise buyers asking for an installable app, users who live on Salesforce record pages, and customers on editions where an API connection alone won't work. If none of those apply yet, a well-built API integration is cheaper to run and easier to change.
The real cost is not the first build. A custom app is a managed package your customers install, so you own its upgrades through three Salesforce releases a year, a security review before listing and support for every org it lands in. Appnigma's marketplace apps work exists for that decision. It is built by ex-Salesforce engineers and covers "a native app, marketplace listing preparation, and review support." If you are building an app for your own company's org rather than for customers, Salesforce's custom application development guide is the better place to start.
Updated October 2026. Checked against the ISVforce Guide, the 1GP and 2GP Developer Guides, the Salesforce DX Developer Guide and Salesforce's partner program pages. The earlier version quoted a longer security review time and a failure rate Salesforce doesn't publish, an outdated customer count and a partner revenue figure the linked study doesn't contain. It also gave the revenue share without a source. This update corrects those and adds the release calendar a package owner works to, what an API-only integration can't reach and a timeline for the first launch.
Custom app, API integration or no Salesforce build yet
The choice for a SaaS company is about where your product has to live for Salesforce customers. A custom app here means a managed package, which Salesforce describes as "ideal for commercial distribution through the AppExchange" in the Apex Developer Guide. An API integration runs on your servers and reads or writes the customer's org over Salesforce APIs.
| Signal from your customers | What it points to | Why |
|---|---|---|
| Users want your data and actions on the Salesforce record page | Custom app | Lightning components ship inside the package and render in the org |
| Many customers are on Professional Edition | Custom app, after security review | Professional Edition has no API access by default |
| Enterprise buyers ask for an AppExchange listing | Custom app or a listed API solution | Both need security review to list |
| You only move records between your product and Salesforce | API integration | No package to version or push |
| Few customers use Salesforce, or the requirements still change monthly | No Salesforce build yet | A package locks in a namespace and a data model |
Most SaaS products that commit to Salesforce end up with both pieces. The package holds the screens and record-level automation, and your backend does heavy processing and calls in where needed. Our post on the Salesforce native app covers which parts belong where and what each side costs a customer org in API requests.
Benefits a custom Salesforce app gives a SaaS company
Each benefit below comes from a specific platform mechanism, which is what a buyer's admin will ask about.
Your product shows up where reps already work. Lightning web components are "custom HTML elements built using HTML and JavaScript," per Get Started with LWC. Packaged, they sit on the account or opportunity page, so users act on your data without switching tabs. Adoption inside the customer's team is usually what decides a renewal.
You can sell to Professional Edition orgs. "API access isn't normally supported in Group and Professional Edition orgs," per API Access in Group and Professional Editions. After the app passes security review, "you're eligible to use some APIs" in those orgs. A listed managed package also "no longer counts against the apps/objects/tabs limits" for the customer's edition, per Limits for Group and Professional Editions. For a product sold to smaller sales teams, this is often the deciding benefit.
Your code stays yours, and you control the version every customer runs. Apex in a managed package "is obfuscated and can't be viewed in an installing org," except global methods, per Protecting Your Intellectual Property. Once the package passes review, push upgrades move customers to a new version, and "a package subscriber doesn't need to do anything to receive the push upgrade," per Push Package Upgrades to Subscribers. That keeps your support team off old versions.
A listing and a billing path come with it. Salesforce's ISV Track overview says "91% of Salesforce customers use one or more AgentExchange apps," per the Partner Program ISV Track. In April 2026 Salesforce "unified AppExchange, AgentExchange, and Slack Marketplace into a single destination," per What Is AgentExchange?. If you charge through AgentExchange Checkout, the published share is 15%, plus $0.30 per card transaction, per How Is Revenue Shared in AgentExchange Checkout?. On a $30,000 annual contract paid by bank transfer, that works out to $4,500. Outside Checkout, the Partner Program FAQ says ISVforce partners "share 15% of your app's revenue with Salesforce." OEM apps, which bundle a Salesforce platform license, share 25% of the combined solution's revenue.
The partner economy behind those listings is large. For every $1 of Salesforce revenue, "partners will generate $6.93 in revenue by 2028," according to an IDC InfoBrief cited on Salesforce's Consulting Partner Program page. That figure covers all partner types, consultancies included. It is not a forecast for any single app.
What a custom app costs you after launch
The ongoing cost comes from the calendar more than from the code. Salesforce's major release transition "happens three times a year," per Select the Salesforce Release for a Scratch Org. Before each one, sandboxes get the new release early in a window Salesforce calls the Salesforce Preview. That is when your package needs testing against it.
The same page publishes the preview dates, so the workload can be counted. These are arithmetic from those dates.
| Release | Sandbox preview window | Days |
|---|---|---|
| Winter '27 | Aug 30 to Oct 10, 2026 | 41 |
| Spring '27 | Jan 10 to Feb 20, 2027 | 41 |
| Summer '27 | May 9 to Jun 12, 2027 | 34 |
That adds up to 116 days, roughly 16 weeks a year when a new release is live in some customer sandboxes and not yet in production. Plan for a regression pass in each window. Salesforce also advises that "it might be better to wait 3-4 weeks after a major Salesforce release before you push major upgrades," per Push Upgrade Best Practices. Put together, about half of each year sits either in a preview window or in the pause after a release. Your own feature releases have to fit around that.
The upkeep also covers compatibility. "Preserving the backwards-compatibility of managed packages is the package developer's responsibility," per the Apex Developer Guide. Approved packages are also re-reviewed over time, and "security review fees apply" to those periodic re-reviews, per Periodic Security Re-Reviews. Salesforce doesn't publish a build cost. For the ranges partners quote and what drives them, see our guide to Salesforce app development cost.
How long does custom Salesforce app development take?
Build time depends on scope, so the dependable part of the estimate is the security review. Salesforce says "Approximately 4 to 6 weeks after you submit a solution for an initial review, your security review is complete," per Act on Security Review Results. That covers 1 to 2 weeks of verification and 3 to 4 weeks of testing. A resubmission adds 2 to 3 weeks of testing, per How the Security Review Works, and Salesforce labels all of these as estimates.
So one failed round turns 4 to 6 weeks into roughly 6 to 9. Salesforce publishes no failure rate. Its Trailhead module says "Most submissions pass on the second attempt," on Guide to Submitting Your Solution. The review guide adds that teams who don't test beforehand "rarely pass and must resubmit." Paid solutions pay a review fee for each attempt, and "if you plan to distribute your solution for free, you don't pay the fee." Later versions are lighter, because an upgraded version of an approved package skips "the full review process."
For a real timeline, Appnigma's Warmly project took two weeks to build and eight weeks from kickoff to AppExchange launch, "including six weeks of Salesforce security review." Our marketplace apps page calls that a project example, not a guaranteed schedule. Our post on how long the security review takes breaks down each stage.
Who should build and maintain a custom Salesforce app
A SaaS company has three ways to get a custom Salesforce app built, and the build is the short part. Ownership lasts as long as customers keep the package installed, so choose by who will carry the upgrades.
| Option | Fits when | What to plan for |
|---|---|---|
| Your own engineers | Salesforce is a long-term channel and you can staff Apex, LWC and 2GP packaging | Hiring or training, plus a regression pass for each of the three Salesforce releases a year |
| A Salesforce development partner | You want a contract team, see our guide to AppExchange development company services | Scope, handover and who fixes issues after launch |
| Appnigma marketplace apps | You want the app, listing and review handled as one project while your engineers stay on the product | A separate maintenance retainer after launch |
Whoever builds it should start with 2GP. "For new apps, we recommend using 2GP managed packages," per the Apex Developer Guide. Appnigma's marketplace apps page calls its delivery "one scoped project" that covers development, listing preparation and install docs. Salesbricks reported "no engineering sprints diverted to the Salesforce package." If the app is one part of a wider integration roadmap, Appnigma's done for you delivery adds a named integration engineer who builds and maintains the integrations your customers need.
Mistakes that make a custom Salesforce app expensive
- Budgeting the build and not the release calendar. Three preview windows a year each need a regression pass, and that cost lasts as long as the app is installed.
- Pushing a major upgrade the week a release lands. Salesforce suggests waiting 3 to 4 weeks and pushing "to the sandbox organizations of your customers first," per Push Upgrade Best Practices.
- Changing validation rules or trigger errors in an upgrade. Salesforce warns these "may negatively impact subscribers' integrations," per Push Upgrades.
- Putting proprietary logic in formulas or Visualforce. Those are components "that you can't hide in your app," per Protecting Your Intellectual Property. Keep it in Apex or on your backend.
- Promising Professional Edition support from an API-only integration. Those orgs lack API access by default, and Bulk API 2.0 stays unavailable even after review.
- Setting the launch date from the build plan. Add 4 to 6 weeks of review, plus 2 to 3 more if a resubmission is needed.
Frequently Asked Questions
What is custom Salesforce app development for a SaaS company?
It means building a managed package that your customers install in their own Salesforce orgs, with your objects, Lightning components and Apex running there. It differs from an API integration, which runs on your servers and connects to the org.
How much does custom Salesforce app development cost?
Salesforce doesn't publish build costs. The fees it does publish are a per-attempt security review fee for paid apps (free apps pay none) and a revenue share of 15% for ISVforce apps or 25% for OEM apps. Ongoing upkeep across three releases a year is usually the larger line.
Can I sell a custom Salesforce app?
Yes. Enroll it in the ISV Partner Program, pass security review and list it on AgentExchange. Salesforce takes 15% of revenue for ISVforce apps, including Checkout sales, and 25% for OEM apps.
Do I need a custom app if I already have an API integration?
Only if customers need your product on Salesforce record pages, run Professional Edition, or ask for an installable listed app. If none of those apply, keep improving the integration.
Can Appnigma build our custom Salesforce app?
Yes. Appnigma's marketplace apps project covers the managed package, listing preparation, security review support and install docs, with maintenance available on a separate retainer.
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
- What Is a Salesforce Native App, and How Does a SaaS Company Get One Built?
- Salesforce App Development Cost
- How Long the Salesforce Security Review Takes
- Is It Worth Listing Your SaaS on AppExchange?
Sources
- Salesforce Developers, Apex Developer Guide, Managed Package Types
- Salesforce Developers, LWC Developer Guide, Get Started with Lightning Web Components
- Salesforce Developers, ISVforce Guide, API Access in Group and Professional Editions
- Salesforce Developers, ISVforce Guide, Limits for Group and Professional Editions
- Salesforce Developers, 2GP Developer Guide, Protecting Your Intellectual Property
- Salesforce Developers, 1GP Developer Guide, Push Package Upgrades to Subscribers
- Salesforce Developers, 1GP Developer Guide, Push Upgrade Best Practices
- Salesforce Developers, 1GP Developer Guide, Push Upgrades
- Salesforce Developers, Salesforce DX Developer Guide, Select the Salesforce Release for a Scratch Org
- Salesforce Developers, AppExchange Install Guide, What Is AgentExchange?
- Salesforce Developers, ISVforce Guide, How Is Revenue Shared in AgentExchange Checkout?
- Salesforce Developers, ISVforce Guide, Act on Security Review Results
- Salesforce Developers, ISVforce Guide, How the AgentExchange Security Review Works
- Salesforce Developers, ISVforce Guide, Periodic Security Re-Reviews
- Trailhead, Guide to Submitting Your Solution
- Salesforce Help, Partner Program FAQ for AgentExchange ISVs
- Salesforce, Partner Program ISV Track overview
- Salesforce, Consulting Partner Program
