# GitHub Marketplace draft plan staging before paid launch

> Stage pricing plans in draft before approval so the team can pressure-test packaging and copy without accidentally exposing a half-finished commercial offer.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/github-marketplace-draft-plan-staging-before-paid-launch/
- Source: [docs.github.com](https://docs.github.com/en/apps/github-marketplace/listing-an-app-on-github-marketplace/setting-pricing-plans-for-your-listing)
- GrowthDex source hub: [GitHub Docs: Setting pricing plans for your listing](/sources/github-docs-setting-pricing-plans-for-your-listing-docs-github-com/)
- Last checked: 2026-05-29
- Rarity: rare
- Budget: low
- Channels: Marketplaces, Pricing, Testing
- Stages: pricing, review workflow, developer tools, launch prep


## Why this can grow

Pricing pages often go live before the billing language is ready because teams treat plan setup like a publishing toggle. GitHub gives you a cleaner lane. Pricing plans can be saved as drafts, and even a published plan behaves like a draft until the listing itself is approved. That lets the team inspect the packaging, bullets, and audience fit before the plan becomes buyable. It is a small workflow detail, but it keeps revenue surfaces from being rehearsed in public.

## 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 draft plan staging before paid launch can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Marketplaces and Pricing 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 pricing-plan docs say plans can be saved in draft or published state, and if the listing has not yet been approved, a published plan still behaves like a draft plan until the listing is shown on GitHub Marketplace.

## Adjacent tactics in the same lane

- [GitHub Marketplace plan retire with same-name replacement](/growth-ideas/github-marketplace-plan-retire-with-same-name-replacement/) - same source, 2 shared channels, 1 shared stage
- [Google Workspace draft tester lane before listing edits](/growth-ideas/google-workspace-draft-tester-lane-before-listing-edits/) - 2 shared channels, 1 shared stage
- [Atlassian Marketplace Timebomb license preflight](/growth-ideas/atlassian-marketplace-timebomb-license-preflight/) - 2 shared channels, 1 shared stage
- [Slice fixed-fee ordering against aggregator tax](/growth-ideas/slice-fixed-fee-ordering-against-aggregator-tax/) - 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.