2GP managed package
A second-generation managed package with your namespace, versions, and permission sets, built from Git.
The Problem
Your Enterprise Buyers Ask If You're on AppExchange
It comes up in late-stage deals: the buyer's Salesforce admin wants an installable app, not a CSV export or a custom script in their org.
01 · Custom installs
Each customer needs custom setup work in their own org.
One managed package installs the same app in every customer org.
02 · Failed review
The security review comes back with pages of findings.
Scans run before submission, with false positives written up for the reviewer.
03 · Old packaging
Your first-generation package makes each release slow and risky.
New products ship as 2GP packages built from source control.
04 · Stuck versions
Customers sit on old versions that nobody can upgrade.
Push upgrades move approved versions to customer orgs on your schedule.
A prospect's Salesforce admin asks for your AppExchange listing, and you send a setup document instead. Your team writes custom Apex in each customer's org, so no two installs look alike. You started a managed package, but the security review came back with pages of findings and a second fee to pay. Customers on older versions can't be upgraded without a call. Every new deal adds another one-off install your engineers have to support.
We start with the record types, screens, and API calls your customers need inside Salesforce, then package them as one second-generation managed package. Scans run before submission, findings get fixed or documented, and the listing and licensing are set up for sales. Every customer installs the same app, instead of your engineers rebuilding it in each org.
Namespace planned before code
A namespace can't change once Salesforce assigns it, so we settle it first.
Review findings fixed early
Code Analyzer and endpoint scans run before submission, not after a rejection.
Upgradeable in every org
Managed package versions upgrade customer orgs instead of leaving them behind.
Our Salesforce AppExchange Development Services Process
From Package Plan to AppExchange Listing in Five Clear Steps
You approve the namespace and package design before code, see every scan result before submission, and review the listing before it goes live.
We review your product, your API, and any existing package or org, then outline the listing type and package plan. You get a scoped plan and a fixed quote. If an API-only listing covers your case, we'll tell you before we quote.
What's Included
What You Get With Salesforce AppExchange App Development
The package, the Salesforce features inside it, the connection to your SaaS, the security review work, and the listing and licensing that let you sell it.
Compare Options
DeveloperLook vs Salesforce Consultancy vs In-House Apex Developer
AppExchange consultants who focus on admin work are strong inside a single org, and your own Apex developer knows your product. Here is where each one fits an ISV package.
| Feature | DeveloperLookBest fit | Salesforce consultancy | In-house Apex developer |
|---|---|---|---|
| Up-front planning | Namespace and package plan first | Org-by-org requirements | Planned around the roadmap |
| ISV packaging experience | 2GP, namespaces, and push upgrades | Usually org implementations | Often first package |
| Security review preparation | Scans and false-positive notes done | Varies by firm | Learned after a failed attempt |
| Connection to your SaaS | Named Credentials and OAuth built in | Often outside scope | Knows your API best |
| Single-org configuration | Not our focus | Their main strength | Possible with time |
| Test coverage | Above 75% Apex coverage | Org-specific tests | Depends on spare time |
| Code ownership | Your namespace and repository | Check the contract | |
| Cost predictability | Fixed scope per plan | Hourly or retainer | Salary plus ramp-up time |
DeveloperLook
Salesforce consultancy
- Up-front planning
- DeveloperLook: Namespace and package plan firstSalesforce consultancy: Org-by-org requirements
- ISV packaging experience
- DeveloperLook: 2GP, namespaces, and push upgradesSalesforce consultancy: Usually org implementations
- Security review preparation
- DeveloperLook: Scans and false-positive notes doneSalesforce consultancy: Varies by firm
- Connection to your SaaS
- DeveloperLook: Named Credentials and OAuth built inSalesforce consultancy: Often outside scope
- Single-org configuration
- DeveloperLook: Not our focusSalesforce consultancy: Their main strength
- Test coverage
- DeveloperLook: Above 75% Apex coverageSalesforce consultancy: Org-specific tests
- Code ownership
- DeveloperLook: Your namespace and repositorySalesforce consultancy: Check the contract
- Cost predictability
- DeveloperLook: Fixed scope per planSalesforce consultancy: Hourly or retainer
Projects We've Built
B2B SaaS and Finance Platforms We Have Built
B2B SaaS, finance, and insurance platforms we designed and built. None is an AppExchange app, but each serves sales and service teams that live in a CRM.
Oasic Finance SaaS Web Design & Development
- Finance
- SaaS Platform
- Dashboard
EverTrust Insurance Web Design & Development
- Insurance
- Dashboard
- Website
Finto Corporate Website Design & Development
- Finance
- Dashboard
- Website
Saasmo Recruiting Software Web Design & Development
- Technology
- HR & Staffing
- SaaS Platform
What Our Clients Say
What Clients Say After Launch
Feedback from teams we have built websites, apps, and integrations for.
We had a pretty specific idea of what we wanted our website to become, but I wasn’t sure how easily we could explain all of it to a development team. There were quite a few moving parts, and we were working toward a deadline, so I expected a few things to get lost along the way. That never really happened. They understood what we were trying to achieve, kept us updated throughout the process, and got everything ready within the agreed timeline. The final site feels much easier to navigate, works beautifully on mobile, and is noticeably smoother for our customers. It was a huge relief seeing the original idea actually turn into the website we had in mind.
The mobile experience is probably my favourite part of the new site. We had spent a lot of time making sure the desktop version looked right, and the team kept pushing us to think about how everything would actually feel on a phone too. They were right. The navigation is clean, the interactions feel natural, and everything we’ve tested so far works exactly as it should. They also went through the links, forms, integrations, and other details more than once before launch, which I really appreciated. And even after going live, we could still reach out when something came up. The whole process felt friendly, organised, and surprisingly straightforward.
What I appreciate most is that the website is actually easy for us to manage now. We can update content ourselves instead of sending a developer a message every time we need to change something small. They also paid attention to the technical SEO side, which mattered to us because we didn’t want a new website to create problems for the traffic we already had. I’ve probably asked more questions than I should have since launch, but every question has been handled patiently and without any fuss. The team is easy to work with, they explain things clearly, and when we need something changed, they focus on getting it done rather than making the process complicated.
1,250+
Projects shipped
10+
Years of experience
Top 3%
Upwork Top Rated Plus
5 stars
Average review score
Want results like these?
Tell us what you are building. You get a reply within 24 hours on business days, then a written estimate.
Work Culture
Why ISVs Trust Us With Their AppExchange App
Choosing a Salesforce AppExchange development company is choosing who shapes your package for years. These habits keep it reviewable and upgradeable.
Namespace decided once
We settle the namespace and package boundaries before writing code. Getting them wrong means a new package and a migration for every customer.
Scans before every submission
Code Analyzer and endpoint scans run on each release candidate before it leaves our hands. You see the findings before Salesforce's reviewers do.
Source control as the record
Every change lives in Git and is built into scratch orgs from there. No release depends on someone's personal sandbox.
Honest about review odds
We tell you what the scans show and what reviewers tend to ask. Salesforce decides the outcome, so we plan time for a second attempt.
Fixed price for each plan
The package scope, features, and review work are priced before we start. Anything new is quoted first, so the approved number holds.
Your namespace and Dev Hub
The namespace, Dev Hub, and listing are registered in your Partner Business Org. Nothing about the app depends on our accounts.
Overview
What do Salesforce AppExchange development services include for an ISV?
DeveloperLook provides Salesforce AppExchange development services for SaaS companies selling to Salesforce customers. We build 2GP managed packages with Apex, Lightning Web Components, and API callouts, prepare the security review, and set up your listing and licenses. Projects start from $1,400 and take 2 to 16 weeks.
DEVELOPERLOOK
Project facts · Salesforce AppExchange Development Services
- Service
- Salesforce AppExchange development services (2GP package, security review, listing)
- Typical timeline
- 2 to 3 weeks review prep, 8 to 16 weeks for a full app
- Platforms
- Salesforce orgs, listed on AppExchange (now AgentExchange)
- Built with
- Apex, Lightning Web Components, Flow, 2GP, Salesforce CLI, and Code Analyzer
- Experience
- 10+ years of development experience and 1,250+ shipped projects
- Post-launch support
- 30, 60, or 90 days, depending on plan
- Communication
- Calls in US, UK, and AU business hours
- Starting price
- From $1,400 USD, fixed scope after a free package review
Reviewed 22 Oct 2026 by Saimul Islam
Good fit
SaaS companies selling to Salesforce customers
Your enterprise prospects ask whether you're on AppExchange, and your team loses weeks to custom setup work in each customer's org.
ISVs stuck in security review
Your package failed the security review once, and you need the findings fixed and false positives documented before the next $999 attempt.
Teams on first-generation packages
Your app ships as a first-generation managed package, and new products should be on 2GP, since Salesforce can't migrate the old one.
AI product teams
Your product has AI features, and you want them packaged as Agentforce actions that customers install from AppExchange, now called AgentExchange.
Agencies with ISV clients
Your agency builds for SaaS clients and needs to hire AppExchange app developer capacity for one packaging and review project.
Not a fit
Work in your own org
You need Apex or Flows for your own company's org, not an app to sell. Our Salesforce Development Services page covers that work.
Sync for your own org
You only need your Salesforce org synced with an ERP, inbox, or helpdesk. Our Salesforce Integration Services page fits that better.
Your users live in Slack
Your customers want your product's updates in Slack rather than inside Salesforce records. Our Slack App Development Services page covers Slack apps.
Promised first-try approval
You need a promise that the security review passes on the first attempt. Salesforce runs the review and decides, so nobody can honestly promise it.
Not sure we're the right fit?
Book a free call or message us. We'll tell you honestly whether we're the right team.
Pricing
Transparent Starting Prices for Salesforce AppExchange Development Services
These are starting points in USD. Your final price depends on package size, your API, and review work, and you get a fixed proposal after a free package review. Salesforce's review fee is separate.
For ISVs with an existing package that needs to pass security review.
$1,400one-time, USD
- Free package and listing review
- Code Analyzer scan with a fix list
- Dynamic scan of your external endpoints
- False-positive documentation
- Submission package for the review
- 30 days of post-launch support
Recommended
For SaaS teams putting their product inside Salesforce for the first time.
$4,500one-time, USD
- Everything in Review Readiness
- 2GP managed package with your namespace
- Apex, Lightning Web Components, and Flows
- Named Credentials and External Client App
- Apex tests above 75% coverage
- 60 days of post-launch support
For ISVs ready to sell: submission, listing, licensing, and upgrades handled.
$9,200one-time, USD
- Everything in Managed Package Build
- Security review submission and resubmission
- Listing set up in the Partner Console
- License Management App and push upgrades
- Agentforce actions packaged where they fit
- 90 days of post-launch support
For Agencies
White-Label AppExchange App Development for Agencies
You own the client relationship. We supply the ISV engineering: package design, Apex and Lightning Web Components, review preparation, and listing setup. All of it runs under your agency's name, in your client's own Partner Business Org.
How the partnership works
White label: your client only ever sees your brand
- Your client
- You, the agency
- DeveloperLook
Share the product brief
Send the client's product, API docs, and what their Salesforce buyers ask for.
- Client needs
- You share the details
- Details received
We plan the package
A package plan, a fixed price, and a named engineer reach you within days.
- Scope and plan
- Proposal to resell
- Your quoteYOUR LOGO
Build and hand off
We build, scan, and submit, then hand the package over under your agency brand.
- Done by our team
- Your brand on it
- Handed to your clientDone
Partner with DeveloperLookDelivered under your brand
Stay client-facing
You lead the client relationship while we build the package.
Predictable delivery
Fixed scope per plan, with review time built into the dates.
Senior Salesforce engineers
Engineers who know 2GP, namespaces, and the security review.
Flexible capacity
Take on ISV projects without hiring a packaging specialist.
The Right Technology for Your Project
Technology Stack
The Salesforce platform features, packaging tools, security scanners, and SaaS-side stack we use to ship reviewable managed packages.
Salesforce- Apex
- Lightning Web Components
- Flow
- Agentforce
- 2GP managed packages
- Salesforce CLI
- Scratch orgs
- Dev Hub
- Salesforce Code Analyzer
- OWASP ZAP
- Burp Suite
- Named Credentials
Node.js
TypeScript
PostgreSQL
AWS
FAQ
Frequently Asked Questions
Straight answers on AppExchange cost, timelines, building and publishing an app, and becoming a partner.
Saimul IslamFounder & CEO, DeveloperLookStill have questions?
Send a message or book a call with the team.
AppExchange app development services start at $1,400 for review readiness on an existing package. A new 2GP managed package build is $4,500, and a full launch with submission, listing, and licensing starts at $9,200. Salesforce's own review fee of $999 per attempt for paid apps is separate.
A full AppExchange app usually takes 8 to 16 weeks to build and prepare. Review readiness for an existing package takes 2 to 3 weeks. Salesforce's ISVforce guide puts the security review itself at about 4 to 6 weeks, so we set your launch date after the review.
You build it as a second-generation managed package, which Salesforce recommends for all new apps. You join the Partner Community, use your Partner Business Org as the Dev Hub, register a namespace, and develop in scratch orgs with the Salesforce CLI. Versions need 75% Apex test coverage to be promoted.
Connect the package to your SaaS with Named Credentials for outbound calls and an External Client App for OAuth. Salesforce stopped creating new Connected Apps from Spring '26, so new apps use External Client Apps. If you only need API access with no package, an API listing may fit, and it still gets reviewed.
You publish an app in AppExchange after it passes Salesforce's security review. Then you create the listing in the Partner Console, get it approved, and sign the Partner Application Distribution Agreement. Paid apps sell through Checkout or your own sales team, with licenses tracked in the License Management App.
You become an AppExchange partner by joining the Salesforce Partner Community and enrolling as an ISV partner. Salesforce then sets up a Partner Business Org with 2 Enterprise Edition licenses for running your business. Salesforce's help pages put the ISVforce revenue share at 15% of app revenue.
Not necessarily: Salesforce's Partner Program Agreement covers a company, another legal entity, or an individual acting for themselves. Whoever signs must be able to bind the business, and Salesforce runs legal checks on applicants. An LLC is one common choice, so ask your own lawyer which entity fits you.
Salesforce checks your package with its Code Analyzer and expects a dynamic scan of every non-Salesforce endpoint you connect to. ZAP and Burp Suite are common scanners, and documented false positives are accepted. Paid solutions pay $999 per attempt, and Salesforce's Trailhead notes that most submissions pass on the second attempt.
Yes, AppExchange (now AgentExchange) has an Agentforce Solution listing type for actions, topics, and prompt templates in managed packages. Agents ship as agent templates, and custom actions can be flows, invocable Apex, or prompt templates. Agentforce solutions carry extra security requirements in the review, so we plan for them early.
You do. The namespace, Dev Hub, and listing live in your Partner Business Org, and the source code sits in your Git repository. Since a namespace can't be changed, we register it in your name from day one, and every plan includes 30 to 90 days of support.
Saimul IslamFounder & CEO, DeveloperLookStill have questions?
Send a message or book a call with the team.
Free 30-min callGoogle Meet
Book a call
Book a free 30-minute call
In 30 minutes on Google Meet we walk you through how we would build it, how long it takes and what it costs. Then you get a written estimate.
Calendar not showing? Book on cal.com or send a brief.