GitHub Marketplace plan retire with same-name replacement
Replace a bad GitHub Marketplace price by retiring the old plan, creating a new one with the same name, and running an upgrade campaign instead of mutating the live plan in place.
Why this can grow a startup
A weak plan usually lingers because founders are afraid that changing it will break existing subscriptions. GitHub's rules make the boundary clearer than most billing systems do. Once a published plan exists, you cannot edit it. You remove it, create a replacement, and existing customers stay on the old plan until they choose to move. That creates a cleaner commercial story: new buyers get the corrected offer, current buyers keep continuity, and the team can run an explicit migration campaign rather than sneaking a pricing rewrite under everyone.
Source-backed example
GitHub's pricing-plan docs say published plans cannot be changed in place; you must remove the plan, create a new plan, and existing customers remain on the removed plan until they cancel or switch. GitHub also notes you can recreate a removed plan under the same name, such as a new "Pro" plan with updated pricing.
Source-reported evidence
Source: GitHub Docs: Setting pricing plans for your listing
GitHub requires a remove-and-recreate flow for published plans, while existing subscribers remain on the retired plan until they opt out.
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, Pricing, Retention is relevant to pricing migration, developer tools, billing and you can run a bounded test with a medium 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 Pricing, using evidence from GitHub Docs: Setting pricing plans for your listing as context—not as a promised result.
- Record a baseline for: Qualified prospects who complete the intended paid 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
Connect activation, customer value, retention, and referral into one measurable loop.