How Much Does It Cost to Build an AppExchange App in 2026?

Updated for 2026 — reflects Salesforce's current AppExchange security review pricing, in effect since March 2023.

Building an AppExchange app typically costs between $30,000 and $300,000 or more, depending on complexity, and that's before you factor in Salesforce's own review and listing costs. A simple utility app can ship in a few months for $30,000–$70,000. An enterprise-grade vertical solution with deep integrations and compliance requirements can run past $300,000 and take over a year.

That range is wide because "an AppExchange app" covers everything from a single custom component to a full commercial ISV product used by thousands of Salesforce orgs, and the factors that move a project from one end to the other — feature scope, integrations, compliance needs, team composition — are specific to what you're building. This guide breaks that range down by project type, shows where the budget actually goes phase by phase, and corrects a fee figure that a surprising number of cost guides still get wrong.

At MagicFuse, we've spent over a decade on Salesforce AppExchange development, building and maintaining AppExchange packages as an AppExchange partner for ISVs including Elements.cloud, Limio, ID-Pal, and E-Sign, so the numbers below come from real project patterns, not a generic estimate.

Key Takeaways

• Building an AppExchange app typically costs $30,000–$300,000+, depending on complexity, feature scope, and compliance needs.
• Salesforce charges a flat $999 per security review submission for paid apps (free apps pay $0), replacing the older $2,550-plus-$150/year model retired in March 2023.
• Package architecture, integration depth, and security review readiness are among the biggest cost drivers, alongside team seniority and compliance requirements.
• Development and QA typically take 45–60% of the budget, with discovery, design, security review prep, and launch prep making up the rest.
• Hidden costs like annual maintenance (15–30% of build cost), re-review fees, and release compatibility testing often get left out of initial estimates.
• A certified AppExchange partner with a proven security review track record usually costs less over a project's life than an in-house team going through the process for the first time.

How Much Does It Cost to Build an AppExchange App?

Here's the range at a glance, based on the same complexity tiers we use across our own AppExchange projects:

If you're validating an idea before committing to a full build, a lightweight MVP with core functionality and a clean UI typically lands at $50,000–$80,000 — enough to test with real users and pass security review, without building out every feature on your roadmap.

These are ballpark ranges based on real AppExchange project patterns, not a fixed price list — your actual cost depends on the specific factors covered in the next section, from feature scope and integrations to compliance requirements and team composition. If you want a number scoped to what you're actually building, our team can put together an estimate based on your requirements.

These figures also cover development only. Salesforce's own AppExchange fees — security review, and revenue share if you sell through AppExchange Checkout — are separate and much smaller by comparison. We'll break those out later in this guide.

What Factors Drive the Cost of Building an AppExchange App?

Eight things push a Salesforce app toward the low or high end of those ranges, and most of them compound each other rather than adding up one at a time.

App Complexity and Feature Scope

The number of custom objects, automations, and user roles your app manages has the single biggest effect on cost. A single-purpose utility with one main workflow costs far less than an app managing multi-role permissions, approval chains, and cross-object logic.

Package Architecture: First-Generation vs. Second-Generation Managed Packages

AppExchange listings must ship as managed packages — Salesforce doesn't allow unmanaged packages for commercial distribution. Within that, you're choosing between first-generation (1GP) and second-generation (2GP) packaging. Salesforce recommends 2GP for new packages: it supports modular development and CI/CD pipelines, which lowers the cost of every future release, even though initial setup can take a bit more planning than 1GP.

External Integrations and Backend Services

Connecting to third-party systems or running your own backend (for data processing, AI, or services Salesforce can't natively provide) adds both build time and ongoing operating cost. It also requires clean data isolation, so your app doesn't leak data across customer orgs or interfere with data a customer already has in their own Salesforce org — a requirement Salesforce checks closely during security review.

UI/UX and Lightning Web Components

Lightning Web Components are powerful tools for building custom user interfaces, and they take real design and engineering time — but they're also what drives adoption once your app is listed. Underinvesting here is a common way ISVs end up with a technically sound app that still struggles to convert potential users into installs.

Data Model Design and Salesforce API Integration Depth

How your custom objects, fields, and relationships are structured affects both build cost now and maintenance cost later. A data model that mirrors how Salesforce data naturally works is cheaper to build, test, and keep compatible with platform upgrades than one that fights the platform.

Team Composition and Seniority

A typical AppExchange build needs a Salesforce architect or tech lead, one or more AppExchange app developers, a quality assurance (QA) engineer, and a UX designer, at minimum — sometimes a product manager too. Rates for certified Salesforce specialists vary by region and experience level, and that development team is usually the largest single line item in your budget.

Security Review Readiness

Apps built with Salesforce security review requirements in mind from day one need far less rework before submission than apps where security posture gets addressed at the end. We cover the security review process and current fees in detail separately.

Compliance Requirements for Regulated Industries

Apps handling healthcare, financial, or other regulated data need additional design, testing, and legal review around data handling to meet standards like HIPAA or GDPR — real cost drivers for vertical apps that a generic utility app never has to budget for.

How Much Does an AppExchange App Cost by Project Type?

Cost tiers only mean something with real examples behind them. Here's how the ranges above map to actual AppExchange work.

Internal and Niche Utility Apps ($30,000–$70,000)

Apps that solve one well-defined problem for a specific team sit at this end of the range. For Ascent Solutions, a logistics and supply-chain ISV, we built two distinct calendar components — a Reservation Calendar with month and week views, and a Sales Calendar for daily item availability — on top of their existing Rental package, along with Lightning styling on legacy Visualforce pages. Scoped, well-defined feature work like this is where utility-tier budgets go.

Commercial ISV Products ($70,000–$200,000)

This is where most standalone AppExchange products for sale live, built by an independent software vendor (ISV) rather than an internal team. Elements.cloud, a UK-based change intelligence platform that helps companies visualize and organize their business processes, and MagicFuse's longest-running Salesforce client, needed a secure, scalable managed package that could sync millions of Salesforce records to an external application in near real time — well beyond what Salesforce's native limits allow out of the box. That meant custom application architecture, a purpose-built logging system, and query optimization on top of the standard managed-package build, which is exactly the kind of complexity that pushes a project from utility-tier to mid-tier cost.

Complex and Regulated Vertical Apps ($200,000+)

Apps handling sensitive data or complex commercial logic land here. ID-Pal, an Irish RegTech company, needed real-time identity verification built into the Salesforce platform with dynamic custom objects and bidirectional authorization — security-sensitive integration work that carries its own testing and review overhead. Limio, a subscription-commerce platform, needed a managed package supporting both B2B and B2C billing, a custom CPQ flow with approval chains and secure payment links, and integration with Zuora for payments — the kind of multi-system, revenue-critical build that justifies enterprise-tier budgets. Apps like this are AppExchange applications built specifically to generate revenue for the ISV, not just support internal business processes.

Not every AppExchange application starts from scratch, either — template-based Lightning Bolt Solutions for Experience Cloud sites and portals start from a pre-built template rather than a blank canvas, which can bring cost down for the right kind of project.

See the full story behind these builds on our AppExchange case studies page.

Where Does the AppExchange Development Budget Actually Go?

Rather than one lump sum, it helps to see how a typical AppExchange budget splits across phases — this scales to any project size, whether you're spending $40,000 or $250,000.

What Are the Steps to Build and List an AppExchange App?

1. Join the Salesforce Partner Program. Register as an ISV partner in the Partner Community to access the Partner Console, documentation, and required tooling.
2. Validate the app idea with market analysis. Study existing apps in your target market to gather valuable insights into gaps you can fill for your target audience.
3. Build and test an MVP. Ship core functionality that matches your business needs first, with unit testing, integration testing, and thorough testing, including automated testing, built in from the start.
4. Package the app and submit for security review. Package as a 2GP managed package where possible, then submit and budget for at least one resubmission cycle.
5. List, launch, and support. Publish your AppExchange listing with documentation and marketing assets ready, then plan for ongoing support and updates. For the full walkthrough of each step, see our step-by-step AppExchange development guide.

How Much Are Salesforce's AppExchange Fees, and How Do They Differ From Development Cost?

Development cost is essentially a one-time fee you pay your team or partner to build the app. AppExchange fees are separate — they're what Salesforce charges to review and list it. A lot of published cost guides blend the two together, and several are also citing a fee structure Salesforce retired years ago.

Here's the current picture:

Tip: Salesforce retired the older $2,550 initial fee plus $150 annual fee for security review on March 16, 2023, replacing it with a flat $999-per-attempt model. If a cost guide you're reading still quotes $2,550 or a separate annual listing fee, it hasn't been updated since that change. See Salesforce's own announcement and the Trailhead submission module for the current figures.

Beyond fees, Salesforce AppExchange offers three pricing models for how you generate revenue: free (no charge to users, but you still carry hosting and support cost as the vendor), freemium (core features free, advanced features paid), and paid, where subscription pricing commonly runs $5–$200 per user per month depending on the app's value and market. These Salesforce AppExchange pricing models are what determine your app sales revenue once you're listed. For the full breakdown of licensing models and how to price your app, see our guide to Salesforce AppExchange pricing.

Should You Build In-House or Hire an AppExchange Development Partner?

What an In-House Development Team Really Costs

Building with an in-house development team means hiring or reassigning a Salesforce architect, developers, a QA engineer, and a UX designer, then keeping that in-house team staffed through every future release. Salesforce architecture expertise is genuinely hard to hire for, and a team with strong general coding skills but no AppExchange-specific experience often spends real budget on mistakes a specialized team wouldn't make in the first place.

What a Certified Partner (PDO) Costs — and Where It Saves Money

A PDO — a certified Partner Development Outsourcer — is a consulting partner that provides Salesforce AppExchange development and consulting services as its core business. Working with one usually costs less over the life of a project than it looks on paper, because a team that has already taken multiple apps through security review tends to avoid the rework and resubmission cycles that quietly inflate in-house budgets, following proven strategies rather than figuring the process out for the first time. A partner with an established AppExchange track record can also improve your AppExchange listing's visibility and adoption once it's live, and keep delivery on schedule and on budget rather than absorbing scope creep.

What It Costs to Get It Wrong the First Time

Two of our own client engagements make this concrete. E-Sign, a UK-based digital signature platform, launched its first AppExchange release without deep Salesforce expertise on the team — the result was slow, hard to use, and missing features. We rebuilt the product for usability, expanded it to cover major e-signature workflows, and prepared it properly for security review; it now has full Salesforce integration and a faster time to market on every subsequent release. Atamis, a UK procurement platform, was originally built by a team without Salesforce experience, mostly on Visualforce with little Lightning. We reviewed and optimized the architecture, added features and a DocuSign integration, brought test coverage up, and prepared it for security review — the product has passed with strong AppExchange reviews since. Both are examples of the same pattern: rebuilding an app to pass review and scale properly usually costs more than building it right the first time would have.

What Hidden Costs Do Most AppExchange Estimates Miss?

The build itself is rarely the whole story. These costs show up after launch and are easy to leave out of an initial budget:

• Annual maintenance, typically 15–30% of the original development cost, covering bug fixes, minor enhancements, and general upkeep.
• Compatibility testing against Salesforce's three major releases a year — each one can affect your app's behavior, so QA against new releases is a recurring, not one-time, cost.
• Backend and cloud service costs for any app that depends on external infrastructure rather than running entirely inside Salesforce.
• Re-review costs, since each resubmission to security review costs another $999 for paid apps — a real incentive to get it right the first time, not just a nice-to-have.
• Post-launch customer support, especially in the first few months after listing, when adoption issues surface fastest.
• Scaling costs as data volume, user count, and the number of customer orgs using your app all grow.

How Can You Reduce the Cost of Building an AppExchange App?

These are proven strategies we rely on across our own AppExchange projects for an efficient development process from the first sprint to launch:

• Start with an MVP and let real user feedback shape the roadmap, instead of building every feature before launch.
• Use native Salesforce and reusable components wherever they fit, rather than custom-building functionality Salesforce already provides.
• Choose 2GP packaging where it fits, so future releases stay cheaper to build and test.
• Design for security review from day one instead of at the end, so you're not paying for rework and a second $999 submission.
• Work with a partner who has already taken apps through security review, so you're not the one paying to learn Salesforce's compliance rules the hard way.

How Does MagicFuse Help ISVs Build AppExchange Apps Without Overspending?

MagicFuse has worked in the Salesforce ecosystem for 12+ years, with 80+ certified Salesforce consultants and 270+ certifications across the team — including Application Architect, Integration Architect, and Platform Developer I and II, the certifications most directly relevant to AppExchange packaging and security review. We've delivered 150+ Salesforce projects, with AppExchange and ISV work as a core part of that portfolio, and that experience is what makes an efficient development process possible instead of a first attempt at learning Salesforce's rules.

Elements.cloud has been a MagicFuse client since roughly 2014 — our longest-running Salesforce relationship — and our team has grown from an initial developer to around 30 people supporting their business solutions today, passing every security review along the way. E-Sign is a newer relationship that shows the other side of that same expertise: taking an app that was struggling on AppExchange and rebuilding it into one with full Salesforce integration and a faster path through future reviews. That range, from long-term flagship partnerships to turnaround projects, is what direct access to a dedicated team of Salesforce specialists gives you that a generalist development shop usually can't.

Is Building an AppExchange App Worth the Cost?

For the right product, yes. AppExchange puts your app in front of Salesforce users and Salesforce customers who are actively looking for business solutions inside the Salesforce platform they already use every day, which is a different kind of distribution than building a standalone SaaS product from zero. The cost isn't small, but it's predictable once you know which tier your app falls into and where the budget actually goes — which is exactly what this guide has walked through.

The apps that get the most out of that investment are the ones built with security review, packaging strategy, and maintenance cost in mind from the start, not bolted on after the fact. That's the difference between a $70,000 app that becomes a durable product and a $70,000 app that needs a $70,000 rebuild two years later.