How do you architect a Salesforce AppExchange ISV solution for B2B verticals?

Building an AppExchange-listed B2B vertical solution requires packaging, licensing, and go-to-market architectural decisions:

Managed Package: Use a managed package with a namespace. Source code (Apex classes, triggers, LWC) is obfuscated to protect IP. Supports upgradeable versioning — subscribers receive updates via package upgrades.

Packaging strategy: Separate the base package (core data model, core logic) from feature packages (premium features, vertical add-ons). This allows tiered pricing and modular deployment.

License Management App (LMA): Install LMA in the ISV's Partner Business Org to manage subscriber licences (trial, active, expired). Configure licence enforcement in Apex using UserPackageLicense checks.

Security review: Pass the Salesforce AppExchange security review (SOQL injection, FLS, XSS, CSRF checks). Integrate Salesforce Code Analyzer into CI/CD pipelines early to catch security issues before review.

Subscriber data model: Minimise post-install metadata footprint. Custom objects contribute to the subscriber's 800-object limit. Use Custom Metadata Types for configuration (metadata deploys with the package).

Partner Portal: Use Salesforce Partner Community for deal registration, trial provisioning, and customer onboarding. Environment Hub manages multiple subscriber org connections for support.