# 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.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/github-marketplace-installable-by-any-user-before-listing/
- Source: [docs.github.com](https://docs.github.com/en/apps/github-marketplace/listing-an-app-on-github-marketplace/drafting-a-listing-for-your-app)
- GrowthDex source hub: [GitHub Docs: Drafting a listing for your app](/sources/github-docs-drafting-a-listing-for-your-app-docs-github-com/)
- Last checked: 2026-05-29
- Rarity: uncommon
- Budget: low
- Channels: Marketplaces, Product, Onboarding
- Stages: setup, developer tools, distribution, launch readiness


## Why this can grow

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.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where github marketplace installable by any user before listing can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Marketplaces and Product channel.
3. Use the evidence from docs.github.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## 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.

## Adjacent tactics in the same lane

- [GitHub Marketplace individual owner emails in contact info](/growth-ideas/github-marketplace-individual-owner-emails-in-contact-info/) - same source, 1 shared channel, 1 shared stage
- [GitHub Marketplace setup URL finishes the purchase](/growth-ideas/github-marketplace-setup-url-finishes-the-purchase/) - 2 shared channels, 2 shared stages
- [Slack Marketplace onboarding that assumes install before account](/growth-ideas/slack-marketplace-onboarding-that-assumes-install-before-account/) - 3 shared channels
- [Google Workspace combined integrations under one listing](/growth-ideas/google-workspace-combined-integrations-under-one-listing/) - 2 shared channels, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The GitHub Marketplace page should survive the billing handoff](/blog/the-github-marketplace-page-should-survive-the-billing-handoff/) - marketplaces, brand trust, conversion

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.