Blog

/

How to Launch Your Salesforce App on the AppExchange

How to Launch Your Salesforce App on the AppExchange

Learn how to launch a Salesforce app on the AppExchange, from Dev Hub and 2GP packaging to business review, security review, and publishing.

How to Launch Your Salesforce App on the AppExchange

If you’re launching an app on the AppExchange for the first time, the biggest challenge is  understanding the process.

Salesforce documentation explains individual steps well, but it doesn’t provide a clear end-to-end picture: which orgs you actually need, how packaging decisions affect downstream steps, how reviews are sequenced, or where teams tend to lose time.

We recently went through this entire process ourselves, from namespace setup and scratch orgs to security review and publishing. This guide is a practical walkthrough of what mattered, what slowed us down, and what we’d do differently next time.

Start With the Right Conceptual Decisions

A few early decisions shape everything that follows. Getting these clear up front avoids rework later.

Target Cloud

Decide which Salesforce cloud your app supports (Sales, Service, Revenue Cloud/CPQ, etc.). This affects both technical setup and how Salesforce evaluates your listing.

Required Sales Edition

Be explicit about which editions your app supports (Professional, Enterprise, Unlimited). Over-restricting reduces adoption; under-restricting increases support risk.

Target User Persona

Define who the app is built for:

  • Admins
  • Architects
  • Ops / RevOps
  • End users (sales, service, CS)

This directly influences listing copy, screenshots, and how the app is positioned during review.

Business Model

Free or paid. This matters later for review sequencing and fees.

The Org Setup (Why You Actually Need Each One)

Most first-time ISVs underestimate the number of Salesforce orgs involved. Each has a specific role.

Partner Business Org (PBO)

Your primary partner org. Required to participate in the AppExchange and access the Partner Community.

Dev Hub Org

Where your namespace is managed and where second-generation managed packages live. This can be your PBO or a separate production org.

Developer Org

Used to create the namespace initially. You’ll also need a developer org with the app installed during security review.

Scratch Orgs

Temporary, configurable environments used for development, testing, and packaging. Required for 2GP workflows.

Packaging Org

If you’re using 2GP, this is effectively your Dev Hub.

Packaging note:

  • 1GP is legacy, org-based, and UI-driven
  • 2GP is source-driven, CLI-based, and far more flexible

For new apps, 2GP is almost always the right choice.

Development & Packaging Flow (High Level)

Once orgs and settings are in place, the process is straightforward:

  1. Apply for a Partner Business Org
  2. Enable Dev Hub
  3. Enable Unlocked Packages and 2GP
  4. Create and register your namespace
  5. Build and test the app
  6. Create a scratch org with minimal required config
  7. Verify all required components are present
  8. Create a package via CLI (beta version)
  9. Complete beta testing
  10. Promote the package
  11. Production installs are now supported

Ready to Measure the Full Funnel and Grow?

Schedule a call

Creating the AppExchange Listing

From the Partner Community:

  • Create a listing in Publishing
  • Connect your Dev Hub org under Technologies
  • Your packages appear automatically under Solutions
  • Complete listing content and metadata

This is also where review sequencing becomes important.

Business Review vs Security Review (Sequence Matters)

If your app is free, submit the Business Review first.

Once approved, Salesforce provides a Security Review voucher, reducing the fee to $1 (Stripe does not allow $0 charges).

Recommended sequence for free apps:

  1. Create listing
  2. Submit Business Review
  3. Receive voucher
  4. Submit Security Review

Submitting security first still works but costs more.

Security Review: What It Actually Involves

Security review requires:

  • A UAT environment
  • Static code scans in your dev environment
  • Checkmarx scans via the Partner Security Portal
  • Documentation of false positives

For lower-risk apps, the process is generally manageable. Our review completed in under a week with minimal back-and-forth.

Managed Package Consideration: Logging Matters

Managed packages hide code to protect IP. That also means you can’t debug issues directly in customer orgs.

Build logging into the app from the start. Even basic error and event logging makes post-install troubleshooting significantly easier.

Where the Time Really Goes

For first-time publishers:

  • Most effort goes into understanding the process
  • Execution is relatively fast once the path is clear
  • Security prep (scans, documentation) is the largest non-development task

Once you’ve done this once, future launches are far more predictable.

Final Thoughts

Publishing on the AppExchange is less about complexity and more about alignment with Salesforce’s packaging and review model.

With the right setup, correct review sequencing, and reasonable security preparation, the process is approachable and repeatable.

If you’re planning an AppExchange launch and want a second set of eyes on packaging, security prep, or listing strategy, this is the kind of work we help teams think through every day.

In case you're interested, below is our founder's presentation on this same topic.

Candybox

Candybox Team

RevOps, Salesforce & HubSpot experts

Candybox designs and runs the Salesforce, HubSpot and AI systems behind fast-growing B2B SaaS companies.

Related

I like that Candybox is not afraid to push back for the good of their customers.
Claudio Cocivera
Sr. Manager Business Systems & Processes
Staffbase logo
Merger migration, no major bugs
6 months
Candybox took a personalised approach to our business; they didn’t build an out of the box solution; they tailored it to our needs with industry knowledge and best practices.
Arran Cruickshanks
Commercial Director
Sleek logo
Adoption in week 1
90%+
They are true thought partners and don't require a structured list of requirements. I gave them a high level set of objectives and they were able to translate that into tactical technical updates.
Chiraag Kapoor
Principal
It felt like I walked into a fully-functioning system.
Kimberly DelSignore
Kimberly DelSignore
RevOps Lead
Omni Analytics logo
How Omni scaled RevOps and built a high-impact data architecture with Candybox.
to a live CPQ (vs. 9 months)
2–3 months
Now, we actually work methodically and have a process.
Keith Jones
Keith Jones
Leader of GTM Systems
MURAL logo

Frequently asked questions

Straight answers to what B2B SaaS teams ask us most. Don't see yours? Just ask us.

Why is RevOps important for scaling companies?

When should a SaaS company hire its first RevOps role?

What’s the difference between RevOps, Sales Ops, and Marketing Ops?

What types of companies do you typically work with?

What is RevOps in SaaS?

What CRMs do you work with?

Can Candybox handle both strategy and implementation?