Back to GrowthDex
Growth idea action plan

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.

epic tacticmedium budget

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.

Company 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 and metric

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.

Source discovered: May 29, 2026

MarketplacesPricingRetentionpricing migrationdeveloper toolsbillingcustomer communication
GrowthDex operator note

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.

Founder checklist

  1. Read GitHub Docs: Setting pricing plans for your listing and identify what is directly supported.
  2. Choose one channel context: Marketplaces, Pricing, Retention.
  3. Define the test around GitHub requires a remove-and-recreate flow for published plans, while existing subscribers remain on the retired plan until they opt out..
  4. Set an owner, evidence window, and stop condition before launch.

Explore the context

Advisory bridge

Apply this with an operator

Connect activation, customer value, retention, and referral into one measurable loop.

Work with Ian