Back to GrowthDex
Growth idea action plan

Salesforce AppExchange non-namespaced install test before trial

Test install and upgrade flows in non-namespaced scratch orgs before promoting the listing, because that org shape behaves more like the customer's environment.

rare tacticfree budget

Why this can grow a startup

A package can look clean in the development path and still stumble in the environment the buyer actually uses. Salesforce draws a sharp line here: namespaced scratch orgs are for building, while non-namespaced scratch orgs are for install, upgrade, QA, and CI because they mimic subscriber orgs. That is valuable growth work, not just engineering hygiene. When the trial or install path behaves like the buyer's world, fewer evaluation sessions turn into support archaeology.

Company example

Salesforce's modern AppExchange development guide recommends namespaced scratch orgs for development but non-namespaced scratch orgs for package installation, upgrade testing, QA, UAT, and CI because customer orgs do not have the package namespace.

Source and metric

Source: Salesforce Developers Blog: Get Started with Modern AppExchange Development

Salesforce explicitly recommends the `--no-namespace` path for install and upgrade testing because customer orgs are non-namespaced.

MarketplacesOnboardingEngineeringinstall testingtrial reliabilitysubscriber orgqa
GrowthDex operator note

When to use it

Use this when Marketplaces, Onboarding, Engineering is relevant to install testing, trial reliability, subscriber org and you can run a bounded test with a free budget.

When not to use it

Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.

Founder checklist

  1. Read Salesforce Developers Blog: Get Started with Modern AppExchange Development and identify what is directly supported.
  2. Choose one channel context: Marketplaces, Onboarding, Engineering.
  3. Define the test around Salesforce explicitly recommends the `--no-namespace` path for install and upgrade testing because customer orgs are non-namespaced..
  4. Set an owner, evidence window, and stop condition before launch.

Explore the context

Product-Led GrowthMarketplacesOnboardingEngineering

Related tactics

Slack Marketplace review rehearsal on a non-dev workspace

Rehearse install, onboarding, use, and uninstall on a workspace that is not your development workspace before submitting, so the review path reflects what a brand-new customer will actually hit.

rareMarketplaces, QA, Onboarding

Figma Community playground file before broad promotion

Ship a playground file before broad promotion so users can try the plugin in a safe example file instead of guessing how to set it up from screenshots alone.

rareOnboarding, Product, Marketplaces

GitHub Marketplace free trial countdown in billing UI

Show the remaining GitHub Marketplace trial days inside the product, because GitHub gives the dates and the buyer should not have to guess when paid access starts.

rareMarketplaces, Onboarding, Retention

Google Chat app audience choice before marketplace push

Choose whether the Chat app is private or public before launch prep hardens, because Google says you cannot change that visibility setting after publish.

rareMarketplaces, Onboarding, Operations

Google Workspace Marketplace admin install by org unit before broad rollout

Route the first Workspace rollout through admin install for a specific organizational unit or access group instead of throwing the app at the whole company on day one.

rareMarketplaces, Sales, Onboarding

HubSpot agent tool config describes the run you can prove

Write the agent tool's type, action description, inputs, and outputs as a contract you can demonstrate on every successful run.

rareMarketplaces, Product-led Growth, Engineering
Advisory bridge

Apply this with an operator

Choose product surfaces that compound distribution without hiding weak activation or retention.

Work with Ian