Salesforce app development costs fall into two layers most guides never separate: the cost to build the app, and the cost to publish and run it on the AppExchange. A native AppExchange app typically costs $25,000 to $150,000+ to build over 6 to 12 months, then carries a $999-per-submission security review fee and a 15% revenue share. Over three years, maintenance and revenue share often exceed the original build cost.

Pro Tip

TL;DR: Building a native Salesforce AppExchange app costs $25,000 to $150,000+ (Noltic), plus a $999 security review fee per submission and a 15% revenue share (Salesforce Trailhead). The biggest hidden cost is the developer hire, with US Salesforce developers earning $94,500 to $140,000 (Salesforce Ben, 2026). No-code generation removes that line item entirely.

Building a native managed package costs $25,000 to $150,000+ for a first app, scaling with complexity (Noltic). Most of that is specialized developer time: Apex, Lightning Web Components, 2GP packaging, and security-review rework.

The build usually breaks into phases: planning and architecture ($5,000 to $20,000), design ($5,000 to $30,000), and development plus testing ($15,000 to $100,000) (Noltic). The reason the build dominates the budget is talent. US Salesforce developers earn $94,500 to $140,000, and the architects who handle packaging and security review are the scarcest role in the ecosystem (Salesforce Ben, 2026).

Separate from building it, Salesforce charges a $999 security review fee per submission for paid apps and a 15% revenue share under the standard ISVforce model (Salesforce Trailhead). Free apps have the review fee waived.

A correction worth knowing: several widely-cited cost guides still quote the old model of a $2,550 security review fee plus a $150 annual listing fee. Salesforce retired that in March 2023 and moved to the $999-per-submission model (Salesforce Partner News). If a page quotes $2,550, or a separate $150 annual listing fee, it is citing the retired model. Confirm any current listing fee in the ISVforce Guide before budgeting.

Pro Tip

Our finding: Because the $999 fee applies to every resubmission, a failed review is not just a delay, it is a repeat charge. Generating code to the security standard up front is cheaper than iterating after a rejection.

The revenue share depends on how your customers license Salesforce. Under the ISVforce model, your customers already own Salesforce licenses and simply buy your app, so Salesforce takes 15% of your net revenue. Under the OEM (embedded) model, you bundle Salesforce platform licenses into your product and sell it as a standalone, so Salesforce takes a larger share, commonly cited at 25% (Magicfuse).

Most B2B SaaS apps that extend an existing Salesforce org use ISVforce at 15%. OEM mainly applies if your product needs to run for customers who do not already have Salesforce. The exact percentages and any volume-tier reductions are negotiated in your partner agreement, so treat published figures as the standard starting point.

The build is a one-time number. Maintenance and revenue share are recurring, and over three years they routinely exceed the original build. Every Salesforce seasonal release (three per year) can require package updates, and a growing app keeps paying 15% of net revenue.

Worked example for a commercial ISV app at $500,000 ARR:

The revenue share alone outweighs the build. That is why reducing the upfront build with no-code does not solve the whole equation, but it removes the single largest controllable cost and shortens time to revenue. Revenue share scales with success, which is acceptable; a six-figure build delay before you earn a dollar is not.

The headline build number is rarely the full story. Budget for these too:

• Failed-review resubmissions. Each failed paid resubmission is another $999, plus the weeks of developer time to fix and the lost time-to-market.

• Sandbox and license costs for development and testing environments.

• Partner Business Org setup and the License Management App to track installs.

• Seasonal-release maintenance, three times a year, for as long as the app lives.

• Documentation and listing assets (demo orgs, screenshots, metadata) that Salesforce requires for the listing.

Pro Tip

Our finding: Across the builders we work with, maintenance and the recurring fees, not the initial build, are what quietly turn a "$50,000 app" into a multi-hundred-thousand-dollar commitment over three years.

The biggest lever is the build, because it is the part dominated by scarce, expensive developer hours. A no-code generation platform removes that line item. Appnigma AI generates an AppExchange-ready managed package from a plain-language description, handling Apex, Lightning Web Components, 2GP packaging, namespace setup, and security-review preparation. You still pay Salesforce's standard fees, but you avoid the $25K to $150K+ build and the multi-month timeline.

The fees and revenue share are set by Salesforce and apply either way. What changes is the build cost and the time before you can earn revenue, and those are exactly where no-code generation moves the numbers.

The build cost is the same whether you list free or paid; the difference is in Salesforce's fees. Free apps have the $999 security review fee waived and pay no revenue share, while paid apps pay the $999 per submission and the 15% revenue share (Salesforce Trailhead). Many ISVs list a free version to clear the review at no fee, then monetize through a paid tier later. The engineering work to reach a listable managed package does not change either way, which is why removing the build cost matters regardless of your pricing model.

Offshore Salesforce developers lower the hourly rate but not the underlying risk. US Salesforce developer rates run roughly $62 to $170 per hour, with freelance marketplaces spanning $50 to $315 (Glassdoor). Offshore can cut that, but security-review rework, packaging mistakes, and seasonal-release maintenance still apply, and each failed resubmission still costs $999. A lower rate on a process that needs several cycles is not the saving it looks like. Removing the hand-build entirely, rather than relocating it, is the larger lever.

Putting the three paths side by side over a three-year horizon clarifies where the money actually goes.

In every path you pay Salesforce's $999 review fee and 15% revenue share, because those are fixed. The build is the only large variable you control, and it is the line item no-code removes. For a lean SaaS team racing to a listing, the time saved is often worth more than the dollars: revenue starts months earlier.

Publishing a paid app costs $999 per security review submission and a 15% revenue share of net revenue under the ISVforce model (Salesforce Trailhead). Free apps have the security review fee waived.

Most of the cost is specialized developer time. US Salesforce developers earn $94,500 to $140,000, and 91.3% report the market is more challenging than before (Salesforce Ben, 2026). Scarce architect talent and security-review rework push first-app budgets to $25K to $150K+.

It is $999 per submission for paid apps as of March 2023, when Salesforce retired the older $2,550 plus $150 model. Pages still quoting $2,550 have not been updated.

Yes, by removing the developer-hour cost. A no-code platform like Appnigma generates the managed package directly, so you pay only Salesforce's standard publishing fees rather than a $25K to $150K+ build.

Yes. The ISVforce share can drop at high revenue volumes (commonly cited above the ~$20M tier), though tiered terms are negotiated in your partner agreement and vary by contract.

ISVforce (15%) is for apps sold to customers who already own Salesforce licenses. OEM (around 25%) is for apps that bundle Salesforce platform licenses and sell as standalone products. Most extension apps use ISVforce.

About the author. Sunny Chauhan is the founder and CEO of Appnigma AI, a no-code platform that generates Salesforce AppExchange-ready managed packages. He advises B2B SaaS teams on the true cost of going native on Salesforce.

Building a native Salesforce AppExchange app costs $25,000 to $150,000+ over 6 to 12 months, plus a $999 security review fee per submission and a 15% ISVforce revenue share (Salesforce Trailhead, 2026). Over three years, maintenance and revenue share typically exceed the build. Appnigma AI removes the development cost by generating the managed package from natural-language prompts.

• How does the AppExchange revenue share work

• Salesforce security review cost and fee

• Salesforce AppExchange development company and services

• How to build a managed package without a Salesforce developer

1. Salesforce Trailhead, ISV Security Review module (fee, duration)

2. Noltic, AppExchange app cost breakdown (phased costs)

3. Salesforce Ben Developer Salary Guide, 2026

4. Concret.io, AppExchange Security Review Cost FAQs (March 2023 fee change)

5. Salesforce ISVforce Guide, AppExchange Checkout revenue share

6. Magicfuse, ISVforce vs OEM revenue share