GitHub Marketplace installable by any user before listing
Turn on installation for any user or organization before marketplace work begins so the listing, insights, and review flow are attached to a product people can actually install.
Why this can grow a startup
A lot of marketplace work starts as copywriting, then dies because the app is still configured like a private experiment. GitHub hides the Marketplace section unless the app can be installed by any user or organization. That means installability is not a later compliance step. It is part of whether the listing can even become a real acquisition surface. Teams that switch this on early can test the full path sooner and avoid polishing a route that is still blocked at the gate.
Source-backed example
GitHub's draft-listing flow says the Marketplace section only appears if the app was registered to allow installation by any user or organization, and the Insights page follows the same rule.
Source-reported evidence
Source: GitHub Docs: Drafting a listing for your app
GitHub only shows the Marketplace section when the app is installable by any user or organization.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
Source discovered: May 29, 2026
When to use it
Use this when Marketplaces, Product, Onboarding is relevant to setup, developer tools, distribution and you can run a bounded test with a low 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.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Marketplaces and Product, using evidence from GitHub Docs: Drafting a listing for your app as context—not as a promised result.
- Record a baseline for: Target users who complete the tactic’s intended next action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.