Learn how to launch a Salesforce app on the AppExchange, from Dev Hub and 2GP packaging to business review, security review, and publishing.
.avif)
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.
A few early decisions shape everything that follows. Getting these clear up front avoids rework later.
Decide which Salesforce cloud your app supports (Sales, Service, Revenue Cloud/CPQ, etc.). This affects both technical setup and how Salesforce evaluates your listing.
Be explicit about which editions your app supports (Professional, Enterprise, Unlimited). Over-restricting reduces adoption; under-restricting increases support risk.
Define who the app is built for:
This directly influences listing copy, screenshots, and how the app is positioned during review.
Free or paid. This matters later for review sequencing and fees.
Most first-time ISVs underestimate the number of Salesforce orgs involved. Each has a specific role.
Your primary partner org. Required to participate in the AppExchange and access the Partner Community.
Where your namespace is managed and where second-generation managed packages live. This can be your PBO or a separate production org.
Used to create the namespace initially. You’ll also need a developer org with the app installed during security review.
Temporary, configurable environments used for development, testing, and packaging. Required for 2GP workflows.
If you’re using 2GP, this is effectively your Dev Hub.
Packaging note:
For new apps, 2GP is almost always the right choice.
Once orgs and settings are in place, the process is straightforward:
From the Partner Community:
This is also where review sequencing becomes important.
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:
Submitting security first still works but costs more.
Security review requires:
For lower-risk apps, the process is generally manageable. Our review completed in under a week with minimal back-and-forth.
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.
For first-time publishers:
Once you’ve done this once, future launches are far more predictable.
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 Team
RevOps, Salesforce & HubSpot experts
Candybox designs and runs the Salesforce, HubSpot and AI systems behind fast-growing B2B SaaS companies.
Straight answers to what B2B SaaS teams ask us most. Don't see yours? Just ask us.
As SaaS companies grow, disconnected tools and teams create data gaps, forecasting issues, and misaligned incentives. RevOps solves this by centralizing GTM operations, ensuring teams share the same metrics, and creating scalable processes that support predictable growth.
Most startups benefit from RevOps as early as Series A, when multiple tools and messy handoffs start creating inefficiencies. Signs it’s time include unreliable forecasts, unclear funnel conversion, poor customer experience at handoffs, and leadership needing trustworthy dashboards.
Sales Ops focuses on sales team processes and CRM upkeep.
Marketing Ops manages martech and the marketing-to-sales handoff.
RevOps spans the entire GTM lifecycle, integrating sales, marketing, and customer success with shared processes, tools, and KPIs.
Most of our clients are B2B SaaS companies - often between 50–500 employees - with fast-moving GTM teams and a need for clean, connected systems. We're especially strong with companies using Salesforce, HubSpot, Stripe, and product-led GTM motions.
RevOps, short for Revenue Operations, is the alignment of sales, marketing, and customer success under a unified strategy. It focuses on people, processes, platforms, and data to reduce silos, improve forecasting, and accelerate growth in SaaS businesses.
Primarily Salesforce and HubSpot. Our tools and processes are built to work natively with both, and we’ve handled orgs running both systems simultaneously.
Yes. We don't just hand you a Notion doc and walk away. We blend RevOps strategy with hands-on systems execution - so we’ll help you define the right logic, then build it directly in Salesforce or HubSpot (or both), end-to-end.